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 conditionJanuary 2003BAE Systems/ADRvector digital data\\lcnas01\share\planning\New folder hierarchy\GIS and maps\Painesville Township\2009\New_Hadden_Buffer.shpPainesville, OhioLake County GISSeptember 1, 20022000ANew_Hadden_BufferBAE Systems/ADRvector digital dataPainesville, OhioLake County GIShttp://www.lakegis.orgSeptember 1, 20022000ACompleteContinuallyNoneNoneLake County GIS Staff.To provide a graphic entity to which attribute data could be assigned for local government business practices.enThose portions of the real estate parcel which are considered during appraisal and/or taxation processes. This excludes rights-of-way easements for roads and other, similar circumstances. Note that some real estate parcels are wholly exempt and may not be represented in any manner by a taxable parcel—examples include public utilities, mineral parcels (oil/gas wells), exempt uses, and etc. This corresponds to the “alpha parcel” as described by Assessor’s staff. Sea LevelLake County, OhioParcelsUnclassifiedMicrosoft Windows XP Version 5.1 (Build 2600) Service Pack 3; ESRI ArcCatalog 9.3.0.1770-81.489708-80.99974641.85861941.5649342244945.2701452377226.500004695097.124613800222.691920Shapefile20091027160342002009102715575900FALSE2009102716034200FeatureClassToFeatureClass "Database Connections\SDEDBO.sde\SDEDBO.CADASTRAL\SDEDBO.PARCELS_poly" "Database Connections\SDEDBO.sde\SDEDBO.CADASTRAL" PARCELS_poly2 # "PIN PIN true true false 30 Text 0 0 ,First,#,Database Connections\SDEDBO.sde\SDEDBO.CADASTRAL\SDEDBO.PARCELS_poly,PIN,-1,-1;M_PARCEL_ID M_PARCEL_ID true true false 20 Text 0 0 ,First,#,Database Connections\SDEDBO.sde\SDEDBO.CADASTRAL\SDEDBO.PARCELS_poly,M_PARCEL_ID,-1,-1;M_PARCEL_ID_DASHES M_PARCEL_ID_DASHES true true false 30 Text 0 0 ,First,#,Database Connections\SDEDBO.sde\SDEDBO.CADASTRAL\SDEDBO.PARCELS_poly,M_PARCEL_ID_DASHES,-1,-1;M_TAX_DISTRICT M_TAX_DISTRICT true true false 3 Text 0 0 ,First,#,Database Connections\SDEDBO.sde\SDEDBO.CADASTRAL\SDEDBO.PARCELS_poly,M_TAX_DISTRICT,-1,-1;M_OWNER_1 M_OWNER_1 true true false 25 Text 0 0 ,First,#,Database Connections\SDEDBO.sde\SDEDBO.CADASTRAL\SDEDBO.PARCELS_poly,M_OWNER_1,-1,-1;M_OWNER_2 M_OWNER_2 true true false 25 Text 0 0 ,First,#,Database Connections\SDEDBO.sde\SDEDBO.CADASTRAL\SDEDBO.PARCELS_poly,M_OWNER_2,-1,-1;M_OWNER_ADD_1 M_OWNER_ADD_1 true true false 25 Text 0 0 ,First,#,Database Connections\SDEDBO.sde\SDEDBO.CADASTRAL\SDEDBO.PARCELS_poly,M_OWNER_ADD_1,-1,-1;M_OWNER_ADD_2 M_OWNER_ADD_2 true true false 25 Text 0 0 ,First,#,Database Connections\SDEDBO.sde\SDEDBO.CADASTRAL\SDEDBO.PARCELS_poly,M_OWNER_ADD_2,-1,-1;M_LEGAL_DESC_1 M_LEGAL_DESC_1 true true false 25 Text 0 0 ,First,#,Database Connections\SDEDBO.sde\SDEDBO.CADASTRAL\SDEDBO.PARCELS_poly,M_LEGAL_DESC_1,-1,-1;M_LEGAL_DESC_2 M_LEGAL_DESC_2 true true false 25 Text 0 0 ,First,#,Database Connections\SDEDBO.sde\SDEDBO.CADASTRAL\SDEDBO.PARCELS_poly,M_LEGAL_DESC_2,-1,-1;M_LEGAL_DESC_3 M_LEGAL_DESC_3 true true false 25 Text 0 0 ,First,#,Database Connections\SDEDBO.sde\SDEDBO.CADASTRAL\SDEDBO.PARCELS_poly,M_LEGAL_DESC_3,-1,-1;M_LOT_NUMBER M_LOT_NUMBER true true false 5 Text 0 0 ,First,#,Database Connections\SDEDBO.sde\SDEDBO.CADASTRAL\SDEDBO.PARCELS_poly,M_LOT_NUMBER,-1,-1;M_ACRES M_ACRES true true false 4 Long 0 8 ,First,#,Database Connections\SDEDBO.sde\SDEDBO.CADASTRAL\SDEDBO.PARCELS_poly,M_ACRES,-1,-1;M_DIVISION_Y M_DIVISION_Y true true false 1 Text 0 0 ,First,#,Database Connections\SDEDBO.sde\SDEDBO.CADASTRAL\SDEDBO.PARCELS_poly,M_DIVISION_Y,-1,-1;M_NEW_CONSTRUCTION M_NEW_CONSTRUCTION true true false 1 Text 0 0 ,First,#,Database Connections\SDEDBO.sde\SDEDBO.CADASTRAL\SDEDBO.PARCELS_poly,M_NEW_CONSTRUCTION,-1,-1;M_LAND_VAL M_LAND_VAL true true false 8 Double 2 16 ,First,#,Database Connections\SDEDBO.sde\SDEDBO.CADASTRAL\SDEDBO.PARCELS_poly,M_LAND_VAL,-1,-1;M_IMPROVEMENT_VAL M_IMPROVEMENT_VAL true true false 8 Double 2 16 ,First,#,Database Connections\SDEDBO.sde\SDEDBO.CADASTRAL\SDEDBO.PARCELS_poly,M_IMPROVEMENT_VAL,-1,-1;M_CAUV_VAL M_CAUV_VAL true true false 8 Double 2 16 ,First,#,Database Connections\SDEDBO.sde\SDEDBO.CADASTRAL\SDEDBO.PARCELS_poly,M_CAUV_VAL,-1,-1;M_PROPERTY_CLASS M_PROPERTY_CLASS true true false 2 Short 0 3 ,First,#,Database Connections\SDEDBO.sde\SDEDBO.CADASTRAL\SDEDBO.PARCELS_poly,M_PROPERTY_CLASS,-1,-1;M_NEIGHBORHOOD_CODE M_NEIGHBORHOOD_CODE true true false 5 Text 0 0 ,First,#,Database Connections\SDEDBO.sde\SDEDBO.CADASTRAL\SDEDBO.PARCELS_poly,M_NEIGHBORHOOD_CODE,-1,-1;M_COUNTY_SPECIFIC_INFO M_COUNTY_SPECIFIC_INFO true true false 22 Text 0 0 ,First,#,Database Connections\SDEDBO.sde\SDEDBO.CADASTRAL\SDEDBO.PARCELS_poly,M_COUNTY_SPECIFIC_INFO,-1,-1;M_BOOK_PAGE_PARCEL M_BOOK_PAGE_PARCEL true true false 12 Text 0 0 ,First,#,Database Connections\SDEDBO.sde\SDEDBO.CADASTRAL\SDEDBO.PARCELS_poly,M_BOOK_PAGE_PARCEL,-1,-1;M_LOCATION_ADDRESS M_LOCATION_ADDRESS true true false 20 Text 0 0 ,First,#,Database Connections\SDEDBO.sde\SDEDBO.CADASTRAL\SDEDBO.PARCELS_poly,M_LOCATION_ADDRESS,-1,-1;M_REMARKS M_REMARKS true true false 5 Text 0 0 ,First,#,Database Connections\SDEDBO.sde\SDEDBO.CADASTRAL\SDEDBO.PARCELS_poly,M_REMARKS,-1,-1;M_MAILING_ACCOUNT_NO M_MAILING_ACCOUNT_NO true true false 5 Text 0 0 ,First,#,Database Connections\SDEDBO.sde\SDEDBO.CADASTRAL\SDEDBO.PARCELS_poly,M_MAILING_ACCOUNT_NO,-1,-1;M_MAILING_NAME_1 M_MAILING_NAME_1 true true false 25 Text 0 0 ,First,#,Database Connections\SDEDBO.sde\SDEDBO.CADASTRAL\SDEDBO.PARCELS_poly,M_MAILING_NAME_1,-1,-1;M_MAILING_NAME_2 M_MAILING_NAME_2 true true false 25 Text 0 0 ,First,#,Database Connections\SDEDBO.sde\SDEDBO.CADASTRAL\SDEDBO.PARCELS_poly,M_MAILING_NAME_2,-1,-1;M_MAILING_ADDRESS_1 M_MAILING_ADDRESS_1 true true false 25 Text 0 0 ,First,#,Database Connections\SDEDBO.sde\SDEDBO.CADASTRAL\SDEDBO.PARCELS_poly,M_MAILING_ADDRESS_1,-1,-1;M_MAILING_ADDRESS_2 M_MAILING_ADDRESS_2 true true false 25 Text 0 0 ,First,#,Database Connections\SDEDBO.sde\SDEDBO.CADASTRAL\SDEDBO.PARCELS_poly,M_MAILING_ADDRESS_2,-1,-1;M_DATA_CODE M_DATA_CODE true true false 6 Text 0 0 ,First,#,Database Connections\SDEDBO.sde\SDEDBO.CADASTRAL\SDEDBO.PARCELS_poly,M_DATA_CODE,-1,-1;M_DEED_VOL_PAGE M_DEED_VOL_PAGE true true false 8 Text 0 0 ,First,#,Database Connections\SDEDBO.sde\SDEDBO.CADASTRAL\SDEDBO.PARCELS_poly,M_DEED_VOL_PAGE,-1,-1;M_DEED_REFERENCE M_DEED_REFERENCE true true false 1 Text 0 0 ,First,#,Database Connections\SDEDBO.sde\SDEDBO.CADASTRAL\SDEDBO.PARCELS_poly,M_DEED_REFERENCE,-1,-1;M_ORIG_CONTRACT_DUE M_ORIG_CONTRACT_DUE true true false 12 Text 0 0 ,First,#,Database Connections\SDEDBO.sde\SDEDBO.CADASTRAL\SDEDBO.PARCELS_poly,M_ORIG_CONTRACT_DUE,-1,-1;M_DELIQ_DATE M_DELIQ_DATE true true false 36 Date 0 0 ,First,#,Database Connections\SDEDBO.sde\SDEDBO.CADASTRAL\SDEDBO.PARCELS_poly,M_DELIQ_DATE,-1,-1;M_CONTRACT_STAGE M_CONTRACT_STAGE true true false 2 Text 0 0 ,First,#,Database Connections\SDEDBO.sde\SDEDBO.CADASTRAL\SDEDBO.PARCELS_poly,M_CONTRACT_STAGE,-1,-1;M_CONTRACT_TERM M_CONTRACT_TERM true true false 2 Text 0 0 ,First,#,Database Connections\SDEDBO.sde\SDEDBO.CADASTRAL\SDEDBO.PARCELS_poly,M_CONTRACT_TERM,-1,-1;M_CONTRACT_FLAG M_CONTRACT_FLAG true true false 1 Text 0 0 ,First,#,Database Connections\SDEDBO.sde\SDEDBO.CADASTRAL\SDEDBO.PARCELS_poly,M_CONTRACT_FLAG,-1,-1;M_RECORD_STATUS M_RECORD_STATUS true true false 1 Text 0 0 ,First,#,Database Connections\SDEDBO.sde\SDEDBO.CADASTRAL\SDEDBO.PARCELS_poly,M_RECORD_STATUS,-1,-1;M_AG_DIST_CODE M_AG_DIST_CODE true true false 2 Text 0 0 ,First,#,Database Connections\SDEDBO.sde\SDEDBO.CADASTRAL\SDEDBO.PARCELS_poly,M_AG_DIST_CODE,-1,-1;M_AG_DIST_YEAR M_AG_DIST_YEAR true true false 4 Text 0 0 ,First,#,Database Connections\SDEDBO.sde\SDEDBO.CADASTRAL\SDEDBO.PARCELS_poly,M_AG_DIST_YEAR,-1,-1;M_SALE_DATE M_SALE_DATE true true false 36 Date 0 0 ,First,#,Database Connections\SDEDBO.sde\SDEDBO.CADASTRAL\SDEDBO.PARCELS_poly,M_SALE_DATE,-1,-1;M_NUMBER_OF_PARCELS M_NUMBER_OF_PARCELS true true false 2 Text 0 0 ,First,#,Database Connections\SDEDBO.sde\SDEDBO.CADASTRAL\SDEDBO.PARCELS_poly,M_NUMBER_OF_PARCELS,-1,-1;M_SALE_TYPE M_SALE_TYPE true true false 2 Text 0 0 ,First,#,Database Connections\SDEDBO.sde\SDEDBO.CADASTRAL\SDEDBO.PARCELS_poly,M_SALE_TYPE,-1,-1;M_SALE_AMOUNT M_SALE_AMOUNT true true false 8 Double 2 16 ,First,#,Database Connections\SDEDBO.sde\SDEDBO.CADASTRAL\SDEDBO.PARCELS_poly,M_SALE_AMOUNT,-1,-1;M_SALE_SOURCE M_SALE_SOURCE true true false 1 Text 0 0 ,First,#,Database Connections\SDEDBO.sde\SDEDBO.CADASTRAL\SDEDBO.PARCELS_poly,M_SALE_SOURCE,-1,-1;M_SALE_VALIDITY M_SALE_VALIDITY true true false 1 Text 0 0 ,First,#,Database Connections\SDEDBO.sde\SDEDBO.CADASTRAL\SDEDBO.PARCELS_poly,M_SALE_VALIDITY,-1,-1;M_SALE_CONVEY_NO M_SALE_CONVEY_NO true true false 5 Text 0 0 ,First,#,Database Connections\SDEDBO.sde\SDEDBO.CADASTRAL\SDEDBO.PARCELS_poly,M_SALE_CONVEY_NO,-1,-1;M_SALE_DEED_NO M_SALE_DEED_NO true true false 10 Text 0 0 ,First,#,Database Connections\SDEDBO.sde\SDEDBO.CADASTRAL\SDEDBO.PARCELS_poly,M_SALE_DEED_NO,-1,-1;RESURVEY RESURVEY true true false 10 Text 0 0 ,First,#,Database Connections\SDEDBO.sde\SDEDBO.CADASTRAL\SDEDBO.PARCELS_poly,RESURVEY,-1,-1;A_HOUSENO A_HOUSENO true true false 4 Long 0 9 ,First,#,Database Connections\SDEDBO.sde\SDEDBO.CADASTRAL\SDEDBO.PARCELS_poly,A_HOUSENO,-1,-1;A_PREDIR A_PREDIR true true false 2 Text 0 0 ,First,#,Database Connections\SDEDBO.sde\SDEDBO.CADASTRAL\SDEDBO.PARCELS_poly,A_PREDIR,-1,-1;A_RDNAME A_RDNAME true true false 40 Text 0 0 ,First,#,Database Connections\SDEDBO.sde\SDEDBO.CADASTRAL\SDEDBO.PARCELS_poly,A_RDNAME,-1,-1;A_RDTYPE A_RDTYPE true true false 2 Text 0 0 ,First,#,Database Connections\SDEDBO.sde\SDEDBO.CADASTRAL\SDEDBO.PARCELS_poly,A_RDTYPE,-1,-1;A_SUFDIR A_SUFDIR true true false 2 Text 0 0 ,First,#,Database Connections\SDEDBO.sde\SDEDBO.CADASTRAL\SDEDBO.PARCELS_poly,A_SUFDIR,-1,-1;JURIS JURIS true true false 4 Text 0 0 ,First,#,Database Connections\SDEDBO.sde\SDEDBO.CADASTRAL\SDEDBO.PARCELS_poly,JURIS,-1,-1;A_APTNO A_APTNO true true false 10 Text 0 0 ,First,#,Database Connections\SDEDBO.sde\SDEDBO.CADASTRAL\SDEDBO.PARCELS_poly,A_APTNO,-1,-1;A_SUF_SUF A_SUF_SUF true true false 12 Text 0 0 ,First,#,Database Connections\SDEDBO.sde\SDEDBO.CADASTRAL\SDEDBO.PARCELS_poly,A_SUF_SUF,-1,-1;D_ACREAGE D_ACREAGE true true false 8 Double 8 38 ,First,#,Database Connections\SDEDBO.sde\SDEDBO.CADASTRAL\SDEDBO.PARCELS_poly,D_ACREAGE,-1,-1;D_ADDRESS D_ADDRESS true true false 50 Text 0 0 ,First,#,Database Connections\SDEDBO.sde\SDEDBO.CADASTRAL\SDEDBO.PARCELS_poly,D_ADDRESS,-1,-1;D_DEED_VOL_PAGE D_DEED_VOL_PAGE true true false 12 Text 0 0 ,First,#,Database Connections\SDEDBO.sde\SDEDBO.CADASTRAL\SDEDBO.PARCELS_poly,D_DEED_VOL_PAGE,-1,-1;D_DOCUMENTS D_DOCUMENTS true true false 240 Text 0 0 ,First,#,Database Connections\SDEDBO.sde\SDEDBO.CADASTRAL\SDEDBO.PARCELS_poly,D_DOCUMENTS,-1,-1;AREA AREA false false true 0 Double 0 0 ,First,#,Database Connections\SDEDBO.sde\SDEDBO.CADASTRAL\SDEDBO.PARCELS_poly,SHAPE.AREA,-1,-1;LEN LEN false false true 0 Double 0 0 ,First,#,Database Connections\SDEDBO.sde\SDEDBO.CADASTRAL\SDEDBO.PARCELS_poly,SHAPE.LEN,-1,-1" # "Database Connections\SDEDBO.sde\SDEDBO.CADASTRAL\SDEDBO.PARCELS_poly2"CopyFeatures "Database Connections\SDEDBO.sde\SDEDBO.CADASTRAL\SDEDBO.PARCELS_poly" "Database Connections\LAKEGIS_SDE.sde\LakeGIS.SDE.CADASTRAL\LakeGIS.SDE.SDEDBO_PARCELS_poly" # 0 0 0Dissolve Hadden_Elementary_Parcels "F:\New folder hierarchy\GIS and maps\Painesville Township\2009\New_Hadden.shp" # # MULTI_PART DISSOLVE_LINESBuffer New_Hadden "F:\New folder hierarchy\GIS and maps\Painesville Township\2009\New_Hadden_Buffer.shp" "2 Miles" FULL ROUND NONE #{9580E057-4802-4D3F-9101-1C3F22FC081E}20091027Richard 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 Profile20091027Digitizing and photo interpretation of apparent lines of occupation.Orthophotos2003070712185300Clark 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.xml2003071008540100Metadata imported.M:\production\Metadata\cadastral_metadata.xml2004032314395800Metadata imported.M:\CountywideShapefiles\Cadastral\Parcels_030504.shp.xml2004032314425000Dataset copied.Server=gissrv; Service=5151; Database=lakegis; User=sde; Version=sde.DEFAULT2009102715575900Quality 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, 2002ParcelsVectorG-polygon0SimplePolygonFALSE0FALSEFALSEThose portions of the real estate parcel which are considered during appraisal and/or taxation processes. This excludes rights-of-way easements for roads and other, similar circumstances. Note that some real estate parcels are wholly exempt and may not be represented in any manner by a taxable parcel—examples include public utilities, mineral parcels (oil/gas wells), exempt uses, and etc. This corresponds to the “alpha parcel” as described by Assessor’s staff.315.000000FALSE192197201202203Lake County GISNew_Hadden_BufferFeature Class0Those portions of the real estate parcel which are considered during appraisal and/or taxation processes. This excludes rights-of-way easements for roads and other, similar circumstances. Note that some real estate parcels are wholly exempt and may not be represented in any manner by a taxable parcel—examples include public utilities, mineral parcels (oil/gas wells), exempt uses, and etc. This corresponds to the “alpha parcel” as described by Assessor’s staff.FIDFIDOID400Internal feature number.ESRISequential unique whole numbers that are automatically generated.SHAPEShapeGeometry000Feature geometry.ESRICoordinates defining the features.IdIdNumber6BUFF_DISTBUFF_DISTFloat1911North 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.1770New_Hadden_Buffer2244945.2701452377226.500004800222.69192695097.1246131-81.489708-80.99974641.85861941.5649341ISO 19115 Geographic Information - MetadataDIS_ESRI1.0datasetShapefile002file://\\lcnas01\share\planning\New folder hierarchy\GIS and maps\Painesville Township\2009\New_Hadden_Buffer.shpLocal Area Network0.000NAD_1983_StatePlane_Ohio_North_FIPS_3401_Feet0