LakeGIS.SDE.GOVT_JURISDICTION

Richard J. Kotapish Lake County GIS Director 440-350-5943 440-350-5942 dkotapish@lakecountyohio.org 8:00 am to 4:30 pm Monday through Friday mailing and physical address

105 Main Street

Painesville Ohio 44077 USA ground condition January 2003 BAE Systems/ADR vector digital data withheld Painesville, Ohio Lake County GIS September 1, 2002 2000 A LakeGIS.SDE.GOVT_JURISDICTION LakeGIS.SDE.GOVT_JURISDICTION BAE Systems/ADR vector digital data Painesville, Ohio Lake County GIS http://www.lakegis.org September 1, 2002 2000 A Complete As needed None None Lake County GIS Staff. To provide a graphic entity to which attribute data could be assigned for local government business practices. en This entity describes the boundaries of any unit of government or jurisdictional body having jurisdiction on any property within Lake County. This includes political jurisdictions such as cities, school systems, counties, and states. It does not, however, include administrative districts such as election districts, U.S. Census geography, and governmental service areas. Sea Level Lake County, Ohio PHYSICAL DATABASE DESIGN FOR LAKE COUNTY, OHIO - September 8, 2000. Jurisdiction Unclassified ESRI ArcCatalog 9.3.1.3000 -81.489708 -80.999746 41.858619 41.564934 2244945.270473 2377226.500661 695097.123957 800222.691920 Feature Class 20230222 13543500 20260213 09191500 FALSE 20230222 13543500 LakeGIS.SDE.GeneralZoningPublic 002 2244945.270473 2377226.500661 695097.123957 800222.691920 1 Projected GCS_North_American_1983 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/3.0.0'><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> Linear Unit: Foot_US (0.304801) 1.0 20091014 Richard J. Kotapish Lake County GIS Director 440-350-5943 440-350-5942 dkotapish@lakecountyohio.org 8:00 am to 4:30 pm Monday through Friday mailing and physical address

105 Main Street

Painesville Ohio 44077 USA None None en FGDC Content Standards for Digital Geospatial Metadata local time Unclassified withheld ESRI Metadata Profile FGDC-STD-001-1998 20230222 Digitizing and photo interpretation of apparent lines of occupation. withheld 20030707 12185300 Clark Selby BAE Systems/ADR 421-967-9577 mailing and physical address

280 Kappa Dr.

Pittsburgh Pennsylvania 15238 USA AutoCAD 2000-2002 withheld BAE Systems/ADR vector digital data Painesville, Ohio Lake County GIS withheld September 1, 2002 2000 A ground condition April 2000 2400 CD-ROM Digitize Aerocon provided ortho imagery. Metadata imported. withheld 20030710 08540100 Metadata imported. withheld 20090728 08163600 Dataset copied. withheld 20100802 14515800 Dataset copied. withheld 20100803 09430100 Quality 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 Program 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. 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. Kotapish Lake County GIS Director mailing and physical address

105 Main Street

Painesville Ohio 44077 U.S.A. 440-350-5943 440-350-5942 dkotapish@lakecountyohio.org 8:00 am to 4:30 pm Monday through Friday None ARCG 8.3 shapefile no compression applied Not Available CD-ROM Incompatible with MacIntosh OS $50/cd 1 day Call 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, 2002 Downloadable Data Vector Simple FALSE 0 TRUE FALSE Lake County GIS LakeGIS.SDE.GeneralZoningPublic Feature Class 0 Lake County GIS Sequential unique whole numbers that are automatically generated. September 1, 2000 September 1, 2002 99% Quality Control Program As needed OBJECTID OBJECTID OID 4 10 0 Internal feature number. JURIS JURIS String 254 0 0 SHORT_NAME SHORT_NAME String 20 0 0 FULL_NAME FULL_NAME String 30 0 0 TYPE TYPE String 15 0 0 SHAPE Shape Geometry 8 0 0 Feature geometry. ESRI Coordinates defining the features. District District String 50 0 0 General_Di General_Di String 50 0 0 NEOSCC_Zon NEOSCC_Zon String 20 0 0 Dist_Name Dist_Name String 50 0 0 Local_Code Local_Code String 10 0 0 Gen_zone Gen_zone String 50 0 0 GIS_NOTES GIS_NOTES String 255 0 0 LAST_UPDATED LAST_UPDATED Date 8 0 0 Community Community String 255 0 0 Contact Contact String 255 0 0 Title Title String 255 0 0 Phone_Number Phone Number String 255 0 0 Email Email String 255 0 0 Website_1 Website String 255 0 0 Map_on_the_Web Map on the Web String 255 0 0 Shape.STArea() Shape.STArea() Double 0 0 0 Shape.STLength() Shape.STLength() Double 0 0 0 North American Vertical Datum of 1988 1.000000 feet Explicit elevation coordinate included with horizontal coordinates Mean sea level From 2' to 50' feet Explicit depth coordinate included with horizontal coordinates GCS_North_American_1983 NAD_1983_StatePlane_Ohio_North_FIPS_3401_Feet coordinate pair survey feet 0.000328 0.000328 North American Datum of 1983 Geodetic Reference System 80 6378137.000000 298.257222 Esri ArcGIS 13.0.4.36057 LakeGIS.SDE.GeneralZoningPublic -81.489708 -80.999746 41.858619 41.564934 1 -81.489708 -80.999746 41.858619 41.564934 1 002 ISO 19115 Geographic Information - Metadata DIS_ESRI1.0 dataset 002 withheld Feature Class Enterprise Geodatabase Feature Class NAD_1983_StatePlane_Ohio_North_FIPS_3401_Feet EPSG 6.13(9.3.0.0) 0