Land Joins GIS Layer is a spatial dataset that maps out how individual land parcels are connected—either by shared borders (adjacency) or by spatial relationships (e.g., overlapping, touching, or within a buffer). This layer is important for managing land ownership, supporting land development and planning infrastructure

The Kresge early childhood interactive map contains data relating to early childhood and education. It is meant to help stakeholders better understand the early childhood landscape better.

Feature layer generated from running the Join Features solution

A feature layer join view used to display information about use of force incidents by person subjected to force. This layer is used for public-facing apps and open data.The view joins the Incidents point layer to the Subject table, both from the UseOfForce feature layer, using a one-to-many relationship based on the agency_case_number field.

Feature layer generated from running the Join Features solution

Feature layer generated from running the Join Features solution

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.

Purpose

City 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 Layers

This dataset is part of a grouping of many datasets:

1. Cities: Only the city boundaries and attributes, without any unincorporated areas
   • With Coastal Buffers
   • Without Coastal Buffers (this dataset)
2. Counties: Full county boundaries and attributes, including all cities within as a single polygon
   • With Coastal Buffers
   • Without Coastal Buffers
3. 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 Buffers
   • Without Coastal Buffers
4. City and County Abbreviations
5. Unincorporated Areas (Coming Soon)
6. Census Designated Places
7. Cartographic Coastline
   • Polygon
   • Line source (Coming Soon)

Point of Contact

California Department of Technology, Office of Digital Services, odsdataservices@state.ca.gov

Field and Abbreviation Definitions

• CDTFA_CITY: CDTFA incorporated city name
• CDTFA_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 Bureau
• CENSUS_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 System
• GNIS_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_CITY_ABBR: Abbreviations of incorporated area names - originally derived from CalTrans Division of Local Assistance and now managed by CDT. Abbreviations are 4 characters. Not present in the county-specific layers.
• 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 county
• CENSUS_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

The blank geodatabase has the required fields for submitting wetland determination polygons and requested map edits for the Vermont Significant Wetlands Inventory. The valid NWI codes are included in the a separate table inside the file geodatabase. Consider joining the Wetland Program's ArcGIS Online Group for submitting determination or wetlands edits. If your organization has an ArcGIS organizational account, make a request to join this group:https://www.arcgis.com/home/group.html?id=164aab9de6e44ec79aa0dfa7ee41dfcb#overviewJoin a groupTo join a group, do the following:Verify that you are signed in.Click Groups at the top of the site, and use the tabs, filters, sort options, and search as needed to find the group you want to join.Click the name of the group to open its group page.On the Overview tab, click Join this group. If necessary, click Submit Request.Depending on the group's membership settings, you will see a message indicating that you are now a member of the group or that your request has been sent to the group owner (after clicking Submit Request). If a request is sent, the owner of the group sees it on the group page and accepts or denies your request for membership. If the owner accepts your request, you are added as a member, and the group appears on your Groups page.

Feature layer generated from running the Join Features solution

This layer package contains GIS data in Esri file geodatabase format. This data is also available for download as a zip archive in shapefile format.Digital parcel files for the Town of Amherst, MA as of December 31, 2013. The Town converted its existing analog tax maps to digital format in 1998. At the time of conversion, tax maps consisted of 108 27"x39" mylar sheets at 1"=100', originally created in 1957 from controlled and rectified photography taken by Air Survey Inc. (VA) in 1956. The tax maps were scanned, and digital line files were created with text annotation. The new line files were then overlayed onto digital color orthophotos produced in 1999, and updated, by first matching road right-of-ways, then adjusting all parcel boundaries. This data set is a spatial view that is created through a one-to-many join between TOA_Parcels_Poly and TOA_CAMA_TABLE. The join is through Map & Lot, which creates stacked parcel polygons in cases where there are multiple block numbers (accounts) for one parcel; this occurs primarily with condominium complexes, as well as with properties with agricultural preservation restrictions. This data set is refreshed on a nightly basis & reflects current information from the Town of Amherst Assessor's Vision Appraisal Database.

Road centerlines with road names and generalized classifications is a snapshot from our spatial roads (addressing) dataset. Maintenance data was pulled from the Borough asset management software, Cartegraph, which is non-spatial. The non-spatial maintenance data was then tied to the spatial roads data through a series of joins and analyses.Roads with multiple maintenance groups listed have shared maintenance responsibilities; for example 1/2 the road may be maintained by the Borough and the other 1/2 maintained by a city. More detailed information regarding the distances each maintenance group is responsible for can be looked up in the Cartegraph database. This more detailed information can not currently be mapped due to differences in design between the spatial roads (911 addressing) dataset and the Cartegraph database.This dataset does not have a scheduled update cycle and should be viewed as just a snapshot in time. It was last updated in Sept 2017.

Feature layer generated from running the Join Features solution

Feature layer generated from running the Join Features solution

Feature layer generated from running the Join Features solution

Feature layer generated from running the Find Centroids solution for Join_Features_to_NYS_Civil_Boundaries_SHP_Counties_Shoreline - copy.

A feature layer join view used to display information about use of force incidents by officer involved. This layer is used for public-facing apps and open data.The view joins the Incidents point layer to the Officers table, both from the UseOfForce feature layer, using a one-to-many relationship based on the agency_case_number field.

Feature layer generated from running the Join Features solution

Feature layer generated from running the Find Centroids solution for Join_CSC_Features_to_NYS_Civil_Boundaries_SHP_Cities_Towns.

Feature layer generated from running the Join Features solution

Feature layer generated from running the Join Features solution