MassGIS' standardized ("Level 3") property tax parcel mapping data set was developed through a competitive procurement funded by MassGIS. Each community in the Commonwealth was bid on by one or more vendors and the unit of work awarded was a city or town. The specification for this work was Level 3 of the MassGIS Digital Parcel Standard. Standardization of assessor parcel mapping is complete for all 351 Massachusetts' cities and towns. MassGIS is now incorporating updates from municipalities into the database.This hosted feature layer is exported from MassGIS' internal database of the feature class GISDATA.L3_TAXPAR_POLY_ASSESS, which links L3_TAXPAR_POLY and L3_ASSESS. The export includes the expression:(POLY_TYPE IN ('FEE', 'TAX')) OR (POLY_TYPE IN ('ROW', 'PRIV_ROW', 'RAIL_ROW', 'WATER') AND PROP_ID IS NOT NULL)It contains several fields from GISDATA.L3_ASSESS and stacked polygons where multiple assessor records link to a parcel. It contains features that do not have an associated record in GISDATA.L3_ASSESS, except for rights of way and water bodies. ROWs and water bodies with a non-null PROP_ID are included. The data in this feature layer is used for the popups in the Massachusetts Interactive Property Map.See full data descriptionA hosted tile layer will draw very quickly at map scale of 1:18,056 (level 15) to 1:564 (level 20).

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

🇺🇸 미국 English Download In State Plane Projection Here ** In addition to the Tax Parcel polygons feature class, the hyperlink download above also contains a parcel point data layer ** Parcel boundaries are developed from deeds, plats of subdivision and other legal documents going back to the mid 1800's, following generally accepted practices used in Public Land Survey System states, and following guidelines established by the Illinois Department of Revenue and the International Association of Assessment Officials. Lake County's parcel coverage is based on resolving the accumulated evidence of all of the legal documents surrounding a particular parcel or subdivision, and not the result of a countywide resurvey. These parcel boundaries are intended to be a visual inventory of property for tax and other administrative purposes; they are not intended to be used in place of an on-site survey or for the precise determination of property corners or PLSS features based on GIS coordinates. In Illinois, only a registered professional land surveyor is authorized to determine boundary locations. Included are the tax parcel boundaries, represented as polygons and centroids, for all changes resulting from legal records submitted to the Recorder of Deeds up to December 31st of the preceding year, as well as any court orders, municipal annexations and other transactions which impact the tax parcel boundaries. NOTE: The ONLY attribute included is the Property Index Number, or PARCEL_NUM. Additional assessment attribute data can be downloaded here This parcel layer is used for tax assessment purposes and for a variety of other local government functions. It changes often, both spatially and in its attribution, based on divisions or consolidations, the sale of property and other transactions. Example: PIN 08-17-304-014 can be interpreted as follows: Township 08, Section 17, Block 304, Parcel 014. Note that the first digit of block, "3" in this example, signifies that the parcel lies in quarter section 3. The quarter sections are labeled from 1 through 4, representing the northwest, northeast, southwest and southeast quarter sections, respectively. Update Frequency: This dataset is updated on a weekly basis.

This feature layer provides digital tax parcels for the Organized Towns of the State of Maine. Within Maine, real property data is maintained by the government organization responsible for assessing and collecting property tax for a given location. Organized towns and townships maintain authoritative data for their communities and may voluntarily submit these data to the Maine GeoLibrary Parcel Project. "Maine Parcels Organized Towns Feature" and "Maine Parcels Organized Towns ADB" are the product of these voluntary submissions. Communities provide updates to the Maine GeoLibrary on a non-regular basis, which affects the currency of Maine GeoLibrary parcels data. Another resource for real property transaction data is the County Registry of Deeds, although organized town data should very closely match registry information, except in the case of in-process property conveyance transactions. In Unorganized Territories (defined as those regions of the state without a local government that assesses real property and collects property tax), the Maine Revenue Service is the authoritative source for parcel data. "Maine Parcels Unorganized Territory Feature" is the authoritative GIS data layer for the Unorganized Territories. However, it must always be used with auxiliary data obtained from the online resources of Maine Revenue Services (https://www.maine.gov/revenue/taxes/property-tax) to compile up-to-date parcel ownership information. Property maps are a fundamental base for many municipal activities. Although GIS parcel data cannot replace detailed ground surveys, the data can assist municipal officials with functions such as accurate property tax assessment, planning and zoning. Towns can link maps to an assessor's database and display local information, while town officials can show taxpayers how proposed development or changes in municipal services and regulations may affect the community. In many towns, parcel data also helps to provide public notices, plan bus routes, and carry out other municipal services.

This dataset contains municipality-submitted parcel data along with previously developed parcel data acquired through the Municipal Grants Project supported by the Maine Library of Geographic Information (Maine GeoLibrary). Grant recipient parcel data submissions were guided by standards presented to the Maine GeoLibrary Board on May 21, 2005, which are outlined in the "Standards for Digital Parcel Files" document available on the Maine GeoLibrary publications page (https://www.maine.gov/geolib/policies/standards.html). This dataset also contains municipal parcel data acquired through other sources; the data sources are identified (where available) by the field “FMSCORG”. Note: Join this feature layer with the "Maine Parcels Organized Towns ADB" table (https://maine.hub.arcgis.com/maps/maine::maine-parcels-organized-towns-feature/about?layer=1) for available ownership information. A date field, “FMUPDAT”, is attributed with the most recent update date for each individual parcel if available. The "FMUPDAT" field will not match the "Updated" value shown for the layer. "FMUPDAT" corresponds with the date of update for the individual data, while "Updated" corresponds with the date of update for the ArcGIS Online layer as a whole. Many parcels have not been updated in several years; use the "FMUPDAT" field to verify currency.

This table represents the Air Lots that exist in the Digital Tax Map Collection. • Updates: Data is extracted from DOF’s internal system on the last Friday of each month and refreshed on ArcGIS Online on the 1st. The online map always shows the most recent version. • Accessing the Data: • Digital Tax Map on NYC Open Data: See the complete collection. • Individual layers: Downloadable from the Digital Tax Map Feature Server. • Complete source: Available through the Digital Tax Map service, which always points to the latest monthly release. Note: To ensure reliability, the Tax Map alternates between Set A and Set B each month. If one set has issues, the previous month’s copy remains online. Both sets are kept about a month apart and are available for download: • Set A link • Set B link • Digital Alteration Book (DAB): The DAB is the official log of map changes—such as new lots, merges, or boundary shifts—providing a clear record of how the Tax Map evolves. It is available through the Property Information Portal. Disclaimer: This dataset reflects formal applications submitted to DOF but may not reflect the latest changes in other City systems (e.g., exemptions or buildings data). It is provided for informational purposes only and is not guaranteed to be accurate as of today’s date.

This data set was developed to provide accurate framework data (including address points, street centerlines, land parcels, and governmental boundaries) for Indiana, as part of the Indiana Data Sharing Initiative (IDSI) of the Indiana Geographic Information Office (IGIO).This dataset is a polygon feature class that contains land parcels maintained by local government agencies in Indiana, provided by personnel of the Indiana Geographic Information Office (IGIO). These data were compiled by IGIO as part of the Indiana Data Sharing Initiative (IDSI) between Indiana Geographic Information Council (IGIC), Indiana Geographic Information Office (IGIO), Indiana Geological and Water Survey (IGWS) and participating Indiana local governments to provide the most accurate framework data (including address points, street centerlines, land parcels, and governmental boundaries) for the citizens of Indiana. The attributes have been expanded to now include parcel ID, dates of harvest from each government, property classification codes, property classification descriptions, street address information, and tax district ID numbers.

This dataset is a compilation of county parcel data from Minnesota counties that have opted-in for their parcel data to be included in this dataset.

It includes the following 59 counties that have opted-in as of the publication date of this dataset: Aitkin County, Anoka County, Becker County, Benton County, Big Stone County, Carlton County, Carver County, Cass County, Chippewa County, Chisago County, Clay County, Clearwater County, Cook County, Crow Wing County, Dakota County, Douglas County, Fillmore County, Grant County, Hennepin County, Houston County, Isanti County, Itasca County, Jackson County, Koochiching County, Lac qui Parle County, Lake County, Lake of the Woods County, Lyon County, Marshall County, McLeod County, Mille Lacs County, Morrison County, Mower County, Murray County, Norman County, Olmsted County, Otter Tail County, Pennington County, Pipestone County, Polk County, Pope County, Ramsey County, Red Lake County, Renville County, Rice County, Scott County, Sherburne County, St. Louis County, Stearns County, Steele County, Stevens County, Traverse County, Wabasha County, Waseca County, Washington County, Wilkin County, Winona County, Wright County, and Yellow Medicine County.

If you represent a county not included in this dataset and would like to opt-in, please contact Heather Albrecht (Heather.Albrecht@hennepin.us), co-chair of the Minnesota Geospatial Advisory Council (GAC)’s Parcels and Land Records Committee's Open Data Subcommittee. County parcel data does not need to be in the GAC parcel data standard to be included. MnGeo will map the county fields to the GAC standard.

County parcel data records have been assembled into a single dataset with a common coordinate system (UTM Zone 15) and common attribute schema. The county parcel data attributes have been mapped to the GAC parcel data standard for Minnesota: https://www.mngeo.state.mn.us/committee/standards/parcel_attrib/parcel_attrib.html

This compiled parcel dataset was created using Python code developed by Minnesota state agency GIS professionals, and represents a best effort to map individual county source file attributes into the common attribute schema of the GAC parcel data standard. The attributes from counties are mapped to the most appropriate destination column. In some cases, the county source files included attributes that were not mapped to the GAC standard. Additionally, some county attribute fields were parsed and mapped to multiple GAC standard fields, such as a single line address. Each quarter, MnGeo provides a text file to counties that shows how county fields are mapped to the GAC standard. Additionally, this text file shows the fields that are not mapped to the standard and those that are parsed. If a county shares changes to how their data should be mapped, MnGeo updates the compilation. If you represent a county and would like to update how MnGeo is mapping your county attribute fields to this compiled dataset, please contact us.

This dataset is a snapshot of parcel data, and the source date of the county data may vary. Users should consult County websites to see the most up-to-date and complete parcel data.

There have been recent changes in date/time fields, and their processing, introduced by our software vendor. In some cases, this has resulted in date fields being empty. We are aware of the issue and are working to correct it for future parcel data releases.

The State of Minnesota makes no representation or warranties, express or implied, with respect to the use or reuse of data provided herewith, regardless of its format or the means of its transmission. THE DATA IS PROVIDED “AS IS” WITH NO GUARANTEE OR REPRESENTATION ABOUT THE ACCURACY, CURRENCY, SUITABILITY, PERFORMANCE, MECHANTABILITY, RELIABILITY OR FITINESS OF THIS DATA FOR ANY PARTICULAR PURPOSE. This dataset is NOT suitable for accurate boundary determination. Contact a licensed land surveyor if you have questions about boundary determinations.

DOWNLOAD NOTES: This dataset is only provided in Esri File Geodatabase and OGC GeoPackage formats. A shapefile is not available because the size of the dataset exceeds the limit for that format. The distribution version of the fgdb is compressed to help reduce the data footprint. QGIS users should consider using the Geopackage format for better results.

BY USING THIS WEBSITE OR THE CONTENT THEREIN, YOU AGREE TO THE TERMS OF USE.
A spatial representation of Tax Parcels. Key attributes include KeyPIN. The KeyPIN is the unique parcel identification number used to link the tax parcel to the parcel attributes which are stored and maintained in Oakland County land records.

There is no definite accuracy related to parcel boundaries. The information shown on these maps is for representation purposes only and is not intended to be a legally recorded map or survey. The information was compiled from a number of sources including recorded deeds, plats, tax maps surveys and other public records and data. Users of this data should consult the information sources listed above for verification of the information.

The Lake County Data Extract provides parcel characteristics and tax information for all properties located in Lake County, Illinois. Casual users can find the standalone Tax Parcel Boundary Data above and Parcel Attribute Data here. The information contained in the extract is "as is", and Lake County does not in any way guarantee the correctness or accuracy of the information contained therein.

See full Data Guide here. Connecticut Parcels for Protected Open Space Mapping is a polygon feature-based layer that includes basic parcel-level information for some towns in Connecticut. This 2009 parcel layer includes information provided by individual municipalities. These parcel data are incomplete and out of date. The accuracy, currency and completeness of the data reflect the content of the data at the time DEEP acquired the data from the individual municipalities. Attribute information is comprised of values such as town name and map lot block number. These data are not updated by CT DEEP and should only be used as a general reference. Critical decisions involving parcel-level information should be based on more recently acquired information from the respective municipalities. These parcels are not to be considered legal boundaries such as boundaries determined from certain classified survey maps or deed descriptions. Parcel boundaries shown in this layer are based on information from municipalities used for property tax purposes. Largely due to differences in horizontal accuracy among various data layers, do not expect these parcel boundaries to line up exactly with or be properly postioned relative to features shown on other layers available from CT DEEP such as scanned USGS topography quadrangle maps, roads, hydrography, town boundaries, and even orthophotograpy. The data in the parcel layer was obtained from individual Connecticut municipalities. An effort was made to collect data once from each municipality. The data acquisition date for each set of municipally-supplied parcel data was not recorded and CT DEEP does not keep this information up-to-date. Consequently, these data are out-of-date, incomplete and do not reflect the current state of property ownership in these municipalities. These parcels are not to be considered legal boundaries such as boundaries determined from certain classified survey maps or deed descriptions. Parcel boundaries shown in this layer are based on information from municipalities used for property tax purposes. Parcel boundaries and attribute information have not been updated in this layer since the time the information was originally acquired by CT DEEP. For example, property boundaries are incorrect where subdivisions have occurred. Also, field attribute values are populated only if the information was supplied to CT DEEP. For example, parcels in some towns lack location (street name) information or possibly map lot block values. Therefore, field attributes are inconsistent, may include gaps, and do not represent complete sets of values among all towns. They should not be compared and analyzed across towns. It is emphasized that critical decisions involving parcel-level information be based on more recently obtained information from the respective municipalities. These data are only suitable for general reference purposes. Be cautious when using these data. Many Connecticut municipalities provide access to more up-to-date and more detailed property ownership information on the Internet. This dataset includes parcel information for the following towns: Andover, Ansonia, Ashford, Avon, Beacon Falls, Berlin, Bethany, Bethel, Bethlehem, Bloomfield, Bolton, Branford, Bridgewater, Brookfield, Brooklyn, Canaan, Canterbury, Canton, Chaplin, Cheshire, Chester, Clinton, Colchester, Colebrook, Columbia, Cornwall, Coventry, Cromwell, Danbury, Darien, Deep River, Derby, East Granby, East Haddam, East Hampton, East Hartford, East Lyme, East Windsor, Eastford, Ellington, Enfield, Essex, Farmington, Franklin, Glastonbury, Granby, Greenwich, Griswold, Groton, Guilford, Haddam, Hamden, Hartford, Hebron, Kent, Killingly, Killingworth, Lebanon, Ledyard, Lisbon, Litchfield, Lyme, Madison, Manchester, Mansfield, Marlborough, Meriden, Middlebury, Middlefield, Middletown, Milford,

Publication Date: April 2025. This polygon layer is updated annually.

This layer contains 2024 parcel data only for NY State counties which gave NYS ITs Geospatatial Services permission to share this data with the public. Work to obtain parcel data from additional counties, as well as permission to share the data, is ongoing. To date, 36 counties have provided the Geospatial Services permission to share their parcel data with the public. Parcel data for counties which do not allow the Geospatial Services to redistribute their data must be obtained directly from those counties. Geospatial Services' goal is to eventually include parcel data for all counties in New York State.

Parcel geometry was incorporated as received from County Real Property Departments. No attempt was made to edge-match parcels along adjacent counties. County attribute values were populated using 2024 Assessment Roll tabular data Geospatial Services obtained from the NYS Department of Tax and Finance’s Office of Real Property Tax Services (ORPTS). Tabular assessment data was joined to the county provided parcel geometry using the SWIS & SBL or SWIS & PRINT KEY unique identifier for each parcel.

Detailed information about assessment attributes can be found in the ORPTS Assessor’s Manuals available here: https://www.tax.ny.gov/research/property/assess/manuals/assersmanual.htm. New York City data comes from NYC MapPluto which can be found here: https://www1.nyc.gov/site/planning/data-maps/open-data/dwn-pluto-mappluto.page.

This layer displays when zoomed in below 1:37,051-scale.

This map service is available to the public.

Geometry accuracy varies by contributing county.

Thanks to the following counties that specifically authorized Geospatial Services to share their GIS tax parcel data with the public: Albany, Cayuga, Chautauqua, Cortland, Erie, Genesee, Greene, Hamilton, Lewis, Livingston, Montgomery, New York City (Bronx, Kings, New York, Queens, Richmond), Oneida, Onondaga, Ontario, Orange, Oswego, Otsego, Putnam, Rensselaer, Rockland, Schuyler, Steuben, St Lawrence, Suffolk, Sullivan, Tioga, Tompkins, Ulster, Warren, Wayne, and Westchester.

The State of New York, acting through the New York State Office of Information Technology Services, makes no representations or warranties, express or implied, with respect to the use of or reliance on the Data provided. The User accepts the Data provided “as is” with no guarantees that it is error free, complete, accurate, current or fit for any particular purpose and assumes all risks associated with its use. The State disclaims any responsibility or legal liability to Users for damages of any kind, relating to the providing of the Data or the use of it. Users should be aware that temporal changes may have occurred since this Data was created.

Note: The schema changed in February 2025 - please see below. We will post a roadmap of upcoming changes, but service URLs and schema are now stable. For deployment status of new services beginning in February 2025, see https://gis.data.ca.gov/pages/city-and-county-boundary-data-status. Additional roadmap and status links at the bottom of this metadata.This dataset is regularly updated as the source data from CDTFA is updated, as often as many times a month. If you require unchanging point-in-time data, export a copy for your own use rather than using the service directly in your applications. PurposeCounty boundaries along with third party identifiers used to join in external data. Boundaries are from the California Department of Tax and Fee Administration (CDTFA). These boundaries are the best available statewide data source in that CDTFA receives changes in incorporation and boundary lines from the Board of Equalization, who receives them from local jurisdictions for tax purposes. Boundary accuracy is not guaranteed, and though CDTFA works to align boundaries based on historical records and local changes, errors will exist. If you require a legal assessment of boundary location, contact a licensed surveyor.This dataset joins in multiple attributes and identifiers from the US Census Bureau and Board on Geographic Names to facilitate adding additional third party data sources. In addition, we attach attributes of our own to ease and reduce common processing needs and questions. Finally, coastal buffers are separated into separate polygons, leaving the land-based portions of jurisdictions and coastal buffers in adjacent polygons. This feature layer is for public use. Related LayersThis dataset is part of a grouping of many datasets:Cities: Only the city boundaries and attributes, without any unincorporated areasWith Coastal BuffersWithout Coastal BuffersCounties: Full county boundaries and attributes, including all cities within as a single polygonWith Coastal Buffers (this dataset)Without Coastal BuffersCities and Full Counties: A merge of the other two layers, so polygons overlap within city boundaries. Some customers require this behavior, so we provide it as a separate service.With Coastal BuffersWithout Coastal BuffersCity and County AbbreviationsUnincorporated Areas (Coming Soon)Census Designated PlacesCartographic CoastlinePolygonLine source (Coming Soon)State BoundaryWith Bay CutsWithout Bay Cuts Working with Coastal Buffers The dataset you are currently viewing includes the coastal buffers for cities and counties that have them in the source data from CDTFA. In the versions where they are included, they remain as a second polygon on cities or counties that have them, with all the same identifiers, and a value in the COASTAL field indicating if it"s an ocean or a bay buffer. If you wish to have a single polygon per jurisdiction that includes the coastal buffers, you can run a Dissolve on the version that has the coastal buffers on all the fields except OFFSHORE and AREA_SQMI to get a version with the correct identifiers. Point of ContactCalifornia Department of Technology, Office of Digital Services, gis@state.ca.gov Field and Abbreviation DefinitionsCDTFA_COUNTY: CDTFA county name. For counties, this will be the name of the polygon itself. For cities, it is the name of the county the city polygon is within.CDTFA_COPRI: county number followed by the 3-digit city primary number used in the Board of Equalization"s 6-digit tax rate area numbering system. The boundary data originate with CDTFA's teams managing tax rate information, so this field is preserved and flows into this dataset.CENSUS_GEOID: numeric geographic identifiers from the US Census BureauCENSUS_PLACE_TYPE: City, County, or Town, stripped off the census name for identification purpose.GNIS_PLACE_NAME: Board on Geographic Names authorized nomenclature for area names published in the Geographic Name Information SystemGNIS_ID: The numeric identifier from the Board on Geographic Names that can be used to join these boundaries to other datasets utilizing this identifier.CDT_COUNTY_ABBR: Abbreviations of county names - originally derived from CalTrans Division of Local Assistance and now managed by CDT. Abbreviations are 3 characters.CDT_NAME_SHORT: The name of the jurisdiction (city or county) with the word "City" or "County" stripped off the end. Some changes may come to how we process this value to make it more consistent.AREA_SQMI: The area of the administrative unit (city or county) in square miles, calculated in EPSG 3310 California Teale Albers.OFFSHORE: Indicates if the polygon is a coastal buffer. Null for land polygons. Additional values include "ocean" and "bay".PRIMARY_DOMAIN: Currently empty/null for all records. Placeholder field for official URL of the city or countyCENSUS_POPULATION: Currently null for all records. In the future, it will include the most recent US Census population estimate for the jurisdiction.GlobalID: While all of the layers we provide in this dataset include a GlobalID field with unique values, we do not recommend you make any use of it. The GlobalID field exists to support offline sync, but is not persistent, so data keyed to it will be orphaned at our next update. Use one of the other persistent identifiers, such as GNIS_ID or GEOID instead. Boundary AccuracyCounty boundaries were originally derived from a 1:24,000 accuracy dataset, with improvements made in some places to boundary alignments based on research into historical records and boundary changes as CDTFA learns of them. City boundary data are derived from pre-GIS tax maps, digitized at BOE and CDTFA, with adjustments made directly in GIS for new annexations, detachments, and corrections.Boundary accuracy within the dataset varies. While CDTFA strives to correctly include or exclude parcels from jurisdictions for accurate tax assessment, this dataset does not guarantee that a parcel is placed in the correct jurisdiction. When a parcel is in the correct jurisdiction, this dataset cannot guarantee accurate placement of boundary lines within or between parcels or rights of way. This dataset also provides no information on parcel boundaries. For exact jurisdictional or parcel boundary locations, please consult the county assessor's office and a licensed surveyor. CDTFA's data is used as the best available source because BOE and CDTFA receive information about changes in jurisdictions which otherwise need to be collected independently by an agency or company to compile into usable map boundaries. CDTFA maintains the best available statewide boundary information. CDTFA's source data notes the following about accuracy: City boundary changes and county boundary line adjustments filed with the Board of Equalization per Government Code 54900. This GIS layer contains the boundaries of the unincorporated county and incorporated cities within the state of California. The initial dataset was created in March of 2015 and was based on the State Board of Equalization tax rate area boundaries. As of April 1, 2024, the maintenance of this dataset is provided by the California Department of Tax and Fee Administration for the purpose of determining sales and use tax rates. The boundaries are continuously being revised to align with aerial imagery when areas of conflict are discovered between the original boundary provided by the California State Board of Equalization and the boundary made publicly available by local, state, and federal government. Some differences may occur between actual recorded boundaries and the boundaries used for sales and use tax purposes. The boundaries in this map are representations of taxing jurisdictions for the purpose of determining sales and use tax rates and should not be used to determine precise city or county boundary line locations. Boundary ProcessingThese data make a structural change from the source data. While the full boundaries provided by CDTFA include coastal buffers of varying sizes, many users need boundaries to end at the shoreline of the ocean or a bay. As a result, after examining existing city and county boundary layers, these datasets provide a coastline cut generally along the ocean facing coastline. For county boundaries in northern California, the cut runs near the Golden Gate Bridge, while for cities, we cut along the bay shoreline and into the edge of the Delta at the boundaries of Solano, Contra Costa, and Sacramento counties. In the services linked above, the versions that include the coastal buffers contain them as a second (or third) polygon for the city or county, with the value in the COASTAL field set to whether it"s a bay or ocean polygon. These can be processed back into a single polygon by dissolving on all the fields you wish to keep, since the attributes, other than the COASTAL field and geometry attributes (like areas) remain the same between the polygons for this purpose. SliversIn cases where a city or county"s boundary ends near a coastline, our coastline data may cross back and forth many times while roughly paralleling the jurisdiction"s boundary, resulting in many polygon slivers. We post-process the data to remove these slivers using a city/county boundary priority algorithm. That is, when the data run parallel to each other, we discard the coastline cut and keep the CDTFA-provided boundary, even if it extends into the ocean a small amount. This processing supports consistent boundaries for Fort Bragg, Point Arena, San Francisco, Pacifica, Half Moon Bay, and Capitola, in addition to others. More information on this algorithm will be provided soon. Coastline CaveatsSome cities have buffers extending into water bodies that we do not cut at the shoreline. These include South Lake Tahoe and Folsom, which extend into neighboring lakes, and San Diego and surrounding cities that extend into San Diego Bay, which our shoreline encloses. If you have feedback on the exclusion of these

Publication Date: April 2025. This polygon layer is updated as needed and is current as of the publication date.

This layer is intended to be used in conjunction with the NYS_Tax_Parcels_Public layer (which only displays when zoomed in below 1:37,051-scale). NYS_Tax_Parcels_Public_Footprint only displays when zoomed out beyond 1:37,050-scale. It contains labeled polygons only for those counties which make their tax parcel GIS data publicly available and are in the NYS_Tax_Parcels_Public layer.

Boundaries were digitized at 1:24,000-scale.

This map service is available to the public.

The State of New York, acting through the New York State Office of Information Technology Services, makes no representations or warranties, express or implied, with respect to the use of or reliance on the Data provided. The User accepts the Data provided “as is” with no guarantees that it is error free, complete, accurate, current or fit for any particular purpose and assumes all risks associated with its use. The State disclaims any responsibility or legal liability to Users for damages of any kind, relating to the providing of the Data or the use of it. Users should be aware that temporal changes may have occurred since this Data was created.

Publication Date: April 2025. Updated annually, or as needed. The data can be downloaded here: https://gis.ny.gov/parcels#data-download. This feature service only contains parcel data for NYS State-owned tax parcels. 2024 Parcel geometry was incorporated as received from County Real Property Departments. No attempt was made to edge-match parcels along adjacent counties. County attribute values were populated using 2024 Assessment Roll tabular data NYS ITS Geospatial Services obtained from the NYS Department of Tax and Finance’s Office of Real Property Tax Services (ORPTS).Tabular assessment data was joined to the county provided parcel geometry using the SWIS & SBL or SWIS & PRINT KEY unique identifier for each parcel. Detailed information about assessment attributes can be found in the ORPTS Assessor’s Manuals available here: https://www.tax.ny.gov/research/property/assess/manuals/assersmanual.htm. New York City data comes from NYC MapPluto which can be found here: https://www1.nyc.gov/site/planning/data-maps/open-data/dwn-pluto-mappluto.page. The State-owned tax parcel polygons in this file are the result of a best effort selection based on the Primary Owner and Additional Owner fields in the NYS Statewide Tax Parcels file, Geospatial Services data, State agency data, and online research. These same data and information are also the basis for a best effort assignment of a NYS agency name (listed in the NYS Name field) to most tax parcel polygons where the Owner Type field value is State. The NYS Name Source field consists of a code that describes how the State-owned designation and agency name were determined, if this was verified, and the means of verification, if applicable.This map service is available to the public.The State of New York, acting through the New York State Office of Information Technology Services, makes no representations or warranties, express or implied, with respect to the use of or reliance on the Data provided. The User accepts the Data provided “as is” with no guarantees that it is error free, complete, accurate, current or fit for any particular purpose and assumes all risks associated with its use. The State disclaims any responsibility or legal liability to Users for damages of any kind, relating to the providing of the Data or the use of it. Users should be aware that temporal changes may have occurred since this Data was created.

WARNING: This is a pre-release dataset and its fields names and data structures are subject to change. It should be considered pre-release until the end of March 2025. The schema changed in February 2025 - please see below. We will post a roadmap of upcoming changes, but service URLs and schema are now stable. For deployment status of new services in February 2025, see https://gis.data.ca.gov/pages/city-and-county-boundary-data-status. Additional roadmap and status links at the bottom of this metadata.This dataset is continuously updated as the source data from CDTFA is updated, as often as many times a month. If you require unchanging point-in-time data, export a copy for your own use rather than using the service directly in your applications.PurposeCounty boundaries along with third party identifiers used to join in external data. Boundaries are from the California Department of Tax and Fee Administration (CDTFA). These boundaries are the best available statewide data source in that CDTFA receives changes in incorporation and boundary lines from the Board of Equalization, who receives them from local jurisdictions for tax purposes. Boundary accuracy is not guaranteed, and though CDTFA works to align boundaries based on historical records and local changes, errors will exist. If you require a legal assessment of boundary location, contact a licensed surveyor.This dataset joins in multiple attributes and identifiers from the US Census Bureau and Board on Geographic Names to facilitate adding additional third party data sources. In addition, we attach attributes of our own to ease and reduce common processing needs and questions. Finally, coastal buffers are separated into separate polygons, leaving the land-based portions of jurisdictions and coastal buffers in adjacent polygons. This layer removes the coastal buffer polygons. This feature layer is for public use.Related LayersThis dataset is part of a grouping of many datasets:Cities: Only the city boundaries and attributes, without any unincorporated areasWith Coastal BuffersWithout Coastal BuffersCounties: Full county boundaries and attributes, including all cities within as a single polygonWith Coastal BuffersWithout Coastal Buffers (this dataset)Cities and Full Counties: A merge of the other two layers, so polygons overlap within city boundaries. Some customers require this behavior, so we provide it as a separate service.With Coastal BuffersWithout Coastal BuffersCity and County AbbreviationsUnincorporated Areas (Coming Soon)Census Designated PlacesCartographic CoastlinePolygonLine source (Coming Soon)Working with Coastal BuffersThe dataset you are currently viewing excludes the coastal buffers for cities and counties that have them in the source data from CDTFA. In the versions where they are included, they remain as a second polygon on cities or counties that have them, with all the same identifiers, and a value in the COASTAL field indicating if it"s an ocean or a bay buffer. If you wish to have a single polygon per jurisdiction that includes the coastal buffers, you can run a Dissolve on the version that has the coastal buffers on all the fields except OFFSHORE and AREA_SQMI to get a version with the correct identifiers.Point of ContactCalifornia Department of Technology, Office of Digital Services, odsdataservices@state.ca.govField and Abbreviation DefinitionsCDTFA_COUNTY: CDTFA county name. For counties, this will be the name of the polygon itself. For cities, it is the name of the county the city polygon is within.CDTFA_COPRI: county number followed by the 3-digit city primary number used in the Board of Equalization"s 6-digit tax rate area numbering system. The boundary data originate with CDTFA's teams managing tax rate information, so this field is preserved and flows into this dataset.CENSUS_GEOID: numeric geographic identifiers from the US Census BureauCENSUS_PLACE_TYPE: City, County, or Town, stripped off the census name for identification purpose.GNIS_PLACE_NAME: Board on Geographic Names authorized nomenclature for area names published in the Geographic Name Information SystemGNIS_ID: The numeric identifier from the Board on Geographic Names that can be used to join these boundaries to other datasets utilizing this identifier.CDT_COUNTY_ABBR: Abbreviations of county names - originally derived from CalTrans Division of Local Assistance and now managed by CDT. Abbreviations are 3 characters.CDT_NAME_SHORT: The name of the jurisdiction (city or county) with the word "City" or "County" stripped off the end. Some changes may come to how we process this value to make it more consistent.AREA_SQMI: The area of the administrative unit (city or county) in square miles, calculated in EPSG 3310 California Teale Albers.OFFSHORE: Indicates if the polygon is a coastal buffer. Null for land polygons. Additional values include "ocean" and "bay".PRIMARY_DOMAIN: Currently empty/null for all records. Placeholder field for official URL of the city or countyCENSUS_POPULATION: Currently null for all records. In the future, it will include the most recent US Census population estimate for the jurisdiction.GlobalID: While all of the layers we provide in this dataset include a GlobalID field with unique values, we do not recommend you make any use of it. The GlobalID field exists to support offline sync, but is not persistent, so data keyed to it will be orphaned at our next update. Use one of the other persistent identifiers, such as GNIS_ID or GEOID instead.Boundary AccuracyCounty boundaries were originally derived from a 1:24,000 accuracy dataset, with improvements made in some places to boundary alignments based on research into historical records and boundary changes as CDTFA learns of them. City boundary data are derived from pre-GIS tax maps, digitized at BOE and CDTFA, with adjustments made directly in GIS for new annexations, detachments, and corrections. Boundary accuracy within the dataset varies. While CDTFA strives to correctly include or exclude parcels from jurisdictions for accurate tax assessment, this dataset does not guarantee that a parcel is placed in the correct jurisdiction. When a parcel is in the correct jurisdiction, this dataset cannot guarantee accurate placement of boundary lines within or between parcels or rights of way. This dataset also provides no information on parcel boundaries. For exact jurisdictional or parcel boundary locations, please consult the county assessor's office and a licensed surveyor.CDTFA's data is used as the best available source because BOE and CDTFA receive information about changes in jurisdictions which otherwise need to be collected independently by an agency or company to compile into usable map boundaries. CDTFA maintains the best available statewide boundary information.CDTFA's source data notes the following about accuracy:City boundary changes and county boundary line adjustments filed with the Board of Equalization per Government Code 54900. This GIS layer contains the boundaries of the unincorporated county and incorporated cities within the state of California. The initial dataset was created in March of 2015 and was based on the State Board of Equalization tax rate area boundaries. As of April 1, 2024, the maintenance of this dataset is provided by the California Department of Tax and Fee Administration for the purpose of determining sales and use tax rates. The boundaries are continuously being revised to align with aerial imagery when areas of conflict are discovered between the original boundary provided by the California State Board of Equalization and the boundary made publicly available by local, state, and federal government. Some differences may occur between actual recorded boundaries and the boundaries used for sales and use tax purposes. The boundaries in this map are representations of taxing jurisdictions for the purpose of determining sales and use tax rates and should not be used to determine precise city or county boundary line locations. Boundary ProcessingThese data make a structural change from the source data. While the full boundaries provided by CDTFA include coastal buffers of varying sizes, many users need boundaries to end at the shoreline of the ocean or a bay. As a result, after examining existing city and county boundary layers, these datasets provide a coastline cut generally along the ocean facing coastline. For county boundaries in northern California, the cut runs near the Golden Gate Bridge, while for cities, we cut along the bay shoreline and into the edge of the Delta at the boundaries of Solano, Contra Costa, and Sacramento counties.In the services linked above, the versions that include the coastal buffers contain them as a second (or third) polygon for the city or county, with the value in the COASTAL field set to whether it"s a bay or ocean polygon. These can be processed back into a single polygon by dissolving on all the fields you wish to keep, since the attributes, other than the COASTAL field and geometry attributes (like areas) remain the same between the polygons for this purpose.SliversIn cases where a city or county"s boundary ends near a coastline, our coastline data may cross back and forth many times while roughly paralleling the jurisdiction"s boundary, resulting in many polygon slivers. We post-process the data to remove these slivers using a city/county boundary priority algorithm. That is, when the data run parallel to each other, we discard the coastline cut and keep the CDTFA-provided boundary, even if it extends into the ocean a small amount. This processing supports consistent boundaries for Fort Bragg, Point Arena, San Francisco, Pacifica, Half Moon Bay, and Capitola, in addition to others. More information on this algorithm will be provided soon.Coastline CaveatsSome cities have buffers extending into water bodies that we do not cut at the shoreline. These include South Lake Tahoe and Folsom, which extend into neighboring lakes, and

PurposeThis dataset has been published by the City Treasurer of the City of Virginia Beach and data.vbgov.com. The mission of data.vbgov.com is to provide timely and accurate City information to increase government transparency and access to useful and well organized data by the general public, non-governmental organizations, and City of Virginia Beach employees.Access constraintsThe data is publicly available and accessible.Use constraintsBy using data made available through this site, the user agrees to all the conditions stated in the following paragraphs, as well as the terms and conditions described in the “Terms of Use” on the “About this Site” page.The City of Virginia Beach makes no claims as to the completeness, accuracy, timeliness, or content of any data contained in this application; makes any representation of any kind, including, but not limited to, warranty of the accuracy or fitness for a particular use; nor are any such warranties to be implied or inferred with respect to the information or data furnished herein. The data is subject to change as modifications and updates are complete. It is understood that the information contained in the site is being used at one’s own risk. Applications using data supplied by this site must include the following disclaimers on their sites:“The data made available here has been modified for use from its original source, which is the City of Virginia Beach. Neither the City of Virginia Beach nor the Office of the Chief Information Officer (CIO) makes any claims as to the completeness, timeliness, accuracy or content of any data contained in this application; makes any representation of any kind, including, but not limited to, warranty of the accuracy or fitness for a particular use; nor are any such warranties to be implied or inferred with respect to the information or data furnished herein. The data is subject to change as modifications and updates are complete. It is understood that the information contained in the web feed is being used at one’s own risk.” As found in the “Terms of Use” on the “About this Site” page.Point of ContactCity Treasurer’s OfficeDonnah Perry, Deputy Treasurer for Real Estate757-385-8258vbre4you@vbgov.comCreditsCity of Virginia Beach Office of the Chief Information Officer (CIO), data.virginiabeach.com staffDistributionDistribution liability: By using data made available through this site, the user agrees to all the conditions started in the following paragraphs, as well as, the terms and conditions described in the “Terms of Use” on the “About this Site” page.The City of Virginia Beach makes no claims as to the completeness, accuracy, timeliness, or content of any data contained in this application; makes any representation of any kind, including, but not limited to, warranty of the accuracy or fitness for a particular use; nor are any such warranties to be implied or inferred with respect to the information or data furnished herein. The data is subject to change as modifications and updates are complete. It is understood that the information contained in the site is being used at one’s own risk. Applications using data supplied by this site must include the following disclaimers on their sites:“The data made available here has been modified for use from its original source, which is the City of Virginia Beach. Neither the City of Virginia Beach nor the Office of the Chief Information Officer (CIO) makes any claims as to the completeness, timeliness, accuracy or content of any data contained in this application; makes any representation of any kind, including, but not limited to, warranty of the accuracy or fitness for a particular use; nor are any such warranties to be implied or inferred with respect to the information or data furnished herein. The data is subject to change as modifications and updates are complete. It is understood that the information contained in the web feed is being used at one’s own risk.” As found in the “Terms of Use” on the “About this Site” page.Distributed bydata.vbgov.com2405 Courthouse Dr.Virginia Beach, VA 23456Entity

PurposeBoundary is derived from the California Department of Tax and Fee Administration (CDTFA). Their county boundaries are the most-up to date statewide data source in that CDTFA receives changes in incorporation and boundary lines from the Board of Equalization, who receives them from local jurisdictions for tax purposes. Boundary accuracy is not guaranteed, and though CDTFA works to align boundaries based on historical records and local changes, errors will exist. If you require a legal assessment of boundary location, contact a licensed surveyor.CDT GIS attached a GEOID attribute with the value ‘06’ to identify California and create ease of joins with other Census-based datasets. Finally, this layer removes the coastal buffer polygons and does not cut out the bay area water region. This feature layer is for public use.Related LayersThis dataset is part of a grouping of many datasets:Cities: Only the city boundaries and attributes, without any unincorporated areasWith Coastal BuffersWithout Coastal BuffersCounties: Full county boundaries and attributes, including all cities within as a single polygonWith Coastal BuffersWithout Coastal BuffersCities and Full Counties: A merge of the other two layers, so polygons overlap within city boundaries. Some customers require this behavior, so we provide it as a separate service.With Coastal BuffersWithout Coastal BuffersCity and County AbbreviationsUnincorporated Areas (Coming Soon)Census Designated PlacesCartographic CoastlinePolygonLine source (Coming Soon)State BoundaryWith Bay CutsWithout Bay Cuts (this dataset) Point of ContactCalifornia Department of Technology, Office of Digital Services, gis@state.ca.gov Field and Abbreviation DefinitionsCENSUS_GEOID: numeric geographic identifiers from the US Census Bureau Boundary AccuracyState boundary is created from county boundaries that were originally derived from a 1:24,000 accuracy dataset, with improvements made in some places to boundary alignments based on research into historical records and boundary changes as CDTFA learns of them. While CDTFA strives to correctly include or exclude parcels from jurisdictions for accurate tax assessment, this dataset does not guarantee that a parcel is placed in the correct jurisdiction. CDTFA's data is used as the best available source because BOE and CDTFA receive information about changes in jurisdictions which otherwise need to be collected independently by an agency or company to compile into usable map boundaries. CDTFA maintains the best available statewide boundary information. CDTFA's source data notes the following about accuracy (derived from the California County Boundaries and Identifiers): City boundary changes and county boundary line adjustments filed with the Board of Equalization per Government Code 54900. This GIS layer contains the boundaries of the unincorporated county and incorporated cities within the state of California. The initial dataset was created in March of 2015 and was based on the State Board of Equalization tax rate area boundaries. As of April 1, 2024, the maintenance of this dataset is provided by the California Department of Tax and Fee Administration for the purpose of determining sales and use tax rates. The boundaries are continuously being revised to align with aerial imagery when areas of conflict are discovered between the original boundary provided by the California State Board of Equalization and the boundary made publicly available by local, state, and federal government. Some differences may occur between actual recorded boundaries and the boundaries used for sales and use tax purposes. The boundaries in this map are representations of taxing jurisdictions for the purpose of determining sales and use tax rates and should not be used to determine precise city or county boundary line locations. Boundary ProcessingThese data make a structural change from the source data. While the full boundaries provided by CDTFA include coastal buffers of varying sizes, many users need boundaries to end at the shoreline of the ocean or a bay. As a result, after examining existing city and county boundary layers, these datasets provide a coastline cut generally along the ocean facing coastline. SliversIn cases where a city or county's boundary ends near a coastline, our coastline data may cross back and forth many times while roughly paralleling the jurisdiction"s boundary, resulting in many polygon slivers. We post-process the data to remove these slivers using a city/county boundary priority algorithm. That is, when the data run parallel to each other, we discard the coastline cut and keep the CDTFA-provided boundary, even if it extends into the ocean a small amount. This processing supports consistent boundaries for Fort Bragg, Point Arena, San Francisco, Pacifica, Half Moon Bay, and Capitola, in addition to others. More information on this algorithm will be provided soon. Coastline CaveatsSome cities have buffers extending into water bodies that we do not cut at the shoreline. These include South Lake Tahoe and Folsom, which extend into neighboring lakes, and San Diego and surrounding cities that extend into San Diego Bay, which our shoreline encloses. If you have feedback on the exclusion of these items, or others, from the shoreline cuts, please reach out using the contact information above. Offline UseThis service is fully enabled for sync and export using Esri Field Maps or other similar tools.

As of November 2023, this map has been updated to use a new format. For details, please see here.
Note: Due to the large file size the Shapefile export option does not work. To access geospatial data please select GeoJSON from the export menu

This data set includes the Office of the Assessor-Recorder’s secured property tax roll spanning from July 1, 2007 to June 30, 2023. It includes all legally disclosable information, including location of property, value of property, the unique property identifier, and specific property characteristics. The data is used to accurately and fairly appraise all taxable property in the City and County of San Francisco. The Office of the Assessor-Recorder makes no representation or warranty that the information provided is accurate and/or has no errors or omissions.

This dataset is updated annually after the roll is closed and certified. This typically happens by August of each year.