2010 Census Tracts for King County - Conflated to Parcels - Major Waterbodies Erased

Metadata also available as - [Outline]

Frequently anticipated questions:


What does this data set describe?

Title:
2010 Census Tracts for King County - Conflated to Parcels - Major Waterbodies Erased
Abstract:
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.
Supplemental_Information:
<http://www5.kingcounty.gov/sdc/addl_doc/CustomizedJoinDetail_Tracts.htm>
  1. How should this data set be cited?

    U.S. Department of Commerce, U.S. Census Bureau, Geography Division, 20110210, 2010 Census Tracts for King County - Conflated to Parcels - Major Waterbodies Erased: King County, King County, WA.

    Online Links:

    Other_Citation_Details: None

  2. What geographic area does the data set cover?

    West_Bounding_Coordinate: -122.542059
    East_Bounding_Coordinate: -121.062937
    North_Bounding_Coordinate: 47.788414
    South_Bounding_Coordinate: 47.073482

  3. What does it look like?

    <http://www5.kingcounty.gov/sdc/DataImages/tracts10_shore.jpg> (JPG)
    JPG File of layer overlain on base of WA counties or local cities

  4. Does the data set describe conditions during a particular time period?

    Beginning_Date: 01-Jan-2010
    Ending_Date: 01-Jul-2010
    Currentness_Reference: publication date

  5. What is the general form of this data set?

    Geospatial_Data_Presentation_Form: vector digital data

  6. How does the data set represent geographic features?

    1. How are geographic features stored in the data set?

      Indirect_Spatial_Reference:
      Federal Information Processing Standards (FIPS), ANSI, and feature names.
      This is a Vector data set. It contains the following vector data types (SDTS terminology):
      • GT-polygon composed of chains (0)

    2. What coordinate system is used to represent geographic features?

      The map projection used is NAD 1983 HARN StatePlane Washington North FIPS 4601 Feet.

      Projection parameters:
      Standard_Parallel: 47.5
      Standard_Parallel: 48.73333333333333
      Longitude_of_Central_Meridian: -120.8333333333333
      Latitude_of_Projection_Origin: 47.0
      False_Easting: 1640416.666666667
      False_Northing: 0.0

      Planar coordinates are encoded using coordinate pair
      Abscissae (x-coordinates) are specified to the nearest 0.0003280833333333334
      Ordinates (y-coordinates) are specified to the nearest 0.0003280833333333334
      Planar coordinates are specified in foot_us

      The horizontal datum used is D North American 1983 HARN.
      The ellipsoid used is GRS 1980.
      The semi-major axis of the ellipsoid used is 6378137.0.
      The flattening of the ellipsoid used is 1/298.257222101.

  7. How does the data set describe geographic features?

    PLIBRARY.CENSUS.xxxx131469
    Polygon attribute table (Source: ESRI)

    OBJECTID
    Internal feature number. (Source: ESRI)

    Sequential unique whole numbers that are automatically generated.

    GEO_ID_TRT
    Geograhic Identifier (Source: U.S. Census)

    String representing state,county and tract

    SHAPE
    Feature Geometry (Source: ESRI)

    Coordinates defining the features

    FEATURE_ID
    Unique serial feature identifier (Source: King County)

    Unique integer for each block starting at 10001

    TRACT_LBL
    Tract label (Source: U.S. Census Bureau)

    Cocantenation of literal Tract with full Tract number

    TRACT_STR
    Tract number as string (Source: U.S. Census Bureau)

    String

    TRACT_INT
    Tract number as integer (Source: U.S. Census Bureau)

    Integer

    TRACT_FLT
    Tract number as floating point (Source: U.S. Census Bureau)

    Range of values
    Minimum:0.00000000
    Maximum:322.10000000

    TRACT_DEL
    Floating point Tract number as string (Source: U.S. Census Bureau)

    Floating point value expressed as string

    TRTLABEL_FULL
    Block label as full expression of all pertinent levels (Source: U.S. Census Bureau)

    Cocantenation with spaces of delimited Tract number

    TRTLABEL_COMP
    Block label as complete expression of all pertinent levels (Source: U.S. Census Bureau)

    Cocantenation with spaces of full Tract number

    TRTLABEL_TRIM
    Block label as trimmed expression of all pertinent levels (Source: U.S. Census Bureau)

    Cocantenation with spaces of delimited Tract number

    COUNTY_STR
    County identifier as string (Source: U.S. Census Bureau)

    ValueDefinition
    (no value)No value
    033King County

    COUNTY_INT
    County identifier as integer (Source: U.S. Census Bureau)

    ValueDefinition
    0No value
    33King County

    STATE_STR
    State identifier as string (Source: U.S. Census Bureau)

    ValueDefinition
    (no value)No value
    53Washington

    STATE_INT
    State identifier as integer (Source: U.S. Census Bureau)

    ValueDefinition
    0No value
    53Washington

    LEVEL_1
    State code (Source: U.S. Census Bureau)

    String

    LEVEL_2
    State code plus County code (Source: U.S. Census Bureau)

    String

    TRACT_AREA
    Calculated area needed as some joins hide system generated items (Source: ESRI)

    TRACT_PERI
    Calculated perimeter necessary as some joins hide system generated items (Source: ESRI)

    LOGRECNO
    Logical record number associating the GEO_ID_TRT to the the Tiger File record. Needed for joins with American Community Survey data, 2006-2010. (Source: U.S. Census)

    LEVEL_3
    State code, County code plus Tract code (Source: U.S. Census Bureau)

    String

    Shape.area
    Area of feature in square feet (Source: ESRI)

    Double

    Shape.len
    Length of feature edge in linear feet (Source: ESRI)

    Double

    Entity_and_Attribute_Overview:
    Original attributes provided by the U.S. Census with Tiger Line files were evaluated. Changes are reformatting was done to create a series of attributes for internal business purposes. Attributes at this time serve only as variations of necessary geometry level identifiers and relates (PK) to possible business tables. Attributes are stored as both string and integer to allow options for joining data.
    Entity_and_Attribute_Detail_Citation: King County


Who produced the data set?

  1. Who are the originators of the data set? (may include formal authors, digital compilers, and editors)

  2. Who also contributed to the data set?

  3. To whom should users address questions about the data?

    King County GIS Center
    Attn: Mary Ullrich
    GIS Analyst
    201 S Jackson St, Suite 706
    Seattle, WA 98104
    US

    206-684-1789 (voice)


Why was the data set created?

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.


How was the data set created?

  1. From what previous works were the data drawn?

    MAF/TIGER (source 1 of 1)
    U.S. Department of Commerce, U.S. Census Bureau, Geography Division, unpublished material, Census MAF/TIGER database.

    Type_of_Source_Media: onLine
    Source_Contribution:
    The selected geographic and cartographic information (line segments) are derived from the U.S. Census Bureau's Master Address File Topologically Integrated Geographic Encoding and Referencing (MAF/TIGER) database.

  2. How were the data generated, processed, and modified?

    (process 1 of 3)
    Major waterbodies erased from TRACTS10_AREA

    Date: 12-Jul-2012 (process 2 of 3)
    Updated blockce10 item in table to match the block number using original block number from Census Bureau. 7 blocks updated.

    Date: 16-Jul-2012 (process 3 of 3)
    Updated tractce10 and blockce10 field items for the following GEOID10 (unique identifier for Blocks). This way the disolve process in python script works properly to create the correct polygons for Block Groups and Tracts. TRACTCE10 BLOCKCE10 GEOID10 008100 1019 530339901000026 032702 5178 530330315021000 026300 2017 530330263002018 032800 2002 530330328002148 032704 3042 530330327044002 032702 5137 530330327025207 031502 1160 530330315021180

  3. What similar or related data should the user be aware of?


How reliable are the data; what problems remain in the data set?

  1. How well have the observations been checked?

    Accurate against Federal Information Processing Standards (FIPS), FIPS Publication 6-4, and FIPS-55 at the 100% level for the codes and base names. The remaining attribute information has been examined but has not been fully tested for accuracy.

  2. How accurate are the geographic locations?

  3. How accurate are the heights or depths?

  4. Where are the gaps in the data? What is missing?

    Data completeness of the TIGER/Line Shapefiles reflects the contents of the Census MAF/TIGER database at the time the TIGER/Line Shapefiles were created. TIGER/Line Shapefiles are extracted from the Census MAF/TIGER database. No changes or updates will be made to this version of the TIGER/Line Shapefiles. Future releases of TIGER/Line Shapefiles will reflect updates made to the Census MAF/TIGER database.

  5. How consistent are the relationships among the observations, including topology?

    The Census Bureau performed automated tests to ensure logical consistency and limits of shapefiles. Segments making up the outer and inner boundaries of a polygon tie end-to-end to completely enclose the area. All polygons are tested for closure. The Census Bureau uses its internally developed geographic update system to enhance and modify spatial and attribute data in the Census MAF/TIGER database. Standard geographic codes, such as FIPS codes for states, counties, municipalities, county subdivisions, places, American Indian/Alaska Native/Native Hawaiian areas, and congressional districts are used when encoding spatial entities. The Census Bureau performed spatial data tests for logical consistency of the codes during the compilation of the original Census MAF/TIGER database files. Most of the codes for geographic entities except states, counties, urban areas, Core Based Statistical Areas (CBSAs), American Indian Areas (AIAs), and congressional districts were provided to the Census Bureau by the USGS, the agency responsible for maintaining FIPS 55. Feature attribute information has been examined but has not been fully tested for consistency. For the TIGER/Line Shapefiles, the Point and Vector Object Count for the G-polygon SDTS Point and Vector Object Type reflects the number of records in the shapefile attribute table. For multi-polygon features, only one attribute record exists for each multi-polygon rather than one attribute record per individual G-polygon component of the multi-polygon feature. TIGER/Line Shapefile multi-polygons are an exception to the G-polygon object type classification. Therefore, when multi-polygons exist in a shapefile, the object count will be less than the actual number of G-polygons.


How can someone get a copy of the data set?

Are there legal restrictions on access or use of the data?

Access_Constraints: None
Use_Constraints:
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. King County data are made available with the understanding that they shall be used exclusively by the obtainer or his/her authorized agents. Digital products may not be reproduced or redistributed in any form or by any means without the express written authorization of King County.

  1. Who distributes the data set? (Distributor 1 of 1)

    KCGIS Center
    Attn: Cheryl Wilder
    Data Sales Coordinator
    201 S Jackson St, Suite 700
    Seattle, WA 98104
    US

    206-263-5220 (voice)

  2. What's the catalog number I need to order this data set?

    /plibrary2/census/shapes/polygon/tracts10_shore.shp

  3. What legal disclaimers am I supposed to read?

    King County disclaims any warranty of use of any digital product or data beyond that for which it was designed. No warranty, expressed or implied is made with regard to the accuracy of these data, and no liability is assumed by the U.S. Government in general or the U.S. Census Bureau in specific as to the spatial or attribute accuracy of the data. The act of distribution shall not constitute any such warranty and no responsibility is assumed by the U.S. government in the use of these files. The boundary information in the TIGER/Line Shapefiles is for statistical data collection and tabulation purposes only; their depiction and designation for statistical purposes do not constitute a determination of jurisdictional authority or rights of ownership or entitlement and they are not legal land descriptions.

  4. How can I download or order the data?


Who wrote the metadata?

Dates:
Last modified: 30-Aug-2012
Metadata author:
King County GIS Center
Attn: Mike Leathers
GIS Data Coordinator
201 S Jackson St, Suite 706
Seattle, WA 98104
US

206-263-4867 (voice)
firstname.lastname@kingcounty.gov

Metadata standard:
FGDC Content Standard for Digital Geospatial Metadata (FGDC-STD-001-1998)


Generated by mp version 2.9.12 on Sat Apr 06 09:26:14 2019