Data scraped from https://census.gov.

Features: * COUNTY: County name * STATE: state county is located in * GEOID: county geoid * DESCRIPTION: county LSAD description * CLASS: county class code * CSA: combined statistical area id * CBSA: core based statistical area id * LAND_AREA: land area in square meters * WATER_AREA: water area in square meters * COORDINATES: geographical coordinates of county * BORDERS: county border shape (polygon)

Field Definition:GEOID - "Census tract identifier; a concatenation of 2020 Census state FIPS code, county FIPS code, and census tract code"NAMELSAD - Census translated legal/statistical area description and the census tract nameALAND - Census Area LandAWATER - Census Area waterINTPTLAT - Census Internal Point (Latitude)INTPTLON - Census Internal Point (Longitude)NAME20 - "2020 Census tract name, this is the census tract code converted to an integer or integer plus two-digit decimal if the last two characters of the code are not both zeros"POPULATION - Total PopulationP18PLUS - Population 18 years and olderHHPOP - Household PopulationGQ - Group Quarters PopulationHOUSING - Total Housing unitsOCCUNITS - Occupied Housing Units (Households)VACUNITS - Vacant Housing UnitsVACRATE -Vacancy RateHISPANIC - Hispanic or Latino NH_WHT - Not Hispanic or Latino, White alone NH_BLK - Not Hispanic or Latino, Black or African American alone NH_IND - Not Hispanic or Latino, American Indian and Alaska Native aloneNH_ASN - Not Hispanic or Latino, Asian aloneNH_HWN - Not Hispanic or Latino, Native Hawaiian and Other Pacific Islander alone NH_OTH - Not Hispanic or Latino, Some Other Race alone NH_TWO - Not Hispanic or Latino, Population of two or more races

US Northeast Census Tracts contains the US Census tract geometries used as the unit of analysis for network metrics. The file "northeast_tracts.shp" includes a merged dataset with the borders of all census tracts in Connecticut, Maine, Massachusetts, New Hampshire, New York, Rhode Island, and Vermont. All other files in this repository are the original state-by-state sources used to create the final merged dataset. Census Tracts The 2020 census tract file is based on the 2020 Census. The following fields are included: USPS: United States Postal Service state abbreviation. GEOID: Geographic identifier — fully concatenated geographic code (State FIPS, County FIPS, Census Tract number). GEOIDFQ: Fully qualified geographic identifier — used to join with data.census.gov data tables. ALAND: Land area (square meters) — created for statistical purposes only. AWATER: Water area (square meters) — created for statistical purposes only. ALAND_SQMI: Land area (square miles) — created for statistical purposes only. AWATER_SQMI: Water area (square miles) — created for statistical purposes only. INTPTLAT: Latitude (decimal degrees). The first character is blank or “–” denoting North or South latitude respectively. INTPTLONG: Longitude (decimal degrees). The first character is blank or “–” denoting East or West longitude respectively. The .shp file in this repository includes its required companion files for correct GIS operation: .shx (spatial index), .dbf (attribute table), .prj (projection information), and .cpg (character encoding).

USE geoid TO JOIN DATA DOWNLOADED FROM DATA.CENSUS.GOV The TIGER/Line Shapefiles are extracts of selected geographic and cartographic information from the Census Bureau's Master Address File (MAF)/Topologically Integrated Geographic Encoding and Referencing (TIGER) System (MTS). The TIGER/Line Shapefiles contain a standard geographic identifier (GEOID) for each entity that links to the GEOID in the data from censuses and surveys. The TIGER/Line Shapefiles do not include demographic data from surveys and censuses (e.g., Decennial Census, Economic Census, American Community Survey, and the Population Estimates Program). Other, non-census, data often have this standard geographic identifier as well. Data from many of the Census Bureau’s surveys and censuses, including the geographic codes needed to join to the TIGER/Line Shapefiles, are available at the Census Bureau’s public data dissemination website (https://data.census.gov/). Public Use Microdata Areas (PUMAs) are statistical geographic areas for the dissemination of decennial census and American Community Survey (ACS) Public Use Microdata Sample files in which the Census Bureau provides selected extracts of raw data from a small sample of census records that are screened to protect confidentiality. The ACS also uses the PUMAs as a tabulation geographic entity. For the 2020 Census, the State Data Centers in each state, the District of Columbia, and Puerto Rico are involved in the delineation of the 2020 PUMAs. Counties and census tracts are used to define PUMAs, and each PUMA must include at least 100,000 people based on the 2020 Census published counts. For the 2020 Census in Guam and the U.S. Virgin Islands, the Census Bureau establishes a single, separate PUMA for each of these two Island Areas. American Samoa and the Commonwealth of the Northern Mariana Islands do not have PUMAs, because the total population of each is under 100,000 people. Downloaded from https://www2.census.gov/geo/tiger/TIGER2022/PUMA/ on June 22, 2023

Standard block groups are clusters of blocks within the same census tract that have the same first digit of their 4-character census block number (e.g., Blocks 3001, 3002, 3003 to 3999 in census tract 1210.02 belong to block group 3). Current block groups do not always maintain these same block number to block group relationships due to boundary and feature changes that occur throughout the decade. For example, block 3001 might move due to a change in the census tract boundary. Even if the block is no longer in block group 3, the block number (3001) will not change. However, the GEOID for that block, identifying block group 3, would remain the same in the attribute information in the TIGER/Line Shapefiles because block GEOIDs are always built using the decennial geographic codes.Block groups delineated for the 2020 Census generally contain 600 to 3,000 people. Local participants delineated most block groups as part of the Census Bureau's PSAP. The Census Bureau delineated block groups only where a local or tribal government declined to participate or where the Census Bureau could not identify a potential local participant.A block group usually covers a contiguous area. Each census tract contains one or more block groups and block groups have unique numbers within census tract. Within the standard census geographic hierarchy, block groups never cross county or census tract boundaries, but may cross the boundaries of county subdivisions, places, urban areas, voting districts, congressional districts, and AIANNH areas.Block groups have a valid range of zero (0) through nine (9). Block groups beginning with a zero generally are in coastal and Great Lakes water and territorial seas. Rather than extending a census tract boundary into the Great Lakes or out to the 3-mile territorial sea limit, the Census Bureau delineated some census tract boundaries along the shoreline or just offshore.

USE geoid TO JOIN DATA DOWNLOADED FROM DATA.CENSUS.GOV The TIGER/Line Shapefiles are extracts of selected geographic and cartographic information from the Census Bureau's Master Address File (MAF)/Topologically Integrated Geographic Encoding and Referencing (TIGER) System (MTS). The TIGER/Line Shapefiles contain a standard geographic identifier (GEOID) for each entity that links to the GEOID in the data from censuses and surveys. The TIGER/Line Shapefiles do not include demographic data from surveys and censuses (e.g., Decennial Census, Economic Census, American Community Survey, and the Population Estimates Program). Other, non-census, data often have this standard geographic identifier as well. Data from many of the Census Bureau’s surveys and censuses, including the geographic codes needed to join to the TIGER/Line Shapefiles, are available at the Census Bureau’s public data dissemination website (https://data.census.gov/). The primary legal divisions of most states are termed counties. In Louisiana, these divisions are known as parishes. In Alaska, which has no counties, the equivalent entities are the organized boroughs, city and boroughs, municipalities, and census areas; the latter of which are delineated cooperatively for statistical purposes by the State of Alaska and the Census Bureau. Additionally, the Census Bureau treats the following entities as equivalents of counties for purposes of data presentation: municipios in Puerto Rico, districts and islands in American Samoa, municipalities in the Commonwealth of the Northern Mariana Islands, and islands in the U.S. Virgin Islands. In four states (Maryland, Missouri, Nevada, and Virginia), there are one or more incorporated places that are independent of any county organization and, thus, constitute primary divisions of their states. These incorporated places are known as independent cities and are treated as equivalent entities for purposes of data presentation. The District of Columbia and Guam have no primary divisions, and each area is considered an equivalent entity for purposes of data presentation in decennial censuses. All of the counties in Connecticut and Rhode Island and nine counties in Massachusetts were dissolved as functioning governmental entities; however, the Census Bureau continues to present data for these historical entities in order to provide comparable geographic units at the county level of the geographic hierarchy for these states and represents them as nonfunctioning legal entities in data products. Each county or statistically equivalent entity is assigned a three-character numeric Federal Information Processing Series (FIPS) code based on alphabetical sequence that is unique within state, and an eight-digit National Standard (NS) code. Downloaded from https://www2.census.gov/geo/tiger/TIGER2022/COUNTY/ on June 22, 2023

GEOID - Census geographic record identifier, a concatenation of 2020 Census state FIPS code, county FIPS code, census tract code, census block group code, and census block code"NAME20 - 2020 Census block nameSTATE – State FIPS codeCOUNTY - County FIPS codePLACE - Place FIPS codeTRACT - Census Tract codeBLKGRP - Block Group codeBLOCK - Block codePOPULATION - Total PopulationHOUSING - Total Housing unitsOCCUPIED_H - Occupied Housing Units (Households)VACANT_H - Vacant Housing Units

Context

The emergence in the United States of large-scale “megaregions” centered on major metropolitan areas is a phenomenon often taken for granted in both scholarly studies and popular accounts of contemporary economic geography.

This dataset comes from a paper (Nelson & Rae, 2016. An Economic Geography of the United States: From Commutes to Megaregions) that uses a data set of more than 4,000,000 commuter flows as the basis for an empirical approach to the identification of such megaregions.

Content

This dataset consists of two files: one contains the commuting data, and one is a gazetteer describing the population and locations of the census tracts referred to by the commuting data. The fields Ofips and Dfips (FIPS codes for the originating and destination census tracts, respectively) in commute_data.csv refer to the GEOID field in census_tracts_2010.csv.

commute_data

This file contains information on over 4 million commute flows. It has the following fields:

• Ofips: the full FIPS code for the origin census tract of an individual flow line
• **Dfips **: the full FIPS code for the destination census tract of an individual flow line
• Ostfips: the FIPS code for the origin state of an individual flow line
• Octfips: the FIPS code for the origin county of an individual flow line
• Otrfips: the FIPS code for the destination census tract of an individual flow line
• Dstfips: the FIPS code for the destination state of an individual flow line
• Dctfips: the FIPS code for the destination county of an individual flow line
• Dtrfips: the FIPS code for the destination census tract of an individual flow line
• Flow: the total number of commuters associated with this individual point to point flow line (i.e. the total number of journeys to work)
• Moe: margin of error of the Flow value above
• LenKM: length of each flow line, in Kilometers
• ESTDIVMOE: the Flow value divided by the Margin of Error of the estimate

census_tracts_2010

This file contains the following fields, which represent information about different U.S. Census Tracts:

• USPS: United States Postal Service State Abbreviation
• GEOID: Geographic Identifier - fully concatenated geographic code (State FIPS and County FIPS)
• ANSICODE: American National Standards Institute code
• NAME: Name
• POP10: 2010 Census population count.
• HU10: 2010 Census housing unit count.
• ALAND: Land Area (square meters) - Created for statistical purposes only.
• AWATER: Water Area (square meters) - Created for statistical purposes only.
• ALAND_SQMI: Land Area (square miles) - Created for statistical purposes only.
• AWATER_SQMI: Water Area (square miles) - Created for statistical purposes only.
• INTPTLAT: Latitude (decimal degrees) First character is blank or "-" denoting North or South latitude respectively.
• INTPTLONG: Longitude (decimal degrees) First character is blank or "-" denoting East or West longitude respectively.

Acknowledgements

This dataset comes from the following article:

Nelson & Rae, 2016. An Economic Geography of the United States: From Commutes to Megaregions

The full dataset (in GIS shapefile format) can be found on figshare here

This data layer is an element of the Oregon GIS Framework. The TIGER/Line shapefiles and related database files (.dbf) are an extract of selected geographic and cartographic information from the U.S. Census Bureau's Master Address File / Topologically Integrated Geographic Encoding and Referencing (MAF/TIGER) Database (MTDB). The MTDB represents a seamless national file with no overlaps or gaps between parts, however, each TIGER/Line shapefile is designed to stand alone as an independent data set, or they can be combined to cover the entire nation.

Census tracts are small, relatively permanent statistical subdivisions of a county or equivalent entity, and were defined by local participants as part of the 2020 Census Participant Statistical Areas Program. The Census Bureau delineated the census tracts in situations where no local participant existed or where all the potential participants declined to participate. The primary purpose of census tracts is to provide a stable set of geographic units for the presentation of census data and comparison back to previous decennial censuses. Census tracts generally have a population size between 1,200 and 8,000 people, with an optimum size of 4,000 people. When first delineated, census tracts were designed to be homogeneous with respect to population characteristics, economic status, and living conditions. The spatial size of census tracts varies widely depending on the density of settlement. Physical changes in street patterns caused by highway construction, new development, and so forth, may require boundary revisions. In addition, census tracts occasionally are split due to population growth, or combined as a result of substantial population decline. Census tract boundaries generally follow visible and identifiable features. They may follow legal boundaries such as minor civil division (MCD) or incorporated place boundaries in some States and situations to allow for census tract-to-governmental unit relationships where the governmental boundaries tend to remain unchanged between censuses. State and county boundaries always are census tract boundaries in the standard census geographic hierarchy. In a few rare instances, a census tract may consist of noncontiguous areas. These noncontiguous areas may occur where the census tracts are coextensive with all or parts of legal entities that are themselves noncontiguous. For the 2010 Census and beyond, the census tract code range of 9400 through 9499 was enforced for census tracts that include a majority American Indian population according to Census 2000 data and/or their area was primarily covered by federally recognized American Indian reservations and/or off-reservation trust lands; the code range 9800 through 9899 was enforced for those census tracts that contained little or no population and represented a relatively large special land use area such as a National Park, military installation, or a business/industrial park; and the code range 9900 through 9998 was enforced for those census tracts that contained only water area, no land area.

USE geoid TO JOIN DATA DOWNLOADED FROM DATA.CENSUS.GOV The TIGER/Line Shapefiles are extracts of selected geographic and cartographic information from the Census Bureau's Master Address File (MAF)/Topologically Integrated Geographic Encoding and Referencing (TIGER) System (MTS). The TIGER/Line Shapefiles contain a standard geographic identifier (GEOID) for each entity that links to the GEOID in the data from censuses and surveys. The TIGER/Line Shapefiles do not include demographic data from surveys and censuses (e.g., Decennial Census, Economic Census, American Community Survey, and the Population Estimates Program). Other, non-census, data often have this standard geographic identifier as well. Data from many of the Census Bureau’s surveys and censuses, including the geographic codes needed to join to the TIGER/Line Shapefiles, are available at the Census Bureau’s public data dissemination website (https://data.census.gov/). ZIP Code Tabulation Areas (ZCTAs) are approximate area representations of U.S. Postal Service (USPS) five-digit Zonal Improvement Plan (ZIP) Code service routes that the Census Bureau creates using whole blocks to present statistical data from censuses and surveys. The Census Bureau defines ZCTAs by allocating each block that contains addresses to a single ZCTA, usually to the ZCTA that reflects the most frequently occurring ZIP Code for the addresses within that tabulation block. Blocks that do not contain addresses, but are surrounded by a single ZCTA (enclaves) are assigned to the surrounding ZCTA; those surrounded by multiple ZCTAs are added to a single ZCTA based on limited buffering performed between multiple ZCTAs. The Census Bureau identifies five-digit ZCTAs using a five-character numeric code that represents the most frequently occurring USPS ZIP Code within that ZCTA, and this code has a fixed length of five digits and may contain leading zeros. Not all ZIP Codes in use by the USPS may have a ZCTA delineated to represent them, The USPS makes periodic changes to ZIP Codes to support more efficient mail delivery. In addition, the ZCTA delineation process primarily uses residential addresses and has a bias towards ZIP Codes used for city-style mail delivery, thus there may be ZIP Codes that are primarily nonresidential or used for PO boxes only that may not have a corresponding ZCTA. ZIP Code is a trademark of the U.S. Postal Service. Downloaded from https://www2.census.gov/geo/tiger/TIGER2022/ZCTA520/ on June 22, 2023

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 Buffers Counties: 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 Places (this dataset)Cartographic CoastlinePolygonLine source (Coming Soon)State BoundaryWith Bay CutsWithout Bay Cuts Point of ContactCalifornia Department of Technology, Office of Digital Services, gis@state.ca.gov Field and Abbreviation DefinitionsPLACENS: An assigned an eight-digit National Standard (NS) code.GEOID: Place identifier; a concatenation of the current state FIPS code and place FIPS codeGEOIDFQ: facilitates joining Census Bureau spatial data to Census Bureau summary file data from data.census.govNAMELSAD: describe the particular typology for each geographic entity.CLASSFP: defines the current FIPS class of a geographic entity.FUNCSTAT: defines the current functional status of a geographic entity.ALAND: Current land areaAWATER: Current water area INTPTLAT: Current latitude of the internal point INTPTLON: Current longitude of the internal point Offline UseThis service is fully enabled for sync and export using Esri Field Maps or other similar tools. Importantly, the GlobalID field exists only to support that use case and should not be used for any other purpose (see note in field descriptions). Updates and Date of Processing(Section coming soon)

Context

This is the 24th decennial US Census. The data was released on August 12, 2021 to public

Content

The dataset contains 12 GB of complete US Census data of 2020 of all 50 states. Column headers for each state file are given below:

FILEID File Identification STUSAB State/US-Abbreviation (USPS) SUMLEV Summary Level GEOVAR Geographic Variant GEOCOMP Geographic Component CHARITER Characteristic Iteration CIFSN Characteristic Iteration File Sequence Number LOGRECNO Logical Record Number GEOID Geographic Record Identifier GEOCODE Geographic Code Identifier REGION Region DIVISION Division STATE State (FIPS) STATENS State (NS) COUNTY County (FIPS) COUNTYCC FIPS County Class Code COUNTYNS County (NS) COUSUB County Subdivision (FIPS) COUSUBCC FIPS County Subdivision Class Code COUSUBNS County Subdivision (NS) SUBMCD Subminor Civil Division (FIPS) SUBMCDCC FIPS Subminor Civil Division Class Code SUBMCDNS Subminor Civil Division (NS) ESTATE Estate (FIPS) ESTATECC FIPS Estate Class Code ESTATENS Estate (NS) CONCIT Consolidated City (FIPS) CONCITCC FIPS Consolidated City Class Code CONCITNS Consolidated City (NS) PLACE Place (FIPS) PLACECC FIPS Place Class Code PLACENS Place (NS) TRACT Census Tract BLKGRP Block Group BLOCK Block AIANHH American Indian Area/Alaska Native Area/Hawaiian Home Land (Census) AIHHTLI American Indian Trust Land/Hawaiian Home Land Indicator AIANHHFP American Indian Area/Alaska Native Area/Hawaiian Home Land (FIPS) AIANHHCC FIPS American Indian Area/Alaska Native Area/Hawaiian Home Land Class Code AIANHHNS American Indian Area/Alaska Native Area/Hawaiian Home Land (NS) AITS American Indian Tribal Subdivision (Census) AITSFP American Indian Tribal Subdivision (FIPS) AITSCC FIPS American Indian Tribal Subdivision Class Code AITSNS American Indian Tribal Subdivision (NS) TTRACT Tribal Census Tract TBLKGRP Tribal Block Group ANRC Alaska Native Regional Corporation (FIPS) ANRCCC FIPS Alaska Native Regional Corporation Class Code ANRCNS Alaska Native Regional Corporation (NS) CBSA Metropolitan Statistical Area/Micropolitan Statistical Area MEMI Metropolitan/Micropolitan Indicator CSA Combined Statistical Area METDIV Metropolitan Division NECTA New England City and Town Area NMEMI NECTA Metropolitan/Micropolitan Indicator CNECTA Combined New England City and Town Area NECTADIV New England City and Town Area Division CBSAPCI Metropolitan Statistical Area/Micropolitan Statistical Area Principal City Indicator NECTAPCI New England City and Town Area Principal City Indicator UA Urban Area UATYPE Urban Area Type UR Urban/Rural CD116 Congressional District (116th) CD118 Congressional District (118th) CD119 Congressional District (119th) CD120 Congressional District (120th) CD121 Congressional District (121st) SLDU18 State Legislative District (Upper Chamber) (2018) SLDU22 State Legislative District (Upper Chamber) (2022) SLDU24 State Legislative District (Upper Chamber) (2024) SLDU26 State Legislative District (Upper Chamber) (2026) SLDU28 State Legislative District (Upper Chamber) (2028) SLDL18 State Legislative District (Lower Chamber) (2018) SLDL22 State Legislative District (Lower Chamber) (2022) SLDL24 State Legislative District (Lower Chamber) (2024) SLDL26 State Legislative District (Lower Chamber) (2026) SLDL28 State Legislative District (Lower Chamber) (2028) VTD Voting District VTDI Voting District Indicator ZCTA ZIP Code Tabulation Area (5-Digit) SDELM School District (Elementary) SDSEC School District (Secondary) SDUNI School District (Unified) PUMA Public Use Microdata Area AREALAND Area (Land) AREAWATR Area (Water) BASENAME Area Base Name NAME Area Name-Legal/Statistical Area Description (LSAD) Term-Part Indicator FUNCSTAT Functional Status Code GCUNI Geographic Change User Note Indicator POP100 Population Count (100%) HU100 Housing Unit Count (100%) INTPTLAT Internal Point (Latitude) INTPTLON Internal Point (Longitude) LSADC Legal/Statistical Area Descrip...

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 2024. Expected changes:Metadata is missing or incomplete for some layers at this time and will be continuously improved.We expect to update this layer roughly in line with CDTFA at some point, but will increase the update cadence over time as we are able to automate the final pieces of the process.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 and incorporated place (city) boundaries along with third party identifiers used to join in external data. Boundaries are from the authoritative source the California Department of Tax and Fee Administration (CDTFA), altered to show the counties as one polygon. This layer displays the city polygons on top of the County polygons so the area isn"t interrupted. The GEOID attribute information is added from the US Census. GEOID is based on merged State and County FIPS codes for the Counties. Abbreviations for Counties and Cities were added from Caltrans Division of Local Assistance (DLA) data. Place Type was populated with information extracted from the Census. Names and IDs from the US Board on Geographic Names (BGN), the authoritative source of place names as published in the Geographic Name Information System (GNIS), are attached as well. Finally, the coastline is used to separate coastal buffers from the land-based portions of jurisdictions. 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 Buffers (this dataset)Without Coastal BuffersPlace AbbreviationsUnincorporated Areas (Coming Soon)Census Designated Places (Coming Soon)Cartographic CoastlinePolygonLine source (Coming Soon)Working with Coastal BuffersThe dataset you are currently viewing includes the coastal buffers for cities and counties that have them in the authoritative 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 COASTAL, Area_SqMi, Shape_Area, and Shape_Length to get a version with the correct identifiers.Point of ContactCalifornia Department of Technology, Office of Digital Services, odsdataservices@state.ca.govField and Abbreviation DefinitionsCOPRI: county number followed by the 3-digit city primary number used in the Board of Equalization"s 6-digit tax rate area numbering systemPlace Name: CDTFA incorporated (city) or county nameCounty: 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.Legal 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.GEOID: numeric geographic identifiers from the US Census Bureau Place Type: Board on Geographic Names authorized nomenclature for boundary type published in the Geographic Name Information SystemPlace Abbr: CalTrans Division of Local Assistance abbreviations of incorporated area namesCNTY Abbr: CalTrans Division of Local Assistance abbreviations of county namesArea_SqMi: The area of the administrative unit (city or county) in square miles, calculated in EPSG 3310 California Teale Albers.COASTAL: Indicates if the polygon is a coastal buffer. Null for land polygons. Additional values include "ocean" and "bay".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.AccuracyCDTFA"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. COUNTY = county name; CITY = city name or unincorporated territory; COPRI = county number followed by the 3-digit city primary number used in the California State Board of Equalization"s 6-digit tax rate area numbering system (for the purpose of this map, unincorporated areas are assigned 000 to indicate that the area is not within a city).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 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. Importantly, the GlobalID field exists only to support that use case and should not be used for any other purpose (see note in field descriptions).Updates and Date of ProcessingConcurrent with CDTFA updates, approximately every two weeks, Last Processed: 12/17/2024 by Nick Santos using code path at https://github.com/CDT-ODS-DevSecOps/cdt-ods-gis-city-county/ at commit 0bf269d24464c14c9cf4f7dea876aa562984db63. It incorporates updates from CDTFA as of 12/12/2024. Future updates will include improvements to metadata and update frequency.

A. SUMMARY Census tracts boundaries in San Francisco county. Census tracts are small, relatively permanent statistical subdivisions of a county. They are uniquely numbered in each county with a numeric code. Census tracts average about 4,000 inhabitants ranging from 1,200 – 8,000. More information on the census tracts can be found here.

B. HOW THE DATASET IS CREATED The boundaries are uploaded from TIGER/Line shapefiles provided by the U.S. Census Bureau.

C. UPDATE PROCESS This dataset is static. Changes to the census tract boundaries are tracked in multiple datasets. See here for 2000 and 2010 census tract boundaries.

D. HOW TO USE THIS DATASET This boundary file can be joined to other census datasets on GEOID.

E. RELATED DATASET 2020 Census Tracts and Analysis Neighborhoods

Census Tracts from the 2020 US Census for New York City clipped to the shoreline. These boundary files are derived from the US Census Bureau's TIGER project and have been geographically modified to fit the New York City base map. Because some census tracts are under water not all census tracts are contained in this file, only census tracts that are partially or totally located on land have been mapped in this file.

All previously released versions of this data are available on the DCP Website: BYTES of the BIG APPLE. Current version: 25d

The classification of land according to what activities take place on it or how it is being used; for example, agricultural, industrial, residential, rural, or commercial. Land use information and analysis is a fundamental tool in the planning process.

DVRPC’s 2020 land use file is based on digital orthophotography created from aerial surveillance completed in the spring of 2020. This dataset supports many of DVRPC's planning analysis goals.

Every five years, since 1990, the Delaware Valley Regional Planning Commission (DVRPC) has produced a GIS Land Use layer for its 9-county region.

lu20cat: Land use main category two-digit code.

lu20catn: Land use main category name.

lu20cat

lu20catn

1 - Residential

3 - Industrial

4 - Transportation

5 - Utility

6 - Commercial

7 - Institutional

8 - Military

9 - Recreation

10 - Agriculture

11 - Mining

12 - Wooded

13 - Water

14 - Undeveloped

lu20sub: Land use subcategory five-digit code. (refer to this data dictionary for code description)

lu20subn: Land use subcategory name.

lu20dev: Development status.

mixeduse: Mixed-Use status (Y/N). Features belonging to one of the Mixed-Use subcategories (Industrial: Mixed-Use, Multifamily Residential: Mixed-Use, or Commercial: Mixed-Use).

acres: Area of feature, in US acres.

geoid: 10-digit geographic identifier. In all DVRPC counties other than Philadelphia, a GEOID is assigned by municipality. In Philadelphia, it is assigned by County Planning Area (CPA).

state_name, co_name, mun_name: State name, county name, municipal/CPA name. In Philadelphia, County Planning Area (CPA) names are used in place of municipal names.

This layer was developed by the Research & Analytics Group of the Atlanta Regional Commission, using data from the U.S. Census Bureau’s American Community Survey 5-year estimates for 2013-2017, to show populations with computer and internet access by Zip Code Tabulation Area in the Atlanta region.

The user should note that American Community Survey data represent estimates derived from a surveyed sample of the population, which creates some level of uncertainty, as opposed to an exact measure of the entire population (the full census count is only conducted once every 10 years and does not cover as many detailed characteristics of the population). Therefore, any measure reported by ACS should not be taken as an exact number – this is why a corresponding margin of error (MOE) is also given for ACS measures. The size of the MOE relative to its corresponding estimate value provides an indication of confidence in the accuracy of each estimate. Each MOE is expressed in the same units as its corresponding measure; for example, if the estimate value is expressed as a number, then its MOE will also be a number; if the estimate value is expressed as a percent, then its MOE will also be a percent.

The user should also note that for relatively small geographic areas, such as census tracts shown here, ACS only releases combined 5-year estimates, meaning these estimates represent rolling averages of survey results that were collected over a 5-year span (in this case 2013-2017). Therefore, these data do not represent any one specific point in time or even one specific year. For geographic areas with larger populations, 3-year and 1-year estimates are also available.

For further explanation of ACS estimates and margin of error, visit Census ACS website.

Naming conventions:

Prefixes:

None

Count

p

Percent

r

Rate

m

Median

a

Mean (average)

t

Aggregate (total)

ch

Change in absolute terms (value in t2 - value in t1)

pch

Percent change ((value in t2 - value in t1) / value in t1)

chp

Change in percent (percent in t2 - percent in t1)

Suffixes:

None

Change over two periods

_e

Estimate from most recent ACS

_m

Margin of Error from most recent ACS

_00

Decennial 2000

Attributes:

SumLevel

Summary level of geographic unit (e.g., County, Tract, NSA, NPU, DSNI, SuperDistrict, etc)

GEOID

Census tract Federal Information Processing Series (FIPS) code

NAME

Name of geographic unit

Planning_Region

Planning region designation for ARC purposes

Acres

Total area within the tract (in acres)

SqMi

Total area within the tract (in square miles)

County

County identifier (combination of Federal Information Processing Series (FIPS) codes for state and county)

CountyName

County Name

TotalHH_e

# Total households, 2017

TotalHH_m

# Total households, 2017 (MOE)

WithAComputer_e

# Households with a computer, 2017

WithAComputer_m

# Households with a computer, 2017 (MOE)

pWithAComputer_e

% Households with a computer, 2017

pWithAComputer_m

% Households with a computer, 2017 (MOE)

WithBroadband_e

# Households with broadband Internet, 2017

WithBroadband_m

# Households with broadband Internet, 2017 (MOE)

pWithBroadband_e

% Households with broadband Internet, 2017

pWithBroadband_m

% Households with broadband Internet, 2017 (MOE)

last_edited_date

Last date the feature was edited by ARC

Source: U.S. Census Bureau, Atlanta Regional Commission

Date: 2013-2017

For additional information, please visit the Census ACS website.

The 2020 Census Redistricting Summary File contains several hundred data fields spread over six different file segments. To facilitate access to more popular variables, the Tennessee State Data Center compiled a “QuickStat” reports detailing population, race/ethnicity and housing information. These fields are combined with geographic fields from the 2020 TIGER/Line Shapefiles for use with mapping software.Field names, descriptions and types selected from the two sources are detailed below.

      Field Name
      Alias
      Data Type
      Length


      OBJECTID

      Object ID



      Shape

      Geometry



      STATEFP
      State FIPS code
      Text
      2


      COUNTYFP
      County FIPS code
      Text
      3


      TRACTCE
      Tract code
      Text
      6


      GEOID
      Geographic identifier
      Text
      12


      NAME
      Name
      Text
      7


      NAMELSAD
      Legal/statistical area description
      Text
      13


      MTFCC
      MAF/TIGER feature class code
      Text
      5


      FUNCSTAT
      Functional status
      Text
      1


      ALAND
      Land area
      Long



      AWATER
      Water area
      Long



      INTPTLAT
      Latitude of the internal point
      Text
      11


      INTPTLON
      Longitude of the internal point
      Text
      12


      SUMLEV
      Summary Level
      Text
      3


      LOGRECNO
      Logical Record Number
      Long



      P0010001
      Total population
      Long



      P0010002
      Population of one race
      Long



      P0010003
      White alone
      Long



      P0010004
      Black or African American alone
      Long



      P0010005
      American Indian and Alaska Native alone
      Long



      P0010006
      Asian alone
      Long



      P0010007
      Native Hawaiian and Other Pacific Islander alone
      Long



      P0010008
      Some Other Race alone
      Long



      P0010009
      Population of two or more races:
      Long



      P0020002
      Hispanic or Latino
      Long



      P0020003
      Not Hispanic or Latino:
      Long



      P0020004
      Population of one race (Not Hispanic or Latino)
      Long



      P0020005
      White alone (Not Hispanic or Latino)
      Long



      P0020006
      Black or African American alone (Not Hispanic or Latino)
      Long



      P0020007
      American Indian and Alaska Native alone (Not Hispanic or Latino)
      Long



      P0020008
      Asian alone (Not Hispanic or Latino)
      Long



      P0020009
      Native Hawaiian and Other Pacific Islander alone (Not Hispanic or Latino)
      Long



      P0020010
      Some Other Race alone (Not Hispanic or Latino)
      Long



      P0020011
      Population of two or more races (Not Hispanic or Latino)
      Long



      P0030001
      Total population 18 years and over
      Long



      H0010001
      Total housing units
      Long



      H0010002
      Occupied housing units
      Long



      H0010003
      Vacant housing units
      Long



      P0050001
      Total population in group quarters
      Long



      P0050002
      Institutionalized population
      Long



      P0050003
      Correctional facilities for adults
      Long



      P0050004
      Juvenile facilities
      Long



      P0050005
      Nursing facilities/Skilled-nursing facilities
      Long



      P0050006
      Other institutional facilities
      Long



      P0050007
      Noninstitutionalized population
      Long



      P0050008
      College/University student housing
      Long



      P0050009
      Military quarters
      Long



      P0050010
      Other noninstitutional facilities
      Long



      Shape_Length

      Double



      Shape_Area

      Double

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 2024. Expected changes:

• Metadata is missing or incomplete for some layers at this time and will be continuously improved.
  
• We expect to update this layer roughly in line with CDTFA at some point, but will increase the update cadence over time as we are able to automate the final pieces of the process.

Purpose

County and incorporated place (city) boundaries along with third party identifiers used to join in external data. Boundaries are from the authoritative source the California Department of Tax and Fee Administration (CDTFA), altered to show the counties as one polygon. This layer displays the city polygons on top of the County polygons so the area isn"t interrupted. The GEOID attribute information is added from the US Census. GEOID is based on merged State and County FIPS codes for the Counties. Abbreviations for Counties and Cities were added from Caltrans Division of Local Assistance (DLA) data. Place Type was populated with information extracted from the Census. Names and IDs from the US Board on Geographic Names (BGN), the authoritative source of place names as published in the Geographic Name Information System (GNIS), are attached as well. Finally, coastal buffers are removed, leaving the land-based portions of jurisdictions. 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
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 (this dataset)
4. Place Abbreviations
5. Unincorporated Areas (Coming Soon)
6. Census Designated Places (Coming Soon)
   
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

• 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
• Place Name: CDTFA incorporated (city) or county name
• 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.
• Legal 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.
• GEOID: numeric geographic identifiers from the US Census Bureau Place Type: Board on Geographic Names authorized nomenclature for boundary type published in the Geographic Name Information System
• Place Abbr: CalTrans Division of Local Assistance abbreviations of incorporated area names
• CNTY Abbr: CalTrans Division of Local Assistance abbreviations of county names
• Area_SqMi: The area of the administrative unit (city or county) in square miles, calculated in EPSG 3310 California Teale Albers.
• COASTAL: Indicates if the polygon is a coastal buffer. Null for land polygons. Additional values include "ocean" and "bay".
• 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.

Accuracy

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. COUNTY = county name; CITY = city name or unincorporated territory; COPRI =

A. SUMMARY This dataset maps 2020 census tracts to Analysis Neighborhoods.

The Department of Public Health and the Mayor’s Office of Housing and Community Development, with support from the Planning Department originally created the 41 Analysis Neighborhoods by grouping 2010 Census tracts, using common real estate and residents’ definitions for the purpose of providing consistency in the analysis and reporting of socio-economic, demographic, and environmental data, and data on City-funded programs and services. They are not codified in Planning Code nor Administrative Code.

B. HOW THE DATASET IS CREATED This dataset is produced by mapping the 2020 Census tracts to Analysis neighborhoods.

C. UPDATE PROCESS This dataset is static. Changes to the census tract boundaries are tracked in multiple datasets. See here for the 2010 census tracts assigned to neighborhoods

D. HOW TO USE THIS DATASET This boundary file can be joined to other census datasets on GEOID, which is the primary key for census tracts in the dataset

E. RELATED DATASET 2020 census tract boundaries for San Francisco can be found here