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.

This is a MD iMAP hosted service layer. Find more information at http://imap.maryland.gov. This layer contains the boundaries and IDs of the Maryland tax maps produced by Maryland Department of Planning. Tax maps - also known as assessment maps - property maps or parcel maps - are a graphic representation of real property showing and defining individual property boundaries in relationship to contiguous real property. Last Updated: Feature Service Layer Link: http://geodata.md.gov/imap/rest/services/PlanningCadastre/MD_PropertyData/MapServer/2 ADDITIONAL LICENSE TERMS: The Spatial Data and the information therein (collectively "the Data") is provided "as is" without warranty of any kind either expressed implied or statutory. The user assumes the entire risk as to quality and performance of the Data. No guarantee of accuracy is granted nor is any responsibility for reliance thereon assumed. In no event shall the State of Maryland be liable for direct indirect incidental consequential or special damages of any kind. The State of Maryland does not accept liability for any damages or misrepresentation caused by inaccuracies in the Data or as a result to changes to the Data nor is there responsibility assumed to maintain the Data in any manner or form. The Data can be freely distributed as long as the metadata entry is not modified or deleted. Any data derived from the Data must acknowledge the State of Maryland in the metadata.

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.

Property lines mapped as parcel polygons within Langley Township. The data includes the following information: Folio, PID, and civic address of existing parcels Description The Township uses two survey systems. The first was 1859 District Lot system which still describes many properties near the Fraser River. The District Lot system was superseded in 1873 with the New Westminster Township Section system which covers the bulk of the municipality and is used to the present day. The cadastral data set originated as hand drawn township-section maps in imperial scales. The lot lines were compiled from historical community maps, registered legal plans surveyed with astronomic bearings and legal descriptions where no surveys exist.

In the late 1970’s the Township's maps were converted to metric scales and all dimension annotation was converted manually to metric. In 1982 parcels BC GAS manually digitized the hand drawn township-section maps and assembled them into a single continuous cadastral fabric encompassing the entire township. The lot line data was rubber sheeted to fit the higher accuracy mapping of neighbouring municipalities, no interior control points were used. In 1983 Langley Township obtains BC GAS Intergraph format lot line data and translated it into Terrasoft format for the Township's GIS.In 1986 the lot lines were converted to parcel polygons linked to BCAA folio numbers and Tempest. In 1987 map annotation was converted to digital. In 1999 the GIS data was converted from Terrasoft to AutoCAD Map format. In 2000 the digital base was again rubber sheeted with a township wide grid pattern of survey monuments used for control. In 2003 lot links were converted from BCAA folio numbers to Township property numbers. In 2004 GIS data is converted from AutoCAD Map format to Munsys Oracle format. In 2005 Langley Township adopts DIGITAL LEGAL SURVEY PLAN STANDARDS and new cadastral is entered directly from high accuracy UTM projected surveys. In 2009 GIS data was converted from Munsys Oracle format to ESRI ArcSDE format.

This parcel lines feature class represents the current city parcel lines within the City of Los Angeles. It shares topology with the Landbase Parcel_polygons feature class. The Mapping and Land Records Division of the Bureau of Engineering, Department of Public Works provides the most current geographic information of the public right of way, ownership and land record information. The legal boundaries are determined on the ground by license surveyors in the State of California, and by recorded documents from the Los Angeles County Recorder's office and the City Clerk's office of the City of Los Angeles. Parcel and ownership information are available on NavigateLA, a website hosted by the Bureau of Engineering, Department of Public Works.Associated information about the landbase parcel lines is entered into attributes. Principal attributes include:CV_LAYER: is the principal field that describes the various types of lines like street and freeway right-of-ways, tract, lots, government property and easements lines, private street lines, utility right-of-ways, and ownership lines. For a complete list of attribute values, please refer to Landbase_parcel_lines_data_dictionary.Landbase parcels lines layer was created in geographical information systems (GIS) software to display the location of parcel lots. The parcels lines layer is a feature class in the LACityLandbaseData.gdb Geodatabase dataset. The layer consists of spatial data as a line feature class and attribute data for the features. The lines are derived from the polygon feature class in the landbase parcels layer, and information about the lines is entered into attributes. The CV_LAYER field values describe the various types of lines. The right-of-way, row, line features consist of CV_LAYER = 6, CV_LAYER = 106, and portions of CV_LAYER = 1 where that line is both the city boundary and the parcel line. In some cases, a parcel line will share two different type descriptions. Refer to CV_LAYER field metadata for further explantion. Parcel information should only be added to the Landbase Parcels layer if documentation exists, such as a Deed or a Plan approved by the City Council. When seeking the definitive description of real property, consult the recorded Deed or Plan.List of Fields:ASSETIDCV_LAYER: This value is a number representing a different type of user-assigned layer. Each of the line segments in the landbase parcels lines are assigned one of the CV_LAYER numbers, representing a different type of line work, described below. In some cases, a parcel line will share two different type descriptions. Such as, a parcel line may have CV_LAYER = 1 City Boundary line, and it is a CV_LAYER = 8 Tract line. The Tract line description is used first, and the City Boundary line description is used second. When selecting City Boundary line using CV_LAYER = 1, then (special way to select data...). The right-of-way, row, line features consist of CV_LAYER = 6, CV_LAYER = 106, and portions of CV_LAYER = 1 where that line is both the city boundary and the parcel line. Values: • 50 - Lot cut linework. • 38 - Freeway ease as easement lines. • 108 - Tract lines that are private street lines. • 8 - Tract lines, Rancho lines, Freeway (Fwy), and Right of way lines. • 30 - Former city boundary lines; other city or county boundary line. • 34 - Overlap lines. • 6 - Right of way (R/W) sidelines. • 19 - LA City easement lines. • 21 - All governmental lines (Fee). • 37 - APN (BPP) lines shown on tax assessors map (PCL maps); but no new PIN is created for the parcels polygon feature. • 48 - Subdivision title anno shown for ownership purpose (lot cut). • 10 - Lot lines. • 68 - SBBM (San Bernardino Base Meridian) section lines. • 1 - Boundary lines (existing). • 110 - Lot lines that are private street lines. • 18 - All governmental easement lines (except LA City and State freeway ease right of way lines). • 106 - Fwy traveled roadway lines; Dash right of way lines; Railroad and transmission lines. • 0 - Cadastral format.SHAPE: Feature geometry.OBJECTID: Internal feature number.ID: A unique numeric identifier of the polygon. The ID value is the last part of the PIN field value.MAPSHEET: The alpha-numeric mapsheet number, which refers to a valid B-map or A-map number on the Cadastral tract index map. Values: • B, A, -5A - Any of these alpha-numeric combinations are used, whereas the underlined spaces are the numbers.

Please note that this dataset is not an official City of Toronto land use dataset. It was created for personal and academic use using City of Toronto Land Use Maps (2019) found on the City of Toronto Official Plan website at https://www.toronto.ca/city-government/planning-development/official-plan-guidelines/official-plan/official-plan-maps-copy, along with the City of Toronto parcel fabric (Property Boundaries) found at https://open.toronto.ca/dataset/property-boundaries/ and Statistics Canada Census Dissemination Blocks level boundary files (2016). The property boundaries used were dated November 11, 2021. Further detail about the City of Toronto's Official Plan, consolidation of the information presented in its online form, and considerations for its interpretation can be found at https://www.toronto.ca/city-government/planning-development/official-plan-guidelines/official-plan/ Data Creation Documentation and Procedures Software Used The spatial vector data were created using ArcGIS Pro 2.9.0 in December 2021. PDF File Conversions Using Adobe Acrobat Pro DC software, the following downloaded PDF map images were converted to TIF format. 9028-cp-official-plan-Map-14_LandUse_AODA.pdf 9042-cp-official-plan-Map-22_LandUse_AODA.pdf 9070-cp-official-plan-Map-20_LandUse_AODA.pdf 908a-cp-official-plan-Map-13_LandUse_AODA.pdf 978e-cp-official-plan-Map-17_LandUse_AODA.pdf 97cc-cp-official-plan-Map-15_LandUse_AODA.pdf 97d4-cp-official-plan-Map-23_LandUse_AODA.pdf 97f2-cp-official-plan-Map-19_LandUse_AODA.pdf 97fe-cp-official-plan-Map-18_LandUse_AODA.pdf 9811-cp-official-plan-Map-16_LandUse_AODA.pdf 982d-cp-official-plan-Map-21_LandUse_AODA.pdf Georeferencing and Reprojecting Data Files The original projection of the PDF maps is unknown but were most likely published using MTM Zone 10 EPSG 2019 as per many of the City of Toronto's many datasets. They could also have possibly been published in UTM Zone 17 EPSG 26917 The TIF images were georeferenced in ArcGIS Pro using this projection with very good results. The images were matched against the City of Toronto's Centreline dataset found here The resulting TIF files and their supporting spatial files include: TOLandUseMap13.tfwx TOLandUseMap13.tif TOLandUseMap13.tif.aux.xml TOLandUseMap13.tif.ovr TOLandUseMap14.tfwx TOLandUseMap14.tif TOLandUseMap14.tif.aux.xml TOLandUseMap14.tif.ovr TOLandUseMap15.tfwx TOLandUseMap15.tif TOLandUseMap15.tif.aux.xml TOLandUseMap15.tif.ovr TOLandUseMap16.tfwx TOLandUseMap16.tif TOLandUseMap16.tif.aux.xml TOLandUseMap16.tif.ovr TOLandUseMap17.tfwx TOLandUseMap17.tif TOLandUseMap17.tif.aux.xml TOLandUseMap17.tif.ovr TOLandUseMap18.tfwx TOLandUseMap18.tif TOLandUseMap18.tif.aux.xml TOLandUseMap18.tif.ovr TOLandUseMap19.tif TOLandUseMap19.tif.aux.xml TOLandUseMap19.tif.ovr TOLandUseMap20.tfwx TOLandUseMap20.tif TOLandUseMap20.tif.aux.xml TOLandUseMap20.tif.ovr TOLandUseMap21.tfwx TOLandUseMap21.tif TOLandUseMap21.tif.aux.xml TOLandUseMap21.tif.ovr TOLandUseMap22.tfwx TOLandUseMap22.tif TOLandUseMap22.tif.aux.xml TOLandUseMap22.tif.ovr TOLandUseMap23.tfwx TOLandUseMap23.tif TOLandUseMap23.tif.aux.xml TOLandUseMap23.tif.ov Ground control points were saved for all georeferenced images. The files are the following: map13.txt map14.txt map15.txt map16.txt map17.txt map18.txt map19.txt map21.txt map22.txt map23.txt The City of Toronto's Property Boundaries shapefile, "property_bnds_gcc_wgs84.zip" were unzipped and also reprojected to EPSG 26917 (UTM Zone 17) into a new shapefile, "Property_Boundaries_UTM.shp" Mosaicing Images Once georeferenced, all images were then mosaiced into one image file, "LandUseMosaic20211220v01", within the project-generated Geodatabase, "Landuse.gdb" and exported TIF, "LandUseMosaic20211220.tif" Reclassifying Images Because the original images were of low quality and the conversion to TIF made the image colours even more inconsistent, a method was required to reclassify the images so that different land use classes could be identified. Using Deep learning Objects, the images were re-classified into useful consistent colours. Deep Learning Objects and Training The resulting mosaic was then prepared for reclassification using the Label Objects for Deep Learning tool in ArcGIS Pro. A training sample, "LandUseTrainingSamples20211220", was created in the geodatabase for all land use types as follows: Neighbourhoods Insitutional Natural Areas Core Employment Areas Mixed Use Areas Apartment Neighbourhoods Parks Roads Utility Corridors Other Open Spaces General Employment Areas Regeneration Areas Lettering (not a land use type, but an image colour (black), used to label streets). By identifying the letters, it then made the reclassification and vectorization results easier to clean up of unnecessary clutter caused by the labels of streets. Reclassification Once the training samples were created and saved, the raster was then reclassified using the Image Classification Wizard tool in ArcGIS Pro, using the Support...

The Ontario Parcel is commercially licensed data with restricted usage.The parcels are managed by the Municipal Property Assessment Corporation (assessment), Teranet Enterprises Inc. (ownership), and the Ontario Government (Crown lands). The Ontario Parcel dataset is a source of assessment, ownership and Crown parcel mapping that can be used for assessment, taxation, land title/registration, as well as land use management and business planning.The Ontario Parcel (OP) consists of three data classes in geodatabase format and supporting information in CAD format:Assessment ParcelOwnership ParcelCrown ParcelOntario Parcel - Supporting Information (CAD format).See Ontario Parcel Guide (coming soon) for a comparison of the products. Public viewing of the standard Ontario Parcel - Assessment Parcel is available through the following web applications:Make a Topographic MapMake a Map: Natural Heritage AreasAgricultural Information Atlas (AgMaps).Licence EligibilityThe Ontario Parcel licensed through LIO is for non-commercial use. To receive data from Land Information Ontario (LIO), the organization must be eligible and sign an Ontario Parcel licensing agreement (MNRF General List User Licence Agreement).Eligible to apply: all Ontario ministries; agencies, boards and commissions; Indigenous communities; conservation authorities; non-profit organizations and others.Ontario Parcel data is available at no cost to those eligible to receive the data. Eligible organizations should contact Ontario Parcel at ontarioparcel@ontario.ca.Corporations and for-profit entities should contact:Municipal Property Assessment Corporation (MPAC)Teranet Enterprises, Inc. - Ontario ParcelTerms of UseOntario Parcel geometry represents an index of property locations, not a legal representation of property boundaries.Ontario Parcel is an indication that a boundary may be in the general area.The data should not be used for legal purposes. The data should not be used to define boundaries on the ground or be relied on to calculate areas of properties (unless for crude estimates) or depths or frontages of lots. The data is not a substitute for a legal survey and should not be used for applications that require accurate positional data.Additional DocumentationOntario Parcel FAQ (PDF)Assessment Parcel - Data Description (PDF)Assessment Parcel - Documentation (Word)Crown Parcel - Data Description (PDF)Crown Parcel - Documentation (Word)Ownership Parcel - Data Description (PDF)Ownership Parcel - Documentation (Word)StatusOn going: data is being continually updatedMaintenance and Update FrequencyFortnightly: data is updated every two weeksContactOntario Parcel, ontarioparcel@ontario.ca

[Superseded] This dataset is a snapshot of the Property boundaries — Parcel, which combines Brisbane City Council property information with the Queensland Government Digital Cadastral Database …Show full description[Superseded] This dataset is a snapshot of the Property boundaries — Parcel, which combines Brisbane City Council property information with the Queensland Government Digital Cadastral Database (DCDB) in Brisbane City Council area. It is a subset of the full cadastre and contains only lots included in the plan when the City Plan 2014 Amendment v18.00/2020 came into effect. 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.This dataset utilises Brisbane City Council's Open Spatial Data website to provide additional features for viewing and downloading the data.The first resource is in HTML format. The GO TO button will launch our Open Spatial Data website and this will let you preview the data and enable additional download options. The resources labelled GeoJSON, KML and SHP will give you a download of the entire dataset. The ESRI REST resource connects to metadata for the layer while the CSV resource will download attribute data in a table. For more information on the new features and other tips and tricks please read our Blog.

This layer provides the latest bearing (direction) and/or distance for cadastral boundaries.

When a cadastral survey is undertaken the relationship between boundary and non-boundary marks is ascertained or measured. • This commonly is in the form or a vector (bearing and distance), but occasionally just one component. • Some relationships are defined as arcs. In this data layer, the arc length is recorded in the distance field and a separate record holds the chord.

Only observations that have been captured in Landonline are available. This includes vectors that were re-captured in the Survey Capture Areas from survey plans lodged prior to Landonline and all survey observations since.

The approach and process to create the regional, standardized parcel data for the project involved the following steps. First convert the collected parcel data from its current format into the required Esri Geodatabase format, and the CT Cadastral Standard file Geodatabase template. All pre-existing parcel polygon attributes and parcel line attributes (including any feature level metadata) that were both part of the standard and also those that are not part of the standard attributes, were preserved as appended fields in the attribute tables. Next the GIS Link currently employed by the town was determined and if there was not an existing link, then AppGeo created one. If necessary, an Intersection table was created to establish the “many-to-one” relationship of condos and these special types of parcels. Analyze the data and report the mismatches for parcels with no CAMA as well as CAMA with no parcels. Analyze the parcels data for duplicate IDs. Document and submit to the towns, the analyses results and a map depicting the parcels that do not have a matching CAMA record, and work with the town to resolve the issues found. Goal was to accurately resolve as many of the mismatches as possible in order to meet at least the minimum required match rate of 90% per the CT Cadastral Standard. Incorporate necessary changes to resolve mismatches into the GIS data. In some cases this involved completely redrawing new parcel boundaries from recorded plans that were located during the resolution step, for changes such as lot splits or merges that will resolve a mismatch. The Coordinate Geometry (COGO) method was employed for creating or updating parcels lines when a recorded plan with the bearings or angles and distances are provided.The next step in the process was to assess the overall quality of the linework, flag areas of major concern with Errata Points, and attempt to acquire additional plans or other input from the town to address these areas. AppGeo adjusted the parcel linework using the more accurate boundaries depicted on plans that were made available. The surrounding (less accurate) parcels were then adjusted to the new (more accurate) parcels. The remaining parcels were visually inspected for alignment to the orthophotos. If determined necessary, the right of way lines and interior lot lines for each block of parcels were adjusted to visually match base map features on a block by block basis. If a town had, and provided to AppGeo, a dimension text layer, then the parcel lines were adjusted while maintaining parcel line lengths as defined by the dimension text per the best fit. If any of the original parcels had been created or maintained using Coordinate Geometry (COGO) and are identified as such in the existing parcel attributes, those parcels’ boundaries were held firmly as is and were not modified during the alignment process. Feature level metadata for all parcels edited during this process were updated in the parcel layers’ attributes according to the CT Cadastral Standard attribution guidelines. Internal QA/QC was done by AppGeo and then the data were reviewed by CRCOG.

The cadastral plane represents the apparent boundaries of the property. The computerized cadastral map in vector format (ICP-vector) is mainly the result of digitization of the cadastral map (paper or raster) carried out within the framework of agreements with local authorities. To a lesser extent, it could be made directly digitally as part of reorganizations (Law No. 74-645 of 18 July 1974) or land development commonly known as land consolidation. The data covers the Grand Est, they come from the shapefile files made available on the data.gouv.fr website, the update is carried out following the availability of the data on this site. (Updated with data as of 1 April 2024). The parent file is that concerning the Computerised Cadastral Plan (CCP) FR-200052264-A0093-0000

Contents This Dataset contains the following maps: 1. Ipswich Planning Scheme Zones 2. Indicative Boundary, subject to further detailed assessment 3. Springfield Structure Plan Designations 4. …Show full description##Contents This Dataset contains the following maps: 1. Ipswich Planning Scheme Zones 2. Indicative Boundary, subject to further detailed assessment 3. Springfield Structure Plan Designations 4. Designation of Land for Community Infrastructure 5. Recorded Approvals 6. Notations ##Ipswich Planning Scheme The 2006 Consolidated Ipswich Planning Scheme covers the entire local government area. In most instances it includes roads and watercourses. The Planning Scheme was prepared in accordance with the requirements of the repealed Integrated Planning Act 1997 (IPA) and the Department of Local Government and Planning guidelines and scheme template. Council adopted the Consolidated Planning Scheme (including all amendments to the 2004 Ipswich Planning Scheme) on 14 December 2005, and took effect (ie commencement date) on 23 January 2006. The Planning Scheme divides the Ipswich Local Government Area into 8 localities- Urban Areas City Centre Regionally Significant Business Enterprise and Industry Areas Amberley Rosewood Township Areas Rural Areas, and Springfield. Each locality is further divided into Zones and in some cases, Sub Areas and Precincts. The planning scheme also provides a secondary organisational layer called Overlays, which are based on special attributes of land that need to be protected, or that may constrain development. There are two types of overlays - character places overlays and development constraints overlays. The Planning Scheme uses the concepts of Overall Outcomes, Specific Outcomes, Probable Solutions and Acceptable Solutions for a zone, overlay or code. Overall Outcomes are essentially the overall purpose or intent statements. Specific Outcomes are the more detailed performance objectives. Probable Solutions represent one way of achieving a specific outcome and may be either increased or decreased by the Local Government depending on the individual circumstances of the proposal. Acceptable Solutions apply only to self-assessable development and represent a precise measure for compliance. In addition to the zoning of a property, it is also imperative to refer to the overlay maps and associated overlay codes (see Part 11) in the planning scheme as these may change the relevant assessment category of development compared to the underlying zone, or provide additional information. Also, in addition to the overlays affecting a property, it is also imperative to refer to the zoning maps and associated zone codes in the planning scheme as these may change the relevant assessment category of development, or provide additional information. Data made available under CC-BY-ND terms. Data updated on changes to Scheme.

Digital line graph (DLG) data are digital representations of cartographic information. DLG's of map features are converted to digital form from maps and related sources. Intermediate-scale DLG data are derived from USGS 1:100,000-scale 30- by 60-minute quadrangle maps. If these maps are not available, Bureau of Land Management planimetric maps at a scale of 1: 100,000 are used. Intermediate-scale DLG's are sold in five categories: (1) Public Land Survey System; (2) boundaries (3) transportation; (4) hydrography; and (5) hypsography. All DLG data distributed by the USGS are DLG - Level 3 (DLG-3), which means the data contain a full range of attribute codes, have full topological structuring, and have passed certain quality-control checks.

This is the land parcels (polygon) dataset for the UKCEH Land Cover Map of 2019 (LCM2019) representing Great Britain. It describes Great Britain's land cover in 2019 using UKCEH Land Cover Classes, which are based on UK Biodiversity Action Plan broad habitats. This dataset was derived from the corresponding LCM2019 20m classified pixels dataset. All further LCM2019 datasets for Great Britain are derived from this land parcel product. A range of land parcel attributes are provided. These include the dominant UKCEH Land Cover Class given as an integer value, and a range of per-parcel pixel statistics to help to assess classification confidence and accuracy; for a full explanation please refer to the dataset documentation. LCM2019 represents a suite of geospatial land cover datasets (raster and polygon) describing the UK land surface in 2019. These were produced at the UK Centre for Ecology & Hydrology by classifying satellite images from 2019. LCM2019 was simultaneously released with LCM2017 and LCM2018. These are the latest in a series of UKCEH land cover maps, which began with the 1990 Land Cover Map of Great Britain (now usually referred to as LCM1990) followed by UK-wide land cover maps LCM2000, LCM2007 and LCM2015. This work was supported by the Natural Environment Research Council award number NE/R016429/1 as part of the UK-SCAPE programme delivering National Capability.

The broad purpose of the Zoning Code is to implement the General Plan, to promote and protect the public health, safety, comfort, and general welfare of the residents of the Town of Gilbert. Generally, the Zoning Code is intended to:A. Direct growth with priority to those areas where infrastructure and urban services can be economically provided; B. Ensure consistency and conformity among the General Plan, zoning districts, and zoning ordinances; C. Maintain and enhance the appearance and function of both new and existing development; D. Promote an efficient use of land resources; E. Ensure compatibility among land uses; F. Ensure the provision of adequate open space for light, air, and fire safety. G. Ensure that service demands of new development will not exceed the capacities of existing or planned streets, utilities, or public services; H. Conserve the natural environment, protect environmentally sensitive areas, and enhance the quality of the built environment; I. Promote energy and water conservation through project design; J. Establish consistent standards regulating the use and physical development of land; and K. Preserve and enhance property values.

Official Zoning Map Adoption. The Town is hereby divided into zones, or districts, as shown on the Official Zoning Map which, together with all explanatory matter thereon, is hereby adopted by reference and declared to be a part of the Zoning Code.District Boundary or Classification Changes. If, in accordance with the provisions of the Zoning Code, changes are made in district boundaries, district classifications, or other matter set forth on the Official Zoning Map, such changes shall be entered on the Official Zoning Map within 15 days following the effective date of the Ordinance adopting the change.Maintenance of Official Zoning Map. The Official Zoning Map shall be maintained in electronic format by the Technology Services department, as authorized by the Director of Planning.Copies of the Official Zoning Map. Paper copies of the Official Zoning Map shall be certified as true and correct by the director of the Technology Services department authorized by the Director of Planning. Electronic copies of the Official zoning map shall not be certified as true and correct.Where uncertainty exists regarding the boundary of a zoning district, the following rules shall apply:District boundaries shown as approximately following the property line of a lot or parcel shall be construed to follow such property line. Where a district boundary divides a lot or parcel, the location of the district boundary shall be determined by the Zoning Administrator using the scale appearing on the Official Zoning Map.District boundaries shown as approximately following right-of-way lines of freeways, streets, railroads, or other identifiable boundary lines shall be construed to follow such right-of-way or boundary lines.District boundaries shown as lying within right-of-way lines of freeways, streets, railroads, or other identifiable boundary lines shall be construed to follow the centerline of such right-of- way or boundary lines.District boundaries shown as lying at the edge of a canal or drainage channel shall be construed to follow the centerline of the canal or drainage channel.If any uncertainty remains as to the location of a district boundary or other feature shown on the Official Zoning Map, the location shall be determined by the Zoning Administrator.Record of Interpretation. The Zoning Administrator shall keep a record of interpretations made pursuant to this section. The record of interpretations shall be available to the public.

The cadastral plane represents the apparent boundaries of the property. The computerized cadastral map in vector format (ICP-vector) is mainly the result of digitization of the cadastral map (paper or raster) carried out within the framework of agreements with local authorities. To a lesser extent, it could be made directly digitally as part of reorganizations (Law No. 74-645 of 18 July 1974) or land development commonly known as land consolidation. The data covers the Grand Est, they come from the shapefile files made available on the data.gouv.fr website, the update is carried out following the availability of the data on this site. (updated to 1 April 2024) The child fiches are: FR-200052264-A0094-0000 DONNEE - Computerized Cadastral Plan (CDP) - Built on the Grand Est FR-200052264-A0095-0000 DONNEE - Computerized Cadastral Plan (CDP) - Plot on the Grand Est FR-200052264-A0096-0000 DONNEE - Computerized Cadastral Plan (CDP) - Section on the Grand Est FR-200052264-A0097-0000 DONNEE - Computerized Cadastral Plan (CDP) - Commune on the Grand Est

The USGS Protected Areas Database of the United States (PAD-US) is the nation's inventory of protected areas, including public land and voluntarily provided private protected areas, identified as an A-16 National Geospatial Data Asset in the Cadastre Theme ( https://communities.geoplatform.gov/ngda-cadastre/ ). The PAD-US is an ongoing project with several published versions of a spatial database including areas dedicated to the preservation of biological diversity, and other natural (including extraction), recreational, or cultural uses, managed for these purposes through legal or other effective means. The database was originally designed to support biodiversity assessments; however, its scope expanded in recent years to include all open space public and nonprofit lands and waters. Most are public lands owned in fee (the owner of the property has full and irrevocable ownership of the land); however, permanent and long-term easements, leases, agreements, Congressional (e.g. 'Wilderness Area'), Executive (e.g. 'National Monument'), and administrative designations (e.g. 'Area of Critical Environmental Concern') documented in agency management plans are also included. The PAD-US strives to be a complete inventory of U.S. public land and other protected areas, compiling “best available” data provided by managing agencies and organizations. The PAD-US geodatabase maps and describes areas using thirty-six attributes and five separate feature classes representing the U.S. protected areas network: Fee (ownership parcels), Designation, Easement, Marine, Proclamation and Other Planning Boundaries. An additional Combined feature class includes the full PAD-US inventory to support data management, queries, web mapping services, and analyses. The Feature Class (FeatClass) field in the Combined layer allows users to extract data types as needed. A Federal Data Reference file geodatabase lookup table (PADUS3_0Combined_Federal_Data_References) facilitates the extraction of authoritative federal data provided or recommended by managing agencies from the Combined PAD-US inventory. This PAD-US Version 3.0 dataset includes a variety of updates from the previous Version 2.1 dataset (USGS, 2020, https://doi.org/10.5066/P92QM3NT ), achieving goals to: 1) Annually update and improve spatial data representing the federal estate for PAD-US applications; 2) Update state and local lands data as state data-steward and PAD-US Team resources allow; and 3) Automate data translation efforts to increase PAD-US update efficiency. The following list summarizes the integration of "best available" spatial data to ensure public lands and other protected areas from all jurisdictions are represented in the PAD-US (other data were transferred from PAD-US 2.1). Federal updates - The USGS remains committed to updating federal fee owned lands data and major designation changes in annual PAD-US updates, where authoritative data provided directly by managing agencies are available or alternative data sources are recommended. The following is a list of updates or revisions associated with the federal estate: 1) Major update of the Federal estate (fee ownership parcels, easement interest, and management designations where available), including authoritative data from 8 agencies: Bureau of Land Management (BLM), U.S. Census Bureau (Census Bureau), Department of Defense (DOD), U.S. Fish and Wildlife Service (FWS), National Park Service (NPS), Natural Resources Conservation Service (NRCS), U.S. Forest Service (USFS), and National Oceanic and Atmospheric Administration (NOAA). The federal theme in PAD-US is developed in close collaboration with the Federal Geographic Data Committee (FGDC) Federal Lands Working Group (FLWG, https://communities.geoplatform.gov/ngda-govunits/federal-lands-workgroup/ ). 2) Improved the representation (boundaries and attributes) of the National Park Service, U.S. Forest Service, Bureau of Land Management, and U.S. Fish and Wildlife Service lands, in collaboration with agency data-stewards, in response to feedback from the PAD-US Team and stakeholders. 3) Added a Federal Data Reference file geodatabase lookup table (PADUS3_0Combined_Federal_Data_References) to the PAD-US 3.0 geodatabase to facilitate the extraction (by Data Provider, Dataset Name, and/or Aggregator Source) of authoritative data provided directly (or recommended) by federal managing agencies from the full PAD-US inventory. A summary of the number of records (Frequency) and calculated GIS Acres (vs Documented Acres) associated with features provided by each Aggregator Source is included; however, the number of records may vary from source data as the "State Name" standard is applied to national files. The Feature Class (FeatClass) field in the table and geodatabase describe the data type to highlight overlapping features in the full inventory (e.g. Designation features often overlap Fee features) and to assist users in building queries for applications as needed. 4) Scripted the translation of the Department of Defense, Census Bureau, and Natural Resource Conservation Service source data into the PAD-US format to increase update efficiency. 5) Revised conservation measures (GAP Status Code, IUCN Category) to more accurately represent protected and conserved areas. For example, Fish and Wildlife Service (FWS) Waterfowl Production Area Wetland Easements changed from GAP Status Code 2 to 4 as spatial data currently represents the complete parcel (about 10.54 million acres primarily in North Dakota and South Dakota). Only aliquot parts of these parcels are documented under wetland easement (1.64 million acres). These acreages are provided by the U.S. Fish and Wildlife Service and are referenced in the PAD-US geodatabase Easement feature class 'Comments' field. State updates - The USGS is committed to building capacity in the state data-steward network and the PAD-US Team to increase the frequency of state land updates, as resources allow. The USGS supported efforts to significantly increase state inventory completeness with the integration of local parks data in the PAD-US 2.1, and developed a state-to-PAD-US data translation script during PAD-US 3.0 development to pilot in future updates. Additional efforts are in progress to support the technical and organizational strategies needed to increase the frequency of state updates. The PAD-US 3.0 included major updates to the following three states: 1) California - added or updated state, regional, local, and nonprofit lands data from the California Protected Areas Database (CPAD), managed by GreenInfo Network, and integrated conservation and recreation measure changes following review coordinated by the data-steward with state managing agencies. Developed a data translation Python script (see Process Step 2 Source Data Documentation) in collaboration with the data-steward to increase the accuracy and efficiency of future PAD-US updates from CPAD. 2) Virginia - added or updated state, local, and nonprofit protected areas data (and removed legacy data) from the Virginia Conservation Lands Database, provided by the Virginia Department of Conservation and Recreation's Natural Heritage Program, and integrated conservation and recreation measure changes following review by the data-steward. 3) West Virginia - added or updated state, local, and nonprofit protected areas data provided by the West Virginia University, GIS Technical Center. For more information regarding the PAD-US dataset please visit, https://www.usgs.gov/gapanalysis/PAD-US/. For more information about data aggregation please review the PAD-US Data Manual available at https://www.usgs.gov/core-science-systems/science-analytics-and-synthesis/gap/pad-us-data-manual . A version history of PAD-US updates is summarized below (See https://www.usgs.gov/core-science-systems/science-analytics-and-synthesis/gap/pad-us-data-history for more information): 1) First posted - April 2009 (Version 1.0 - available from the PAD-US: Team pad-us@usgs.gov). 2) Revised - May 2010 (Version 1.1 - available from the PAD-US: Team pad-us@usgs.gov). 3) Revised - April 2011 (Version 1.2 - available from the PAD-US: Team pad-us@usgs.gov). 4) Revised - November 2012 (Version 1.3) https://doi.org/10.5066/F79Z92XD 5) Revised - May 2016 (Version 1.4) https://doi.org/10.5066/F7G73BSZ 6) Revised - September 2018 (Version 2.0) https://doi.org/10.5066/P955KPLE 7) Revised - September 2020 (Version 2.1) https://doi.org/10.5066/P92QM3NT 8) Revised - January 2022 (Version 3.0) https://doi.org/10.5066/P9Q9LQ4B Comparing protected area trends between PAD-US versions is not recommended without consultation with USGS as many changes reflect improvements to agency and organization GIS systems, or conservation and recreation measure classification, rather than actual changes in protected area acquisition on the ground.

This dataset is refreshed on a weekly basis from the datasets the team works on daily.Last update date: 06 March 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.

[Superseded] This dataset is a snapshot of the Property boundaries — Holding dataset, which combines Brisbane City Council property information with the Queensland Government Digital Cadastral …Show full description[Superseded] This dataset is a snapshot of the Property boundaries — Holding dataset, which combines Brisbane City Council property information with the Queensland Government Digital Cadastral Database (DCDB) to show property holdings in Brisbane City Council area. It is a subset of the full cadastre and contains only lots included in the plan when the City Plan 2014 Amendment v15.00/2019 came into effect. 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 dataset utilises Brisbane City Council's Open Spatial Data website to provide additional features for viewing and downloading the data.The first resource is in HTML format. The GO TO button will launch our Open Spatial Data website and this will let you preview the data and enable additional download options. The resources labelled GeoJSON, KML and SHP will give you a download of the entire dataset. The ESRI REST resource connects to metadata for the layer while the CSV resource will download attribute data in a table. For more information on the new features and other tips and tricks please read our Blog.

March 2025