2007092509053800FALSE20090908115143002009090811514300{B26E30B9-EBFF-421D-B886-5E8424CC9296}CopyFeatures "Database Connections\SDEDBO.sde\SDEDBO.BLDGS_BUILDINGS" "Database Connections\SDE-LakeGIS.sde\LakeGIS.SDE.SDEDBO_BLDGS_BUILDINGS" # 0 0 0Clip LakeGIS.SDE.BLDGS_BUILDINGS Study C:\Lost_Nation\Structures.shp #Microsoft Windows XP Version 5.1 (Build 2600) Service Pack 3; ESRI ArcCatalog 9.3.0.1770enA building is a manmade structure which is habitable by human beings, or which houses human activities in a manner which limits other modes of human utilization. A building may house a variety of activities at one time, or sequentially over its life. It may also sit vacant. This entity will be implemented as a polygon feature representing the building roof print or footprint, depending on source.Aerocon Photogrammetric Services Inc.Structuresvector digital data\\JBOYD1\C$\LN\StructuresPainesville, OhioLake County GISSeptember 1, 20022000AUnknownground conditionApril 2000CompleteIrregular-81.490213-80.99970841.85830741.5648772244807.1201562377238.866839695076.462185800107.410379BuildingLake County, OhioApril 2000Sea LevelNoneNoneShapefileRichard J. KotapishLake County GISDirector440-350-5943440-350-5942dkotapish@lakecountyohio.org8:00 am - 4:30 pm Monday through Fridaymailing and physical address

105 Main St.

PainesvilleOhio44077USAAerocon Photogrammetric Services Inc.vector digital datawww.lakegis.orgPainesville, OhioLake County GISSeptember 1, 20022000ALake County GIS Staff.UnclassifiedenFGDC Content Standards for Digital Geospatial MetadataFGDC-STD-001-1998local timeRichard J. KotapishLake County GISmailing and physical addressPainesvilleOhio44077

105 Main St.

USA440-350-5943Director440-350-5942dkotapish@lakecountyohio.org8:00 am - 4:30 pm Monday through Friday20090908NoneNonehttp://www.lakegis.orgESRI Metadata ProfileUnclassifiedhttp://www.esri.com/metadata/esriprof80.htmlESRI Metadata ProfileVectorSimplePolygonFALSE0FALSEFALSEA building is a manmade structure which is habitable by human beings, or which houses human activities in a manner which limits other modes of human utilization. A building may house a variety of activities at one time, or sequentially over its life. It may also sit vacant.G-polygon0SimpleLabelFALSE87627FALSEFALSELabel point87627SimplePolygonTRUE87627FALSEFALSEGT-polygon composed of chains87627SimpleTicFALSE4FALSEFALSEPoint4ShapePERIMETERDouble19188Feature geometry.ESRICoordinates defining the features.SHAPEFIDOID400Feature geometry.ESRICoordinates defining the features.PERIMETER195NumberInternal feature number.ESRISequential unique whole numbers that are automatically generated.BUILDING_8SDEDBO_BUISDEDBO_BUINumber198BUILDING_105NumberUser-defined feature number.ESRISTATUSStructuresFeature Class0A building is a manmade structure which is habitable by human beings, or which houses human activities in a manner which limits other modes of human utilization. A building may house a variety of activities at one time, or sequentially over its life. It may also sit vacant.Lake County GISBUILDING_IBUILDING_INumber10TAX_PARCELTAX_PARCELString19STATUSPINString20PINXString30XYNumber198YShapeNumber19Feature geometry.ESRICoordinates defining the features.8SHAPE_areaSHAPE_areaFloat19Area of feature in internal units squared.ESRIPositive real numbers that are automatically generated.11SHAPE_lenSHAPE_lenFloat1911A building is a manmade structure which is habitable by human beings, or which houses human activities in a manner which limits other modes of human utilization. A building may house a variety of activities at one time, or sequentially over its life. It may also sit vacant.Attribute table shows area and perimeter of building polygon.0.0000.000ARCG8.3shapefileno compression appliedNot AvailableCD-ROMIncompatible with MacIntosh OS$50/cd1 dayRichard J. KotapishLake County GISDirector440-350-5943440-350-5942dkotapish@lakecountyohio.org8:00 am - 4:30 pm Monday through Fridaymailing and physical address

105 Main St.

PainesvilleOhio44077USASeptember 1, 2002BuildingNoneCall 440-350-5943 for cost quote. Upon receipt of fees, data will be mailed.Experience working with shapefiles in a GIS software program.Microsoft Windows XP Version 5.1 (Build 2600) Service Pack 3; ESRI ArcCatalog 9.3.0.1770Structures2244807.1201562377238.866839800107.410379695076.4621851-81.490213-80.99970841.85830741.5648771ISO 19115 Geographic Information - MetadataDIS_ESRI1.0dataset002file://\\JBOYD1\C$\LN\StructuresLocal Area Network0.000ShapefileGCS_North_American_1983NAD_1983_StatePlane_Ohio_North_FIPS_3401_Feetcoordinate pairsurvey feet0.0000000.000000Lambert Conformal Conic40.43333341.700000-82.50000039.6666671968500.0000000.000000North American Datum of 1983Geodetic Reference System 806378137.000000298.257222North American Vertical Datum of 19881.000000feetExplicit elevation coordinate included with horizontal coordinatesMean sea level2feetExplicit depth coordinate included with horizontal coordinatesNAD_1983_StatePlane_Ohio_North_FIPS_3401_Feet020090908Quality control performed by GIS StaffAerocon Photogrammetric Survey Inc.vector digital datawww.lakegis.orgSeptember 1, 20022000APainesville, OhioLake County GISApril, 2000ground condition1200CD-ROMStereoComAerocon provided planimetric and ortho imagery.Mark HammondAerocon Photogrammetric Survey Inc.Senior Mapping Technicianmailing and physical address

4515 Glenbrook Rd.

WilloughbyOhio44077USA440-946-6277440-946-2646mhammond@Aerocon.comStereocompilation to National Map Accuracy Standards.Microstation and AutoCAD2000-2002OrthophotosAeroconDataset copied.\\Gissql\tempshare\CountywideShapefiles\Planimetric\Planimetric\Building2003102813381000Dataset moved.M:\CountywideShapefiles\Planimetric\Building2006050310463000Metadata imported.M:\CountywideShapefiles\Structures\Building.shp.xml2006051011021000Dataset copied.Server=gissql; Service=5151; User=sdedbo; Version=SDE.DEFAULT2007092509053800Dataset moved.C:\Lost_Nation\Structures20090908120755001) All digitized features must be both visual and coordinate edgematched with features in adjacent sheet files and at model breaks or other artificial boundaries within a sheet. No edgematch tolerance will be allowed. Attributes for adjoining features must also be identical. 2) Common Boundaries - All graphic features that share a common boundary, regardless of digital map layer, must have the exact same digital representation of that feature in all common layers. 3) Point Duplication - No duplication of points that occur within a data string is permitted. 4) Connectivity - Where graphic elements visually meet, they must also digitally meet. All confluences of line, area, and polygon data must be exact mathematically; that is, no “overshoots,” “undershoots,” or “offsets” or “pseudo nodes” are permitted. Lines that connect polygons must intersect those polygons precisely; that is, every end point must be an intersection point of the respective polygon. 5) Line Quality - A high quality cartographic appearance shall be achieved. Transitions from straight line to curvilinear line segments shall be smooth, and without angular inflections at the point of intersection. The digital representation must not contain extraneous data at a non-visible level. There shall be no jags or hooks or zero length segments. Curvilinear graphic features should be smooth with a minimum number of points. When appropriate, line-smoothing programs should be used to minimize the angular inflection in curvilinear lines. Any lines that are straight, or should be straight, should be digitized using only two points that represent the beginning and ending points of the line. 6) Segmentation - The digital representation of linear elements must reflect the visual network structure of the data type. An element should not be broken or segmented unless that segmentation reflects a visual or attribute code characteristic, or unless the break is forced by database limitations. 7) Area and Polygon Closure and Centroids - For area features being digitized, the last coordinate pair must be exactly (mathematically) equal to the first coordinate pair. 8) Point Criteria - all point features shall be digitized as a single x , y coordinate pair at the visual center of that graphic feature.99%Quality Control ProgramDigitizing Production Requirements 1) Edgematching-All digitized features must be both visual and coordinate edgematched with features in adjacent sheet files and at model breaks or other artificial boundaries within a sheet. No edgematch tolerance will be allowed. Attributes for adjoining features must also be identical. 2) Common Boundaries-All graphic features that share a common boundary, regardless of digital map layer, must have the exact same digital representation of that feature in all common layers. 3) Point Duplication-No duplication of points that occur within a data string is permitted. 4) Connectivity-Where graphic elements visually meet, they must also digitally meet. All confluences of line, area, and polygon data must be exact mathematically; that is, no "overshoots," "undershoots," or "offsets" or "pseudo nodes" are permitted. Lines that connect polygons must intersect those polygons precisely; that is, every end point must be an intersection point of the respective polygon. 5) Line Quality-A high quality cartographic appearance shall be achieved. Transitions from straight line to curvilinear line segments shall be smooth, and without angular inflections at the point of intersection. The digital representation must not contain extraneous data at a non-visible level. There shall be no jags or hooks or zero length segments. Curvilinear graphic features should be smooth with a minimum number of points. When appropriate, line-smoothing programs should be used to minimize the angular inflection in curvilinear lines. Any lines that are straight, or should be straight, should be digitized using only two points that represent the beginning and ending points of the line. 6) Segmentation-The digital representation of linear elements must reflect the visual network structure of the data type. An element should not be broken or segmented unless that segmentation reflects a visual or attribute code characteristic, or unless the break is forced by database limitations. 7) Area and Polygon Closure and Centroids-For area features being digitized, the last coordinate pair must be exactly (mathematically) equal to the first coordinate pair. 8) Point Criteria-All point features shall be digitized as a single x , y coordinate pair at the visual center of that graphic feature. The structure of the map data will not inhibit the execution of GIS functions across boundaries or artificial discontinuities (sheet edges, model edges, or other delimitations). 1%A total of 261 ground control points were used in the final analytical triangulation solution. Exising Lake County monuments were used for 83 of the points and new locations were positioned for 178 points by GPS methods. The horizontal datum is NAD 83 and the coordinated are Ohio State Plane North Zone. Control was existing Lake County monuments. A total of 261 ground control points were used in the final analytical triangulation solution. Exising Lake County monuments were used for 83 of the points and new locations were positioned for 178 points by GPS methods. The horizontal datum is NAD 83 and the coordinated are Ohio State Plane North Zone. Control was existing Lake County monuments.