ArcGIS REST Services Directory Login
Home > services > Hosted > ACS_Update_Test (FeatureServer) > CensusTracts2020_ACS22 Help | API Reference
JSON

Layer: CensusTracts2020_ACS22 (ID: 0)

View In:   ArcGIS Online Map Viewer

Name: CensusTracts2020_ACS22

Display Field: name

Type: Feature Layer

Geometry Type: esriGeometryPolygon

Description: <DIV STYLE="text-align:Left;"><P STYLE="margin:0 0 11 0;"><SPAN><SPAN>Census tracts are small, relatively permanent statistical subdivisions of a county or equivalent entity and are reviewed and updated by local participants prior to each decennial census as part of the Census Bureau’s PSAP. The Census Bureau updates census tracts in situations where no local participant existed or where local or tribal governments declined to participate. The primary purpose of census tracts is to provide a stable set of geographic units for the presentation of decennial census data.</SPAN></SPAN></P><P STYLE="margin:0 0 11 0;"><SPAN><SPAN>Census tracts generally have a population size of 1,200 to 8,000 people with an optimum size of 4,000 people. The spatial size of census tracts varies widely depending on the density of settlement. Ideally, census tract boundaries remain stable over time to facilitate statistical comparisons from census to census. However, physical changes in street patterns caused by highway construction, new development, and so forth, may require boundary revisions. In addition, significant changes in population may result in splitting or combining census tracts. Census tract boundaries generally follow visible and identifiable features. </SPAN></SPAN></P><P STYLE="margin:0 0 11 0;"><SPAN>Census tract boundaries may follow legal boundaries (e.g., MCD or incorporated place boundaries in some states 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.</SPAN></P><P STYLE="margin:0 0 11 0;"><SPAN><SPAN>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. Census Tract Codes and Numbers—Census tract numbers have up to a 4-character basic number and may have an optional 2-character suffix: </SPAN></SPAN></P><P STYLE="margin:0 0 11 0;"><SPAN><SPAN>For example: 1457.02 </SPAN></SPAN></P><P STYLE="margin:0 0 11 0;"><SPAN><SPAN>The census tract numbers (used as names) eliminate any leading zeroes and append a suffix only if required. The 6-digit census tract codes, however, include leading zeroes and have an implied decimal point for the suffix. Census tract codes (000100 to 998999) are unique within a county or equivalent area. </SPAN></SPAN></P><P STYLE="margin:0 0 11 0;"><SPAN><SPAN>The Census Bureau assigned a census tract code of 9900 to represent census tracts delineated to cover large bodies of water. In addition, census tract codes in the 9400s represent American Indian Areas and codes in the 9800s represent special land use areas. </SPAN></SPAN></P><P STYLE="margin:0 0 11 0;"><SPAN><SPAN>The Census Bureau uses suffixes to help identify census tract changes for comparison purposes. Local participants have an opportunity to review the existing census tracts before each census. If local participants split a census tract, the split parts usually retain the basic number, but receive different suffixes. In a few counties, local participants request major changes to, and renumbering of, the census tracts. Changes to individual census tract boundaries usually do not result in census tract numbering changes.</SPAN></SPAN></P></DIV>

Service Item Id: 6c590c4c67834fa2a303f48065e65db2

Copyright Text: The file was created from Census 2020 TIGER Files The TIGER/Line Shapefile products are not copyrighted however TIGER/Line and Census TIGER are registered trademarks of the U.S. Census Bureau. These products are free to use in a product or publication, however acknowledgement must be given to the U.S. Census Bureau as the source. The boundary information in the TIGER/Line Shapefiles are for statistical data collection and tabulation purposes only; their depiction and designation for statistical purposes does not constitute a determination of jurisdictional authority or rights of ownership or entitlement and they are not legal land descriptions. Coordinates in the TIGER/Line shapefiles have six implied decimal places, but the positional accuracy of these coordinates is not as great as the six decimal places suggest.

Default Visibility: true

MaxRecordCount: 2000

Supported Query Formats: JSON, geoJSON, PBF

Min Scale: 0

Max Scale: 0

Supports Advanced Queries: true

Supports Statistics: true

Can Scale Symbols: false

Use Standardized Queries: true

Supports ValidateSQL: true

Supports Calculate: true

Extent:
Drawing Info: Advanced Query Capabilities:
HasZ: true

HasM: true

Has Attachments: false

HTML Popup Type: esriServerHTMLPopupTypeAsHTMLText

Type ID Field:

Fields: Templates:
Capabilities: Query,Extract

Sync Can Return Changes: true

Is Data Versioned: false

Supports Rollback On Failure: true

Supports ApplyEdits With Global Ids: false

Supports ApplyEdits By Upload Id: true

Supports Query With Historic Moment: false

Supports Coordinates Quantization: true

Supported Operations:   Query   Query Attachments   Calculate   Validate SQL   Generate Renderer   Return Updates   Metadata