ArcGIS REST Services Directory | Login | Get Token |
Home > services > TMA_Boundary_2020 (FeatureServer) > TMA_Boundary_2020 > iteminfo | API Reference |
JSON |
snippet: | In order for others to use the information in the Census MAF/TIGER database in a geographic information system (GIS) or for other geographic applications. this file was created from the 2010 census block group boundaries. The selected block groups were dissolved to create the TMA boundary file. This boundary is used primarily for the purposes of transportation planning within the Tulsa metropolitan area. In order for others to use the information in the Census MAF/TIGER database in a geographic information system (GIS) or for other geographic applications, the Census Bureau releases to the public extracts of the database in the form of TIGER/Line Shapefiles. |
summary: | In order for others to use the information in the Census MAF/TIGER database in a geographic information system (GIS) or for other geographic applications. this file was created from the 2010 census block group boundaries. The selected block groups were dissolved to create the TMA boundary file. This boundary is used primarily for the purposes of transportation planning within the Tulsa metropolitan area. In order for others to use the information in the Census MAF/TIGER database in a geographic information system (GIS) or for other geographic applications, the Census Bureau releases to the public extracts of the database in the form of TIGER/Line Shapefiles. |
accessInformation: | This boundary was created by INCOG based on 2012 census geography for the purposes of transportation planning in the Tulsa metropolitan area. INCOG, 2 West 2nd Street Suite 800, Tulsa, OK 74103 918.584.7526 |
thumbnail: | |
maxScale: | 5000 |
typeKeywords: | [] |
description: | <DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN><SPAN>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. Block Groups (BGs) are defined before tabulation block delineation and numbering, but are clusters of blocks within the same census tract that have the same first digit of their 4-digit census block number from the same decennial census. For example, 2010 Census tabulation blocks 3001, 3002, 3003,.., 3999 within 2010 Census tract 1210.02 are also within BG 3 within that census tract. 2010 Census BGs generally contained between 600 and 3,000 people. Most BGs were delineated by local participants in the Census Bureau's Participant Statistical Areas Program (PSAP). The Census Bureau delineated BGs only where the PSAP participant declined to delineate BGs or where the Census Bureau could not identify any local PSAP participant. A BG usually covers a contiguous area. Each census tract contains at least one BG, and BGs are uniquely numbered within census tract. Within the standard census geographic hierarchy, BGs never cross county or census tract boundaries, but may cross the boundaries of other geographic entities like county subdivisions, places, urban areas, voting districts, congressional districts, and American Indian / Alaska Native / Native Hawaiian areas. BGs have a valid code range of 0 through 9. BGs coded 0 were intended to only include water area, no land area, and they are generally in territorial seas, coastal water, and Great Lakes water areas. For the 2010 Census, rather than extending a census tract boundary into the Great Lakes or out to the U.S. nautical three-mile limit, the Census Bureau delineated some census tract boundaries along the shoreline or just offshore. The Census Bureau assigned a default census tract number beginning with 99 and a BG number of 0 to these offshore, water-only areas not included in regularly numbered census tract areas.</SPAN></SPAN></P><P><SPAN /></P></DIV></DIV></DIV> |
licenseInfo: | <DIV STYLE="text-align:Left;"><P STYLE="font-size:16ptmargin:7 0 7 0;"><SPAN><SPAN>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.</SPAN></SPAN></P><DIV><P><SPAN /></P></DIV></DIV> |
catalogPath: | |
title: | SDE.TMA_2020 |
type: | |
url: | |
tags: | ["transportation management area boundary","based upon 2020 block group geography"] |
culture: | en-US |
portalUrl: | |
name: | |
guid: | |
minScale: | 150000000 |
spatialReference: |