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
PainesvilleOhio44077USAground conditionApril 2000BAE Systems/ADRvector digital data\\JBOYD1\C$\LN\ROWPainesville, OhioLake County GISSeptember 1, 20022000AROWROWBAE Systems/ADRvector digital dataPainesville, OhioLake County GIShttp://www.lakegis.orgSeptember 1, 20022000ASDEDBO.CDSTRL_RIGHTOFWAYCompleteContinuallyNoneNoneLake County GIS Staff.To provide a graphic entity to which attribute data could be assigned for local government business practices.en This entity refers to the legal right to use a piece of land for passage. More specifically, it relates to the legally defined and delineated geographic area adjacent to a highway, railroad, or utility transmission line. Creation of a ROW often involves the transfer of a portion of the earth’s surface from one owner to another as part of a recorded plat or via separate instrument. Sea LevelLake County, OhioApril 2000CadastralUnclassifiedMicrosoft Windows XP Version 5.1 (Build 2600) Service Pack 3; ESRI ArcCatalog 9.3.0.1770-81.490165-80.99976441.85785441.5649372244820.0912612377226.388784695098.113128799942.681654Shapefile20090908115819002004032315030200FALSE2009090811581900{38449B4A-7196-44FF-A7C2-40ED91903EBC}CopyFeatures "Database Connections\SDEDBO.sde\SDEDBO.CADASTRAL\SDEDBO.CDSTRL_RIGHTOFWAY" "Database Connections\SDE-LakeGIS.sde\LakeGIS.SDE.CADASTRAL\LakeGIS.SDE.SDEDBO_CDSTRL_RIGHTOFWAY" # 0 0 0Clip LakeGIS.SDE.CDSTRL_RIGHTOFWAY Study C:\Lost_Nation\ROW.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
PainesvilleOhio44077USANoneNoneenFGDC Content Standards for Digital Geospatial Metadatalocal timeUnclassifiedwww.lakegis.orgESRI Metadata ProfileFGDC-STD-001-1998http://www.esri.com/metadata/esriprof80.htmlESRI Metadata Profile20090908Digitizing and photo interpretation of apparent lines of occupation.Orthophotos20030707Clark SelbyBAE Systems/ADR421-967-9577mailing and physical address
280 Kappa Dr.
PittsburghPennsylvania15238USAAutoCAD2000-2002BAE Systems/ADRBAE Systems/ADRvector digital dataPainesville, OhioLake County GISwww.lakegis.orgSeptember 1, 20022000Aground conditionApril 20002400CD-ROMDigitizeAerocon provided ortho imagery.Metadata imported.M:\CountywideShapefiles\planimetric_template.xml20030710Metadata imported.M:\production\Metadata\cadastral_metadata.xml20040323Metadata imported.M:\CountywideShapefiles\Cadastral\row.shp.xml20040323Dataset moved.C:\Lost_Nation\ROW2009090812075500Quality Control performed by GIS Staff. Visual inspection of vectors overlayed on raster orthophotos and comparison of 24"x30" prints to current county taxmaps.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) 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 ProgramA 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. Range of accuracy varies from excellent - orthophoto's- to questionable - old county taxmaps drawn at various scales. 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. Range of accuracy varies from excellent - orthophoto's- to questionable - old county taxmaps drawn at various scales. The horizontal datum is NAD 83 and the coordinated are Ohio State Plane North Zone. Control was existing Lake County monuments.Richard J. KotapishLake County GISDirectormailing and physical address
105 Main Street
PainesvilleOhio44077U.S.A.440-350-5943440-350-5942dkotapish@lakecountyohio.org8:00 am to 4:30 pm Monday through FridayNoneARCG8.3shapefileno compression applied0.0000.000Not AvailableCD-ROMIncompatible with MacIntosh OS$50/cd1 dayCall 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, 2002Right-of-WayVectorG-polygon0SimplePolygonFALSE0FALSEFALSE This entity refers to the legal right to use a piece of land for passage. More specifically, it relates to the legally defined and delineated geographic area adjacent to a highway, railroad, or utility transmission line. Creation of a ROW often involves the transfer of a portion of the earth’s surface from one owner to another as part of a recorded plat or via separate instrument.515.000000FALSELake County GISROWFeature Class0This entity refers to the legal right to use a piece of land for passage. More specifically, it relates to the legally defined and delineated geographic area adjacent to a highway, railroad, or utility transmission line. Creation of a ROW often involves the transfer of a portion of the earth’s surface from one owner to another as part of a recorded plat or via separate instrument.FIDFIDOID400Internal feature number.ESRISequential unique whole numbers that are automatically generated.PERIMETERPERIMETERNumber19Perimeter of feature in internal units. ESRI8SDEDBO_RIGSDEDBO_RIGNumber198ROW_ROW_Number10Internal feature number. ESRIROW_IDROW_IDNumber10User-defined feature number. ESRIROW_TYPEROW_TYPEString10Feature type.ESRISHAPEShapeGeometry000Feature geometry.ESRICoordinates defining the features.SHAPE_areaSHAPE_areaFloat19Area of feature in internal units squared.ESRIPositive real numbers that are automatically generated.11SHAPE_lenSHAPE_lenFloat1911North American Vertical Datum of 19881.000000feetExplicit elevation coordinate included with horizontal coordinatesMean sea levelFrom 2' to 50'feetExplicit depth coordinate included with horizontal coordinatesGCS_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.257222Microsoft Windows XP Version 5.1 (Build 2600) Service Pack 3; ESRI ArcCatalog 9.3.0.1770ROW2244820.0912612377226.388784799942.681654695098.1131281-81.490165-80.99976441.85785441.5649371ISO 19115 Geographic Information - MetadataDIS_ESRI1.0datasetShapefile002file://\\JBOYD1\C$\LN\ROWLocal Area Network0.000NAD_1983_StatePlane_Ohio_North_FIPS_3401_Feet0