Facebook
TwitterThis 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.
Facebook
TwitterThis polyline feature class represents the arc features that will define the boundaries of BLM Land Use Planning Area (LUPA) anticipated, in-progress, existing and historic polygons. Their attributes serve to store feature level metadata information for the polygon boundaries, as well as document the origin and characteristics of each arc.
Facebook
TwitterThis data has been collected by the U.S. Bureau of Land Management (BLM) in New Mexico at the New Mexico State Office. The initial data source is the statewide Public Land Survey System (PLSS) coverage for the state of New Mexico, generated at the BLM New Mexico State Office. Additional data was onscreen-digitized from BLM Cadastral Survey Plats and Master Title Plats, or tablet-digitized from 1:24,000 paper maps. This revision reflects boundary adjustments made in the Albuquerque area to more accurately reflect boundaries as depicted on USGS 1:24,000 topographic maps. Note for Shapefiles: Shapefiles have been created from coverages using the "Export Coverage to Shapefile" function in ArcGIS 8.3. All occurrences of "#" and "-" in INFO item names are replaced with an underscore character. This includes COVER# and COVER-ID, which become "COVER_" and "COVER_ID". Additionally, the Shapefile format only allows 10 characters in item names, so long item names are truncated. To avoid duplicate names, the items are truncated and assigned consecutive numbers. For example, in a coverage called CITY_STREET the items "CITY_STREET#" and "CITY_STREET-ID" become "CITY_STRE" and "CITY_STR_1" .
Facebook
TwitterThis 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.
Facebook
TwitterThis dataset is refreshed on a weekly basis from the datasets the team works on daily.Last update date: 20 November 2025.National Highways Operational Highway Boundary (RedLine) maps out the land belonging to the highway for the whole Strategic Road Network (SRN). It comprises two layers; one being the an outline and another showing the registration status / category of land of land that makes up the boundary. Due to the process involved in creating junctions with local highway authority (LHA) roads, land in this dataset may represent LHA highway (owned by National Highways but the responsibility of the LHA to maintain). Surplus land or land held for future projects does not form part of this dataset.The highway boundary is derived from:Ordnance Survey Mastermap Topography,HM Land Registry National Polygon Service (National Highway titles only), andplots researched and digitised during the course of the RedLine Boundary Project.The boundary is split into categories describing the decisions made for particular plots of land. These categories are as follows:Auto-RedLine category is for plots created from an automated process using Ordnance Survey MasterMap Topography as a base. Land is not registered under National Highways' name. For example, but not limited to, unregistered ‘ancient’ highway vested in Highways England, or bridge carrying highways over a rail line.NH Title within RedLine category is for plots created from Land Registry Cadastral parcels whose proprietor is National Highways or a predecessor. Land in this category is within the highway boundary (audited) or meets a certain threshold by the algorithm.NH Title outside RedLine category is for plots created in the same way as above but these areas are thought to be outside the highway boundary. Where the Confidence is Low, land in this category is yet to be audited. Where the Confidence is High, land in this category has been reviewed and audited as outside our operational boundary.National Highways (Technician) Data category is for plots created by National Highways, digitised land parcels relating to highway land that is not registered, not yet registered or un-registerable.Road in Tunnel category, created using tunnel outlines from Ordnance Survey MasterMap Topography data. These represent tunnels on Highways England’s network. Land is not registered under National Highways' name, but land above the tunnel may be in National Highways’ title. Please refer to the definitive land ownership records held at HM Land Registry.The process attribute details how the decision was made for the particular plot of land. These are as follows:Automated category denotes data produced by an automated process. These areas are yet to be audited by the company.Audited category denotes data that has been audited by the company.Technician Data (Awaiting Audit) category denotes data that was created by National Highways but is yet to be audited and confirmed as final.The confidence attribute details how confident you can be in the decision. This attribute is derived from both the decisions made during the building of the underlying automated dataset as well as whether the section has been researched and/or audited by National Highways staff. These are as follows:High category denotes land that has a high probability of being within the RedLine boundary. These areas typically are audited or are features that are close to or on the highway.Moderate category denotes land that is likely to be within the highway boundary but is subject to change once the area has been audited.Low category denotes land that is less likely to be within the highway boundary. These plots typically represent Highways England registered land that the automated process has marked as outside the highway boundary.Please note that this dataset is indicative only. For queries about this dataset please contact the GIS and Research Team.
Facebook
TwitterOpen Government Licence 3.0http://www.nationalarchives.gov.uk/doc/open-government-licence/version/3/
License information was derived automatically
Otherwise known as Land Registry Index polygons, these polygons are shapes that show the position and indicative extent of a registered property.
Facebook
TwitterWorld land boundaries (disputed borders and treaty demarcation lines etc) at 1:10 million scale.
Made with Natural Earth. Free vector and raster map data @ naturalearthdata.com.
Facebook
TwitterMIT Licensehttps://opensource.org/licenses/MIT
License information was derived automatically
This layer is the US/Canada international boundary, which extends on land and through the Great Lakes.
Facebook
TwitterData licence Germany – Attribution – Version 2.0https://www.govdata.de/dl-de/by-2-0
License information was derived automatically
In the inventory data of the land register, plots, uses and buildings are displayed and described. Additional point information of the property cadastre includes information on the point type, demarcation and position accuracy. The plot boundaries shown are based on data from the property cadastre. These differ according to origin, accuracy and trustworthiness. The data with its contents are therefore not suitable for a calculation of dimensions, in particular of boundary dimensions or boundary distances. The joint presentation of the parcel boundaries together with other map contents (e.g. aerial image/DOP) cannot be used to infer the actual legal situation on site. The presentation of data from the real estate register, in particular the parcel boundaries, is not considered official evidence, but merely has an informative character.
Facebook
TwitterU.S. Government Workshttps://www.usa.gov/government-works
License information was derived automatically
Improving the quality of water discharged from agricultural watersheds requires comprehensive and adaptive approaches for planning and implementing conservation practices. These measures will need to consider landscape hydrology, distributions of soil types, land cover, and crop distributions in an integrated manner. The two most consistent challenges to these efforts will be consistency and reliability of data, and the capacity to translate conservation planning from watershed to farm and field scales. The translation of scale is required because, while conservation practices can be planned based on a watershed scale framework, they must be implemented by landowners in specific fields and riparian sites that are under private ownership. To support these goals, it has been necessary to develop planning approaches, high-resolution spatial datasets, and conservation practice assessment tools that will allow the agricultural and conservation communities to characterize and mitigate these challenges. The field boundary dataset represents a spatial framework for assembling and maintaining geospatial data to support conservation planning at the scale where conservation practices are implemented. This field boundaries dataset has been assembled to support field-scale agricultural conservation planning using the USDA/ARS Agricultural Conservation Planning Framework (ACPF). The original data used to create this database are the pre-2008 Farm Bill FSA common land unit (CLU) datasets. A portion of metadata found herein pertains to the USDA FSA CLU. The remaining information has been developed to reflect the repurposing of the data in its aggregated form. It is important to note that all USDA programmatic and ownership information that was associated with the original data have been removed. Beyond that, these data has been extensively edited to reflect crop-specific land use consistent with 2015 land cover as derived from 2015 NASS Crop Data Layer datasets and 2015 aerial photography, and no longer reflects discrete ownership patterns. Resources in this dataset:Resource Title: Agricultural land use by field: Minnesota 2010-2019. File Name: MN_ACPFfields2019.zipResource Description: This field boundaries dataset has been assembled to support field-scale agricultural conservation planning using the USDA/ARS Agricultural Conservation Planning Framework (ACPF).Resource Software Recommended: ArcGIS,url: https://www.esri.com/en-us/home Resource Title: Minnesota Field Boundaries 2019. File Name: MN_ACPF_fieldBoundaries_2019.pdfResource Description: Minnesota Field Boundaries 2019Resource Title: Minnesota ACPF Crop History 2010-2019. File Name: MN_ACPFfields_CropHistory2010_2019.pdfResource Description: Minnesota ACPF Crop History 2010-2019Resource Title: Minnesota ACPF Land Use 2014-2019. File Name: MN_ACPFfields_LandUse2014_2019.pdfResource Description: Minnesota ACPF Land Use 2014-2019
Facebook
TwitterDOB_LAND_POLY: This theme shows the polygon representation of Bureau of Land Management Districts for Oregon and Washington up to the coastline and including the off-shore islands within the district boundaries.
Facebook
TwitterU.S. Government Workshttps://www.usa.gov/government-works
License information was derived automatically
This polygon feature class represents the spatial extent and boundaries for in-progress BLM Land Use Planning Areas (LUPAs). Land Use Planning Areas are geographic areas within which the BLM will make decisions during a land use planning effort. "In Progress" Planning Area Boundaries are created during the planning process and do not have a Record of Decision.
Facebook
TwitterCC0 1.0 Universal Public Domain Dedicationhttps://creativecommons.org/publicdomain/zero/1.0/
License information was derived automatically
UMBC Forest Plot boundaries in Google Earth KMZ format. The two 250m x 250m plots, at Herbert Run and The Knoll, are outlined in red.
Facebook
TwitterAustralia's Land Borders is a product within the Foundation Spatial Data Framework (FSDF) suite of datasets. It is endorsed by the ANZLIC - the Spatial Information Council and the Intergovernmental Committee on Surveying and Mapping (ICSM) as a nationally consistent and topologically correct representation of the land borders published by the Australian states and territories.
The purpose of this product is to provide: (i) a building block which enables development of other national datasets; (ii) integration with other geospatial frameworks in support of data analysis; and (iii) visualisation of these borders as cartographic depiction on a map. Although this dataset depicts land borders, it is not nor does it suggests to be a legal definition of these borders. Therefore it cannot and must not be used for those use-cases pertaining to legal context.
This product is constructed by Geoscience Australia (GA), on behalf of the ICSM, from authoritative open data published by the land mapping agencies in their respective Australian state and territory jurisdictions. Construction of a nationally consistent dataset required harmonisation and mediation of data issues at abutting land borders. In order to make informed and consistent determinations, other datasets were used as visual aid in determining which elements of published jurisdictional data to promote into the national product. These datasets include, but are not restricted to: (i) PSMA Australia's commercial products such as the cadastral (property) boundaries (CadLite) and Geocoded National Address File (GNAF); (ii) Esri's World Imagery and Imagery with Labels base maps; and (iii) Geoscience Australia's GEODATA TOPO 250K Series 3. Where practical, Land Borders do not cross cadastral boundaries and are logically consistent with addressing data in GNAF.
It is important to reaffirm that although third-party commercial datasets are used for validation, which is within remit of the licence agreement between PSMA and GA, no commercially licenced data has been promoted into the product. Australian Land Borders are constructed exclusively from published open data originating from state, territory and federal agencies.
This foundation dataset consists of edges (polylines) representing mediated segments of state and/or territory borders, connected at the nodes and terminated at the coastline defined as the Mean High Water Mark (MHWM) tidal boundary. These polylines are attributed to convey information about provenance of the source. It is envisaged that land borders will be topologically interoperable with the future national coastline dataset/s, currently being built through the ICSM coastline capture collaboration program. Topological interoperability will enable closure of land mass polygon, permitting spatial analysis operations such as vector overly, intersect, or raster map algebra. In addition to polylines, the product incorporates a number of well-known survey-monumented corners which have historical and cultural significance associated with the place name.
This foundation dataset is constructed from the best-available data, as published by relevant custodian in state and territory jurisdiction. It should be noted that some custodians - in particular the Northern Territory and New South Wales - have opted out or to rely on data from abutting jurisdiction as an agreed portrayal of their border. Accuracy and precision of land borders as depicted by spatial objects (features) may vary according to custodian specifications, although there is topological coherence across all the objects within this integrated product. The guaranteed minimum nominal scale for all use-cases, applying to complete spatial coverage of this product, is 1:25 000. In some areas the accuracy is much better and maybe approaching cadastre survey specification, however, this is an artefact of data assembly from disparate sources, rather than the product design. As the principle, no data was generalised or spatially degraded in the process of constructing this product.
Some use-cases for this product are: general digital and web map-making applications; a reference dataset to use for cartographic generalisation for a smaller-scale map applications; constraining geometric objects for revision and updates to the Mesh Blocks, the building blocks for the larger regions of the Australian Statistical Geography Standard (ASGS) framework; rapid resolution of cross-border data issues to enable construction and visual display of a common operating picture, etc.
This foundation dataset will be maintained at irregular intervals, for example if a state or territory jurisdiction decides to publish or republish their land borders. If there is a new version of this dataset, past version will be archived and information about the changes will be made available in the change log.
Facebook
TwitterClick to downloadClick for metadataService URL: https://gis.dnr.wa.gov/site3/rest/services/Public_Boundaries/WADNR_PUBLIC_Cadastre_OpenData/FeatureServer/10Official Washington State boundary
Facebook
TwitterThis product is a multi-variate data compilation that reconciles the variation scales of these multiple measurements from varies resources, merges and maps them into a comprehensive description of the near-surface atmospheric properties together with the land surface property variations on diurnal-to-decadal time scales. Many of these data products, especially those based on surface measurements, are spatially and/or temporally sparse or incomplete in coverage, so procedures were developed to fill missing values. The data product is comprised of a sequence of daily global files, where quantities are mapped into 1.0-degree equivalent equal-area grid, with time sampling is reported at daily or 3-hourly intervals. The time period overlap among the products covers 10 years from 1998 to 2007.
Facebook
TwitterThis polyline feature class represents the arc features that will define the boundaries of the Bureau of Land Management (BLM) Eastern States (ES) Land Use Planning Areas (LUPA) polygons. Land Use Planning Areas are geographic areas within which the BLM makes decisions during land use planning efforts.
Facebook
TwitterAttribution 4.0 (CC BY 4.0)https://creativecommons.org/licenses/by/4.0/
License information was derived automatically
An area encompassing all the National Forest System lands administered by an administrative unit. The area encompasses private lands, other governmental agency lands, and may contain National Forest System lands within the proclaimed boundaries of another administrative unit. All National Forest System lands fall within one and only one Administrative Forest Area. Click this link for full metadata description: MetadataThis record was taken from the USDA Enterprise Data Inventory that feeds into the https://data.gov catalog. Data for this record includes the following resources: ISO-19139 metadata ArcGIS Hub Dataset ArcGIS GeoService OGC WMS CSV Shapefile GeoJSON KML For complete information, please visit https://data.gov.
Facebook
TwitterStatistics on vehicular throughput at different land boundary control points of the Customs and Excise Department
Facebook
TwitterTable with boundary categories and characteristics of each plot and abundance data of all plants (%).
General description see mother table: (https://doi.org/10.4228/zalf-ebfq-0075); Related datasets are listed in the metadata element 'Related Identifier'. Dataset version 1.0
Facebook
TwitterThis 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.