This parcels polygons feature class represents current city parcels within the City of Los Angeles. It shares topology with the Landbase parcel lines feature class. The Mapping and Land Records Division of the Bureau of Engineering, Department of Public Works provides the most current geographic information of the public right of way, ownership and land record information. The legal boundaries are determined on the ground by license surveyors in the State of California, and by recorded documents from the Los Angeles County Recorder's office and the City Clerk's office of the City of Los Angeles. Parcel and ownership information are available on NavigateLA, a website hosted by the Bureau of Engineering, Department of Public Works.Associated information about the landbase parcels is entered into attributes. Principal attributes include:PIN and PIND: represents the unique auto-generated parcel identifier and key to related features and tables. This field is related to the LA_LEGAL, LA_APN and LA_HSE_NBR tables. PIN contains spaces and PIND replaces those spaces with a dash (-).LA_LEGAL - Table attributes containing legal description. Principal attributes include the following:TRACT: The subdivision tract number as recorded by the County of Los AngelesMAP_REF: Identifies the subdivision map book reference as recorded by the County of Los Angeles.LOT: The subdivision lot number as recorded by the County of Los Angeles.ENG_DIST: The four engineering Districts (W=Westla, C=Central, V= Valley and H=Harbor).CNCL_DIST: Council Districts 1-15 of the City of Los Angeles. OUTLA means parcel is outside the City.LA_APN- Table attributes containing County of Los Angeles Assessors information. Principal attributes include the following:BPP: The Book, Page and Parcel from the Los Angeles County Assessors office. SITUS*: Address for the property.LA_HSE_NBR - Table attributes containing housenumber information. Principal attributes include the following:HSE_ID: Unique id of each housenumber record.HSE_NBR: housenumber numerical valueSTR_*: Official housenumber addressFor a complete list of attribute values, please refer to Landbase_parcel_polygons_data_dictionary.Landbase parcels polygons data layer was created in geographical information systems (GIS) software to display the location of the right of way. The parcels polygons layer delineates the right of way from Landbase parcels lots. The parcels polygons layer is a feature class in the LACityLandbaseData.gdb Geodatabase dataset. The layer consists of spatial data as a polygon feature class and attribute data for the features. The area inside a polygon feature is a parcel lot. The area outside of the parcel polygon feature is the right of way. Several polygon features are adjacent, sharing one line between two polygons. For each parcel, there is a unique identifier in the PIND and PIN fields. The only difference is PIND has a dash and PIN does not. The types of edits include new subdivisions and lot cuts. Associated legal information about the landbase parcels lots is entered into attributes. The landbase parcels layer is vital to other City of LA Departments, by supporting property and land record operations and identifying legal information for City of Los Angeles. The landbase parcels polygons are inherited from a database originally created by the City's Survey and Mapping Division. Parcel information should only be added to the Landbase Parcels layer if documentation exists, such as a Deed or a Plan approved by the City Council. When seeking the definitive description of real property, consult the recorded Deed or Plan.List of Fields:ID: A unique numeric identifier of the polygon. The ID value is the last part of the PIN field value.ASSETID: User-defined feature autonumber.MAPSHEET: The alpha-numeric mapsheet number, which refers to a valid B-map or A-map number on the Cadastral grid index map. Values: • B, A, -5A - Any of these alpha-numeric combinations are used, whereas the underlined spaces are the numbers. An A-map is the smallest grid in the index map and is used when there is a large amount of spatial information in the map display. There are more parcel lines and annotation than can fit in the B-map, and thus, an A-map is used. There are 4 A-maps in a B-map. In areas where parcel lines and annotation can fit comfortably in an index map, a B-map is used. The B-maps are at a scale of 100 feet, and A-maps are at a scale of 50 feet.OBJECTID: Internal feature number.BPPMAP_REFTRACTBLOCKMODLOTARBCNCL_DIST: LA City Council District. Values: • (numbers 1-15) - Current City Council Member for that District can be found on the mapping website http://navigatela.lacity.org/navigatela, click Council Districts layer name, under Boundaries layer group.SHAPE: Feature geometry.BOOKPAGEPARCELPIND: The value is a combination of MAPSHEET and ID fields, creating a unique value for each parcel. The D in the field name PIND, means "dash", and there is a dash between the MAPSHEET and ID field values. This is a key attribute of the LANDBASE data layer. This field is related to the APN and HSE_NBR tables.ENG_DIST: LA City Engineering District. The boundaries are displayed in the Engineering Districts index map. Values: • H - Harbor Engineering District. • C - Central Engineering District. • V - Valley Engineering District. • W - West LA Engineering District.PIN: The value is a combination of MAPSHEET and ID fields, creating a unique value for each parcel. There are spaces between the MAPSHEET and ID field values. This is a key attribute of the LANDBASE data layer. This field is related to the APN and HSE_NBR tables.

BY USING THIS WEBSITE OR THE CONTENT THEREIN, YOU AGREE TO THETERMS OF USE.A spatial representation of land use. The polygons contained in this feature class were derived from the Oakland County Tax Parcel feature class. Each parcel was categorized by its land use. When a parcel has multiple land uses, the dominant land use is shown. Assessing records and orthophotography were the main sources used to attribute each tax parcel with land use information. The data was collected in 2011. Key attributes are the land use and key pin (Sidwell number). Land Use stores the Land Use description for each parcel. The Key Pin is the unique Parcel Identification Number (Pin) used to link the parcel to the parcel attributes which are stored and maintained in Oakland County Land Records.The 2011 version of land use was created using the 2010 version as a primary source. It was assumed that if the Parcel Identification Number and the Use Code were equal in both years, then the land use did not change. Thus, only the parcels where a change occured had to be assigned a land use. To ensure the quality of the land use data, however, several types of use codes were manually checked again for this update to enusre the assigned use is still accurate. Also, reference data such as the Adult Care, Public Beach, and Recreation Land feature classes the were used to locate misrepresented parcels.The development process consists of three basic steps. First, parcels with use codes that are assumed to relate to a single land use are categorized as such. Second, parcels with a use code that is assumed to relate to more than one land use are manually classified using orthophotography and ownership as a reference. Lastly, tax parcels, right-of-way, and hydrography are unioned to create a single land use dataset.Assumptions:In 2005, Oakland County Equalization and many of the local assessors have changed from using the use codes described below to property class codes. These codes were interpreted to simliar use codes for the purpose of this data. One major change is that tax exempt property is no longer recorded using the "ME, Miscellaneous Exempt" use code, but are instead usually classifed as "RV, Residential Vacant." The "Taxable" field was referenced to locate tax exempt property such as schools, churches, and governemnt-owned property during this land use update.Any parcel classified as vacant may be an accessory use to an adjacent, commonly owned, improved parcel. In this event, the vacant parcel is reclassified as the use of the adjacent, commonly owned, improved parcel. It should be noted, however, that parcels with use codes of RV, SV, and LV, that represent a single family vacant use, are exempt from this assumption.Parcels with an Equalization use code of RV, SV, or LV may include uses to be reclassified as Vacant or Recreation & Conservation (due to subdivision open space). These parcels are not manually checked. Queries are conducted to search for those parcels that are subdivision open space. The following strings are queried from the Owner1 and Owner2 fields: "*own*" (unknown, homeowner), "ass*" (association, ass'n, etc), and "park."The Equalization use code BI, Business Improved includes uses that are reclassified as Commercial/Office. Uses may also fall into Public/Institutional, however, all BI parcels are not manually checked for reclassification.The Equalization use code MM, Miscellaneous Business includes uses that are reclassified as Recreation and Conservation, Multiple Family, Commercial/Office, or Mobile Home Park.The Equalization use code ME, Miscellaneous Exempt includes uses that are reclassified as Recreation & Conservation, Public/Institutional, Transportation, Utility & Communication, Industrial (municipal landfills), or any Single Family classification.The Equalization use code KI, Condominium Improved includes uses that are reclassified as Multiple Family, Single Family, or Commercial/Office. Any parcel with an Equalization use code of FI, Farm Improved or FV, Farm Vacant is considered to be an active agricultural use.Any parcel with an Equalization use code of II, Industrial Improved is considered to be an industrial use.Any parcel with an Equalization use code of FC, Farm Conservation is considered to be a recreational/conservation use.Any parcel with an Equalization use code of AI, Apartment Improved is considered to be a multiple family residential use.Any parcel with an Equalization use code of UI, Utility Improved is considered to be a transportation, utility, or communication related use.Parcels with an Equalization use code of DI, Developmental Improved are reclassified as Single Family or Vacant.Any parcel with an Equalization use code of DV for Developmental Vacant may be reclassified as Vacant, Recreation & Conservation, (golf courses) or Industrial (mining or extractive).Polygons in the ROW region of the parcel coverage will be classified as Recreation and Conservation, and Commercial/Office, Vacant, Road ROW, and Railroad ROW.Because of inconsistencies in Use Code data, unique uses, and the goal of creating an accurate coverage that is not limited by its metadata, there may be exceptions from these assumptions.Exceptions:There are nine isolated cases where the land use would be tremendously overstated if the whole parcel was shown in a single use. In these cases, the polygon was split to show the use of the rest of the parcel vacant. These parcels are listed below: 01-29-451-001 01-35-300-014 04-08-200-002 04-24-100-004 07-13-301-006 14-04-376-002 18-19-476-015 21-10-200-001 21-10-200-002

This dataset contains the spatial representation (polygon) of all parcels of land surveyed for statutory access or Right-of-Way purposes, with active surveys, that are or have been within the purview of the B.C. Crown Land Management program. The view was created to provide a simplified view of this data from the survey parcel information in the Tantalis operational system.

This data is intended as a reference material of street and alley vacations, but not designed for survey, accurate positioning, or legal documents. It is created as polygon feature class, vacation information based on field measurements, types of Right of Way, and citations of Journal of the Common Council (J.C.C.) and the plat Liber and Page is listed under the column titled 'Sub_Plat'. The paper maps of the Street and Alley Vacation, the raster layer version of those maps (Linen Map Markup Mosaic), and the Detroit parcel layer are used as base maps to create this data.

The street and alley vacations were recorded from 1831 to 2022 throughout the whole city, and it will be updated weekly. The existed and/or active street and alley vacations are ready to view, the authors are working on pending and historical records.

Spatial Reference: WGS 1984 Web Mercator Auxiliary Sphere

The layer displays the roads and rights-of-way (sidewalks, berms, and dedicated public city land) that were either outright vacated or vacated with an easement. It is created as polygon feature class, vacation information based on field measurements, types of Right of Way, and citations of Journal of the Common Council (J.C.C.) and the plat Liber and Page is listed under the column titled "Sub_Plat". The paper maps of the Street and Alley Vacation, the raster layer version of those maps (Linen Map Markup Mosaic), and the Detroit parcel layer are used as base maps to create this data. The street and alley vacations are from 1831 to 2025 throughout the whole city, and it will be updated on monthly basis.For more information please visit the Maps and Records website.

BY USING THIS WEBSITE OR THE CONTENT THEREIN, YOU AGREE TO THE TERMS OF USE. A spatial representation of parcel history. This polygon feature class is created and maintained through the use of a customized tool for parcel maintenance management. As parcel splits and combinations create child parcels, the parent parcels are saved out to the parcel history feature class. Retired tax parcels have been maintained since 1998. Right of way and alley vacations are also maintained in this feature class. Vacations have been maintained since Spring, 2005. The key attributes include parcel identification number (KeyPIN) and the creation date (RevisionDate).

TA_SURVEYED_ROW_PARCELS_SVW contains the spatial representation (polygon) of all parcels of land surveyed for statutory access or Right-of-Way purposes, with active surveys, that are or have been within the purview of the B.C. Crown Land Management program. The view was created to provide a simplified view of this data from the survey parcel information in the Tantalis operational system

A polygon feature class of Right Of Way (ROW) boundaries within Miami-Dade County. This data was derived from the Lot layer and is maintain in the Esri Parcel Fabric (PF) data model.Updated: Not Planned The data was created using: Projected Coordinate System: WGS_1984_Web_Mercator_Auxiliary_SphereProjection: Mercator_Auxiliary_Sphere

This file is a digital geospatial Environmental Systems Research Institute (ESRI) ArcGIS File Geodatabase Polygon Feature Class representing land use in the seven northeastern Illinois counties (Cook, DuPage, Kane, Kendall, Lake, McHenry and Will). Land use is identified to 60 categories, and was created using county parcel GIS boundaries and Assessor data, along with color orthorectificed aerial photography captured in April, 2010. Land uses were assigned to parcels using a combination of automated and manual techniques, using a variety of reference data sets for land use identification and validation. Parcels were then dissolved on common land uses (to the limits of PLS sections or assessor blocks); polygons were generated for “non-parcel” (water, right-of-way) areas and classified using automated processes, and extnesive topological cleaning was necessary to minimize gap/overlap issues.In addition to this metadata record, additional information can be found in the following documents:2010 Land Use Inventory Classification Scheme2010 Land Use Inventory Geodatabase Schema2010 Land Use Inventory MetadataLANDUSE lookup .csv table to support shapefile downloadsProcess Narrative: Creating the 2010 Land Use Inventory for Northeastern IllinoisProcess Narrative Addendum: Creating Version 2.0Comparison Guide: Differences between the 2010 and 2005 Land Use InventoriesNOTE: Land use polygons are based on county parcel boundaries; special care must be exercised when comparing these data to earlier (2005, 2001, 1990) Inventories, which relied on manual drafting of land use boundaries that would extend to road centerlines. Additionally, the classification scheme was rewritten to accommodate the parcel approach; see the "comparison guide" link above for inter-inventory analysis guidance.

BY USING THIS WEBSITE OR THE CONTENT THEREIN, YOU AGREE TO THE TERMS OF USE.

Summary: This dataset contains an inventory of City of Los Angeles Sidewalks and related features (Access Ramps, Curbs, Driveways, and Parkways).Background: This inventory was performed throughout 2017 using a combination of G.I.S software, aerial imagery (2014 LARIAC), and a geographic dataset of property/right-of way lines. The dataset has not been updated since its creation.Description: The following provides more detail about the feature classes in this dataset. All features were digitized (“traced”) as observed in the orthophotography (digital aerial photos) and assigned the Parcel Identification Number (PIN) of their corresponding property:Sidewalk (polygon) – represents paved pedestrian walkways. Typical widths are between 3‐6 feet in residential areas and larger and more variable in commercial and high‐density traffic areas.Alley-Sidewalk (polygon) – represents the prevailing walkway or path of travel at the entrance/exit of an alley. Digitized as Sidewalk features but categorized as Alley Sidewalk and assigned a generic PIN value, ALLEY SIDEWALK.Corner Polygon (polygon) - feature created where sidewalks from two streets meet but do not intersect (i.e. at corner lots). There’s no standard shape/type and configurations vary widely. These are part of the Sidewalk feature class.In commercial and high‐density residential areas where there is only continuous sidewalk (no parkway strip), the sidewalk also functions as a Driveway.Driveway (polygon) – represents area that provides vehicular access to a property. Features are not split by extended parcel lot lines except when two adjacent properties are served by the same driveway approach (e.g. a common driveway), in which case they are and assigned a corresponding PIN.Parkway (polygon) – represents the strip of land behind the curb and in front of the sidewalk. Generally, they are landscaped with ground cover but they may also be filled in with decorative stone, pavers, decomposed granite, or concrete. They are created by offsetting lines, the Back of Curb (BOC) line and the Face of Walk (FOW). The distance between the BOC and FOW is measured off the aerial image and rounded to the nearest 0.5 foot, typically 6 – 10 feet.Curb (polygon) – represents the concrete edging built along the street to form part of the gutter. Features are always 6” wide strips and are digitized using the front of curb and back of curb digitized lines. They are the leading improvement polygon and are created for all corner, parkway, driveway and, sidewalk (if no parkway strip is present) features.Curb Ramp, aka Access Ramp (point) – represents the geographic center (centroid) of Corner Polygon features in the Sidewalk feature class. They have either a “Yes” or “No” attribute that indicates the presence or absence of a wheelchair access ramp, respectively.Fields: All features include the following fields...FeatureID – a unique feature identifier that is populated using the feature class’ OBJECTID fieldAssetID – a unique feature identifier populated by Los Angeles City staff for internal usePIND – a unique Parcel Identification Number (PIN) for all parcels within the City of L.A. All Sidewalk related features will be split, non-overlapping, and have one associated Parcel Identification Number (PIN). CreateDate – indicates date feature was createdModifiedDate – indicates date feature was revised/editedCalc_Width (excluding Access Ramps) – a generalized width of the feature calculated using spatial and mathematical algorithms on the feature. In almost all cases where features have variable widths, the minimum width is used. Widths are rounded to the nearest whole number. In cases where there is no value for the width, the applied algorithms were unable to calculate a reliable value.Calc_Length (excluding Access Ramps) – a generalized length of the feature calculated using spatial and mathematical algorithms on the feature. Lengths are rounded to the nearest whole number. In cases where there is no value for the length, the applied algorithms were unable to calculate a reliable value.Methodology: This dataset was digitized using a combination of G.I.S software, aerial imagery (2014 LARIAC), and a geographic dataset of property/right-of way lines.The general work flow is as follows:Create line work based on digital orthophotography, working from the face‐of‐curb (FOC) inward to the property right-of-way (ROW)Build sidewalk, parkway, driveway, and curb polygons from the digitized line workPopulate all polygons with the adjacent property PIN and classify all featuresCreate Curb Ramp pointsWarnings: This dataset has been provided to allow easy access and a visual display of Sidewalk and related features (Parkways, Driveway, Curb Ramps and Curbs). Every reasonable effort has been made to assure the accuracy of the data provided; nevertheless, some information may not be accurate. The City of Los Angeles assumes no responsibility arising from use of this information. THE MAPS AND ASSOCIATED DATA ARE PROVIDED WITHOUT WARRANTY OF ANY KIND, either expressed or implied, including but not limited to, the implied warranties of merchantability and fitness for a particular purpose. Other things to keep in mind about this dataset are listed below:Obscured Features – The existence of dense tree canopy or dark shadows in the aerial imagery tend to obscure or make it difficult to discern the extent of certain features, such as Driveways. In these cases, they may have been inferred from the path in the corresponding parcel. If a feature and approach was completely obscured, it was not digitized. In certain instances the coloring of the sidewalk and adjacent pavement rendered it impossible to identify the curb line or that a sidewalk existed. Therefore a sidewalk may or may not be shown where one actually may or may not exist.Context: The following links provide information on the policy context surrounding the creation of this dataset. It includes links to City of L.A. websites:Willits v. City of Los Angeles Class Action Lawsuit Settlementhttps://www.lamayor.org/willits-v-city-la-sidewalk-settlement-announcedSafe Sidewalks LA – program implemented to repair broken sidewalks in the City of L.A., partly in response to the above class action lawsuit settlementhttps://sidewalks.lacity.org/Data Source: Bureau of EngineeringNotes: Please be aware that this dataset is not actively being maintainedLast Updated: 5/20/20215/20/2021 - Added Calc_Width and Calc_Length fieldsRefresh Rate: One-time deliverable. Dataset not actively being maintained.

Polygon Parcel data for the city of Norfolk, VA***DISCLAIMER***Parcel Boundaries contained in this data set should not be used as a means of determining Right of Way (ROW). These polygons were created to show generalized property boundaries, and to hold the Real Estate Assessor attribute data pertaining to tax accounts associated with these properties. Only a survey by a licensed professional can determine accurate ROW boundaries.

Description

The PARCELS layer depicts mapped land parcels or real estate properties within Chester County. This data contains geometric representations capturing the general size, shape and location for all of the real estate properties, which can be mapped, on the County's land surface.

ContactsTim Cassel, County of Chester

Tcassel@chesco.org, 610-344-5441, 313 W. Market St Suite 5302 West Chester, PA 19380ResourceUpdate frequency of dataset: Weekly Last Update Date: August 2023Accuracy of attribute: Attributes are correct as per County of Chester Assessment DepartmentPositional accuracy of dataset:The PARCELS layer (and derived copies PARCEL_PUBLISH and PRCL_POLY) was originally created through a conversion process of digitizing hand drawn tax maps into digital form and orientating the tax map sheets and parcels to the features depicted in the 1993 orthophotos. These parcel polygon features were adjusted based on aerial photography dated April 7, 1993, and road centerlines, right-of-way lines and other physical features generated from the same photography. While the imagery has a pixel resolution of 1.5 square feet, a positional accuracy of +/- 5 feet and is designed for use at a scale of 1 inch = 200 feet, the resulting PARCELS horizontal accuracy varies from reasonably accurate in the best cases to less accurate in the worst cases. Subsequent and current map update processes include metes and bounds entry from subdivision and deed information, as well as property corner locations based on GPS points and the utilization of our newest imagery datasets. While the update processes include more accurate methods, the resultant overall accuracy is still dependent on the surrounding parcel fabric's varied accuracy. Planimetric coordinates are based on the Pennsylvania State Plane Coordinate System South Zone and North American Datum 1983 Spatial ReferenceType: ProjectedGeographic Coordinate Reference: GCS North America 1983Projected Coordinate System: NAD 1983 State Plane Pennsylvania SouthLinear Unit: US Survey Feet

Note: There is a difference between land use code and zoning. Land management occurs via a land use designation which determines the land use code. This designation specifies how land and resources within it is managed. Zoning designations define how a property can be developed and used and it is controlled by each township/borough. See below for list of codes.Field DescriptionUPI - Uniform Parcel Identification Number, a unique value given to each parcelPIN_MAP - A Tie-back parcel identification number used to link UPI values to the parcel on which they residePIN_COMMON - A variation of UPI which adds and E for Exempt, U for Utility or T for TrailerPIN_ASMNT - A long form of the UPI number used for assessment purposesCODE (see below for list of codes)MULTI_POLY - Number listing for each parcel of a Multi-Poly parcel. (Example 1 of 20, 2 of 20)POLY_PER_PARCEL - Number of polygons that make up a parcel (0 indicates it is just one polygon)SQFT_PLAN_TOT - The square footage of a parcel (taken from the recorded plan or deed)ACRE_PLAN_TOT - The acreage of a parcel (taken from the recorded plan or deed)ACRE_PLAN_POLY - The acreage of the polygon depicting the parcel, derived by mapping softwareXCOORD - X coordinate of the centroid of the polygonYCOORD - Y coordinate of the centroid of the polygonLOC_ADDRESS - The location address for a parcelMUNI - The municipality the parcel resides inST_NUM - Street Number of the Situs AddressNUM_SUF - Street Number Suffix of the Situs AddressDIR - Street directional of the Situs Address (N, E, S, W)ST_NAME - Street Name of the Situs AddressST_TYPE - Street thorough fair type of the Situs AddressUNIT - Unit Type (see codes below)UNIT_N - Unit numberAD_ROLE - Situs Address Functional Role (see below for list of codes)NO_ADDR_CODE - No longer usedTILE_1200 - Outdated reference system, no longer usedTILE_2400 - Outdated reference system, no longer usedSUBDIV_NUMBER - Number assigned by Recorder of Deeds to a recorded documentLOT - Lot number given to parcel on the recorded planLAND_DEV_ID - Number assigned by Planning Commission for their tracking purposesCREATE_DATE - Date the parcel was mapped into the inactive parcel layerACTIVE_DATE - Date the parcel was added to the active parcel layerOWN1 - Owner of recordOWN2 - Owner of record if more than oneADDR1 - Component of the mailing address on recordADDR2 - Component of the mailing address on recordADDR3 - Component of the mailing address on recordZIP1 - Zipcode of mailing address on recordTAXYR - For Assessment purposesJURIS - Municipality Number where parcel is taxedBOOK - The book number of the recorded deedPAGE - The page number of the recorded deedDEED_REC_DATE - Date the latest deed was recordedLEGAL1 - Description of property location according to the deedLEGAL2 - Description of the taxable property and buildings according to the deedLUC - Landuse code assigned by assessment office. (unrelated to municipal zoning of a parcel) ((see below for list of codes))CLASS - General landuse classification assigned by assessment office (see below for list of codes)LOT_ASSESS - Assessed value of the landPROP_ASSESS - Assessed value of the structuresTOT_ASSESS - Assessed value of the combination of land and structuresFMV319 - Fair Market Value if not under 319FMV515 - Fair Market Value if not under 515LAST_SALE_PRICE - Last recorded sale priceASMNT_DATE - For Assessment Department use onlySCHDIST - The school district within which the parcel resides (see below for list of codes)SUBDIV_NAME - Name of the recorded planPLAN_NUM - Number assigned by the Planning Commission for their tracking purposesMODIFY_DATE - Last edit date of the parcel Data Dictionary Code1000= Parcel1010= Condominium (mother or host parcel)1011= Common Law Condo1020= Hydrography1031= Paper ROW1033= Land polygon with a ROW1034= Land dedicated to an existing ROW1035=- Private Road1040= Open Space1042= Common Area1043= Open Space owned by Homeowners Association1710= Parcel Assessed in Lancaster County but located in Chester County1711= Parcel Assessed in Berks County but located in Chester County1712= Parcel Assessed in Montgomery County but located in Chester County1713= Parcel Assessed in Delaware County but located in Chester County1714= Parcel Assessed in New Castle County but located in Chester County1715= Parcel Assessed in Cecil County but located in Chester County2000= Parcel bisected by a ROW (Duplicate Pin)2040= Open Space (Duplicate Pin)2042= Common Area (Duplicate Pin)2043= Open Space owned by Homeowners Association2010= Condominium (Duplicate Pin) LUCC-10= Banks, Savings&LoanC-20= Gas StationC-30= Restaurants, Stores (Retail)C-35= Condominium StoresC-40= Motels, HotelsC-41= Nursing HomesC-50= Shopping CentersC-60= Office Bldgs/Laboratory/LibraryC-65= Office CondoC-67= Office Condo Common LawC-70= Commercial Garage/Shop/Car DealersC-80= WarehouseC-81= Storage TanksC-90= Entertainment, RecreationC-91= Recreation (Private)C-92= Mobile Home Parks (4+)C-93= Burial Grounds/MausoleumC-94= AirportsC-95= Private SchoolsC-96= Commercial OBY onlyE-10= ChurchesE-11= CemetariesE-12= Service ConnectedE-13= Chester County PropertyE-20= SchoolsE-30= Public UtilitiesE-40= RailroadsE-50= Hospitals, etcE-60= StateE-61= State ParksE-62= FederalE-63= FederalE-70= Local Government (Townships & Boroughs)E-71= Local Government ParksE-80= Non-Profit OrganizationsE-90= Fire CompaniesF-10= Farm 10-19.99 AcresF-20= Farm 20-79.99 AcresF-40= Farm 80 Acres and overM-10= Heavy IndustrialM-20= Light IndustrialM-25= Light Industrial CondominiumM-30= Quarry/LandfillN-01= Not assessed in Chester CountyR-10= Single Family/CabinR-20= Two FamilyR-30= Multi Family/Dorms/SingleR-40= Apartments (4-19 Units)R-50= CodominiumR-55= Town House (Common Law Condo)R-60= Dwelling W/Comm Use Primary RR-61= Dwelling W/Comm Use Primary CR-70= Mobile HomeR-80= Barns, Stables, Pools, Misc BldgR-90= Apartment Complex (20 or more units)R-95= Common Elements (Not Open Space)T-10= Trailers and Mobile HomesU-03= Public UtilitiesU-04= RailroadsV-10= Vacant Land ResidentialV-11= Vacant Land CommercialV-12= Open SpaceV-13= Road Beds, Right of Way, Access WayV-14= Basins, Drainage ControlV-35= Condo Store/Vacant Common ElementV-50= Condo/Vacant Common ElementV-55= Condo Common Law/Common AreaV-65= Condo Office/Vacant Common ElementV-67= Condo Common Law Office/Common AreaClassA= ApartmentC= CommercialE= ExemptF= FarmI= IndustrialR= ResidentialU= Utility

SchDist1= Avon Grove2= Coatesville3= Downingtown4= Kennett Consolidated5= Octorara6= Owen J. Roberts7= Oxford8= Phoenixville9= Twin Valley10= Unionville Chaddsford11= West Chester12= Great Valley13= Tredyffrin-Easttown14= Springford

This service depicts National Park Service tract and boundary data that was created by the Land Resources Division. NPS Director's Order #25 states: "Land status maps will be prepared to identify the ownership of the lands within the authorized boundaries of the park unit. These maps, showing ownership and acreage, are the 'official record' of the acreage of Federal and non-federal lands within the park boundaries. While these maps are the official record of the lands and acreage within the unit's authorized boundaries, they are not of survey quality and not intended to be used for survey purposes." As such this data is intended for use as a tool for GIS analysis. It is in no way intended for engineering or legal purposes. The data accuracy is checked against best available sources which may be dated and vary by location. NPS assumes no liability for use of this data. The boundary polygons represent the current legislated boundary of a given NPS unit. NPS does not necessarily have full fee ownership or hold another interest (easement, right of way, etc...) in all parcels contained within this boundary. Equivalently NPS may own or have an interest in parcels outside the legislated boundary of a given unit. In order to obtain complete information about current NPS interests both inside and outside a unit’s legislated boundary tract level polygons are also created by NPS Land Resources Division and should be used in conjunction with this boundary data. To download this data directly from the NPS go to https://irma.nps.gov Property ownership data is compiled from deeds, plats, surveys, and other source data. These are not engineering quality drawings and should be used for administrative purposes only. The National Park Service (NPS) shall not be held liable for improper or incorrect use of the data described and/or contained herein. These data and related graphics are not legal documents and are not intended to be used as such. The information contained in these data is dynamic and may change over time. The data are not better than the original sources from which they were derived. It is the responsibility of the data user to use the data appropriately and consistent within the limitations of geospatial data in general and these data in particular. The related graphics are intended to aid the data user in acquiring relevant data; it is not appropriate to use the related graphics as data. The National Park Service gives no warranty, expressed or implied, as to the accuracy, reliability, or completeness of these data. It is strongly recommended that these data are directly acquired from an NPS server and not indirectly through other sources which may have changed the data in some way. Although these data have been processed successfully on a computer system at the National Park Service, no warranty expressed or implied is made regarding the utility of the data on another system or for general or scientific purposes, nor shall the act of distribution constitute any such warranty. This disclaimer applies both to individual use of the data and aggregate use with other data.