Data DictionaryThe Allparcels data set is a thematic layer depicting past, present and future tax year real property parcel boundaries within Snohomish County, Washington based on the legal descriptions contained in the assessment roll. Parcels in this data set are defined as real property entities that can be valued for the purpose of collecting taxes. Parcels include, but are not limited to land, buildings on leased land, mobile homes and condominium units. Parcels may overlap. Parcels such as condominium units and mobile homes that may occupy a single polygon are represented as non-planar features (regions) of the same geographic extent. The Parcels data set does not depict legal ownership boundaries nor does it represent legal building lots. Snohomish County does not maintain parcels for the complete geographic coverage of the county. There is no parcel fabric in much of the eastern mountainous area. This data set is not designed to be used in connection with tabular attribute files. Its sole purpose is for historical tracking of changes in the parcel geometry. For current parcel geometry and tabular attributes, see the Parcels data set.

The Canadian County Parcel Data Public View is a set of geospatial features representing the surface ownership of property in fee simple for property tax purposes as required by 68 O.S. § 2821 and other related data used to produce the parcels such as subdivision boundaries and subdivision lots. The data is created from source documentation filed with the Canadian County Clerk's Office including deeds, easements, and plats. Other data sources such as filed Certified Corner Records filed with the State of Oklahoma or highway plans produced by the Department of Transportation may be used to adjust parcel boundaries. Single legal descriptions may be split up into two or more parcels if the description crosses the boundaries of multiple taxing jurisdictions or crosses quarter section boundaries. Accuracy of parcel data can vary considerably due to a combination of factors. Most parcels and subdivision legal descriptions reference a quarter section or quarter section corner. The accuracy of the quarter section corners is discussed with Canadian County's Public Land Survey System Data. Accuracy is further enhanced or degraded by the quality of the legal description used to create the feature. Generally, legal descriptions created from surveys will have higher accuracy the newer they were created due to improvements in the field of surveying. However, it can be difficult to determine the age of a legal description as descriptions are generally reused on subsequent deeds after the description was first created. Legal descriptions can occasionally contain updated bearings and distances and may denote the updates. The Assessor's Office uses the latest available legal description for creating parcels. Legal descriptions may lack specificity such as the use of "North" instead of a measured bearing or have missing parameters such as missing bearings for curved boundaries. In these cases, parcel data accuracy can be degraded. Further, if a legal description contains a specific landmark or boundary, sometimes called a "bound", the boundary is drawn to that point or landmark regardless of whether the bearing and/or distance accurately arrive at that point. For instance, if a legal description reads "...to the south line of the southeast quarter", the boundary is drawn to the south line of the quarter section even if the bearing and distance are short of or extend beyond that point. Because parcel data must be created for the entire county regardless of the accuracy of the descriptions used to create those parcels, parcels may need to be "stretched" or "squeezed" to make them fit together. When possible, the Assessor's Office relies on the most accurate legal descriptions to set the boundaries and then fits older boundaries to them. Due to the large number of variables, parcel data accuracy cannot be guaranteed nor can the level of accuracy be described for the entire dataset. While Canadian County makes every reasonable effort to make sure parcel data is accurate, this data cannot be used in place of a survey performed by an Oklahoma Licensed Professional Land Surveyor.ParcelDataExternal - Polygons representing surface fee simple title. This parcel data formatted and prepared for public use. Some fields may be blank to comply with 22 O.S. § 60.14 & 68 O.S. § 2899.1Attributes:Account (account): The unique identifier for parcel data generated by the appraisal software used by the Assessor's Office"A" Number (a_number): An integer assigned in approximate chronological order to represent each parcel divided per quarter sectionParcel ID (parcel_id): Number used to identify parcels geographically, see Parcel Data Export Appendix A for an in-depth explanation. This identifier is not unique for all parcelsParcel Size (parcel_size): Size of the parcels, must be used in conjunction with following units fieldParcel Size Units (parcel_size_units): Units for the size of the parcel. Can be "Acres" or "Lots" for parcels within subdivisions that are valued per lotOwner's Name (owners_name): Name of the surface owner of the property in fee simple on recordMailing Information (mail_info): Extra space for the owners name if needed or trustee namesMailing Information 2 (mail_info2): Forwarded mail or "In care of" mailing informationMailing Address (mail_address): Mailing address for the owner or forwarding mailing addressMailing City (mail_city): Mailing or postal cityMailing State (mail_state): Mailing state abbreviated to standard United States Postal Service codesMailing ZIP Code (mail_zip): Mailing ZIP code as determined by the United States Postal ServiceTax Area Code (tax_area): Integer numeric code representing an area in which all the taxing jurisdictions are the same. See Parcel Data Appendix B for a more detailed description of each tax areaTax Area Description (tax_area_desc): Character string code representing the tax area. See Parcel Data Appendix B for a more detailed description of each tax areaProperty Class (prop_class): The Assessor's Office classification of each parcel by rural (no city taxes) or urban (subject to city taxes) and exempt, residential, commercial, or agriculture. This classification system is for property appraisal purposes and does not reflect zoning classifications in use by municipalities. See Parcel Data Appendix B for a more detailed description of each property classificationLegal Description (legal): A highly abbreviated version of the legal description for each parcel. This legal description may not match the most recent legal description for any given property due to administrative divisions as described above, or changes made to the property by way of recorded instruments dividing smaller parcels from the original description. This description may NOT be used in place of a true legal descriptionSubdivision Code (subdiv_code): A numeric code representing a recorded subdivision plat which contains the parcel. This value will be "0" for any parcel not part of a recorded subdivision plat.Subdivision Name (subdiv_name): The name of the recorded subdivision plat abbreviated as needed to adapt to appraisal software field limitationsSubdivision Block Number (subdiv_block): Numeric field representing the block number of a parcel. This value will be "0" if the parcel is not in a recorded subdivision plat or if the plat did not contain block numbersSubdivision Lot Number (subdiv_lot): Numeric field representing the lot number of a parcel. This value will be "0" if the parcel is not in a recorded subdivision platTownship Number (township): Numeric field representing the Public Land Survey System tier or township the parcel is located in. All townships or tiers in Canadian County are north of the base line of the Indian Meridian.Range Number (range): Numeric field representing the Public Land Survey System range the parcel is located in. All Ranges in Canadian County are west of the Indian MeridianSection Number (section): Numeric field representing the Public Land Survey System section number the parcel is located inQuarter Section Code (quarter_sec): Numeric field with a code representing the quarter section a majority of the parcel is located in, 1 = Northeast Quarter, 2 = Northwest Quarter, 3 = Southwest Quarter, 4 = Southeast QuarterSitus Address (situs): Address of the property itself if it is knownSitus City (situs_city): Name of the city the parcel is actually located in (regardless of the postal city) or "Unincorporated" if the parcel is outside any incorporated city limitsSitus ZIP Code (situs_zip): ZIP Code as determined by the United States Postal Service for the property itself if it is knownLand Value (land_val): Appraised value of the land encompassed by the parcel as determined by the Assessor's OfficeImprovement Value (impr_val): Appraised value of the improvements (house, commercial building, etc.) on the property as determined by the Assessor's OfficeManufactured Home Value (mh_val): Appraised value of any manufactured homes on the property and owned by the same owner of the land as determined by the Assessor's OfficeTotal Value (total_val): Total appraised value for the property as determined by the Assessor's OfficeTotal Capped Value (cap_val): The capped value as required by Article X, Section 8B of the Oklahoma ConstitutionTotal Assessed Value (total_assess): The capped value multiplied by the assessment ratio of Canadian County, which is 12% of the capped valueHomestead Exempt Amount (hs_ex_amount): The amount exempt from the assessed value if a homestead exemption is in placeOther Exempt Value (other_ex_amount): The amount exempt from the assessed value if other exemptions are in placeTaxable Value (taxable_val): The amount taxes are calculated on which is the total assessed value minus all exemptionsSubdivisions - Polygons representing a plat or subdivision filed with the County Clerk of Canadian County. Subdivision boundaries may be revised by vacations of the plat or subdivision or by replatting a portion or all of a subdivision. Therefore, subdivision boundaries may not match the boundaries as shown on the originally filed plat.Attributes:Subdivision Name (subdivision_name): The name of the plat or subdivisionSubdivision Number (subdivision_number): An ID for each subdivision created as a portion of the parcel ID discussed in Parcel Data Export Appendix APlat Book Number (book): The book number for the recorded documentPlat Book Page Number (page): The page number for the recorded documentRecorded Acres (acres): The number of acres within the subdivision if knownRecorded Date (recorded_date): The date the document creating the subdivision was recordedDocument URL (clerk_url): URL to download a copy of the document recorded by the Canadian County Clerk's OfficeBlocks - Polygons derived from subdivision lots representing the blocks

A current-year-only universe of Cook County parcels with attached geographic, governmental, and spatial data. When working with Parcel Index Numbers (PINs) make sure to zero-pad them to 14 digits. Some datasets may lose leading zeros for PINs when downloaded. Additional notes:Non-taxing district data is attached via spatial join (st_contains) to each parcel's centroid. Tax district data (school district, park district, municipality, etc.) are attached by a parcel's assigned tax code. Centroids are based on Cook County parcel shapefiles. Older properties may be missing coordinates and thus also missing attached spatial data (usually they are missing a parcel boundary in the shapefile). Newer properties may be missing a mailing or property address, as they need to be assigned one by the postal service. This dataset contains data for the current tax year, which may not yet be complete or final. Assessed values for any given year are subject to change until review and certification of values by the Cook County Board of Review, though there are a few rare circumstances where values may change for the current or past years after that. Rowcount for a given year is final once the Assessor has certified the assessment roll all townships. Data will be updated monthly. Depending on the time of year, some third-party and internal data will be missing for the most recent year. Assessments mailed this year represent values from last year, so this isn't an issue. By the time the Data Department models values for this year, those data will have populated. Current property class codes, their levels of assessment, and descriptions can be found on the Assessor's website. Note that class codes details can change across time. Due to discrepancies between the systems used by the Assessor and Clerk's offices, tax_district_code is not currently up-to-date in this table. For more information on the sourcing of attached data and the preparation of this dataset, see the Assessor's Standard Operating Procedures for Open Data on GitHub. Read about the Assessor's 2025 Open Data Refresh.

Parcels and property data maintained and provided by Lee County Property Appraiser are converted to points. Property attribute data joined to parcel GIS layer by Lee County Government GIS. This dataset is generally used in spatial analysis.Process description: Parcel polygons, condominium points and property data provided by the Lee County Property Appraiser are processed by Lee County's GIS Department using the following steps:Join property data to parcel polygons Join property data to condo pointsConvert parcel polygons to points using ESRI's ArcGIS tool "Feature to Point" and designate the "Source" field "P".Load Condominium points into this layer and designate the "Source" field "C". Add X/Y coordinates in Florida State Plane West, NAD 83, feet using the "Add X/Y" tool.Projected coordinate system name: NAD_1983_StatePlane_Florida_West_FIPS_0902_FeetGeographic coordinate system name: GCS_North_American_1983

 Name
 Type
 Length
 Description


 STRAP
 String
 25
 17-digit Property ID (Section, Township, Range, Area, Block, Lot)


 BLOCK
 String
 10
 5-digit portion of STRAP (positions 9-13)


 LOT
 String
 8
 Last 4-digits of STRAP


 FOLIOID
 Double
 8
 Unique Property ID


 MAINTDATE
 Date
 8
 Date LeePA staff updated record


 MAINTWHO
 String
 20
 LeePA staff who updated record


 UPDATED
 Date
 8
 Data compilation date


 HIDE_STRAP
 String
 1
 Confidential parcel ownership


 TRSPARCEL
 String
 17
 Parcel ID sorted by Township, Range & Section


 DORCODE
 String
 2
 Department of Revenue. See https://leepa.org/Docs/Codes/DOR_Code_List.pdf


 CONDOTYPE
 String
 1
 Type of condominium: C (commercial) or R (residential)


 UNITOFMEAS
 String
 2
 Type of Unit of Measure (ex: AC=acre, LT=lot, FF=frontage in feet)


 NUMUNITS
 Double
 8
 Number of Land Units (units defined in UNITOFMEAS)


 FRONTAGE
 Integer
 4
 Road Frontage in Feet


 DEPTH
 Integer
 4
 Property Depth in Feet


 GISACRES
 Double
 8
 Total Computed Acres from GIS


 TAXINGDIST
 String
 3
 Taxing District of Property


 TAXDISTDES
 String
 60
 Taxing District Description


 FIREDIST
 String
 3
 Fire District of Property


 FIREDISTDE
 String
 60
 Fire District Description


 ZONING
 String
 10
 Zoning of Property


 ZONINGAREA
 String
 3
 Governing Area for Zoning


 LANDUSECOD
 SmallInteger
 2
 Land Use Code


 LANDUSEDES
 String
 60
 Land Use Description


 LANDISON
 String
 5
 BAY,CANAL,CREEK,GULF,LAKE,RIVER & GOLF


 SITEADDR
 String
 55
 Lee County Addressing/E911


 SITENUMBER
 String
 10
 Property Location - Street Number


 SITESTREET
 String
 40
 Street Name


 SITEUNIT
 String
 5
 Unit Number


 SITECITY
 String
 20
 City


 SITEZIP
 String
 5
 Zip Code


 JUST
 Double
 8
 Market Value


 ASSESSED
 Double
 8
 Building Value + Land Value


 TAXABLE
 Double
 8
 Taxable Value


 LAND
 Double
 8
 Land Value


 BUILDING
 Double
 8
 Building Value


 LXFV
 Double
 8
 Land Extra Feature Value


 BXFV
 Double
 8
 Building Extra Feature value


 NEWBUILT
 Double
 8
 New Construction Value


 AGAMOUNT
 Double
 8
 Agriculture Exemption Value


 DISAMOUNT
 Double
 8
 Disability Exemption Value


 HISTAMOUNT
 Double
 8
 Historical Exemption Value


 HSTDAMOUNT
 Double
 8
 Homestead Exemption Value


 SNRAMOUNT
 Double
 8
 Senior Exemption Value


 WHLYAMOUNT
 Double
 8
 Wholly Exemption Value


 WIDAMOUNT
 Double
 8
 Widow Exemption Value


 WIDRAMOUNT
 Double
 8
 Widower Exemption Value


 BLDGCOUNT
 SmallInteger
 2
 Total Number of Buildings on Parcel


 MINBUILTY
 SmallInteger
 2
 Oldest Building Built


 MAXBUILTY
 SmallInteger
 2
 Newest Building Built


 TOTALAREA
 Double
 8
 Total Building Area


 HEATEDAREA
 Double
 8
 Total Heated Area


 MAXSTORIES
 Double
 8
 Tallest Building on Parcel


 BEDROOMS
 Integer
 4
 Total Number of Bedrooms


 BATHROOMS
 Double
 8
 Total Number of Bathrooms / Not For Comm


 GARAGE
 String
 1
 Garage on Property 'Y'


 CARPORT
 String
 1
 Carport on Property 'Y'


 POOL
 String
 1
 Pool on Property 'Y'


 BOATDOCK
 String
 1
 Boat Dock on Property 'Y'


 SEAWALL
 String
 1
 Sea Wall on Property 'Y'


 NBLDGCOUNT
 SmallInteger
 2
 Total Number of New Buildings on ParcelTotal Number of New Buildings on Parcel


 NMINBUILTY
 SmallInteger
 2
 Oldest New Building Built


 NMAXBUILTY
 SmallInteger
 2
 Newest New Building Built


 NTOTALAREA
 Double
 8
 Total New Building Area


 NHEATEDARE
 Double
 8
 Total New Heated Area


 NMAXSTORIE
 Double
 8
 Tallest New Building on Parcel


 NBEDROOMS
 Integer
 4
 Total Number of New Bedrooms


 NBATHROOMS
 Double
 8
 Total Number of New Bathrooms/Not For Comm


 NGARAGE
 String
 1
 New Garage on Property 'Y'


 NCARPORT
 String
 1
 New Carport on Property 'Y'


 NPOOL
 String
 1
 New Pool on Property 'Y'


 NBOATDOCK
 String
 1
 New Boat Dock on Property 'Y'


 NSEAWALL
 String
 1
 New Sea Wall on Property 'Y'


 O_NAME
 String
 30
 Owner Name


 O_OTHERS
 String
 120
 Other Owners


 O_CAREOF
 String
 30
 In Care Of Line


 O_ADDR1
 String
 30
 Owner Mailing Address Line 1


 O_ADDR2
 String
 30
 Owner Mailing Address Line 2


 O_CITY
 String
 30
 Owner Mailing City


 O_STATE
 String
 2
 Owner Mailing State


 O_ZIP
 String
 9
 Owner Mailing Zip


 O_COUNTRY
 String
 30
 Owner Mailing Country


 S_1DATE
 Date
 8
 Most Current Sale Date > $100.00


 S_1AMOUNT
 Double
 8
 Sale Amount


 S_1VI
 String
 1
 Sale Vacant or Improved


 S_1TC
 String
 2
 Sale Transaction Code


 S_1TOC
 String
 2
 Sale Transaction Override Code


 S_1OR_NUM
 String
 13
 Original Record (Lee County Clerk)


 S_2DATE
 Date
 8
 Previous Sale Date > $100.00


 S_2AMOUNT
 Double
 8
 Sale Amount


 S_2VI
 String
 1
 Sale Vacant or Improved


 S_2TC
 String
 2
 Sale Transaction Code


 S_2TOC
 String
 2
 Sale Transaction Override Code


 S_2OR_NUM
 String
 13
 Original Record (Lee County Clerk)


 S_3DATE
 Date
 8
 Next Previous Sale Date > $100.00


 S_3AMOUNT
 Double
 8
 Sale Amount


 S_3VI
 String
 1
 Sale Vacant or Improved


 S_3TC
 String
 2
 Sale Transaction Code


 S_3TOC
 String
 2
 Sale Transaction Override Code


 S_3OR_NUM
 String
 13
 Original Record (Lee County Clerk)


 S_4DATE
 Date
 8
 Next Previous Sale Date > $100.00


 S_4AMOUNT
 Double
 8
 Sale Amount


 S_4VI
 String
 1
 Sale Vacant or Improved


 S_4TC
 String
 2
 Sale Transaction Code


 S_4TOC
 String
 2
 Sale Transaction Override Code


 S_4OR_NUM
 String
 13

Download In State Plane Projection Here.

The 2017 Parcel Fabric Data is a copy of the Lake County Chief Assessor's Office spatial dataset, consisting of separate layers which represent the boundaries for Tax Parcels, Lots, Units, Subs, Condos, Rights of Way, and Encumbrance parcels, along with points, lines, and PLSS townships for reference, which have all been captured for the 2017 Tax Year.

This data is spatial in nature and does not include extensive fields of attributes to which each layer may be associated. This data is provided for use to individuals or entities with an understanding of Esri's ArcMap (specifically the Parcel Fabric), and those with access to ArcMap, which is necessary to view or manipulate the data.

Casual users can find the standalone Tax Parcel Boundary Data above and Parcel Attribute Data here.

Update Frequency: Yearly

AT_2004_BACO

   File Geodatabase Feature Class


   Thumbnail Not Available

   Tags

   Socio-economic resources, Information, Social Institutions, Hierarchy, Territory, BES, Parcel, Property, Property View, A&T, Database, Assessors, Taxation




   Summary


   Serves as a basis for performing various analyses based on parcel data.


   Description


   Assessments & Taxation (A&T) Database from MD Property View 2004 for Baltimore County. The A&T Database contains parcel data from the State Department of Assessments and Taxation; it incorporates parcel ownership and address information, parcel valuation information and basic information about the land and structure(s) associated with a given parcel. These data form the basis for the 2004 Database, which also includes selected Computer Assisted Mass Appraisal (CAMA) characteristics, text descriptions to make parcel code field data more readily accessible and logical True/False fields which identify parcels with certain characteristics. Documentation for A&T, including a thorough definition for all attributes is enclosed. Complete Property View documentation can be found at http://www.mdp.state.md.us/data/index.htm under the "Technical Background" tab.


   It should be noted that the A&T Database consists of points and not parcel boundaries. For those areas where parcel polygon data exists the A&T Database can be joined using the ACCTID or a concatenation of the BLOCK and LOT fields, whichever is appropriate. (Spaces may have to be excluded when concatenating the BLOCK and LOT fields).


   A cursory review of the 2004 version of the A&T Database indicates that it has more accurate data when compared with the 2003 version, particularly with respect to dwelling types. However, for a given record it is not uncommon for numerous fields to be missing attributes. Based on previous version of the A&T Database it is also not unlikely that some of the information is inaccurate. This layer was edited to remove points that did not have a valid location because they failed to geocode. There were 5870 such points. A listing of the deleted points is in the table with the suffix "DeletedRecords."


   Credits


   Maryland Department of Planning


   Use limitations


   BES use only.


   Extent



   West -76.897802  East -76.335214 

   North 39.726520  South 39.192552 




   Scale Range

   There is no scale range for this item.

An area depicting ownership parcels of the surface estate. Each surface ownership parcel is tied to a particular legal transaction. The same individual or organization may currently own many parcels that may or may not have been acquired through the same legal transaction. Therefore, they are captured as separate entities rather than merged together. This is in contrast to Basic Ownership, in which the surface ownership parcels having the same owner are merged together. Basic Ownership provides the general user with the Forest Service versus non-Forest Service view of land ownership within National Forest boundaries. Surface Ownership provides the land status user with a current snapshot of ownership within National Forest boundaries. Metadata

AT_2004_HOWA

   File Geodatabase Feature Class


   Thumbnail Not Available

   Tags

   Socio-economic resources, Information, Social Institutions, Hierarchy, Territory, BES, Parcel, Property, Property View, A&T, Database, Assessors, Taxation




   Summary


   Serves as a basis for performing various analyses based on parcel data.


   Description


   Assessments & Taxation (A&T) Database from MD Property View 2004 for Howard County. The A&T Database contains parcel data from the State Department of Assessments and Taxation; it incorporates parcel ownership and address information, parcel valuation information and basic information about the land and structure(s) associated with a given parcel. These data form the basis for the 2004 Database, which also includes selected Computer Assisted Mass Appraisal (CAMA) characteristics, text descriptions to make parcel code field data more readily accessible and logical True/False fields which identify parcels with certain characteristics. Documentation for A&T, including a thorough definition for all attributes is enclosed. Complete Property View documentation can be found at http://www.mdp.state.md.us/data/index.htm under the "Technical Background" tab.


   It should be noted that the A&T Database consists of points and not parcel boundaries. For those areas where parcel polygon data exists the A&T Database can be joined using the ACCTID or a concatenation of the BLOCK and LOT fields, whichever is appropriate. (Spaces may have to be excluded when concatenating the BLOCK and LOT fields).


   A cursory review of the 2004 version of the A&T Database indicates that it has more accurate data when compared with the 2003 version, particularly with respect to dwelling types. However, for a given record it is not uncommon for numerous fields to be missing attributes. Based on previous version of the A&T Database it is also not unlikely that some of the information is inaccurate. This layer was edited to remove points that did not have a valid location because they failed to geocode. There were 1160 such points. A listing of the deleted points is in the table with the suffix "DeletedRecords."


   Credits


   Maryland Department of Planning


   Use limitations


   BES use only.


   Extent



   West -77.186932  East -76.699458 

   North 39.373967  South 39.099693 




   Scale Range

   There is no scale range for this item.

Cook County 10-digit parcels with attached distances to various spatial features. When working with 10-digit Parcel Index Numbers (PINs) make sure to zero-pad them to 10 digits. Some datasets may lose leading zeros for PINs when downloaded. 10-digit PINs do not identify individual condominium units. Additional notes:Centroids are based on Cook County parcel shapefiles. Older properties may be missing coordinates and thus also missing attached spatial data (usually they are missing a parcel boundary in the shapefile). Attached spatial data does NOT all go back to 2000. It is only available for more recent years, primarily those after 2012. This dataset contains data for the current tax year, which may not yet be complete or final. Assessed values for any given year are subject to change until review and certification of values by the Cook County Board of Review, though there are a few rare circumstances where values may change for the current or past years after that. Rowcount for a given year is final once the Assessor has certified the assessment roll all townships. Data will be updated annually as new parcel shapefiles are made available.For more information on the sourcing of attached data and the preparation of this dataset, see the Assessor's Standard Operating Procedures for Open Data on GitHub. Read about the Assessor's 2025 Open Data Refresh.

Description: Parcels represent taxable pieces of property. A parcel is created by the San Diego County Assessor/Recorder/County Clerk (ARCC) to identify a specific portion of real property that is taxed at a certain rate for a certain owner. Tax parcels are typically the same as a legally subdivided lot but are not necessessarily so. For example, a single owner may own a legally subdivided piece of property but there may be two or more tax parcels covering that property. Legal subdivisions are shown in the LOTS layer.Parcels are keyed to the Assessor Parcel Number (APN) and the parcel polygon identifier (PARCELID).The SanGIS parcel layers are “stacked” parcels. That means that for any piece of ground there may be multiple parcels. For example, a condominium building in downtown San Diego may have 200 individual condos. Each condo is a separate taxable parcel. All 200 parcels will be associated with the same physical lot on the ground. When the SanGIS parcel layer is created each individual condo has a polygon representing the physical location of the parent parcel. In this example there will be 200 polygons all stacked on top of each other that represent the taxable parcels and each polygon will have the same physical characteristics (shape, size, area, location) – they are, essentially, copies of each other. However, other associated information (owner, document numbers, etc) will be different for each. In this case, each condo unit will have its own parcel number and there will be no single parcel representing the lot on the ground. Besides condominiums there are two other cases where you will see stacked parcels – possessory interest and mobile homes. Possessory interests have Assessor Parcel Numbers (APNs) that start with 76x. A possessory interest (or PI) parcel represents a taxable interest in the underlying, or parent, parcel but not necessarily ownership. For instance, a private company may have an arrangement with a University to operate a business on campus – a coffee shop or gift shop for example. The private business is taxable and is assigned a 76x APN and that APN is associated with the parent parcel which is owned by the University. Possessory interests do not represent ownership on the parcel, only a taxable interest in the underlying parent parcel.Mobile home parcel APNs start with 77x. In a manner similar to the possessory interests, mobile home owners own their home (coach) but not the underlying property on which the house sits. The actual mobile home is a separate taxable parcel associated with the mobile home park parent parcel. These taxable parcels all have the same polygon as the underlying parent parcel and will show as stacked parcels as well.This dataset contains parcels as shown on the Assessor Parcel Maps (APM). However, parcels shown in this layer may lag that of the official APM by a number of weeks due to how SanGIS is notified of the newly created parcel and the timing of publication of the parcel layer.This dataset contains the parcel polygon and associated parcel information provided by the County ARCC in thier Master Property Record (MPR file) and Parcel Assessment Record (PAR file). In addition to the MPR and PAR data assigned by ARCC, SanGIS may add situs address information if it has been provided by the addressing authority in which the parcel is situated. The situs address information provided by SanGIS may not be the same as the SITUS address data in the MPR.This dataset contains site address information along with owner names and addresses, and other property information. Key fields in this dataset include:Land use information provided in the NUCLEUS_USE_CD field (225 types with a 3-digit domain). The ASR_LANDUSE field is an older version of this field but comprises more generalized land uses (91 types). Generalized land use zoning information is provided in the NUCLEUS_ZONE_CD field. The ASR_ZONE field is an older version of this field. Land use zoning is generalized comprising 9 zone types. This can provide a useful approximation for parcels that are outside of the San Diego City and County zoning jurisdictions.Please note that land use and zoning fields are not regularly maintained by the Assessor's Office and should only be used as an approximate guide. Updates are only made when there is new construction, or a change in ownership. They are not updated when the County and Local Cities update their zoning data or when permit changes to properties are completed. Please refer to city and County official zoning datasets for official zoning information, and to SANDAG for more current land use data.

​

Copyright Text: SanGIS using legal recorded data provided by the County Recorders and Assessor's Office. See the County ARCC website at https://arcc.sdcounty.ca.gov/Pages/default.aspx for more information about tax parcels

This Esri File GeoDatabase (FGDB) contains digital tax parcel data for Maine Organized Towns and includes the following: Parcels (feature layer); Parcels_ADB (table); and GEOCODES (table).Within Maine, real property data is maintained by the government organization responsible for assessing and collecting property tax for a given location. Organized towns and townships maintain authoritative data for their communities and may voluntarily submit these data to the Maine GeoLibrary Parcel Project. Maine Parcels Organized Towns and Maine Parcels Organized Towns ADB are the product of these voluntary submissions. Communities provide updates to the Maine GeoLibrary on a non-regular basis, which affects the currency of Maine GeoLibrary parcels data; some data are more than ten years old. Another resource for real property transaction data is the County Registry of Deeds, although organized town data should very closely match registry information, except in the case of in-process property conveyance transactions.In Unorganized Territories (defined as those regions of the state without a local government that assesses real property and collects property tax), the Maine Revenue Service is the authoritative source for parcel data. Maine Parcels Unorganized Territory is the authoritative GIS data layer for the Unorganized Territories. However, it must always be used with auxiliary data obtained from the online resources of the Maine Revenue Service to compile up-to-date parcel ownership information.Property maps are a fundamental base for many municipal activities. Although GIS parcel data cannot replace detailed ground surveys, the data can assist municipal officials with functions such as accurate property tax assessment, planning and zoning. Towns can link maps to an assessor's database and display local information, while town officials can show taxpayers how proposed development or changes in municipal services and regulations may affect the community. In many towns, parcel data also helps to provide public notices, plan bus routes, and carry out other municipal services.This dataset contains municipality-submitted parcel data along with previously developed parcel data acquired through the Municipal Grants Project supported by the Maine Library of Geographic Information (MLGI). Grant recipient parcel data submissions were guided by standards presented to the MLGI Board on May 21, 2005,outlined in "Standards for Digital Parcel Files".GEOCODES is a table that lists standardized names and unique identifiers for Maine minor civil divisions and reservations, which represents the first official Standard Geographic Code endorsed and adopted by the Governor of Maine, on July 1, 1971.

We constructed a time-series spatial dataset of parcel boundaries for the period 1962-2005, in roughly 4-year intervals, by digitizing historical plat maps for Dane County and combining them with the 2005 GIS digital parcel dataset. The resulting datasets enable the consistent tracking of subdivision and development for all parcels over a given time frame. The process involved 1) dissolving and merging the 2005 digital Dane County parcel dataset based on contiguity and name, 2) further merging 2005 parcels based on the hard copy 2005 Plat book, and then 3) the reverse chronological merging of parcels to reconstruct previous years, at 4-year intervals, based on historical plat books. Additional land use information such as 1) whether a structure was actually constructed (using the companion digitized aerial photo dataset), 2) cover crop, and 3) permeable surface area, can be added to these datasets at a later date.

AT_2004_ANNE File Geodatabase Feature Class Thumbnail Not Available Tags Socio-economic resources, Information, Social Institutions, Hierarchy, Territory, BES, Parcel, Property, Property View, A&T, Database, Assessors, Taxation Summary Serves as a basis for performing various analyses based on parcel data. Description Assessments & Taxation (A&T) Database from MD Property View 2004 for Anne Arundel County. The A&T Database contains parcel data from the State Department of Assessments and Taxation; it incorporates parcel ownership and address information, parcel valuation information and basic information about the land and structure(s) associated with a given parcel. These data form the basis for the 2004 Database, which also includes selected Computer Assisted Mass Appraisal (CAMA) characteristics, text descriptions to make parcel code field data more readily accessible and logical True/False fields which identify parcels with certain characteristics. Documentation for A&T, including a thorough definition for all attributes is enclosed. Complete Property View documentation can be found at http://www.mdp.state.md.us/data/index.htm under the "Technical Background" tab. It should be noted that the A&T Database consists of points and not parcel boundaries. For those areas where parcel polygon data exists the A&T Database can be joined using the ACCTID or a concatenation of the BLOCK and LOT fields, whichever is appropriate. (Spaces may have to be excluded when concatenating the BLOCK and LOT fields). A cursory review of the 2004 version of the A&T Database indicates that it has more accurate data when compared with the 2003 version, particularly with respect to dwelling types. However, for a given record it is not uncommon for numerous fields to be missing attributes. Based on previous version of the A&T Database it is also not unlikely that some of the information is inaccurate. This layer was edited to remove points that did not have a valid location because they failed to geocode. There were 897 such points. A listing of the deleted points is in the table with the suffix "DeletedRecords." Credits Maryland Department of Planning Use limitations BES use only. Extent West -76.838738 East -76.395283 North 39.238726 South 38.708588 Scale Range There is no scale range for this item.

Parcels represent taxable pieces of property. A parcel is created by the San Diego County Assessor/Recorder/County Clerk (ARCC) to identify a specific portion of real property that is taxed at a certain rate for a certain owner. Tax parcels are typically the same as a legally subdivided lot but are not necessessarily so. For example, a single owner may own a legally subdivided piece of property but there may be two or more tax parcels covering that property. Legal subdivisions are shown in the LOTS layer.Parcels are keyed to the Assessor Parcel Number (APN) and the parcel polygon identifier (PARCELID).The SanGIS parcel layers are “stacked” parcels. That means that for any piece of ground there may be multiple parcels. For example, a condominium building in downtown San Diego may have 200 individual condos. Each condo is a separate taxable parcel. All 200 parcels will be associated with the same physical lot on the ground. When the SanGIS parcel layer is created each individual condo has a polygon representing the physical location of the parent parcel. In this example there will be 200 polygons all stacked on top of each other that represent the taxable parcels and each polygon will have the same physical characteristics (shape, size, area, location) – they are, essentially, copies of each other. However, other associated information (owner, document numbers, etc) will be different for each. In this case, each condo unit will have its own parcel number and there will be no single parcel representing the lot on the ground. Besides condominiums there are two other cases where you will see stacked parcels – possessory interest and mobile homes. Possessory interests have Assessor Parcel Numbers (APNs) that start with 76x. A possessory interest (or PI) parcel represents a taxable interest in the underlying, or parent, parcel but not necessarily ownership. For instance, a private company may have an arrangement with a University to operate a business on campus – a coffee shop or gift shop for example. The private business is taxable and is assinged a 76x APN and that APN is associated with the parent parcel which is owned by the University. Possessory intestests do not represent ownership on the parcel, only a taxable interest in the underlying parent parcel.Mobile home parcel APNs start with 77x. In a manner similar to the possessory interests, mobile home owners own their home (coach) but not the underlying property on which the house sits. The actual mobile home is a separate taxable parcel associated with the mobile home park parent parcel. These taxable parcels all have the same polygon as the underlying parent parcel and will show as stacked parcels as well.This dataset contains parcels as shown on the Assessor Parcel Maps (APM). However, parcels shown in this layer may lag that of the official APM by a number of weeks due to how SanGIS is notified of the newly created parcel and the timing of publication of the parcel layer.This dataset contains the parcel polygon and associated parcel information provided by the County ARCC in thier Master Property Record (MPR file) and Parcel Assessment Record (PAR file). In addition to the MPR and PAR data assigned by ARCC, SanGIS may add situs address information if it has been provided by the addressing authority in which the parcel is situated. The situs address information provided by SanGIS may not be the same as the SITUS address data in the MPR.This dataset contains site address information along with owner names and addresses, and other property information. Key fields in this dataset include:Land use information provided in the NUCLEUS_USE_CD field (225 types with a 3-digit domain). The ASR_LANDUSE field is an older version of this field but comprises more generalized land uses (91 types). Generalized land use zoning information is provided in the NUCLEUS_ZONE_CD field. The ASR_ZONE field is an older version of this field. Land use zoning is generalized comprising 9 zone types. This can provide a useful approximation for parcels that are outside of the San Diego City and County zoning jurisdictions.Please note that land use and zoning fields are not regularly maintained by the Assessor's Office and should only be used as an approximate guide. Updates are only made when there is new construction, or a change in ownership. They are not updated when the County and Local Cities update their zoning data or when permit changes to properties are completed. Please refer to city and County official zoning datasets for official zoning information, and to SANDAG for more current land use data. NOTE: If the name of this layer includes "_NORTH", "_SOUTH", or "_EAST" it represents a subset of the entire San Diego County Parcel Base. That is, the "_NORTH" layer includes only parcels generally in the Northwestern portion of the County. The "_SOUTH" layer includes parcels in the Southwestern portion. And the "_EAST" layer includes parcels in the approximate Eastern half of the County.

Abstract

Historical tax assessment data for all U.S. states, the U.S. Virgin Islands, Guam, and Washington, D.C. Each table represents a previous edition of CoreLogic's tax assessment data.

The CoreLogic Smart Data Platform (SDP) Historical Property data was formerly known as the CoreLogic Tax History data. The CoreLogic SDP Historical Property data is an enhanced version of the CoreLogic Tax History data. The CoreLogic SDP Historical Property data contains almost all of the variables that were included in the CoreLogic Tax History data, as well as additional property-level characteristics.

Methodology

In the United States, parcel data is public record information that describes a division of land (also referred to as "property" or "real estate"). Each parcel is given a unique identifier called an Assessor’s Parcel Number or APN. The two principal types of records maintained by county government agencies for each parcel of land are deed and property tax records. When a real estate transaction takes place (e.g. a change in ownership), a property deed must be signed by both the buyer and seller. The deed will then be filed with the County Recorder’s offices, sometimes called the County Clerk-Recorder or other similar title. Property tax records are maintained by County Tax Assessor’s offices; they show the amount of taxes assessed on a parcel and include a detailed description of any structures or buildings on the parcel, including year built, square footages, building type, amenities like a pool, etc. There is not a uniform format for storing parcel data across the thousands of counties and county equivalents in the U.S.; laws and regulations governing real estate/property sales vary by state. Counties and county equivalents also have inconsistent approaches to archiving historical parcel data.

To fill researchers’ needs for uniform parcel data, CoreLogic collects, cleans, and normalizes public records that they collect from U.S. County Assessor and Recorder offices. CoreLogic augments this data with information gathered from other public and non-public sources (e.g., loan issuers, real estate agents, landlords, etc.). The Stanford Libraries has purchased bulk extracts from CoreLogic’s parcel data, including mortgage, owner transfer, pre-foreclosure, and historical and contemporary tax assessment data. Data is bundled into pipe-delimited text files, which are uploaded to Data Farm (Redivis) for preview, extraction and analysis.

For more information about how the data was prepared for Redivis, please see CoreLogic 2024 GitLab.

Usage

Each table contains an archived snapshot of the property data, roughly corresponding to the following assessed years:

• Historical Property 1 = 2022-2023
• Historical Property 2 = 2021-2022
• Historical Property 3 = 2020-2021
• Historical Property 4 = 2019-2020
• Historical Property 5 = 2018-2019
• Historical Property 6 = 2017-2018
• Historical Property 7 = 2016-2017
• Historical Property 8 = 2015-2016
• Historical Property 9 = 2014-2015
• Historical Property 10 = 2013-2014
• Historical Property 11 = 2012-2013
• Historical Property 12 = 2011-2012
• Historical Property 13 = 2010-2011
• Historical Property 14 = 2009-2010
• Historical Property 15 = 2008-2009

%3C!-- --%3E

Users can check theASSESSED_YEAR variable to confirm the year of assessment.

Roughly speaking, the tables use the following census geographies:

• 2020 Census Tract: Historical Property 1-2
• 2010 Census Tract: Historical Property 3 – 12
• 2000 Census Tract: Historical Property 13 – 15

%3C!-- --%3E

The Property, Mortgage, Owner Transfer, Historical Property and Pre-Foreclosure data can be linked on the CLIP, a unique identification number assigned to each property.

For more information about included variables, please see **core_logic_sdp_historical_property_data_dictionary_2024.txt **and Historical Property_v3.xlsx.

Under Supporting files, users can also find record counts per FIPS code for each edition of the Historical Property data.

For more information about how the CoreLogic Smart Data Platform: Historical Property data compares to legacy data, please see core_logic_legacy_content_mapping.pdf.

Bulk Data Access

Data access is required to view this section.

Historically, the earliest Bakersfield “urban” subdivisions were not called tracts. The downtown area was subdivided into blocks and lots. Early citywide maps show the city blocks numbered from 1 to over 700. Some blocks were designated by letters rather than numbers. Each block was further subdivided into numbered lots. Thereafter housing subdivisions were called tracts and initially were named (example; Lowell Addition). Many of these “Named” tracts were also subdivided into blocks and lots. The earliest rural land subdivisions are the Sales Map Lands of J. B. Haggin and the Sales Map Lands of the Kern County l Land Company. The legal description of most modern lots is comprised of some combination of the fields: Document Type, Map Number, Phase and Lot Number. A “Block” field should be added for old parcels whose legal description is comprised of tract, block and lot (or just block and lot). The legal description fields for most of the older parcels are not populated at this time. PARCEL FEATURE CLASS ATTRIBUTES Document Type (Domain)Aliquot – subdivision of a public land survey system section i.e. the northeast quarter of the south east quarter of the southwest quarter of section 10 of T28S, R27ETract MapParcel Map Lot Line Adjustment (ex. LLA17-0684)Parcel Map Waiver (ex. PMW17-0398)Parcel Merger (ex. LM17-0695)Map Number Tracts – Old named tracts and numbered tracts, currently into the 7000’sParcel maps – numbered, currently into the 12,000’sMinor land subdivisions (lot line adjustments, parcel map waivers, parcel mergers) format YY-NNNN, where YY is a 2-digit designation of the year and NNNN is a zero-filled number (county files is reversed, ex. NN – YY)Phase Applicable to tract and parcel maps only; i.e. 1, 2, 3 etc. or A, B, C etc. Lot Number i.e. 1, 2, 3 etc. or A, B, C etc. Quality (Domain)In reference to the geometric and positional accuracy of the parcel features. All COGO’d parcels are considered “Excellent” quality User Flag This field is for temporary data storage. However the following user flag values provide information about how the parcel features originally built or subsequently edited: CAD CONVERSION - parcels were developed from georeferenced CAD data. Quality is considered excellent. COGO - parcels were first developed employing COGO editing tools. Quality is considered excellent REBUILT - parcels were originally Valleywide GIS features that were rebuilt using COGO and other editing tools. Quality is considered excellent except parcels that were rebuilt where only assessor maps were available. SHIFTED - original parcels were considered geometrically adequate but required a slight positional shift. Whole blocks of contiguous lots were shifted together. Quality is considered good. Class(Domain)This field provides an opportunity to classify lots for specific purposes. The Private road lot class was created so these lots could be neglected when exporting parcels for the Community Maps Project. Landscape lot Private road lot School lot Sump lot Water Well lot Additional classes could be developed. For the vast majority of parcels the class field is not populated. Address The street address of a lot can be populated if the address point feature class objects have already been created and populated by the GIS Analyst at Community Development. Where there are multiple addresses on a parcel, this data is captured on the Address Point feature class. Assessor Parcel Number (APN) and Assessor Tax Numbers (ATN)The most important parcel layer attributes are the APN and ATN values that are assigned by the Kern County Assessor. An 8 digit APN is assigned to a property that has a specific geometry as defined by a legal description. If any new change occurs such as a lot line adjustment, then the geometry of the parcel(s) are changed and the APN’s for the affected properties are dropped and are never re-assigned. New unique APN’s are assigned to the affected properties and remain as long as the legal description of the geometry does not change. It usually takes at least a few months after a tract is recorded and the parcel feature class objects are developed before the County assigns APN’s to those parcels. The APN field is populated with “NEW” until such time as values are assigned. Parcel APNs can be acquired from the following sources: https://kernpublicworks.com/maps/parcel-maps/, Preliminary (January) and final (July) Kern County parcel GIS releases. Some Condominium common areas do not have an APN. The APN field is populated with “CONDOLOT”. These parcels are retained in order to preserve road right of ways. Compare City parcel layer features with County features to visualize why we retain these parcels.

See full Data Guide here. This layer includes polygon features that depict protected open space for towns of the Protected Open Space Mapping (POSM) project, which is administered by the Connecticut Department of Energy and Environmental Protection, Land Acquisition and Management. Only parcels that meet the criteria of protected open space as defined in the POSM project are in this layer. Protected open space is defined as: (1) Land or interest in land acquired for the permanent protection of natural features of the state's landscape or essential habitat for endangered or threatened species; or (2) Land or an interest in land acquired to permanently support and sustain non-facility-based outdoor recreation, forestry and fishery activities, or other wildlife or natural resource conservation or preservation activities. Includes protected open space data for the towns of Andover, Ansonia, Ashford, Avon, Beacon Falls, Canaan, Clinton, Berlin, Bethany, Bethel, Bethlehem, Bloomfield, Bridgewater, Bolton, Brookfield, Brooklyn, Canterbury, Canton, Chaplin, Cheshire, Colchester, Colebrook, Columbia, Cornwall, Coventry, Cromwell, Danbury, Derby, East Granby, East Haddam, East Hampton, East Hartford, East Windsor, Eastford, Ellington, Enfield, Essex, Farmington, Franklin, Glastonbury, Goshen, Granby, Griswold, Groton, Guilford, Haddam, Hampton, Hartford, Hebron, Kent, Killingworth, Lebanon, Ledyard, Lisbon, Litchfield, Madison, Manchester, Mansfield, Marlborough, Meriden, Middlebury, Middlefield, Middletown, Monroe, Montville, Morris, New Britain, New Canaan, New Fairfield, New Milford, New Hartford, Newington, Newtown, Norfolk, North, Norwich, Preston, Ridgefield, Shelton, Stonington, Oxford, Plainfield, Plainville, Pomfret, Portland, Prospect, Putnam, Redding, Rocky Hill, Roxbury, Salem, Salisbury, Scotland, Seymour, Sharon, Sherman, Simsbury, Somers, South Windsor, Southbury, Southington, Sprague, Sterling, Suffield, Thomaston, Thompson, Tolland, Torrington, Union, Vernon, Wallingford, Windham, Warren, Washington, Waterbury, Watertown, West Hartford, Westbrook, Weston, Wethersfield, Willington, Wilton, Windsor, Windsor Locks, Wolcott, Woodbridge, Woodbury, and Woodstock. Additional towns are added to this list as they are completed. The layer is based on information from various sources collected and compiled during the period from March 2005 through the present. These sources include but are not limited to municipal Assessor's records (the Assessor's database, hard copy maps and deeds) and existing digital parcel data. The layer represents conditions as of the date of research at each city or town hall. The Protected Open Space layer includes the parcel shape (geometry), a project-specific parcel ID based on the Town and Town Assessor's lot numbering system, and system-defined (automatically generated) fields. The Protected Open Space layer has an accompanying table containing more detailed information about each feature (parcel). This table is called Protected Open Space Dat, and can be joined to Protected Open Space in ArcMap using the parcel ID (PAR_ID) field. Detailed information in the Protected Open Space Data attribute table includes the Assessor's Map, Block and Lot numbers (the Assessor's parcel identification numbering system), the official name of the parcel (such as the park or forest name if it has one), address and owner information, the deed volume and page numbers, survey information, open space type, the unique parcel ID number (Par_ID), comments collected by researchers during city/town hall visits, and acreage. This layer does not include parcels that do not meet the definition of open space as defined above. Features are stored as polygons that represent the best available locational information, and are "best fit" to the land base available for each.

The Connecticut Department of Environmental Protection's (CTDEP) Permanently Protected Open Space Phase Mapping Project Phase 1 (Protected Open Space Phase1) layer includes permanently protected open space parcels in towns in Phase 1 that meet the CTDEP's definition for this project, the Permanently Protected Open Space Mapping (CT POSM) Project. The CTDEP defines permanently protected open space as (1) Land or interest in land acquired for the permanent protection of natural features of the state's landscape or essential habitat for endangered or threatened species; or (2) Land or an interest in land acquired to permanently support and sustain non facility-based outdoor recreations, forestry and fishery activities, or other wildlife or natural resource conservation or preservation activities.

Towns in Phase 1 of the CT POSM project are situated along the CT coast and portions of the Thames River and are the following: Branford, Bridgeport, Chester, Clinton, Darien, Deep River, East Haven, East Lyme, Essex, Fairfield, Greenwich, Groton, Guilford, Hamden, Ledyard, Lyme, Madison, Milford, Montville, New Haven, New London, North Branford, North Haven, Norwalk, Norwich, Old Lyme, Old Saybrook, Orange, Preston, Shelton, Stamford, Stonington, Stratford, Waterford, West Haven, Westbrook, Westport.

For the purposes of the project a number of categories or classifications of open space have also been created. These include: Land Trust, Land Trust with buidlings, Private, Private with buildings, Utility Company, Utility Company with buildings, Federal, State, Municipal, Municipal with buildings, Conservation easement, and non-DEP State land. The layer is based on information from various sources collected and compiled during the period from August 2002 trhough October 2003. These sources include municipal Assessor's records (the Assessor's database, hard copy maps and deeds) and existing digital parcel data. The layer represents conditions on the date of research at each city or town hall.

The Protected Open Space Phase1 layer includes the parcel shape (geometry), a project-specific parcel ID based on the Town and Town's Assessor lot numbering system, and system-defined (automatically generated) fields. In addition, the Protected_Open_Space_Phase1 layer has an accompanying table containing more detailed information about each parcel's collection, standardization and storage. This table is called Protected Open Space Phase1 Data and can be joined to Protected Open Space Phase1 in ArcMap using the parcel ID (PAR_ID) field. Detailed information includes the Assessor's Map, Block and Lot numbers (the Assessor's parcel identification numbering system), the official name of the parcel (such as the park or forest name if it has one), address and owner information, the deed volume and page numbers, survey information, open space type, the project-specific parcel ID number (Par_ID), comments collected by researchers during city/town hall visits, acreage collected during site reconaissance and the data source. This layer does not include parcels that do not meet the definition of open space as defined above. Features are stored as polygon feature type that represent the best available locational information, i.e. "best fit" to the land base available for each.

Phase 1 of the Protected Open Space Mapping (POSM) Project was accomplished by a contractor using only a querying process to identify open space. The contractor obtained assessor's data from the various towns and created programs to cull open space parcels strictly by query processes. We have found many errors and omissions in the data, but at this point in the project we cannot revisit all the coastal towns. Therefore, this data is being sent with a disclaimer for accuracy. You are welcome to use it but not to publish it. Please note that we do not include any water company parcels despite them being listed as part of our criteria because we must first obtain written clarification and clearance from the U.S. Department of Homeland Security.

We have since changed our data collection method for Phase 2 of this project. DEP staff now visit each town hall and thoroughly research the land records. The project is expected to be complete by 2010.

Connecticut Parcels for Protected Open Space Mapping is a polygon feature-based layer that includes basic parcel-level information for some towns in Connecticut. This 2009 parcel layer includes information provided by individual municipalities. These parcel data are incomplete and out of date. The accuracy, currency and completeness of the data reflect the content of the data at the time DEEP acquired the data from the individual municipalities. Attribute information is comprised of values such as town name and map lot block number. These data are not updated by CT DEEP and should only be used as a general reference. Critical decisions involving parcel-level information should be based on more recently acquired information from the respective municipalities. These parcels are not to be considered legal boundaries such as boundaries determined from certain classified survey maps or deed descriptions. Parcel boundaries shown in this layer are based on information from municipalities used for property tax purposes. Largely due to differences in horizontal accuracy among various data layers, do not expect these parcel boundaries to line up exactly with or be properly postioned relative to features shown on other layers available from CT DEEP such as scanned USGS topography quadrangle maps, roads, hydrography, town boundaries, and even orthophotograpy.

The data in the parcel layer was obtained from individual Connecticut municipalities. An effort was made to collect data once from each municipality. The data acquisition date for each set of municipally-supplied parcel data was not recorded and CT DEEP does not keep this information up-to-date. Consequently, these data are out-of-date, incomplete and do not reflect the current state of property ownership in these municipalities. These parcels are not to be considered legal boundaries such as boundaries determined from certain classified survey maps or deed descriptions. Parcel boundaries shown in this layer are based on information from municipalities used for property tax purposes. Parcel boundaries and attribute information have not been updated in this layer since the time the information was originally acquired by CT DEEP. For example, property boundaries are incorrect where subdivisions have occurred. Also, field attribute values are populated only if the information was supplied to CT DEEP. For example, parcels in some towns lack location (street name) information or possibly map lot block values. Therefore, field attributes are inconsistent, may include gaps, and do not represent complete sets of values among all towns. They should not be compared and analyzed across towns. It is emphasized that critical decisions involving parcel-level information be based on more recently obtained information from the respective municipalities. These data are only suitable for general reference purposes. Be cautious when using these data. Many Connecticut municipalities provide access to more up-to-date and more detailed property ownership information on the Internet. This dataset includes parcel information for the following towns: Andover, Ansonia, Ashford, Avon, Beacon Falls, Berlin, Bethany, Bethel, Bethlehem, Bloomfield, Bolton, Branford, Bridgewater, Brookfield, Brooklyn, Canaan, Canterbury, Canton, Chaplin, Cheshire, Chester, Clinton, Colchester, Colebrook, Columbia, Cornwall, Coventry, Cromwell, Danbury, Darien, Deep River, Derby, East Granby, East Haddam, East Hampton, East Hartford, East Lyme, East Windsor, Eastford, Ellington, Enfield, Essex, Farmington, Franklin, Glastonbury, Granby, Greenwich, Griswold, Groton, Guilford, Haddam, Hamden, Hartford, Hebron, Kent, Killingly, Killingworth, Lebanon, Ledyard, Lisbon, Litchfield, Lyme, Madison, Manchester, Mansfield, Marlborough, Meriden, Middlebury, Middlefield, Middletown, Milford, Monroe, Montville, Morris, New Britain, New Canaan, New Hartford, New Haven, New London, New Milford, Newington, Newtown, Norfolk, North Branford, North Canaan, North Haven, North Stonington, Norwalk, Norwich, Old Lyme, Old Saybrook, Orange, Oxford, Plainfield, Plainville, Plymouth, Pomfret, Portland, Preston, Prospect, Putnam, Redding, Rocky Hill, Roxbury, Salem, Salisbury, Scotland, Seymour, Sharon, Shelton, Sherman, Simsbury, Somers, South Windsor, Southbury, Southington, Sprague, Stamford, Sterling, Stonington, Stratford, Suffield, Thomaston, Tolland, Torrington, Union, Vernon, Voluntown, Wallingford, Warren, Washington, Waterbury, Waterford, Watertown, West Hartford, West Haven, Westbrook, Westport, Wethersfield, Willington, Wilton, Winchester, Windsor, Windsor Locks, Wolcott, Woodbridge, Woodbury, and Woodstock. For additional information on the Protected Open Space Mapping project, contact the Department of Energy and Environmental Protection, Division of Land Acquisition and Management at 860-424-3016.

A complete, historic universe of Cook County parcels with attached geographic, governmental, and spatial data. When working with Parcel Index Numbers (PINs) make sure to zero-pad them to 14 digits. Some datasets may lose leading zeros for PINs when downloaded. Additional notes:Data is attached via spatial join (st_contains) to each parcel's centroid. Centroids are based on Cook County parcel shapefiles. Older properties may be missing coordinates and thus also missing attached spatial data (usually they are missing a parcel boundary in the shapefile). Newer properties may be missing a mailing or property address, as they need to be assigned one by the postal service. Attached spatial data does NOT go all the way back to 1999. It is only available for more recent years, primarily those after 2012. The universe contains data for the current tax year, which may not be complete or final. PINs can still be added and removed to the universe up until the Board of Review closes appeals. Data will be updated monthly. Rowcount and characteristics for a given year are final once the Assessor has certified the assessment roll for all townships. Depending on the time of year, some third-party and internal data will be missing for the most recent year. Assessments mailed this year represent values from last year, so this isn't an issue. By the time the Data Department models values for this year, those data will have populated. Current property class codes, their levels of assessment, and descriptions can be found on the Assessor's website. Note that class codes details can change across time. Due to decrepencies between the systems used by the Assessor and Clerk's offices, tax_district_code is not currently up-to-date in this table. For more information on the sourcing of attached data and the preparation of this dataset, see the Assessor's data architecture repo on GitLab. Read about the Assessor's 2022 Open Data Refresh.

This ownership dataset utilizes a methodology that results in a federal ownership extent that matches the Federal Responsibility Areas (FRA) footprint from CAL FIRE's State Responsibility Areas for Fire Protection (SRA) data. FRA lands are snapped to county parcel data, thus federal ownership areas will also be snapped. Since SRA Fees were first implemented in 2011, CAL FIRE has devoted significant resources to improve the quality of SRA data. This includes comparing SRA data to data from other federal, state, and local agencies, an annual comparison to county assessor roll files, and a formal SRA review process that includes input from CAL FIRE Units. As a result, FRA lands provide a solid basis as the footprint for federal lands in California (except in the southeastern desert area). The methodology for federal lands involves: 1) snapping federal data sources to parcels; 2) clipping to the FRA footprint; 3) overlaying the federal data sources and using a hierarchy when sources overlap to resolve coding issues (BIA, UFW, NPS, USF, BLM, DOD, ACE, BOR); 4) utilizing an automated process to merge “unknown” FRA slivers with appropriate adjacent ownerships;5) a manual review of FRA areas not assigned a federal agency by this process. Non-Federal ownership information was obtained from the California Protected Areas Database (CPAD), was clipped to the non-FRA area, and an automated process was used to fill in some sliver-gaps that occurred between the federal and non-federal data. Southeastern Desert Area: CAL FIRE does not devote the same level of resources for maintaining SRA data in this region of the state, since we have no fire protection responsibility. This includes almost all of Imperial County, and the desert portions of Riverside, and San Bernardino Counties. In these areas, we used federal protection areas from the current version of the Direct Protection Areas (DPA) dataset. Due to the fact that there were draw-issues with the previous version of ownership, this version does NOT fill in the areas that are not assigned to one of the owner groups (it does not cover all lands in the state). Also unlike previous versions of the dataset, this version only defines ownership down to the agency level - it does not contain more specific property information (for example, which National Forest). The option for a more detailed future release remains, however, and due to the use of automated tools, could always be created without much additional effort.This dataset includes a representation to symbolize based on the Own_Group field using the standard color scheme utilized on DPA maps.For more details about data inputs, see the Lineage section of the metadata. For detailed notes on previous versions, see the Supplemental Information section of the metadata.This ownership dataset is derived from CAL FIRE's SRA dataset, and GreenInfo Network's California Protected Areas Database. CAL FIRE tracks lands owned by federal agencies as part of our efforts to maintain fire protection responsibility boundaries, captured as part of our State Responsiblity Areas (SRA) dataset. This effort draws on data provided by various federal agencies including USDA Forest Service, BLM, National Park Service, US Fish and Wildlife Service, and Bureau of Inidan Affairs. Since SRA lands are matched to county parcel data where appropriate, often federal land boundaries are also adjusted to match parcels, and may not always exactly match the source federal data. Federal lands from the SRA dataset are combined with ownership data for non-federal lands from CPAD, in order to capture lands owned by various state and local agencies, special districts, and conservation organizations. Data from CPAD are imported directly and not adjusted to match parcels or other features. However, CPAD features may be trimmed if they overlap federal lands from the SRA dataset. Areas without an ownership feature are ASSUMED to be private (but not included in the dataset as such). This service represents the latest release of the dataset by FRAP, and is updated twice a year when new versions are released.