This dataset contains a listing of incorporated places (cities and towns) and counties within the United States including the GNIS code, FIPS code, name, entity type and primary point (location) for the entity. The types of entities listed in this dataset are based on codes provided by the U.S. Census Bureau, and include the following: C1 - An active incorporated place that does not serve as a county subdivision equivalent; C2 - An active incorporated place legally coextensive with a county subdivision but treated as independent of any county subdivision; C3 - A consolidated city; C4 - An active incorporated place with an alternate official common name; C5 - An active incorporated place that is independent of any county subdivision and serves as a county subdivision equivalent; C6 - An active incorporated place that partially is independent of any county subdivision and serves as a county subdivision equivalent or partially coextensive with a county subdivision but treated as independent of any county subdivision; C7 - An incorporated place that is independent of any county; C8 - The balance of a consolidated city excluding the separately incorporated place(s) within that consolidated government; C9 - An inactive or nonfunctioning incorporated place; H1 - An active county or statistically equivalent entity; H4 - A legally defined inactive or nonfunctioning county or statistically equivalent entity; H5 - A census areas in Alaska, a statistical county equivalent entity; and H6 - A county or statistically equivalent entity that is areally coextensive or governmentally consolidated with an incorporated place, part of an incorporated place, or a consolidated city.

State, County and City FIPS (Federal Information Processing Standards) codes are a set of numeric designations given to state, cities and counties by the U.S. federal government. All geographic data submitted to the FRA must have a FIPS code.

A list of Connecticut municipalities with the 3-digit tax code and the 2010 10-digit FIPS code for county subdivisions, assigned by the U.S. Census Bureau

This CT Planning Regions layer consists of individual polygons representing each of the 169 municipalities that make up the state of Connecticut.

This feature layer is directly derived from the 'https://geodata.ct.gov/datasets/CTDOT::ct-municipalities/about' rel='nofollow ugc'>CTDOT Municipalities feature layer geometry, created by CT Department of Transportation. The municipalities are dissolved into their associated regional Councils of Governments.

This feature layer includes US Census Federal Information Processing Standards (FIPS) codes that are associated with each municipality. This was included based on information from 'https://www.census.gov/programs-surveys/geography/technical-documentation/county-changes/2020.html' rel='nofollow ugc'>Connecticut County to County Subdivision Crosswalk from the US Census.

A list of Connecticut municipalities with the 3-digit tax code and the 10-digit FIPS code for county subdivisions, assigned by the U.S. Census Bureau

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 =

This layer was developed by the Research & Analytics Division of the Atlanta Regional Commission to represent the United States Census Bureau's 2010 Decennial Census data at the block group geography.Attributes:STATEFP10 = The Federal Information Processing Series (FIPS) state code. FIPS codes were formerly known as Federal Information Processing Standards codes, until the National Institute of Standards and Technology (NIST) announced its decision in 2005 to remove geographic entity codes from its oversight. The Census Bureau continues to maintain and issue codes for geographic entities covered under FIPS oversight, albeit with a revised meaning for the FIPS acronym. Geographic entities covered under FIPS include states, counties, congressional districts, core based statistical areas, places, county subdivisions, subminor civil divisions, consolidated cities, and all types of American Indian, Alaska Native, and Native Hawaiian areas. FIPS codes are assigned alphabetically according to the name of the geographic entity and may change to maintain alphabetic sort when new entities are created or names change. FIPS codes for specific geographic entity types are usually unique within the next highest level of geographic entity with which a nesting relationship exists. For example, FIPS state, congressional district, and core based statistical area codes are unique within nation; FIPS county, place, county subdivision, and subminor civil division codes are unique within state. The codes for American Indian, Alaska Native, and Native Hawaiian areas also are unique within state; those areas in multiple states will have different codes for each state.COUNTYFP10 = The Federal Information Processing Series (FIPS) county code. TRACTCE10 = Census Tract Codes and Numbers—Census tracts are identified by an up to four-digit integer number and may have an optional two-digit suffix; for example 1457.02 or 23. The census tract codes consist of six digits with an implied decimal between the fourth and fifth digit corresponding to the basic census tract number but with leading zeroes and trailing zeroes for census tracts without a suffix. The tract number examples above would have codes of 145702 and 002300, respectively.BLKGRPCE10 = Block Group Codes—Block Groups have a valid code range of 0 through 9. Block Groups beginning with a zero only contain water area and are generally in coastal and Great Lakes water and territorial seas, but also in larger inland water bodies.GEOID10 = A concatenation of STATEFP10, COUNTYFP10, TRACTCE10, and BLKGRPCE10, which produces the entire FIPS code for this geography.NAMELSAD10 = Block Group nameMTFCC10 = MAF/TIGER feature class codeFUNCSTAT10 = Functional statusALAND10 = Land area in square metersAWATER10 = Water area in square metersINTPTLAT10 = Latitude of the centroid (center of this geography)INTPLON10 = Longitude of the centroid (center of this geography)STFID = The entire FIPS code of this geographyCOUNTY_NM = County namePLNG_REGIO = Planning regionSUMLEV = Summary level of census geography (code)STATE = The state FIPS codeCOUNTY = The county FIPS codeTRACT = The tract FIPS codeBLKGRP = The block group FIPS codetotpop10 = Total populationoner_10 = One race populationwhite_or10 = White, one race populationbl_or10 = Black, one race populationaian_or10 = American Indian and Alaska Native, one race populationasia_or10 = Asian, one race populationnhpi_or10 = Native Hawaiian and Other Pacific Islander, one race populationsomoth_or1 = Some other, one race populationtwoplusr10 = Two-plus races populationtotpop101 = Total populationhisp_lat10 = Total Hispanic/Latino populationnonhisp10 = Total non-Hispanic/Latino populationnh_or10 = Non-Hispanic/Latino, one race populationnhw_or10 = Non-Hispanic/Latino White, one race populationnhbl_or10 = Non-Hispanic/Latino Black, one race populationnhai_or10 = Non-Hispanic/Latino American Indian and Alaskan Native, one race populationnhas_or10 = Non-Hispanic/Latino Asian, one race populationnhhp_or10 = Non-Hispanic/Latino Native Hawaiian and Other Pacific Islander, one race populationnhot_or10 = Non-Hispanic/Latino Other, one race populationnh_twor10 = Non-Hispanic/Latino, two or more races populationtothu10 = Total housing unitstotoccu_10 = Total occupied housing unitstotvach_10 = Total vacant housing unitsAcresLand = Land area in acresAcresWater = Water area in acresAcresTotal = Total area in acresSq_Miles = Total area in square milesShape.STArea() = Total area in square feetSource: U.S. Census Bureau, Atlanta Regional CommissionDate: 2010For additional information, please visit the Atlanta Regional Commission at www.atlantaregional.com

This is a lookup table containing various data related to cities, townships, unorganized territories (CTUs) and any divisions created by county boundaries splitting them. These are termed Minor Civil Division (MCDs) by the Census Bureau. The table encompases the Twin Cities 7-county metropolitan area. It is intended to be a Council wide master lookup table for these entites. It contains official federal and state unique identifiers for CTUs and MCDs as well as identifiers created and used by other organizations. The table also contains historical MCDs dating back to the 1990s and a few other non-MCD records that are of importance to Met. Council use of this table.

The County CTU Lookup Table relates to the Counties and Cities & Townships, Twin Cities Metropolitan Area dataset here: https://gisdata.mn.gov/dataset/us-mn-state-metc-bdry-metro-counties-and-ctus

NOTES:

- On 5/28/2014 a new field was added to reflect the new community designations defined in the Council's Thrive MSP 2040 regional plan - COMDES2040

- On 3/17/2011 it was discovered that the CTU ID used for the City of Lake St. Croix Beach was incorrect. It was changed from 2394379 to 2395599 to match GNIS.

- On 3/17/2011 it was discovered that the CTU ID used for the City of Lilydale was incorrect. It was changed from 2394457 to 2395708 to match GNIS.

- On 11/9/2010 it was discovered that the CTU ID used for the City of Crystal was incorrect. It was changed from 2393541 to 2393683 to match GNIS.

- Effective April 2008, a change was made in GNIS to match the FIPS place codes to the "civil" feature for each city instead of the "populated place" feature. Both cities and townships are now "civil" features within GNIS. This means that the official GNIS unique ID for every city in Minnesota has changed.

- As of January 1, 2006, the five digit FIPS 55-3 Place codes that were used as unique identifiers in this dataset (CTU_CODE and COCTU_CODE fields) were officially retired by the Federal governement. They are replaced by a set of integer codes from the Geographic Names Information System (GNIS_CODE field). Both codes will be kept in this database, but the GNIS_CODE is considered the official unique identifier from this point forward. The GNIS codes are also slated to become official ANSI codes for these geographic features. While GNIS treats these codes as 6 to 8 digit integer data types, the Census Bureau formats them as 8 digit text fields, right justified with leading zeros included.

- The Census Bureau will continue to create FIPS 55 Place codes for new cities and townships through the 2010 Census. After that, no new FIPS 55 codes will be created. Note that for townships that wholly incorporate into cities, the same FIPS 55 code will be used for the new city. (GNIS creates a new ID for the new city.)

- Cities and townships have also been referred to as ''MCDs'' (a Census term), however this term technically refers to the part of each city or township within a single county. Thus, a few cities in the metro area that are split by county boundaries are actually comprised of two different MCDs. This was part of the impetus for a proposed MN state data standard that uses the ''CTU'' terminology for clarity.

- A variety of civil divisions of the land exist within the United States. In Minnesota, only three types exist - cities, townships and unorganized territories. All three of these exist within the Twin Cities seven county area. The only unorganized territory is Fort Snelling (a large portion of which is occupied by the MSP International Airport).

- Some cities are split between two counties. Only those parts of cities within the 7-county area are included.

- Prior to the 2000 census, the FIPS Place code for the City of Greenwood in Hennepin County was changed from 25928 to 25918. This dataset reflects that change.

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.

This layer was developed by the Research & Analytics Division of the Atlanta Regional Commission using U.S. Census Bureau TIGER/Line files. The polygon features in Census_2010_Blocks_GA are subsets of Census_Blockgroups and Census_Tracts.Attributes:STATEFP10 = The Federal Information Processing Series (FIPS) state code. FIPS codes were formerly known as Federal Information Processing Standards codes, until the National Institute of Standards and Technology (NIST) announced its decision in 2005 to remove geographic entity codes from its oversight. The Census Bureau continues to maintain and issue codes for geographic entities covered under FIPS oversight, albeit with a revised meaning for the FIPS acronym. Geographic entities covered under FIPS include states, counties, congressional districts, core based statistical areas, places, county subdivisions, subminor civil divisions, consolidated cities, and all types of American Indian, Alaska Native, and Native Hawaiian areas. FIPS codes are assigned alphabetically according to the name of the geographic entity and may change to maintain alphabetic sort when new entities are created or names change. FIPS codes for specific geographic entity types are usually unique within the next highest level of geographic entity with which a nesting relationship exists. For example, FIPS state, congressional district, and core based statistical area codes are unique within nation; FIPS county, place, county subdivision, and subminor civil division codes are unique within state. The codes for American Indian, Alaska Native, and Native Hawaiian areas also are unique within state; those areas in multiple states will have different codes for each state.COUNTYFP10 = The Federal Information Processing Series (FIPS) county code. TRACTCE10 = Census Tract Codes and Numbers—Census tracts are identified by an up to four-digit integer number and may have an optional two-digit suffix; for example 1457.02 or 23. The census tract codes consist of six digits with an implied decimal between the fourth and fifth digit corresponding to the basic census tract number but with leading zeroes and trailing zeroes for census tracts without a suffix. The tract number examples above would have codes of 145702 and 002300, respectively.BLOCKCE10 = Census block number - Census blocks are numbered uniquely with a four-digit census block number from 0000 to 9999 within census tract, which nest within state and county. The first digit of the census block number identifies the block group. Block numbers beginning with a zero (in Block Group 0) are only associated with water-only areas.GEOID10 = A concatenation of STATEFP10, COUNTYFP10, TRACTCE10, and BLOCKCE10, which produces the entire FIPS code for this geography.NAME10 = Block nameMTFCC10 = MAF/TIGER feature class codeUR10 = Census urban/rural indicatorUACE10 = Census urbanized area codesFUNCSTAT10 = Functional statusALAND10 = Land area in square metersAWATER10 = Water area in square metersINTPTLAT10 = Latitude of the centroid (center of this geography)INTPLON10 = Longitude of the centroid (center of this geography)STFID = The entire FIPS code of this geographyCOUNTY_NM = County namePLNG_REGIO = Planning regionSUMLEV = Summary level of census geography (code)NAME = Block namePLACE = Census place codeSTATE = The state FIPS codeCOUNTY = The county FIPS codeTRACT = The tract FIPS codeBLOCK = The block FIPS codetotpop10 = Total populationoner_10 = One race populationwhite_or10 = White, one race populationbl_or10 = Black, one race populationaian_or10 = American Indian and Alaska Native, one race populationasia_or10 = Asian, one race populationnhpi_or10 = Native Hawaiian and Other Pacific Islander, one race populationsomoth_or1 = Some other, one race populationtwoplusr10 = Two-plus races populationtotpop101 = Total populationhisp_lat10 = Total Hispanic/Latino populationnonhisp10 = Total non-Hispanic/Latino populationnh_or10 = Non-Hispanic/Latino, one race populationnhw_or10 = Non-Hispanic/Latino White, one race populationnhbl_or10 = Non-Hispanic/Latino Black, one race populationnhai_or10 = Non-Hispanic/Latino American Indian and Alaskan Native, one race populationnhas_or10 = Non-Hispanic/Latino Asian, one race populationnhhp_or10 = Non-Hispanic/Latino Native Hawaiian and Other Pacific Islander, one race populationnhot_or10 = Non-Hispanic/Latino Other, one race populationnh_twor10 = Non-Hispanic/Latino, two or more races populationtothu10 = Total housing unitstotoccu_10 = Total occupied housing unitstotvach_10 = Total vacant housing unitsAcresLand = Land area in acresAcresWater = Water area in acresAcresTotal = Total area in acresSqMiLand = Land area in square milesDensPPSqMi = Density: Population per square mile of landShape.STArea() = Total area in square feetSource: U.S. Census Bureau, Atlanta Regional CommissionDate: 2010For additional information, please visit the Atlanta Regional Commission at www.atlantaregional.com

Dataset Summary About this data: This layer presents the USA 2020 Census tracts within the City of Rochester boundary. The geography is sourced from US Census Bureau 2020 TIGER FGDB (National Sub-State) and cut by the City of Rochester boundary. Data Dictionary: STATE_ABBR: The two-letter abbreviation for a state (such as NY). STATE_FIPS: The two-digit Federal Information Processing Standards (FIPS) code assigned to each US state. New York State is 36. COUNTY_FIP: The three-digit Federal Information Processing Standards (FIPS) code assigned to each US county. Monroe County is 055. STCO_FIPS: The five-digit Federal Information Processing Standards (FIPS) code assigned to iedntify a unique county, typically as a concatenation of the State FIPS code and the County FIPS code. TRACT_FIPS: The six-digit number assigned to each census tract in a US county. FIPS: A unique geographic identifier, typically as a concatenation of State FIPS code, County FIPS code, and Census tract code. POPULATION: The population of a census tract. POP_SQMI: The population per square mile of a census tract. SQMI: The size of a census tract in square miles. Division: The name of the City of Rochester data division that the census tract falls in to. Source: This data comes from the Census Bureau.

This filtered contains a listing of incorporated places (cities and towns) and counties within Iowa including the GNIS code, FIPS code, name, entity type and primary point (location) for the entity. The types of entities listed in this dataset are based on codes provided by the U.S. Census Bureau, and include the following:

1. C1 - An active incorporated place that does not serve as a county subdivision equivalent;
2. C2 - An active incorporated place legally coextensive with a county subdivision but treated as independent of any county subdivision;
3. C4 - An active incorporated place with an alternate official common name;
4. C5 - An active incorporated place that is independent of any county subdivision and serves as a county subdivision equivalent;
5. C6 - An active incorporated place that partially is independent of any county subdivision and serves as a county subdivision equivalent or partially coextensive with a county subdivision but treated as independent of any county subdivision; and
6. H1 - An active county or statistically equivalent entity.

Population by age groups, race and gender, and the poverty by race is attached to the split tract geography to create this split tract with population and poverty data. Split tract data is the product of 2020 census tracts split by 2023 incorporated city boundaries and unincorporated community/countywide statistical areas (CSA) boundaries as of July 1, 2023. The census tract boundaries have been altered and aligned where necessary with legal city boundaries and unincorporated areas, including shoreline/coastal areas. Census Tract:Every 10 years the Census Bureau counts the population of the United States as mandated by Constitution. The Census Bureau (https://www.census.gov/)released 2020 geographic boundaries data including census tracts for the analysis and mapping of demographic information across the United States. City Boundary:City Boundary data is the base map information for the County of Los Angeles. These City Boundaries are based on the Los Angeles County Seamless Cadastral Landbase. The Landbase is jointly maintained by the Los Angeles County Assessor and the Los Angeles County Department of Public Works (DPW). This layer represents current city boundaries within Los Angeles County. The DPW provides the most current shapefiles representing city boundaries and city annexations. True, legal boundaries are only determined on the ground by surveyors licensed in the State of California.Countywide Statistical Areas (CSA): The countywide Statistical Area (CSA) was defined to provide a common geographic boundary for reporting departmental statistics for unincorporated areas and incorporated Los Angeles city to the Board of Supervisors. The CSA boundary and CSA names are established by the CIO and the LA County Enterprise GIS group worked with the Los Angeles County Board of Supervisors Unincorporated Area and Field Deputies that reflect as best as possible the general name preferences of residents and historical names of areas. This data is primarily focused on broad statistics and reporting, not mapping of communities. This data is not designed to perfectly represent communities, nor jurisdictional boundaries such as Angeles National Forest. CSA represent board approved geographies comprised of Census block groups split by cities.Data Fields:CT20: 2020 Census tractFIP22: 2023 City FIP CodeCITY: City name for incorporated cities and “Unincorporated” for unincorporated areas (as of July 1, 2023) CSA: Countywide Statistical Area (CSA) - Unincorporated area community names and LA City neighborhood names.CT20FIP23CSA: 2020 census tract with 2023 city FIPs for incorporated cities and unincorporated areas and LA neighborhoods. SPA22: 2022 Service Planning Area (SPA) number.SPA_NAME: Service Planning Area name.HD22: 2022 Health District (HD) number: HD_NAME: Health District name.POP23_AGE_0_4: 2023 population 0 to 4 years oldPOP23_AGE_5_9: 2023 population 5 to 9 years old POP23_AGE_10_14: 2023 population 10 to 14 years old POP23_AGE_15_17: 2022 population 15 to 17 years old POP23_AGE_18_19: 2023 population 18 to 19 years old POP23_AGE_20_44: 2023 population 20 to 24 years old POP23_AGE_25_29: 2023 population 25 to 29 years old POP23_AGE_30_34: 2023 population 30 to 34 years old POP23_AGE_35_44: 2023 population 35 to 44 years old POP23_AGE_45_54: 2023 population 45 to 54 years old POP23_AGE_55_64: 2023 population 55 to 64 years old POP23_AGE_65_74: 2023 population 65 to 74 years old POP23_AGE_75_84: 2023 population 75 to 84 years old POP23_AGE_85_100: 2023 population 85 years and older POP23_WHITE: 2023 Non-Hispanic White POP23_BLACK: 2023 Non-Hispanic African AmericanPOP23_AIAN: 2023 Non-Hispanic American Indian or Alaska NativePOP23_ASIAN: 2023 Non-Hispanic Asian POP23_HNPI: 2023 Non-Hispanic Hawaiian Native or Pacific IslanderPOP23_HISPANIC: 2023 HispanicPOP23_MALE: 2023 Male POP23_FEMALE: 2023 Female POV23_WHITE: 2023 Non-Hispanic White below 100% Federal Poverty Level POV23_BLACK: 2023 Non-Hispanic African American below 100% Federal Poverty Level POV23_AIAN: 2023 Non-Hispanic American Indian or Alaska Native below 100% Federal Poverty Level POV23_ASIAN: 2023 Non-Hispanic Asian below 100% Federal Poverty Level POV23_HNPI: 2023 Non-Hispanic Hawaiian Native or Pacific Islander below 100% Federal Poverty Level POV23_HISPANIC: 2023 Hispanic below 100% Federal Poverty Level POV23_TOTAL: 2023 Total population below 100% Federal Poverty Level POP23_TOTAL: 2023 Total PopulationAREA_SQMil: Area in square mile.POP23_DENSITY: 2023 Population per square mile.POV23_PERCENT: 2023 Poverty rate/percentage.How this data created?Population by age groups, ethnic groups and gender, and the poverty by ethnic groups is attributed to the split tract geography to create this data. Split tract polygon data is created by intersecting 2020 census tract polygons, LA Country City Boundary polygons and Countywide Statistical Areas (CSA) polygon data. The resulting polygon boundary aligned and matched with the legal city boundary whenever possible. Notes:1. Population and poverty data estimated as of July 1, 2023. 2. 2010 Census tract and 2020 census tracts are not the same. Similarly, city and community boundaries are as of July 1, 2023.

Tabular data of population by age groups, race and gender, and the poverty by race is attached to the split tract geography to create this split tract with population and poverty data. Split tract data is the product of 2020 census tracts split by 2022 incorporated city boundaries and unincorporated community/countywide statistical areas (CSA) boundaries. The census tract boundaries have been altered and aligned where necessary with legal city boundaries and unincorporated areas, including shoreline/coastal areas. Census Tract:Every 10 years the Census Bureau counts the population of the United States as mandated by Constitution. The Census Bureau (https://www.census.gov/) released 2020 geographic boundaries data including census tracts for the analysis and mapping of demographic information across the United States. City Boundary:City Boundary data is the base map information for the County of Los Angeles. These City Boundaries are based on the Los Angeles County Seamless Cadastral Landbase. The Landbase is jointly maintained by the Los Angeles County Assessor and the Los Angeles County Department of Public Works (DPW). This layer represents current city boundaries within Los Angeles County. The DPW provides the most current shapefiles representing city boundaries and city annexations. True, legal boundaries are only determined on the ground by surveyors licensed in the State of California.Countywide Statistical Areas (CSA): The countywide Statistical Area (CSA) was defined to provide a common geographic boundary for reporting departmental statistics for unincorporated areas and incorporated Los Angeles city to the Board of Supervisors. The CSA boundary and CSA names are established by the CIO and the LA County Enterprise GIS group worked with the Los Angeles County Board of Supervisors Unincorporated Area and Field Deputies that reflect as best as possible the general name preferences of residents and historical names of areas. This data is primarily focused on broad statistics and reporting, not mapping of communities. This data is not designed to perfectly represent communities, nor jurisdictional boundaries such as Angeles National Forest. CSA represent board approved geographies comprised of Census block groups split by cities.Data Field:CT20: 2020 Census tractFIP22: 2022 City FIP CodeCITY: City name for incorporated cities and “Unincorporated” for unincorporated areas (as of July 1, 2022) CSA: Countywide Statistical Area (CSA) - Unincorporated area community names and LA City neighborhood names.CT20FIP22CSA: 2020 census tract with 2022 city FIPs for incorporated cities and unincorporated areas and LA neighborhoods. SPA22: 2022 Service Planning Area (SPA) number.SPA_NAME: Service Planning Area name.HD22: 2022 Health District (HD) number: HD_NAME: Health District name.POP22_AGE_0_4: 2022 population 0 to 4 years oldPOP22_AGE_5_9: 2022 population 5 to 9 years old POP22_AGE_10_14: 2022 population 10 to 14 years old POP22_AGE_15_17: 2022 population 15 to 17 years old POP22_AGE_18_19: 2022 population 18 to 19 years old POP22_AGE_20_44: 2022 population 20 to 24 years old POP22_AGE_25_29: 2022 population 25 to 29 years old POP22_AGE_30_34: 2022 population 30 to 34 years old POP22_AGE_35_44: 2022 population 35 to 44 years old POP22_AGE_45_54: 2022 population 45 to 54 years old POP22_AGE_55_64: 2022 population 55 to 64 years old POP22_AGE_65_74: 2022 population 65 to 74 years old POP22_AGE_75_84: 2022 population 75 to 84 years old POP22_AGE_85_100: 2022 population 85 years and older POP22_WHITE: 2022 Non-Hispanic White POP22_BLACK: 2022 Non-Hispanic African AmericanPOP22_AIAN: 2022 Non-Hispanic American Indian or Alaska NativePOP22_ASIAN: 2022 Non-Hispanic Asian POP22_HNPI: 2022 Non-Hispanic Hawaiian Native or Pacific IslanderPOP22_HISPANIC: 2022 HispanicPOP22_MALE: 2022 Male POP22_FEMALE: 2022 Female POV22_WHITE: 2022 Non-Hispanic White below 100% Federal Poverty Level POV22_BLACK: 2022 Non-Hispanic African American below 100% Federal Poverty Level POV22_AIAN: 2022 Non-Hispanic American Indian or Alaska Native below 100% Federal Poverty Level POV22_ASIAN: 2022 Non-Hispanic Asian below 100% Federal Poverty Level POV22_HNPI: 2022 Non-Hispanic Hawaiian Native or Pacific Islander below 100% Federal Poverty Level POV22_HISPANIC: 2022 Hispanic below 100% Federal Poverty Level POV22_TOTAL: 2022 Total population below 100% Federal Poverty Level POP22_TOTAL: 2022 Total PopulationAREA_SQMil: Area in square mile.POP22_DENSITY: Population per square mile.POV22_PERCENT: Poverty rate/percentage.How this data created?The tabular data of population by age groups, by ethnic groups and by gender, and the poverty by ethnic groups is attributed to the split tract geography to create this data. Split tract polygon data is created by intersecting 2020 census tract polygons, LA Country City Boundary polygons and Countywide Statistical Areas (CSA) polygon data. The resulting polygon boundary aligned and matched with the legal city boundary whenever possible. Note:1. Population and poverty data estimated as of July 1, 2022. 2. 2010 Census tract and 2020 census tracts are not the same. Similarly, city and community boundary are not the same because boundary is reviewed and updated annually.

Tabular data of population by age groups, race and gender, and the poverty by race is attached to the split tract geography to create this split tract with population and poverty data. Split tract data is the product of 2010 census tracts split by 2019 incorporated city boundaries and unincorporated community/countywide statistical areas (CSA) boundaries. The census tract boundaries have been altered and aligned where necessary with legal city boundaries and unincorporated areas, including shoreline/coastal areas. Census Tract:Every 10 years the Census Bureau counts the population of the United States as mandated by Constitution. The Census Bureau (https://www.census.gov/) released 2010 geographic boundaries data including census tracts for the analysis and mapping of demographic information across the United States. City Boundary:City Boundary data is the base map information for the County of Los Angeles. These City Boundaries are based on the Los Angeles County Seamless Cadastral Landbase. The Landbase is jointly maintained by the Los Angeles County Assessor and the Los Angeles County Department of Public Works (DPW). This layer represents current city boundaries within Los Angeles County. The DPW provides the most current shapefiles representing city boundaries and city annexations. True, legal boundaries are only determined on the ground by surveyors licensed in the State of California.Countywide Statistical Areas (CSA): The countywide Statistical Area (CSA) was defined to provide a common geographic boundary for reporting departmental statistics for unincorporated areas and incorporated Los Angeles city to the Board of Supervisors. The CSA boundary and CSA names are established by the CIO and the LA County Enterprise GIS group worked with the Los Angeles County Board of Supervisors Unincorporated Area and Field Deputies that reflect as best as possible the general name preferences of residents and historical names of areas. This data is primarily focused on broad statistics and reporting, not mapping of communities. This data is not designed to perfectly represent communities, nor jurisdictional boundaries such as Angeles National Forest. CSA represent board approved geographies comprised of Census block groups split by cities.Data Field:CT10: 2010 Census tractFIP19: 2019 City FIP CodeCITY: City name for incorporated cities and “Unincorporated” for unincorporated areas (as of July 1, 2019) CSA: Countywide Statistical Area (CSA) - Unincorporated area community names and LA City neighborhood names.CT10FIP19CSA: 2010 census tract with 2019 city FIPs for incorporated cities, unincorporated areas and LA neighborhoods. SPA12: 2012 Service Planning Area (SPA) number.SPA_NAME: Service Planning Area name.HD12: 2012 Health District (HD) number: HD_NAME: Health District name.POP19_AGE_0_4: 2019 population 0 to 4 years oldPOP19_AGE_5_9: 2019 population 5 to 9 years old POP19_AGE_10_14: 2019 population 10 to 14 years old POP19_AGE_15_17: 2019 population 15 to 17 years old POP19_AGE_18_19: 2019 population 18 to 19 years old POP19_AGE_20_44: 2019 population 20 to 24 years old POP19_AGE_25_29: 2019 population 25 to 29 years old POP19_AGE_30_34: 2019 population 30 to 34 years old POP19_AGE_35_44: 2019 population 35 to 44 years old POP19_AGE_45_54: 2019 population 45 to 54 years old POP19_AGE_55_64: 2019 population 55 to 64 years old POP19_AGE_65_74: 2019 population 65 to 74 years old POP19_AGE_75_84: 2019 population 75 to 84 years old POP19_AGE_85_100: 2019 population 85 years and older POP19_WHITE: 2019 Non-Hispanic White POP19_BLACK: 2019 Non-Hispanic African AmericanPOP19_AIAN: 2019 Non-Hispanic American Indian or Alaska NativePOP19_ASIAN: 2019 Non-Hispanic Asian POP19_HNPI: 2019 Non-Hispanic Hawaiian Native or Pacific IslanderPOP19_HISPANIC: 2019 HispanicPOP19_MALE: 2019 Male POP19_FEMALE: 2019 Female POV19_WHITE: 2019 Non-Hispanic White below 100% Federal Poverty Level POV19_BLACK: 2019 Non-Hispanic African American below 100% Federal Poverty Level POV19_AIAN: 2019 Non-Hispanic American Indian or Alaska Native below 100% Federal Poverty Level POV19_ASIAN: 2019 Non-Hispanic Asian below 100% Federal Poverty Level POV19_HNPI: 2019 Non-Hispanic Hawaiian Native or Pacific Islander below 100% Federal Poverty Level POV19_HISPANIC: 2019 Hispanic below 100% Federal Poverty Level POV19_TOTAL: 2019 Total population below 100% Federal Poverty Level POP19_TOTAL: 2019 Total PopulationAREA_SQMIL: Area in square milePOP19_DENSITY: Population per square mile.POV19_PERCENT: Poverty percentage.How this data created?The tabular data of population by age groups, by ethnic groups and by gender, and the poverty by ethnic groups is attributed to the split tract geography to create this data. Split tract polygon data is created by intersecting 2010 census tract polygons, LA Country City Boundary polygons and Countywide Statistical Areas (CSA) polygon data. The resulting polygon boundary aligned and matched with the legal city boundary whenever possible. Note:1. Population and poverty data estimated as of July 1, 2019. 2. 2010 Census tract and 2020 census tracts are not the same. Similarly, city and community boundary are not the same because boundary is reviewed and updated annually.

This CT Counties layer consists of individual polygons representing each of the 8 counties that make up the state of Connecticut.

This feature layer is directly derived from the CTDOT Municipalities feature layer geometry, created by CT Department of Transportation. The municipalities are dissolved into their associated counties.

This feature layer includes US Census Federal Information Processing Standards (FIPS) codes that are associated with each municipality. This was included based on information from 'https://www.census.gov/programs-surveys/geography/technical-documentation/county-changes/2020.html' rel='nofollow ugc'>Connecticut County to County Subdivision Crosswalk from the US Census.

The 9 Planning Regions in Connecticut have replaced the counties for statistical and administrative functions, so these 8 counties are used only in legacy geography.

Connecticut’s 9 planning regions provide a geographic framework within which municipalities can jointly address common interests and coordinate such interests with state plans and programs. CGS Section 16a-4a authorizes the Secretary of the Office of Policy and Management (OPM) to designate or redesignate the boundaries of logical planning regions. CGS Section 4-124j authorizes the member municipalities of each planning region to establish a formal regional governance structure known as a council of governments (COG).

For more information see:

• 'https://portal.ct.gov/opm/igpp/org/planning-regions/planning-regions---overview' rel='nofollow ugc'>CT Office of Policy and Management, Regional Councils of Governments in Connecticut
• 'https://www2.census.gov/geo/pdfs/reference/ct_county_equiv_change.pdf' rel='nofollow ugc'>Final Change to County Equivalents in Connecticut [PDF]
• 'https://www.federalregister.gov/documents/2022/06/06/2022-12063/change-to-county-equivalents-in-the-state-of-connecticut' rel='nofollow ugc'>Final Federal Register Notice
• 'https://portal.ct.gov/sots/register-manual/section-vii/regional-councils-of-governments' rel='nofollow ugc'>CT Office of the Secretary of the State, Regional Councils of Governments

CT Municipalities

CT Counties

CT Councils of Governments

CT Planning Regions

This layer was developed by the Research & Analytics Division of the Atlanta Regional Commission to represent the United States Census Bureau's 2010 Decennial Census data at the block geography.Attributes:STATEFP10 = The Federal Information Processing Series (FIPS) state code. FIPS codes were formerly known as Federal Information Processing Standards codes, until the National Institute of Standards and Technology (NIST) announced its decision in 2005 to remove geographic entity codes from its oversight. The Census Bureau continues to maintain and issue codes for geographic entities covered under FIPS oversight, albeit with a revised meaning for the FIPS acronym. Geographic entities covered under FIPS include states, counties, congressional districts, core based statistical areas, places, county subdivisions, subminor civil divisions, consolidated cities, and all types of American Indian, Alaska Native, and Native Hawaiian areas. FIPS codes are assigned alphabetically according to the name of the geographic entity and may change to maintain alphabetic sort when new entities are created or names change. FIPS codes for specific geographic entity types are usually unique within the next highest level of geographic entity with which a nesting relationship exists. For example, FIPS state, congressional district, and core based statistical area codes are unique within nation; FIPS county, place, county subdivision, and subminor civil division codes are unique within state. The codes for American Indian, Alaska Native, and Native Hawaiian areas also are unique within state; those areas in multiple states will have different codes for each state.COUNTYFP10 = The Federal Information Processing Series (FIPS) county code. TRACTCE10 = Census Tract Codes and Numbers—Census tracts are identified by an up to four-digit integer number and may have an optional two-digit suffix; for example 1457.02 or 23. The census tract codes consist of six digits with an implied decimal between the fourth and fifth digit corresponding to the basic census tract number but with leading zeroes and trailing zeroes for census tracts without a suffix. The tract number examples above would have codes of 145702 and 002300, respectively.BLOCKCE10 = Census block number - Census blocks are numbered uniquely with a four-digit census block number from 0000 to 9999 within census tract, which nest within state and county. The first digit of the census block number identifies the block group. Block numbers beginning with a zero (in Block Group 0) are only associated with water-only areas.GEOID10 = A concatenation of STATEFP10, COUNTYFP10, TRACTCE10, and BLOCKCE10, which produces the entire FIPS code for this geography.NAME10 = Block nameMTFCC10 = MAF/TIGER feature class codeUR10 = Census urban/rural indicatorUACE10 = Census urban area typeFUNCSTAT10 = Functional statusALAND10 = Land area in square metersAWATER10 = Water area in square metersINTPTLAT10 = Latitude of the centroid (center of this geography)INTPLON10 = Longitude of the centroid (center of this geography)STFID = The entire FIPS code of this geographyCOUNTY_NM = County namePLNG_REGIO = Planning regionSUMLEV = Summary level of census geography (code)NAME = Block namePLACE = Census place codeSTATE = The state FIPS codeCOUNTY = The county FIPS codeTRACT = The tract FIPS codeBLOCK = The block FIPS codetotpop10 = Total populationoner_10 = One race populationwhite_or10 = White, one race populationbl_or10 = Black, one race populationaian_or10 = American Indian and Alaska Native, one race populationasia_or10 = Asian, one race populationnhpi_or10 = Native Hawaiian and Other Pacific Islander, one race populationsomoth_or1 = Some other, one race populationtwoplusr10 = Two-plus races populationtotpop101 = Total populationhisp_lat10 = Total Hispanic/Latino populationnonhisp10 = Total non-Hispanic/Latino populationnh_or10 = Non-Hispanic/Latino, one race populationnhw_or10 = Non-Hispanic/Latino White, one race populationnhbl_or10 = Non-Hispanic/Latino Black, one race populationnhai_or10 = Non-Hispanic/Latino American Indian and Alaskan Native, one race populationnhas_or10 = Non-Hispanic/Latino Asian, one race populationnhhp_or10 = Non-Hispanic/Latino Native Hawaiian and Other Pacific Islander, one race populationnhot_or10 = Non-Hispanic/Latino Other, one race populationnh_twor10 = Non-Hispanic/Latino, two or more races populationtothu10 = Total housing unitstotoccu_10 = Total occupied housing unitstotvach_10 = Total vacant housing unitsAcresLand = Land area in acresAcresWater = Water area in acresAcresTotal = Total area in acresCD = Congressional Districe (111th)SLDU = State Legislative District (Upper; Year 1)SLDL = State Legislative District (Lower; Year 1)VTD = Voting DistrictVTDI = Voting District Indicatortotpop10_1 = Total populationoner_10_11 = One race populationwhite_or10_11 = White, one race populationbl_or10_1 = Black, one race populationaian_or10_1 = American Indian and Alaska Native, one race populationasia_or10_1 = Asian, one race populationnhpi_or10_1 = Native Hawaiian and Other Pacific Islander, one race populationsomoth_or10 = Some other, one race populationtwoplusr10_1 = Two-plus races populationhisp_lat10_1 = Total Hispanic/Latino populationnonhisp10_1 = Total non-Hispanic/Latino populationnh_or10_1 = Non-Hispanic/Latino, one race populationnhw_or10_1 = Non-Hispanic/Latino White, one race populationnhbl_or10_1 = Non-Hispanic/Latino Black, one race populationnhai_or10_1 = Non-Hispanic/Latino American Indian and Alaskan Native, one race populationnhas_or10_1 = Non-Hispanic/Latino Asian, one race populationnhhp_or10_1 = Non-Hispanic/Latino Native Hawaiian and Other Pacific Islander, one race populationnhot_or10_1 = Non-Hispanic/Latino Other, one race populationnh_twor10_1 = Non-Hispanic/Latino, two or more races populationtotvpop10 = Total 18+ populationvoner_10 = 18+ One race populationvwhite_or10 = 18+ White, one race populationvbl_or10 = 18+ Black, one race populationvaian_or10 = 18+ American Indian and Alaska Native, one race populationvasia_or10 = 18+ Asian, one race populationvnhpi_or10 = 18+ Native Hawaiian and Other Pacific Islander, one race populationvsomoth_or1 = 18+ Some other, one race populationvtwoplusr10 = 18+ Two-plus races populationvhisp_lat10 = 18+ Total Hispanic/Latino population of any racevnonhisp10 = 18+ Total non-Hispanic/Latino population of any racevnh_or10 = 18+ Non-Hispanic/Latino, one race populationvnhw_or10 = 18+ Non-Hispanic/Latino White, one race populationvnhbl_or10 = 18+ Non-Hispanic/Latino Black, one race populationvnhai_or10 = 18+ Non-Hispanic/Latino American Indian and Alaskan Native, one race populationvnhas_or10 = 18+ Non-Hispanic/Latino Asian, one race populationvnhhp_or10 = 18+ Non-Hispanic/Latino Native Hawaiian and Other Pacific Islander, one race populationvnhot_or10 = 18+ Non-Hispanic/Latino Other, one race populationvnh_twor10 = 18+ Non-Hispanic/Latino, two or more races populationvhisp_or10 = 18+ Hispanic, one race populationvhsw_or10 = 18+ Hispanic white, one race populationvhsbl_or10 = 18+ Hispanic black, one race populationvhsai_or10 = 18+ Hispanic American Indian, one race populationvhsas_or10 = 18+ Hispanic Asian, one race populationvhshp_or10 = 18+ Hispanic Hawaiian/Pacific Islander, one race populationvhsot_or10 = 18+ Hispanic other, one race populationvhs_twor10 = 18+ Hispanic, two or more races populationtotu18pop10 = Total under 18 populationu18oner_10 = Under 18, one race populationu18white_or10 = Under 18 white, one race populationu18bl_or10 = Under 18 black, one race populationu18aian_or10 = Under 18 American Indian, one race populationu18asia_or10 = Under 18 Asian, one race populationu18nhpi_or10 = Under 18 Hawaiian/Pacific Islander, one race populationu18somoth_or10 = Under 18 some other, one race populationu18twoplusr10 = Under 18, two or more races populationu18hisp_lat10 = Under 18, Hispanic/Latino of any race populationu18nonhisp10 = Under 18, non-Hispanic/Latino of any race populationu18nh_or10 = Under 18 non-Hispanic , one race populationu18nhw_or10 = Under 18 non-Hispanic white, one race populationu18nhbl_or10 = Under 18 non-Hispanic black, one race populationu18nhai_or10 = Under 18 non-Hispanic American Indian, one race populationu18nhas_or10 = Under 18 non-Hispanic Asian, one race populationu18nhhp_or10 = Under 18 non-Hispanic Hawaiian/Pacific Islander, one race populationu18nhot_or10 = Under 18 non-Hispanic other, one race populationu18nh_twor10 = Under 18 non-Hispanic, two or more races populationu18hs_or10 = Under 18 Hispanic, one race populationu18hishw_or10 = Under 18 Hispanic white, one race populationu18hisbl_or10 = Under 18 Hispanic black, one race populationu18hisai_or10 = Under 18 Hispanic American Indian, one race populationu18hisas_or10 = Under 18 Hispanic Asian, one race populationu18hishp_or10 = Under 18 Hispanic Hawaiian/Pacific Islander, one race populationu18hisoth_or10 = Under 18 Hispanic other, one race populationu18his_twor10 = Under 18 Hispanic, two or more races populationShape.STArea() = Total area in square feetSource: U.S. Census Bureau, Atlanta Regional CommissionDate: 2010For additional information, please visit the Atlanta Regional Commission at www.atlantaregional.com

Tabular data of population by age groups, race and gender, and the poverty by race is attached to the split tract geography to create this split tract with population and poverty data. Split tract data is the product of 2020 census tracts split by 2020 incorporated city boundaries and unincorporated community/countywide statistical areas (CSA) boundaries. The census tract boundaries have been altered and aligned where necessary with legal city boundaries and unincorporated areas, including shoreline/coastal areas. Census Tract:Every 10 years the Census Bureau counts the population of the United States as mandated by Constitution. The Census Bureau (https://www.census.gov/) released 2020 geographic boundaries data including census tracts for the analysis and mapping of demographic information across the United States. City Boundary:City Boundary data is the base map information for the County of Los Angeles. These City Boundaries are based on the Los Angeles County Seamless Cadastral Landbase. The Landbase is jointly maintained by the Los Angeles County Assessor and the Los Angeles County Department of Public Works (DPW). This layer represents current city boundaries within Los Angeles County. The DPW provides the most current shapefiles representing city boundaries and city annexations. True, legal boundaries are only determined on the ground by surveyors licensed in the State of California.Countywide Statistical Areas (CSA): The countywide Statistical Area (CSA) was defined to provide a common geographic boundary for reporting departmental statistics for unincorporated areas and incorporated Los Angeles city to the Board of Supervisors. The CSA boundary and CSA names are established by the CIO and the LA County Enterprise GIS group worked with the Los Angeles County Board of Supervisors Unincorporated Area and Field Deputies that reflect as best as possible the general name preferences of residents and historical names of areas. This data is primarily focused on broad statistics and reporting, not mapping of communities. This data is not designed to perfectly represent communities, nor jurisdictional boundaries such as Angeles National Forest. CSA represent board approved geographies comprised of Census block groups split by cities.Data Field:CT20: 2020 Census tractFIP21: 2020 City FIP CodeCITY: City name for incorporated cities and “Unincorporated” for unincorporated areas (as of July 1, 2020) CSA: Countywide Statistical Area (CSA) - Unincorporated area community names and LA City neighborhood names.CT20FIP21CSA: 2020 census tract with 2020 city FIPs for incorporated cities, unincorporated areas and LA neighborhoods. SPA22: 2022 Service Planning Area (SPA) number.SPA_NAME: Service Planning Area name.HD22: 2022 Health District (HD) number: HD_NAME: Health District name.POP20_AGE_0_4: 2020 population 0 to 4 years oldPOP20_AGE_5_9: 2020 population 5 to 9 years old POP20_AGE_10_14: 2020 population 10 to 14 years old POP20_AGE_15_17: 2020 population 15 to 17 years old POP20_AGE_18_19: 2020 population 18 to 19 years old POP20_AGE_20_44: 2020 population 20 to 24 years old POP20_AGE_25_29: 2020 population 25 to 29 years old POP20_AGE_30_34: 2020 population 30 to 34 years old POP20_AGE_35_44: 2020 population 35 to 44 years old POP20_AGE_45_54: 2020 population 45 to 54 years old POP20_AGE_55_64: 2020 population 55 to 64 years old POP20_AGE_65_74: 2020 population 65 to 74 years old POP20_AGE_75_84: 2020 population 75 to 84 years old POP20_AGE_85_100: 2020 population 85 years and older POP20_WHITE: 2020 Non-Hispanic White POP20_BLACK: 2020 Non-Hispanic African AmericanPOP20_AIAN: 2020 Non-Hispanic American Indian or Alaska NativePOP20_ASIAN: 2020 Non-Hispanic Asian POP20_HNPI: 2020 Non-Hispanic Hawaiian Native or Pacific IslanderPOP20_HISPANIC: 2020 HispanicPOP20_MALE: 2020 Male POP20_FEMALE: 2020 Female POV20_WHITE: 2020 Non-Hispanic White below 100% Federal Poverty Level POV20_BLACK: 2020 Non-Hispanic African American below 100% Federal Poverty Level POV20_AIAN: 2020 Non-Hispanic American Indian or Alaska Native below 100% Federal Poverty Level POV20_ASIAN: 2020 Non-Hispanic Asian below 100% Federal Poverty Level POV20_HNPI: 2020 Non-Hispanic Hawaiian Native or Pacific Islander below 100% Federal Poverty Level POV20_HISPANIC: 2020 Hispanic below 100% Federal Poverty Level POV20_TOTAL: 2020 Total population below 100% Federal Poverty Level POP20_TOTAL: 2020 Total PopulationAREA_SQMIL: Area in square milePOP20_DENSITY: Population per square mile.POV20_PERCENT: Poverty rate/percentage.How this data created?The tabular data of population by age groups, by ethnic groups and by gender, and the poverty by ethnic groups is attributed to the split tract geography to create this data. Split tract polygon data is created by intersecting 2020 census tract polygons, LA Country City Boundary polygons and Countywide Statistical Areas (CSA) polygon data. The resulting polygon boundary aligned and matched with the legal city boundary whenever possible. Note:1. Population and poverty data estimated as of July 1, 2019.2. 2010 Census tract and 2020 census tracts are not the same. Similarly, city and community boundary are not the same because boundary is reviewed and updated annually.

This CT Planning Regions layer consists of individual polygons representing each of the 9 planning regions that make up the state of Connecticut.

This feature layer is directly derived from the CTDOT Municipalities feature layer geometry, created by CT Department of Transportation. The municipalities are dissolved into their associated regional Councils of Governments.

This feature layer includes US Census Federal Information Processing Standards (FIPS) codes that are associated with each municipality. This was included based on information from Connecticut County to County Subdivision Crosswalk from the US Census.

Connecticut’s 9 planning regions provide a geographic framework within which municipalities can jointly address common interests and coordinate such interests with state plans and programs. CGS Section 16a-4a authorizes the Secretary of the Office of Policy and Management (OPM) to designate or redesignate the boundaries of logical planning regions. CGS Section 4-124j authorizes the member municipalities of each planning region to establish a formal regional governance structure known as a council of governments (COG).

These regions have been recognized as county-equivalents and supersede the eight legacy counties in the state.

For more information see:

CT Office of Policy and Management, Regional Councils of Governments in Connecticut Final Change to County Equivalents in Connecticut [PDF] Final Federal Register Notice CT Office of the Secretary of the State, Regional Councils of Governments

Field name

Field description

PlanningRegion

Name of the Councils of Governments planning region.

PlanningRegion FIPS

US Census FIPS code associated with the Councils of Governments planning region.

StateFIPS

US Census FIPS code associated with the state.

PlanningRegionFIPS_GEOID

Full US Census FIPS for the COG.

ObjectID

Unique Object ID.

CT Municipalities

CT Counties

CT Councils of Governments

CT Planning Regions

Upper Holston River watershed city/town locations. Provides the name of the city or town and the FIPS code for the county the town is situated within.