Parcels and Land Ownership dataset current as of unknown. This data set consists of digital map files containing parcel-level cadastral information obtained from property descriptions. Cadastral features contained in the data set include real property boundary lines, rights-of-way boundaries, property dimensions.

The property cadastral boundaries include lot lines, property lines and their dimensions (lengths). Other related datasets can be found by filtering on the property keyword. Data currencyThis data in City systems is updated frequently in the normal course of business, however priorities and resources determine how fast a change in reality is reflected in the database. The extract on this website is updated weekly. Data accuracyMuch of the City's land base is created using survey accuracy however some features are not as precise.

This layer is derived from the Common Ownership Lots and represents property transactions as they’ve occurred since the implementation of the Vector Property Mapping program in September 2006. A property transaction entails new geometry (split/combination of Lot(s) or property type conversion (from Air Rights, Record, or Tax Lots to Condo lots). The layer contains locations and attributes of archived features (inactive lots – dead lots) and corresponds with Office of Tax and Revenue's Public Extract files (ITSPE). It occurs weekly for the current calendar year and geometry updated when a transaction occurs.

Property boundaries represent the extent of ownership of an address in line with NSW Valuer General for the purposes of address verification and rating. The spatial layer is derived from land parcel boundaries (cadastre) originally supplied by NSW Spatial Services who remain the source of cadastral information. See SiX mapsThis spatial layer has been significantly changed and maintained by City of Sydney Spatial Services. This layer is not survey accurate.Geoservice API disabled, but geojson and download permitted.

Provides locations and land boundaries / cadastre of each property within the Adelaide City Council area. Note only contains site designated as common property for Strata and community properties.

"Cadastral Area Boundary is a line layer belonging to Vicmap Property and consists of data representing Victoria's land parcels and properties and is used extensively in Geographic Information Systems (GIS) by the public and private sectors. More Information: https://www.data.vic.gov.au/data/dataset/cadastral-area-boundary-vicmap-property Author: Department of Environment and Primary Industries Owner: Department of Environment and Primary Industries"

This dataset combines Brisbane City Council property information with the Queensland Government Digital Cadastral Database (DCDB) in Brisbane City Council area.Land Parcels are the building blocks of Council properties. Land parcels (also called lots) are mapped and the title details shown on a Plan of Subdivision. The parcel is a graphical representation of surveyed boundaries together with identifiers such as Lot/Plan description and house numbers.The Digital Cadastral Database (DCDB) is the spatial representation of every current parcel of land in Queensland, and its legal Lot on Plan description and relevant attributes. It provides the map base for systems dealing with land related information. The DCDB is considered to be the point of truth for the graphical representation of property boundaries. It is not the point of truth for the legal property boundary or related attribute information, this will always be the plan of survey or the related titling information and administrative data sets.Warning. Downloading this entire dataset in shapefile format exceeds the current 2GB download limit set by ESRI. Information from ESRI has the following suggestions. Consider the following options: Output to a file geodatabase instead of a shapefile or Process the data in sections.

This dataset contains boundaries of individual parcels in Allegheny County, including the county block and lot number. As this is a very large dataset, you may wish to use our property information extractor (http://tools.wprdc.org/parcels-n-at/) to download filtered versions of this parcel dataset. The most authoritative source for this data is now the PASDA page (https://www.pasda.psu.edu/uci/DataSummary.aspx?dataset=1214), which includes links to historical versions of the shapefile representations of this data.

This dataset is designed to represent and identify the property boundaries in Lexington-Fayette County. The original dataset was created in late 1990's by a third party that converted existing paper maps to digital GIS files. The data has since been updated by georeferencing recorded plats for corrections and new additions. In cases where the plats do not appear accurate, aerial photos are utilized in attempt to properly locate the property lines. The only except for this process are changes to highway right-of-way in which calls are run from deeds. The geometry of this data is not of survey quality and should not be used for survey purposes. The data is intended for general reference purposes only.As part of the basemap data layers, the parcel boundary map layer is an integral part of the Lexington Fayette-Urban County Government Geographic Information System. Basemap data layers are accessed by personnel in most LFUCG divisions for basic applications such as viewing, querying, and map output production. More advanced user applications may focus on thematic mapping, summarization of data by geography, or planning purposes (including defining boundaries, managing assets and facilities, integrating attribute databases with geographic features, spatial analysis, and presentation output).

This dataset is available on Brisbane City Council’s open data website – data.brisbane.qld.gov.au. The site provides additional features for viewing and interacting with the data and for downloading the data in various formats.

This dataset combines Brisbane City Council property information with the Queensland Government Digital Cadastral Database (DCDB) in Brisbane City Council area.

Land Parcels are the building blocks of Council properties. Land parcels (also called lots) are mapped and the title details shown on a Plan of Subdivision. The parcel is a graphical representation of surveyed boundaries together with identifiers such as Lot/Plan description and house numbers.

The Digital Cadastral Database (DCDB) is the spatial representation of every current parcel of land in Queensland, and its legal Lot on Plan description and relevant attributes. It provides the map base for systems dealing with land related information. The DCDB is considered to be the point of truth for the graphical representation of property boundaries. It is not the point of truth for the legal property boundary or related attribute information, this will always be the plan of survey or the related titling information and administrative data sets.

Warning. Downloading this entire dataset in shapefile format exceeds the current 2GB download limit set by ESRI. Information from ESRI has the following suggestions. Consider the following options: Output to a file geodatabase instead of a shapefile or Process the data in sections.

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.

A resubdivision involves the adjustment of Arlington property boundaries and sometimes results in the creation of additional subset properties. This dataset contains all real estate properties created as the result of a resubdivision and can be associated with other Real Estate datasets by the RPC (RealEstatePropertyCode).

This dataset was updated April, 2024.This ownership dataset was generated primarily from CPAD data, which already tracks the majority of ownership information in California. CPAD is utilized without any snapping or clipping to FRA/SRA/LRA. CPAD has some important data gaps, so additional data sources are used to supplement the CPAD data. Currently this includes the most currently available data from BIA, DOD, and FWS. Additional sources may be added in subsequent versions. Decision rules were developed to identify priority layers in areas of overlap.Starting in 2022, the ownership dataset was compiled using a new methodology. Previous versions attempted to match federal ownership boundaries to the FRA footprint, and used a manual process for checking and tracking Federal ownership changes within the FRA, with CPAD ownership information only being used for SRA and LRA lands. The manual portion of that process was proving difficult to maintain, and the new method (described below) was developed in order to decrease the manual workload, and increase accountability by using an automated process by which any final ownership designation could be traced back to a specific dataset.The current process for compiling the data sources includes: Clipping input datasets to the California boundary Filtering the FWS data on the Primary Interest field to exclude lands that are managed by but not owned by FWS (ex: Leases, Easements, etc) Supplementing the BIA Pacific Region Surface Trust lands data with the Western Region portion of the LAR dataset which extends into California. Filtering the BIA data on the Trust Status field to exclude areas that represent mineral rights only. Filtering the CPAD data on the Ownership Level field to exclude areas that are Privately owned (ex: HOAs) In the case of overlap, sources were prioritized as follows: FWS > BIA > CPAD > DOD As an exception to the above, DOD lands on FRA which overlapped with CPAD lands that were incorrectly coded as non-Federal were treated as an override, such that the DOD designation could win out over CPAD.In addition to this ownership dataset, a supplemental _source dataset is available which designates the source that was used to determine the ownership in this dataset.Data Sources: GreenInfo Network's California Protected Areas Database (CPAD2023a). https://www.calands.org/cpad/; https://www.calands.org/wp-content/uploads/2023/06/CPAD-2023a-Database-Manual.pdf US Fish and Wildlife Service FWSInterest dataset (updated December, 2023). https://gis-fws.opendata.arcgis.com/datasets/9c49bd03b8dc4b9188a8c84062792cff_0/explore Department of Defense Military Bases dataset (updated September 2023) https://catalog.data.gov/dataset/military-bases Bureau of Indian Affairs, Pacific Region, Surface Trust and Pacific Region Office (PRO) land boundaries data (2023) via John Mosley John.Mosley@bia.gov Bureau of Indian Affairs, Land Area Representations (LAR) and BIA Regions datasets (updated Oct 2019) https://biamaps.doi.gov/bogs/datadownload.htmlData Gaps & Changes:Known gaps include several BOR, ACE and Navy lands which were not included in CPAD nor the DOD MIRTA dataset. Our hope for future versions is to refine the process by pulling in additional data sources to fill in some of those data gaps. Additionally, any feedback received about missing or inaccurate data can be taken back to the appropriate source data where appropriate, so fixes can occur in the source data, instead of just in this dataset.24_1: Input datasets this year included numerous changes since the previous version, particularly the CPAD and DOD inputs. Of particular note was the re-addition of Camp Pendleton to the DOD input dataset, which is reflected in this version of the ownership dataset. We were unable to obtain an updated input for tribral data, so the previous inputs was used for this version.23_1: A few discrepancies were discovered between data changes that occurred in CPAD when compared with parcel data. These issues will be taken to CPAD for clarification for future updates, but for ownership23_1 it reflects the data as it was coded in CPAD at the time. In addition, there was a change in the DOD input data between last year and this year, with the removal of Camp Pendleton. An inquiry was sent for clarification on this change, but for ownership23_1 it reflects the data per the DOD input dataset.22_1 : represents an initial version of ownership with a new methodology which was developed under a short timeframe. A comparison with previous versions of ownership highlighted the some data gaps with the current version. Some of these known gaps include several BOR, ACE and Navy lands which were not included in CPAD nor the DOD MIRTA dataset. Our hope for future versions is to refine the process by pulling in additional data sources to fill in some of those data gaps. In addition, any topological errors (like overlaps or gaps) that exist in the input datasets may thus carry over to the ownership dataset. Ideally, any feedback received about missing or inaccurate data can be taken back to the relevant source data where appropriate, so fixes can occur in the source data, instead of just in this dataset.

This dataset is available on Brisbane City Council’s open data website – data.brisbane.qld.gov.au. The site provides additional features for viewing and interacting with the data and for downloading the data in various formats.

This dataset combines Brisbane City Council property information with the Queensland Government Digital Cadastral Database (DCDB) to show property holdings in Brisbane City Council area.

A property holding is a Council-defined and managed information entity. Its boundaries are generally based on land parcels. A property holding may consist of one or multiple land parcels.

The Digital Cadastral Database (DCDB) is the spatial representation of every current parcel of land in Queensland, and its legal Lot on Plan description and relevant attributes. It provides the map base for systems dealing with land related information. The DCDB is considered to be the point of truth for the graphical representation of property boundaries. It is not the point of truth for the legal property boundary or related attribute information, this will always be the plan of survey or the related titling information and administrative data sets.

This details the boundaries of all properties within the City of Melbourne. A boundary is described as a division between adjacent political entities, tracts of private land, or geographic zones. Boundary lines may be imaginary lines, physical features that follow those lines, or the graphical representation of those lines on a map. Boundary lines between privately owned land parcels are usually called property lines.

Parcels and Land Ownership dataset current as of 1995. ParcelPoly-The data set is a polygon feature consisting of more than 93,000 polygons representing property boundaries. It was created to maintain land ownership..

This layer shows the boundaries of properties owned or leased by the Columbus Recreation and Parks Department (CRPD). Types of properties include community parks, conservation/natural areas, golf courses, neighborhood parks, and others.

This data is a GIS file that outlines the geographical area of all properties in the City of Toronto. While every attempt is made to keep this dataset up to date, it has been compiled over many years, from numerous records of varying age and reliability. As such, the resulting accuracy of the boundary mapping information renders it suitable for general planning purposes only and is not a substitute for a plan of survey. Column Definition + OBJECTID represents a unique identifier. It is not guaranteed to be consistent between data updates. + F_TYPE represents Feature Type. Can be one of the following values "COMMON", "CONDO", "CORRIDOR", "RESERVE" Feature Type Definition + Condo - A closed boundary that represents the extent of ownership by a Condominium Corporation. + Corridor - Describes a section of legal Right-of-Way. + Reserve - A unit of land of varying width (usually 0.3 metres (1 foot) wide) used to restrict access to private/public properties, such as access to adjoining public highways. + Common - A municipal parcel that is not designated as Corridor, Reserve or Condominium. A subdivision lot is a typical Common parcel.

Only active parcels are included in this dataset. This layer shows the latest parcel boundaries and owner information recorded in the city's property records. Since some parcels have more than one owner (like condos), this dataset connects each parcel shape (GPIN) to all its owners (PIN).Neighborhood Development Services (NDS) assigns zoning and addresses, then shares this information with the City Assessor's Office to be added to the property records system (CAMA).This file is not a legal document for any parcel. Any mistakes or missing information can be directed to the Assessor's Office to have them corrected.