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
PainesvilleOhio44077USApublication dateApril 2000BAE Systems/ADR, Lake County GISvector digital datawithheldPainesville, OhioLake County GISMarch 12, 20032000ASDEDBO_CDSTRL_TWP_RANGESDEDBO_CDSTRL_TWP_RANGE10:12:18 amn/aBAE Systems/ADR, Lake County GISvector digital dataPainesville, OhioLake County GIShttp://www.lakegis.orgMarch 12, 20032000ASDEDBO.CDSTRL_TWP_RANGE10:12:18 amn/aUnknownNoneNoneLake County GIS Staff.To provide a graphic entity to which attribute data could be assigned for local government business practices.enThe Connecticut Western Reserve opened in 1786. It was located in the northeast corner of the state (Huron Co. and all counties to its north and east) and was surveyed into 5 mile square townships that were further subdivided, usually into 25 one mile square sections. The Land Ordinance of 1785 was Congress's attempt to coordinate the surveying and sale of land north of the Ohio River with the aim of raising sorely needed cash. The land was to be surveyed into 6 mile square townships, and those townships were to be divided into 1 mile square 'lots'. Half the land was to be sold as townships and half as lots. This scheme featured a different numbering scheme than that defined by the Land Ordinance of 1796. The 36 lots (sections) in a township counted northward from the southeast corner of the township, east to west. The Land Ordinance of 1796 was passed. It defined the surveying system to be used by all future public land surveys. In this system the townships are 6 miles square, composed of 36 one mile square sections, each of which may be subdivided into quarters or smaller. The numbering of the sections is serpentine, starting in the northeast corner of the township. Townships are identified as being north or south of a baseline and in a range east or west of a longitudinal meridian line.Sea LevelLake County, OhioApril 2000Township/Range BoundaryUnclassifiedESRI ArcCatalog 9.0.0.535-81.489708-80.99974641.85861941.5649342244945.2692762377226.388887695097.123945800222.691787Shapefile20230323142449002006051914563100FALSE2023032314244900{4CC6B5EF-9AD5-4B5C-A1B4-BEABAC222ECC}Twp_Range002ProjectedGCS_North_American_1983Linear Unit: Foot_US (0.304801)NAD_1983_StatePlane_Ohio_North_FIPS_3401_Feet<ProjectedCoordinateSystem xsi:type='typens:ProjectedCoordinateSystem' xmlns:xsi='http://www.w3.org/2001/XMLSchema-instance' xmlns:xs='http://www.w3.org/2001/XMLSchema' xmlns:typens='http://www.esri.com/schemas/ArcGIS/10.8'><WKT>PROJCS["NAD_1983_StatePlane_Ohio_North_FIPS_3401_Feet",GEOGCS["GCS_North_American_1983",DATUM["D_North_American_1983",SPHEROID["GRS_1980",6378137.0,298.257222101]],PRIMEM["Greenwich",0.0],UNIT["Degree",0.0174532925199433]],PROJECTION["Lambert_Conformal_Conic"],PARAMETER["False_Easting",1968500.0],PARAMETER["False_Northing",0.0],PARAMETER["Central_Meridian",-82.5],PARAMETER["Standard_Parallel_1",40.43333333333333],PARAMETER["Standard_Parallel_2",41.7],PARAMETER["Latitude_Of_Origin",39.66666666666666],UNIT["Foot_US",0.3048006096012192],AUTHORITY["EPSG",3734]]</WKT><XOrigin>-118963900</XOrigin><YOrigin>-96373800</YOrigin><XYScale>3048.0060960121928</XYScale><ZOrigin>0</ZOrigin><ZScale>1</ZScale><MOrigin>0</MOrigin><MScale>1</MScale><XYTolerance>0.0032808333333333331</XYTolerance><ZTolerance>0.001</ZTolerance><MTolerance>0.001</MTolerance><HighPrecision>true</HighPrecision><WKID>102722</WKID><LatestWKID>3734</LatestWKID></ProjectedCoordinateSystem>20060519Richard 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 timeUnclassifiedwithheldESRI Metadata ProfileFGDC-STD-001-199820230323Digitizing and photo interpretation of apparent lines of occupation.withheld20030707Clark SelbyBAE Systems/ADR421-967-9577mailing and physical address
280 Kappa Dr.
PittsburghPennsylvania15238USAAutoCAD, ArcGIS 8.3200-2003withheldBAE Systems/ADRvector digital dataPainesville, OhioLake County GISwithheldSeptember 1, 20022000ATownship/Range Boundaryground conditionApril 20002400CD-ROMAerocon provided ortho imagery.Metadata imported.withheld20030710Metadata imported.withheld20030820Metadata imported.withheld20060519Quality Control performed by GIS Staff. 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.1950.195Not 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, 2002Township/Range BoundaryVectorSimpleFALSE0TRUEFALSEShapeShapeGeometry400Feature geometry.ESRICoordinates defining the features.SDEDBO_TWPOBJECTIDOID4100Internal feature number.EsriSequential unique whole numbers that are automatically generated.Lake County GISTwp_RangeFeature Class0The Land Ordinance of 1796 was passed. It defined the surveying system to be used by all future public land surveys. In this system the townships are 6 miles square, composed of 36 one mile square sections, each of which may be subdivided into quarters or smaller. The numbering of the sections is serpentine, starting in the northeast corner of the township. Townships are identified as being north or south of a baseline and in a range east or west of a longitudinal meridian line.SHAPETWP_RANGEString1000Feature geometry.ESRICoordinates defining the features.TWP_RANGEPERIMETERDouble8188PERIMETERSDEDBO_TWPDouble8188Shape.STArea()Shape.STArea()Double000Shape.STLength()Shape.STLength()Double000The Connecticut Western Reserve opened in 1786. It was located in the northeast corner of the state (Huron Co. and all counties to its north and east) and was surveyed into 5 mile square townships that were further subdivided, usually into 25 one mile square sections. The Land Ordinance of 1785 was Congress's attempt to coordinate the surveying and sale of land north of the Ohio River with the aim of raising sorely needed cash. The land was to be surveyed into 6 mile square townships, and those townships were to be divided into 1 mile square 'lots'. Half the land was to be sold as townships and half as lots. This scheme featured a different numbering scheme than that defined by the Land Ordinance of 1796. The 36 lots (sections) in a township counted northward from the southeast corner of the township, east to west. The Land Ordinance of 1796 was passed. It defined the surveying system to be used by all future public land surveys. In this system the townships are 6 miles square, composed of 36 one mile square sections, each of which may be subdivided into quarters or smaller. The numbering of the sections is serpentine, starting in the northeast corner of the township. Townships are identified as being north or south of a baseline and in a range east or west of a longitudinal meridian line.North American Vertical Datum of 19881.000000feetExplicit elevation coordinate included with horizontal coordinatesMean sea levelFrom 2' to 50'feetExplicit depth coordinate included with horizontal coordinatescoordinate pairsurvey feet0.0002560.000256GCS_North_American_1983NAD_1983_StatePlane_Ohio_North_FIPS_3401_FeetNorth American Datum of 1983Geodetic Reference System 806378137.000000298.257222 Version 6.2 (Build 9200) ; Esri ArcGIS 10.8.1.14362Twp_Range2244945.2692762377226.388887800222.691787695097.1239451-81.489708-80.99974641.85861941.5649341ISO 19115 Geographic Information - MetadataDIS_ESRI1.0dataset002withheldLocal Area Network0.195ShapefileFeature Class0NAD_1983_StatePlane_Ohio_North_FIPS_3401_FeetEPSG6.13(9.3.0.0)