Richard J. KotapishLake County GISDirector440-350-5943440-350-5942dkotapish@lakecountyohio.org8:00 am to 4:30 pm Monday through Fridaymailing and physical address

105 Main Street

PainesvilleOhio44004USAground conditionApril 2000Aerocon Photogrammetric Services Inc.vector digital data\\JBOYD1\C$\LN\Pavement_edgePainesville, OhioLake County GISSeptember 1, 2002Pavement_edge2000AAerocon Photogrammetric Services Inc.vector digital dataPainesville, OhioLake County GISwww.lakegis.orgSeptember 1, 20022000ACompleteIrregularNoneNoneLake County GIS Staff.Microsoft Windows XP Version 5.1 (Build 2600) Service Pack 3; ESRI ArcCatalog 9.3.0.1770enPavement edges are the visible boundaries of paved sections of road as determined from digital orthophotos.-81.490270-80.99904841.85793941.5644202244793.4997792377420.999944694913.062645799973.249834Pavement EdgeLake County, OhioSea LevelApril 2000ShapefileUnclassified20090908114703002006051814094400FALSE2009090811470300{829EBE0B-C713-4F99-A225-65F69E251E44}FeatureClassToFeatureClass "Database Connections\SDEDBO.sde\SDEDBO.TRANS_PAVEMENT_EDGE" M:\production\CPike\CodyEditing.gdb TRANS_PAVEMENT_EDGE # "FNODE_ FNODE_ true true true 4 Long 0 10 ,First,#,Database Connections\SDEDBO.sde\SDEDBO.TRANS_PAVEMENT_EDGE,FNODE_,-1,-1;TNODE_ TNODE_ true true true 4 Long 0 10 ,First,#,Database Connections\SDEDBO.sde\SDEDBO.TRANS_PAVEMENT_EDGE,TNODE_,-1,-1;LPOLY_ LPOLY_ true true true 4 Long 0 10 ,First,#,Database Connections\SDEDBO.sde\SDEDBO.TRANS_PAVEMENT_EDGE,LPOLY_,-1,-1;RPOLY_ RPOLY_ true true true 4 Long 0 10 ,First,#,Database Connections\SDEDBO.sde\SDEDBO.TRANS_PAVEMENT_EDGE,RPOLY_,-1,-1;LENGTH LENGTH true true true 8 Double 8 38 ,First,#,Database Connections\SDEDBO.sde\SDEDBO.TRANS_PAVEMENT_EDGE,LENGTH,-1,-1;PAVEMENT_EDGE_ PAVEMENT_EDGE_ true true true 4 Long 0 10 ,First,#,Database Connections\SDEDBO.sde\SDEDBO.TRANS_PAVEMENT_EDGE,PAVEMENT_EDGE_,-1,-1;PAVEMENT_EDGE_ID PAVEMENT_EDGE_ID true true true 4 Long 0 10 ,First,#,Database Connections\SDEDBO.sde\SDEDBO.TRANS_PAVEMENT_EDGE,PAVEMENT_EDGE_ID,-1,-1;LEN LEN false false true 0 Double 0 0 ,First,#,Database Connections\SDEDBO.sde\SDEDBO.TRANS_PAVEMENT_EDGE,SHAPE.LEN,-1,-1" # M:\production\CPike\CodyEditing.gdb\TRANS_PAVEMENT_EDGEFeatureClassToFeatureClass M:\production\CPike\CodyEditing.gdb\TRANS_PAVEMENT_EDGE M:\CountywideShapefiles\Transportation "Pavement_Edge_updated 071607.shp" # "FNODE_ FNODE_ true true true 4 Long 0 0 ,First,#,M:\production\CPike\CodyEditing.gdb\TRANS_PAVEMENT_EDGE,FNODE_,-1,-1;TNODE_ TNODE_ true true true 4 Long 0 0 ,First,#,M:\production\CPike\CodyEditing.gdb\TRANS_PAVEMENT_EDGE,TNODE_,-1,-1;LPOLY_ LPOLY_ true true true 4 Long 0 0 ,First,#,M:\production\CPike\CodyEditing.gdb\TRANS_PAVEMENT_EDGE,LPOLY_,-1,-1;RPOLY_ RPOLY_ true true true 4 Long 0 0 ,First,#,M:\production\CPike\CodyEditing.gdb\TRANS_PAVEMENT_EDGE,RPOLY_,-1,-1;LENGTH LENGTH true true true 8 Double 0 0 ,First,#,M:\production\CPike\CodyEditing.gdb\TRANS_PAVEMENT_EDGE,LENGTH,-1,-1;PAVEMENT_E PAVEMENT_EDGE_ true true true 4 Long 0 0 ,First,#,M:\production\CPike\CodyEditing.gdb\TRANS_PAVEMENT_EDGE,PAVEMENT_EDGE_,-1,-1;PAVEMENT_1 PAVEMENT_EDGE_ID true true true 4 Long 0 0 ,First,#,M:\production\CPike\CodyEditing.gdb\TRANS_PAVEMENT_EDGE,PAVEMENT_EDGE_ID,-1,-1;LEN LEN false true true 8 Double 0 0 ,First,#,M:\production\CPike\CodyEditing.gdb\TRANS_PAVEMENT_EDGE,LEN,-1,-1;Shape_Leng Shape_Length false true true 8 Double 0 0 ,First,#,M:\production\CPike\CodyEditing.gdb\TRANS_PAVEMENT_EDGE,Shape_Length,-1,-1" # "M:\CountywideShapefiles\Transportation\Pavement_Edge_updated 071607.shp"FeatureClassToFeatureClass "M:\CountywideShapefiles\Transportation\Pavement_Edge_updated 071607.shp" "Database Connections\LAKEGIS_SDE.sde" TRANS_PAVEMENT_EDGE_NEW # "FNODE_ 'FNODE_' true true false 9 Long 0 9 ,First,#,M:\CountywideShapefiles\Transportation\Pavement_Edge_updated 071607.shp,FNODE_,-1,-1;TNODE_ 'TNODE_' true true false 9 Long 0 9 ,First,#,M:\CountywideShapefiles\Transportation\Pavement_Edge_updated 071607.shp,TNODE_,-1,-1;LPOLY_ 'LPOLY_' true true false 9 Long 0 9 ,First,#,M:\CountywideShapefiles\Transportation\Pavement_Edge_updated 071607.shp,LPOLY_,-1,-1;RPOLY_ 'RPOLY_' true true false 9 Long 0 9 ,First,#,M:\CountywideShapefiles\Transportation\Pavement_Edge_updated 071607.shp,RPOLY_,-1,-1;LENGTH 'LENGTH' true true false 19 Double 0 0 ,First,#,M:\CountywideShapefiles\Transportation\Pavement_Edge_updated 071607.shp,LENGTH,-1,-1;PAVEMENT_E 'PAVEMENT_E' true true false 9 Long 0 9 ,First,#,M:\CountywideShapefiles\Transportation\Pavement_Edge_updated 071607.shp,PAVEMENT_E,-1,-1;PAVEMENT_1 'PAVEMENT_1' true true false 9 Long 0 9 ,First,#,M:\CountywideShapefiles\Transportation\Pavement_Edge_updated 071607.shp,PAVEMENT_1,-1,-1;LEN 'LEN' true true false 19 Double 0 0 ,First,#,M:\CountywideShapefiles\Transportation\Pavement_Edge_updated 071607.shp,LEN,-1,-1;Shape_Leng 'Shape_Leng' true true false 19 Double 0 0 ,First,#,M:\CountywideShapefiles\Transportation\Pavement_Edge_updated 071607.shp,Shape_Leng,-1,-1" # "Database Connections\LAKEGIS_SDE.sde\LakeGIS.SDE.TRANS_PAVEMENT_EDGE_NEW"Clip LakeGIS.SDE.TRANS_PAVEMENT_EDGE_NEW Study C:\Lost_Nation\Pavement_edge.shp #20090908Richard J. KotapishLake County GISDirector440-350-5943440-350-5942dkotapish@lakecountyohio.org8:00 am to 4:30 pm Monday through Fridaymailing and physical address

105 Main Street

PainesvilleOhio44004USANoneNoneenFGDC Content Standards for Digital Geospatial MetadataFGDC-STD-001-1998local timewww.lakegis.orgESRI Metadata ProfileUnclassifiedhttp://www.esri.com/metadata/esriprof80.htmlESRI Metadata Profile20090908Stereocompilation to National Map Accuracy Standards.Orthophotos2003070712185300Mark HammondsAerocon Photogrammetric Services, Inc.Senior Mapping Technicianmailing and physical address

4515 Glenbrook Rd.

WilloughbyOhio44094-8215USA440-946-6277440-946-2646mhammonds@Aerocon.comMicrostation and AutoCAD2000-2002AeroconMetadata imported.M:\CountywideShapefiles\metadata_template.xml2003070809291100Aerocon Photogrammetric Services, Inc.September 1, 2002vector digital data2000APainesville, OhioLake County GISwww.lakegis.org1200CD-ROMApril 2000ground conditionStereoCompAerocon provided planimetric and ortho imagery.Dataset moved.M:\CountywideShapefiles\Planimetric\Pavement_edge2006050310541300Metadata imported.M:\CountywideShapefiles\Transportation\Pavement_edge.shp.xml2006051814094400Dataset moved.C:\Lost_Nation\Pavement_edge2009090812075500Quality control completed by GIS Staff.1) 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 Program.Digitizing 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). 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. 1%Richard J. KotapishLake County GISDirectormailing and physical address

105 Main Street

PainesvilleOhio44004U.S.A.440-350-5943440-350-5942dkotapish@lakecountyohio.org8:00 am to 4:30 pm Monday through Friday0.0000.000ARCG8.3shapefileno compression appliedNot AvailableCD-ROMIncompatible with MacIntosh OS$50/cd1 dayPavement EdgeNoneCall 440-350-5943 for cost quote. Upon receipt of fees, data will be mailed.Experience working with shapefiles in a GIS software program.September 1, 2002VectorString0SimplePolylineFALSE0FALSEFALSEPavement edges are the visible boundaries of paved sections of road as determined from digital orthophotos.Lake County GISPavement_edgeFeature Class0Pavement edges are the visible boundaries of paved sections of road as determined from digital orthophotos.LENGTHFIDNumber19Internal feature number.ESRISequential unique whole numbers that are automatically generated.8PAVEMENT_EPAVEMENT_ENumber10Internal feature number.ESRISequential unique whole numbers that are automatically generated.PAVEMENT_1PAVEMENT_1Number10Internal feature number.ESRISequential unique whole numbers that are automatically generated.Shape_LengShape_LengNumber19Internal feature number.ESRISequential unique whole numbers that are automatically generated.8ShapeTNODE_Double10100Feature geometry.ESRICoordinates defining the features.TNODE_LPOLY_Number10LPOLY_ShapeNumber10Feature geometry.ESRICoordinates defining the features.SHAPERPOLY_Double10Feature geometry.ESRICoordinates defining the features.100RPOLY_FNODE_Number10LakeGIS_SDLakeGIS_SDNumber198FNODE_LENGTHNumber10Shape_lenShape_lenFloat1911Pavement edges are the visible boundaries of paved sections of road as determined from digital orthophotos.Microsoft Windows XP Version 5.1 (Build 2600) Service Pack 3; ESRI ArcCatalog 9.3.0.1770Pavement_edge2244793.4997792377420.999944799973.249834694913.0626451-81.49027-80.99904841.85793941.564421ISO 19115 Geographic Information - MetadataDIS_ESRI1.0dataset002file://\\JBOYD1\C$\LN\Pavement_edgeLocal 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 level2'feetExplicit depth coordinate included with horizontal coordinatesNAD_1983_StatePlane_Ohio_North_FIPS_3401_Feet0