ArcGIS REST Services Directory Login | Get Token
Home > services > Kentucky > DixieHwy_Access_Study_WebService (MapServer) > Census Tracts 2010 API Reference
JSON

Layer: Census Tracts 2010 (ID: 380)

Parent Layer: Admin and Planning

Name: Census Tracts 2010

Display Field: NAME

Type: Feature Layer

Geometry Type: esriGeometryPolygon

Description: LOJIC produced the MetroTract_2010 polygon feature class as a subset of 2010 Census Tiger/Line Files that is comprised of counties relevant to the Louisville- Jefferson County Metropolitan area and relevant surrounding Indiana and Kentucky counties. Attribution for this feature class consists of selected fields from the original shapefile, Geographic Header file and 2010 Redisticting population summary files, Part 1 and Part 2. Field naming conventions comply with those set forth by the U.S. Census. This is discussed to a greater degree below. The geographic coverage of MetroTract_2010 includes census tracts for Indiana and Kentucky counties that are tangent or within relevant proximity to Louisville-Jefferson County Metro Area. Indiana counties include Clark, Floyd and Harrison. Kentucky counties include Bullitt, Hardin, Henry, Jefferson, Meade, Oldham, Shelby, Spencer and Trimble. LOJIC census feature classes have been populated with a selected subset of relevant Census geographic and jurisdictional information derived from the Census Geographic Header file. A selected subset of population statistics from the Redistricting data summary files has also been incorporated. Please note that the included geographic header and population counts are not comprehensive. More specifically, not all fields from from the original shape, geographic header or summary files is contained in the feature class. Geographic Header, Part 1 and Part 2 tables that constitute the previously listed Indiana and Kentucky counties have been published in their entirety for any additional information that the end user may desire. This will require the end user to join the feature class to these tables. Feature classes can be joined to the Geographic Header table (PL_GEO_H_2010) with the [GEOID] field. To insure a 1:1 relationship and correct population data, the [GEOID] has been calculated only for relevant Census summary levels. Feature classes can be joined to the Part 1 (PL_PART1_2010) and Part 2 (PL_PART2_2010) tables with the [LOGRECSTID] field. This field insures a 1:1 relationship between the geography and its accurate population statistics. Part 1 includes categorizations of Populaton by Race (P001 fields) and Population by Hispanic or Latino Ethnicity and Race (P002 fields). Part 2 includes categorizations of Population by Race and Age 18 and Over (P003 fields), Population by Hispanic or Latino Ethnicity and Race and Ages 18 and Over (P004 fields), and finally, Occupancy Status (H001 fields). Currently, 2010 Census population counts are limited to what has been released by the U.S. Census Bureau, namely 2010 Redistricting Data. Full documentation for all Census Geographic Headerand Population fields can be referenced in the published tables, HEADER_DESCRIPT_2010 and POP_DESCRIPT_2010 respectively. These tables indicate field names and their respective descriptions. Please familiarize yourself with the Census abstract information that follows. The TIGER/Line Files are shapefiles and related database files (.dbf) that 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 File is designed to stand alone as an independent data set, or they can be combined to cover the entire nation. Census Blocks are statistical areas bounded on all sides by visible features, such as streets, roads, streams, and railroad tracks, and/or by nonvisible boundaries such as city, town, township, and county limits, and short line-of-sight extensions of streets and roads. Census blocks are relatively small in area; for example, a block in a city bounded by streets. However, census blocks in remote areas are often large and irregular and may even be many square miles in area. A common misunderstanding is that data users think census blocks are used geographically to build all other census geographic areas, rather all other census geographic areas are updated and then used as the primary constraints, along with roads and water features, to delineate the tabulation blocks. As a result, all 2010 Census blocks nest within every other 2010 Census geographic area, so that Census Bureau statistical data can be tabulated at the block level and aggregated up to the appropriate geographic areas. Census blocks cover all territory in the United States, Puerto Rico, and the Island Areas (American Samoa, Guam, the Commonwealth of the Northern Mariana Islands, and the U.S. Virgin Islands). Blocks are the smallest geographic areas for which the Census Bureau publishes data from the decennial census. A block may consist of one or more faces.The attribute field "SQ_MILES" contains the area calculated to the thousandth (0.001) square mile. For entries showing 0, refer to the SHAPE_Area field for values in square feet.

Copyright Text:

Default Visibility: true

MaxRecordCount: 1000

Supported Query Formats: JSON, geoJSON, PBF

Min Scale: 0

Max Scale: 0

Supports Advanced Queries: true

Supports Statistics: true

Has Labels: true

Can Modify Layer: true

Can Scale Symbols: false

Use Standardized Queries: true

Supports Datum Transformation: true

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

HasM: false

Has Attachments: false

HTML Popup Type: esriServerHTMLPopupTypeAsHTMLText

Type ID Field: null

Fields:
Supported Operations:   Query   Query Attachments   Query Analytic   Generate Renderer   Return Updates

  Iteminfo   Thumbnail   Metadata