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.

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 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.

For large areas, like Washington State, download as a file geodatabase. Large data sets like this one, for the State of Washington, may exceed the limits for downloading as shape files, excel files, or KML files. For areas less than a county, you may use the map to zoom to your area and download as shape file, excel or KML, if that format is desired.The Boundary layer consists of lines representing the boundaries of Parcels and Legal Descriptions. (See the metadata for those two layers.) Boundary lines are the places that are surveyed in order to delimit the extent of Parcels and Legal Descriptions. The character and accuracy of Boundary locations is held in the attributes of the Points that are at the ends of Boundary lines. All the boundaries of Parcels and Legal Descriptions are covered by a Boundary line. Currently the Boundary layer has little functionality. The only distinction it makes is between upland boundaries and shorelines. In the future Boundary lines will have a richer set of attributes in order to accommodate cartographic needs to distinguish between types of boundaries.WA Boundaries Metadata

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 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.

NZ Parcel Boundaries Wireframe provides a map of land, road and other parcel boundaries, and is especially useful for displaying property boundaries.
This map service is for visualisation purposes only and is not intended for download. You can download the full parcels data from the NZ Parcels dataset.
This map service provides a dark outline and transparent fill, making it perfect for overlaying on our basemaps or any map service you choose.
Data for this map service is sourced from the NZ Parcels dataset which is updated weekly with authoritative data direct from LINZ’s Survey and Title system. Refer to the NZ Parcel layer for detailed metadata.
To simplify the visualisation of this data, the map service filters the data from the NZ Parcels layer to display parcels with a status of 'current' only.
This map service has been designed to be integrated into GIS, web and mobile applications via LINZ’s WMTS and XYZ tile services. View the Services tab to access these services.
See the LINZ website for service specifications and help using WMTS and XYZ tile services and more information about this service.

"Due to the size of this dataset, both Shapefile and Spreadsheet download options will not work as expected. The File Geodatabase is an alternative option for this data download"This is SCAG's 2019 Annual Land Use (ALU v. 2019.1) at the parcel-level, updated as of February 2021. This dataset has been modified to include additional attributes in order to feed SCAG's Housing Element Parcel Tool (HELPR), version 2.0. The dataset will be further reviewed and updated as additional information is released. Please refer to the tables below for data dictionary and SCAG’s land use classification.Field NameData TypeField DescriptionPID19Text2019 SCAG’s parcel unique IDAPN19Text2019 Assessor’s parcel numberCOUNTYTextCounty name (based on 2016 county boundary)COUNTY_IDDoubleCounty FIPS code (based on 2016 county boundary)CITYTextCity name (based on 2016 city boundary)CITY_IDDoubleCity FIPS code (based on 2016 city boundary)MULTIPARTShort IntegerMultipart feature (the number of multiple polygons; '1' = singlepart feature)STACKLong IntegerDuplicate geometry (the number of duplicate polygons; '0' = no duplicate polygons)ACRESDoubleParcel area (in acreage)GEOID20Text2020 Census Block Group GEOIDSLOPEShort IntegerSlope information1APN_DUPLong IntegerDuplicate APN (the number of multiple tax roll property records; '0' = no duplicate APN)IL_RATIODoubleRatio of improvement assessed value to land assessed valueLU19Text2019 existing land useLU19_SRCTextSource of 2019 existing land use2SCAGUID16Text2016 SCAG’s parcel unique IDAPNText2016 Assessor’s parcel numberCITY_GP_COText2016 Jurisdiction’s general plan land use designationSCAG_GP_COText2016 SCAG general plan land use codeSP_INDEXShort IntegerSpecific plan index ('0' = outside specific plan area; '1' = inside specific plan area)CITY_SP_COText2016 Jurisdiction’s specific plan land use designationSCAG_SP_COText2016 SCAG specific plan land use codeCITY_ZN_COText2016 Jurisdiction’s zoning codeSCAG_ZN_COText2016 SCAG zoning codeLU16Text2016 existing land useYEARLong IntegerDataset yearPUB_OWNShort IntegerPublic-owned land index ('1' = owned by public agency)PUB_NAMETextName of public agencyPUB_TYPETextType of public agency3BF_SQFTDoubleBuilding footprint area (in square feet)4BSF_NAMETextName of brownfield/superfund site5BSF_TYPETextType of brownfield/superfund site5FIREShort IntegerParcel intersects CalFire Very High Hazard Local Responsibility Areas or State Responsibility Areas (November 2020 version) (CalFIRE)SEARISE36Short IntegerParcel intersects with USGS Coastal Storm Modeling System (CoSMos)1 Meter Sea Level Rise inundation areas for Southern California (v3.0, Phase 2; 2018)SEARISE72Short IntegerParcel intersects with USGS Coastal Storm Modeling System (CoSMos)2 Meter Sea Level Rise inundation areas for Southern California (v3.0, Phase 2; 2018)FLOODShort IntegerParcel intersects with a FEMA 100 Year Flood Plain data from the Digital Flood Insurance Rate Map (DFIRM), obtained from Federal Emergency Management Agency (FEMA) in August 10, 2017EQUAKEShort IntegerParcel intersects with an Alquist-Priolo Earthquake Fault Zone (California Geological Survey; 2018)LIQUAFAShort IntegerParcel intersects with a Liquefaction Susceptibility Zone (California Geological Survey; 2016)LANDSLIDEShort IntegerParcel intersects with a Landslide Hazard Zone (California Geological Survey; 2016)CPADShort IntegerParcel intersects with a protected area from the California Protected Areas Database(CPAD) – www.calands.org (accessed April 2021)RIPARIANShort IntegerParcel centroid falls within Active River Areas(2010)or parcel intersects with a Wetland Area in the National Wetland Inventory(Version 2)WILDLIFEShort IntegerParcel intersects with wildlife habitat (US Fish & Wildlife ServiceCritical Habitat, Southern California Missing Linkages, Natural Lands & Habitat Corridors from Connect SoCal, CEHC Essential Connectivity Areas,Critical Coastal Habitats)CNDDBShort IntegerThe California Natural Diversity Database (CNDDB)includes the status and locations of rare plants and animals in California. Parcels that overlap locations of rare plants and animals in California from the California Natural Diversity Database (CNDDB)have a greater likelihood of encountering special status plants and animals on the property, potentially leading to further legal requirements to allow development (California Department of Fish and Wildlife). Data accessed in October 2020.HCPRAShort IntegerParcel intersects Natural Community & Habitat Conservation Plans Reserve Designs from the Western Riverside MHSCP, Coachella Valley MHSCP, and the Orange County Central Coastal NCCP/HCP, as accessed in October 2020WETLANDShort IntegerParcel intersects a wetland or deepwater habitat as defined by the US Fish & Wildlife Service National Wetlands Inventory, Version 2.UAZShort IntegerParcel centroid lies within a Caltrans Adjusted Urbanized AreasUNBUILT_SFDoubleDifference between parcel area and building footprint area expressed in square feet.6GRCRY_1MIShort IntegerThe number of grocery stores within a 1-mile drive7HEALTH_1MIShort IntegerThe number of healthcare facilities within a 1-mile drive7OPENSP_1MIShort IntegerQuantity of open space (roughly corresponding to city blocks’ worth) within a 1-mile drive7TCAC_2021TextThe opportunity level based on the 2021 CA HCD/TCAC opportunity scores.HQTA45Short IntegerField takes a value of 1 if parcel centroid lies within a 2045 High-Quality Transit Area (HQTA)JOB_CTRShort IntegerField takes a value of 1 if parcel centroid lies within a job centerNMAShort IntegerField takes a value of 1 if parcel centroid lies within a neighborhood mobility area.ABS_CONSTRShort IntegerField takes a value of 1 if parcel centroid lies within an absolute constraint area. See the Sustainable Communities Strategy Technical Reportfor details.VAR_CONSTRShort IntegerField takes a value of 1 if parcel centroid lies within a variable constraint area. See the Sustainable Communities Strategy Technical Reportfor details.EJAShort IntegerField takes a value of 1 if parcel centroid lies within an Environmental Justice Area. See the Environmental Justice Technical Reportfor details.SB535Short IntegerField takes a value of 1 if parcel centroid lies within an SB535 Disadvantaged Community area. See the Environmental Justice Technical Reportfor details.COCShort IntegerField takes a value of 1 if parcel centroid lies within a Community of Concern See the Environmental Justice Technical Reportfor details.STATEShort IntegerThis field is a rudimentary estimate of which parcels have adequate physical space to accommodate a typical detached Accessory Dwelling Unit (ADU)8.SBShort IntegerIndex of ADU eligibility according to the setback reduction policy scenario (from 4 to 2 feet) (1 = ADU eligible parcel, Null = Not ADU eligible parcel)SMShort IntegerIndex of ADU eligibility according to the small ADU policy scenario (from 800 to 600 square feet ADU) (1 = ADU eligible parcel, Null = Not ADU eligible parcel)PKShort IntegerIndex of ADU eligibility according to parking space exemption (200 square feet) policy scenario (1 = ADU eligible parcel, Null = Not ADU eligible parcel)SB_SMShort IntegerIndex of ADU eligibility according to both the setback reduction and small ADU policy scenarios (1 = ADU eligible parcel, Null = Not ADU eligible parcel)SB_PKShort IntegerIndex of ADU eligibility according to both the setback reduction and parking space exemption scenarios (1 = ADU eligible parcel, Null = Not ADU eligible parcel)SM_PKShort IntegerIndex of ADU eligibility according to both the small ADU policy and parking space exemption scenarios (1 = ADU eligible parcel, Null = Not ADU eligible parcel)SB_SM_PKShort IntegerIndex of ADU eligibility according to the setback reduction, small ADU, and parking space exemption scenarios (1 = ADU eligible parcel, Null = Not ADU eligible parcel)1. Slope: '0' - 0~4 percent; '5' - 5~9 percent; '10' - 10~14 percent; '15' = 15~19 percent; '20' - 20~24 percent; '25' = 25 percent or greater.2. Source of 2019 existing land use: SCAG_REF- SCAG's regional geospatial datasets;ASSESSOR- Assessor's 2019 tax roll records; CPAD- California Protected Areas Database (version 2020a; accessed in September 2020); CSCD- California School Campus Database (version 2018; accessed in September 2020); FMMP- Farmland Mapping and Monitoring Program's Important Farmland GIS data (accessed in September 2020); MIRTA- U.S. Department of Defense's Military Installations, Ranges, and Training Areas GIS data (accessed in September 2020)3. Type of public agency includes federal, state, county, city, special district, school district, college/university, military.4. Based on 2019 building footprint data obtained from BuildingFootprintUSA (except that 2014 building footprint data was used for Imperial County). Please note that 2019 building footprint data does not cover the entire SCAG region (overlapped with 83% of parcels in the SCAG Region).5. Includes brownfield/superfund site whose address information are matched by SCAG rooftop address locator. Brownfield data was obtained from EPA's Assessment, Cleanup and Redevelopment Exchange System (ACRES) database, Cleanups in my community (CIMC), DTSC brownfield Memorandum of Agreement (MOA). Superfund site data was obtained from EPA's Superfund Enterprise Management System (SEMS) database.6. Parcels with a zero value for building footprint area are marked as NULL to indicate this field is not reliable.7. These values are intended as a rudimentary indicator of accessibility developed by SCAG using 2016 InfoUSA business establishment data and 2017 California Protected Areas data. See documentation for details.8. A detailed study conducted by Cal Poly Pomona (CPP) and available hereconducted an extensive review of state and local requirements and development trends for ADUs in the SCAG region and developed a baseline set of assumptions for estimating how many of a jurisdiction’s parcels

While the Waimakariri District Council has taken all reasonable care in providing correct information, all information should be considered as being illustrative and indicative only. Your use of this information is entirely at your own risk. You should independently verify the accuracy of any information before taking any action in reliance upon it.Read full disclaimer here.Abstract:This layer is derived from current primary parcels, as per the NZ Parcels layer on the LINZ Data Service, joined to data on matching current/future properties in WDC’S rating database.Note, this dataset includes a boundary for the primary property address only (as identified in WDC’s rating database) and does not include a boundary for all addresses that may exist on a property.Other information:Addresses:The address datasets contain street number, street name and suburb for physical addresses in Waimakariri.There can be multiple addresses on a property and an example of these are granny flats, farm cottages etc.Click here to view Address Boundary LayerClick here to view Address Point LayerUpdate Frequency:DailyPoint of Contact:Waimakariri District CouncilLineage:Data has been compiled from a number of sources and its accuracy may vary (e.g. Field Verification, Deposited Plans, AsBuilt plans and forms, sketches, aerial photo, Google Street View). There may be delays before data is updated to reflect changes in an area.

This feature class depicts the boundaries of Land Survey features called sections, defined by the Public Lands Survey System Grid. Normally, 36 sections make up a township. The entire extent of each of these units should be collected, not just the portion on National Forest System lands. This dataset is derived from the USFS Southwestern Region ALP (Automated Lands Program) data Project. This is one of six layers derived from ALP for the purpose of supplying data layers for recourse GIS analysis and data needs within the Forest Service. The six layers are Surface Ownership, Administrative Forest Boundary, District Boundary, Townships, Sections, and Wilderness. There were some gapes in the ALP data so a small portion of this dataset comes from CCF (Cartographic Feature Files) datasets and the USFS Southwestern Region Core Data Project. ALP data is developed from data sources of differing accuracy, scales, and reliability. Where available it is developed from GCDB (Geographic Coordinate Data Base) data. GCDB data is maintained by the Bureau of Land Management in their State Offices. GCDB data is mostly corner data. Not all corners and not all boundaries are available in GCDB so ALP also utilizes many other data sources like CFF data to derive its boundaries. GCDB data is in a constant state of change because land corners are always getting resurveyed. The GCDB data used in this dataset represents a snapshot in time at the time the GCDB dataset was published by the BLM and may not reflect the most current GCDB dataset available. The Forest Service makes no expressed or implied warranty with respect to the character, function, or capabilities of these data. These data are intended to be used for planning and analyses purposes only and are not legally binding with regards to title or location of National Forest System lands.

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 service shows the datasets listed below. All datasets are in the ITM coordnate system. This data is subject to change and will be updated from time to time. Datasets included in this zip are - Business Area Units -Forest boundary - Property boundary - Compartment boundary - Forest Inventory . Please refer to terms of use for this dataset before using. These are available below or on the Coillte Public Viewer. The link to this is also included on this page below. Use of data All data on this viewer is available to download and subject to the terms of use – by downloading the data you are agreeing to the terms of use. Data is in ITM format. You agree not to copy, publish or use the data on another website or in any manner likely to confuse members of the public or amount to misrepresentation as to your identity or relationship with Coillte. You agree not to access the data contained therein in any way which is unlawful, illegal, fraudulent or harmful or in connection with any for any unlawful, illegal, fraudulent or harmful activity, including data privacy breaches. The dataset is made available free of charge. We do not guarantee that this dataset, or any content in our Arc GIS online platform, will always be available or be uninterrupted. Coillte may suspend or withdraw or restrict the availability of all or part of the Viewer for business or operational reasons. The content on the Coillte ArcGIS platform is for general information only. Reasonable care has been exercised in the compilation of the information available through the ArcGIS online platform. There is no representation or warranty made as to the accuracy, completeness or currency of such information. The use of any such information, which may be altered or updated at any time without notice, is at the sole risk of the user. Coillte cannot accept responsibility for any errors or omissions or any consequential loss as a result of the same. Before relying on the information on this site, users should carefully evaluate its accuracy, currency, completeness and relevance for their purposes. The site and data are provided on an "as is" and "as available" basis and Coillte does not guarantee and assumes no legal liability or responsibility for the accuracy, timeliness, completeness, performance or fitness for a particular purpose, of the site or any content. Copyright Declaration You agree not to use the information provided except for research or private study and will not supply a copy of this information to any other person without seeking prior permission from Coillte. You may not use any part of this content for commercial purposes without obtaining permission from Coillte to do so, for which a license may be required. Coillte is the owner or licensee of all intellectual property rights in this layer and such rights are protected by copyright. You acknowledge that data downloaded are subject to change and update. If this information is to be published in any format (written or electronic) you will acknowledge this source and forward a copy of the material in published form to the Coillte office in Newtownmountkennedy or to info@coillte.ie For further information please contact info@coillte.ie

This line feature layer contains Legal City boundaries within Los Angeles County.

The principal attribute is BDRY_TYPE which represents the boundary feature types. Use its values below for definition queries and layer symbology for your mapping needs.

Coast - This value represents the coastline. This data is carefully maintained by DPW staff, based Los Angeles Region Imagery Acquisition Consortium data.

Land City - This value represents city boundaries on land.

Land County - This value represents the county boundary on land.

Pier - One example is the Santa Monica Pier. Man-made features may be regarded as extensions of the coastline.

Breakwater - Examples include the breakwater barriers that protect the Los Angeles Harbor.

Water - This value is used to separate features representing internal navigable waters and the ocean. Examples of internal waters are found in the Long Beach Harbor and in Marina del Rey.

Ocean - This value is used to represent ocean boundaries between cities in addition to the seaward boundaries of coastal cities. Per the Submerged Lands Act, the seaward boundaries of coastal cities and unincorporated county areas are three nautical miles (a nautical mile is 1852 meters) from the coastline.

Ravine & Natural Feature Protection area and limit as regulated by City of Toronto Municipal Code Chapter 658 - Ravine & Natural Feature Protection. Please note: Dataset is limited to the City of Toronto geographical boundary. Dataset works best if you open it with GIS/CAD software and reference these layers: City of Toronto Street Centreline, Address Points and Property Boundaries. If your original design drawing has been created without a coordinate system, you will need to reference the city's datasets and then move, scale and/or rotate your data to line up with the property limits for the property you are working with.

This layer provides the latest captured boundary mark information that defines existing parcel boundaries and associated information such as the mark name.

A boundary mark is on a node which defines the boundaries of primary parcels or non primary parcels.

Not all boundary points have a physical monument (e.g. a peg) placed. In this case the boundary mark is recorded as “unmarked”

This dataset extends the Landonline stored data by including the network accuracy which is based upon its assigned Landonline order - refer LINZS25006 (http://www.linz.govt.nz/about-linz/news-publications-and-consultations/search-for-regulatory-documents/DocumentSummary.aspx?document=256 ).

The accuracy provided relates to the accuracy of coordinates of the mark and has little relevance to the accuracy of the boundary in relation to other boundaries. For example, if the coordinates of the mark were used to locate it, a user would expect to find the existing mark within the nominal accuracy (distance) stated.

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 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.

This dataset contains existing and approved residential boundaries in Cary, NC. For additional information on properties check out our website. This dataset is updated as residential boundaries are changed.

Queensland's spatial cadastre datasets are changing! From a planned date of 1 July 2025 the current Digital Cadastral Database (DCDB) will be migrated to an entirely new operating environment, and there will be some changes to the data provided. Visit our Spatial Applications Support page (https://spatial-qld-support.atlassian.net/wiki/spaces/QSUITE/pages/1067515932/Cadastre+and+Address+Modernisation+CAM) for more information.The Digital Cadastre 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 Digital Cadastre 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 data is updated weekly on Sunday.Data dictionary https://www.publications.qld.gov.au/dataset/queensland-digital-cadastral-database-supporting-documents/resource/b59bb1a1-3818-4754-8dc4-3669f0ec3f8b Spatial cadastre accuracy map https://www.publications.qld.gov.au/dataset/queensland-digital-cadastral-database-supporting-documents/resource/d6f029ad-b3a4-428b-bcf1-2f7c7326132b

To access parcel information:Enter an address or zoom in by using the +/- tools or your mouse scroll wheel. Parcels will draw when zoomed in.Click on a parcel to display a popup with information about that parcel.Click the "Basemap" button to display background aerial imagery.From the "Layers" button you can turn map features on and off.Complete Help (PDF)Parcel Legend:Full Map LegendAbout this ViewerThis viewer displays land property boundaries from assessor parcel maps across Massachusetts. Each parcel is linked to selected descriptive information from assessor databases. Data for all 351 cities and towns are the standardized "Level 3" tax parcels served by MassGIS. More details ...Read about and download parcel dataUpdatesV 1.1: Added 'Layers' tab. (2018)V 1.2: Reformatted popup to use HTML table for columns and made address larger. (Jan 2019)V 1.3: Added 'Download Parcel Data by City/Town' option to list of layers. This box is checked off by default but when activated a user can identify anywhere and download data for that entire city/town, except Boston. (March 14, 2019)V 1.4: Data for Boston is included in the "Level 3" standardized parcels layer. (August 10, 2020)V 1.4 MassGIS, EOTSS 2021