Richard J. KotapishLake County GISDirector440-350-5943440-350-5942dkotapish@lakecountyohio.org8:00 am to 4:30 pm Monday through Fridaymailing and physical address105 Main StreetPainesvilleOhio44077USAground conditionApril 2000Aerocon Photogrammetric Services Inc.vector digital data\\JBOYD1\C$\LN\RailPainesville, OhioLake County GISSeptember 1, 20022000ARailRailAerocon Photogrammetric Services Inc.vector digital dataPainesville, OhioLake County GIShttp://www.lakegis.orgSeptember 1, 20022000ARailroadUnknownNoneNoneLake County GIS Staff.To provide a graphic entity to which attribute data could be assigned for local government business practices.enThis entity includes all components of transportation utilizing trains. It includes both the network of railroad tracks, and the sidings, yards, and other support appurtenances required for the operations of the trains.Sea LevelLake County, OhioApril 2000RailroadUnclassifiedMicrosoft Windows XP Version 5.1 (Build 2600) Service Pack 3; ESRI ArcCatalog 9.3.0.1770-81.489053-81.00160441.80312941.5976292244986.3283482377067.767959707009.451636780000.527288Shapefile20090908114728002006051814081400FALSE2009090811472800{994F44E8-E289-4456-A271-74D3FC75B553}CopyFeatures "Database Connections\SDEDBO.sde\SDEDBO.TRANS_RAILROAD" "Database Connections\SDE-LakeGIS.sde\LakeGIS.SDE.SDEDBO_TRANS_RAILROAD" # 0 0 0Clip LakeGIS.SDE.TRANS_RAILROAD Study C:\Lost_Nation\Rail.shp #20090908Richard J. KotapishLake County GISDirector440-350-5943440-350-5942dkotapish@lakecountyohio.org8:00 am to 4:30 pm Monday through Fridaymailing and physical address105 Main StreetPainesvilleOhio44077USANoneNoneFGDC Content Standards for Digital Geospatial MetadataFGDC-STD-001-1998local timeUnclassifiedwww.lakegis.orgESRI Metadata Profileenhttp://www.esri.com/metadata/esriprof80.htmlESRI Metadata Profile20090908Stereocompilation to National Map Accuracy Standards.Orthophotos20030707Mark HammondAerocon Photogrammetric Services, Inc.Senior Mapping Technician440-946-6277440-946-2646mhammond@aerocon.commailing and physical address4515 Glenbrook RoadWilloughbyOhio44094-8215USAMicroStation and AutoCAD2000-2002AeroconAerocon Photogrammetric Services Inc.vector digital dataPainesville, OhioLake County GISwww.lakegis.orgSeptember 1, 20022000Aground conditionApril 20001200CD-ROMStereoCompAerocon provided planimetric and ortho imagery.Metadata imported.M:\CountywideShapefiles\planimetric_template.xml20030820Dataset moved.M:\CountywideShapefiles\Planimetric\Railroad20060503Metadata imported.M:\CountywideShapefiles\Transportation\Railroad.shp.xml20060518Dataset moved.C:\Lost_Nation\Rail2009090812075500Quality Control performed by GIS Staff. Visual inspection of vectors overlayed on raster orthophotos.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).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. 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.Richard J. KotapishLake County GISDirectormailing and physical address105 Main StreetPainesvilleOhio44007U.S.A.440-350-5943440-350-5942dkotapish@lakecountyohio.org8:00 am to 4:30 pm Monday through FridayARCG8.3shapefileno compression applied0.0000.000Not AvailableCD-ROMIncompatible with MacIntosh OS$50/cd1 dayNoneCall 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, 2002RailroadVectorString0SimplePolylineFALSE0FALSEFALSELake County GISRailFeature Class0This entity includes all components of transportation utilizing trains. It includes both the network of railroad tracks, and the sidings, yards, and other support appurtenances required for the operations of the trains.SHAPEFIDOID400Feature geometry.ESRICoordinates defining the features.ShapeFNODE_Double10100Feature geometry.ESRICoordinates defining the features.FNODE_LPOLY_Number10LPOLY_RPOLY_Number10RPOLY_LENGTHNumber10LENGTHRAILROAD_Number198RAILROAD_TNODE_Number10TNODE_ShapeNumber10Feature geometry.ESRICoordinates defining the features.RAILROAD_IRAILROAD_INumber10RR_OPERATORR_OPERATOString40SHAPE_lenSHAPE_lenFloat1911North American Datum of 1983Geodetic Reference System 806378137.000000298.257222GCS_North_American_1983NAD_1983_StatePlane_Ohio_North_FIPS_3401_Feetcoordinate pairsurvey feet0.0000000.000000Lambert Conformal Conic40.43333341.700000-82.50000039.6666671968500.0000000.000000North American Vertical Datum of 19881.000000feetExplicit elevation coordinate included with horizontal coordinatesMean sea level2'feetExplicit depth coordinate included with horizontal coordinatesMicrosoft Windows XP Version 5.1 (Build 2600) Service Pack 3; ESRI ArcCatalog 9.3.0.1770Rail2244986.3283482377067.767959780000.527288707009.4516361-81.489053-81.00160441.80312941.5976291ISO 19115 Geographic Information - MetadataDIS_ESRI1.0dataset002file://\\JBOYD1\C$\LN\RailLocal Area Network0.000ShapefileNAD_1983_StatePlane_Ohio_North_FIPS_3401_Feet0