TIGER/Line Shapefile, 2008, state, North Carolina, Congressional District

Metadata also available as - [Outline] - [Parseable text] - [XML]

Frequently-anticipated questions:


What does this data set describe?

Title:
TIGER/Line Shapefile, 2008, state, North Carolina, Congressional District
Abstract:
The TIGER/Line Shapefiles are an extract of selected geographic and cartographic information from the Census MAF/TIGER database. The Census MAF/TIGER database 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 the shapefiles can be combined to cover the whole nation.
  1. How should this data set be cited?

    U.S. Department of Commerce, U.S. Census Bureau, Geography Divisi, 2008, TIGER/Line Shapefile, 2008, state, North Carolina, Congressional District.

    Online Links:

  2. What geographic area does the data set cover?

    West_Bounding_Coordinate: -84.321869
    East_Bounding_Coordinate: -75.400119
    North_Bounding_Coordinate: 36.588157
    South_Bounding_Coordinate: 33.752878

  3. What does it look like?

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

    Calendar_Date: REQUIRED: The year (and optionally month, or month and day) for which the data set corresponds to the ground.
    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):
      • G-polygon (13)

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

      Grid_Coordinate_System_Name: State Plane Coordinate System 1983
      State_Plane_Coordinate_System:
      SPCS_Zone_Identifier: 3200
      Lambert_Conformal_Conic:
      Standard_Parallel: 34.333333
      Standard_Parallel: 36.166667
      Longitude_of_Central_Meridian: -79.000000
      Latitude_of_Projection_Origin: 33.750000
      False_Easting: 609601.220000
      False_Northing: 0.000000

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

      The horizontal datum used is North American Datum of 1983 in the 48 contiguous states, the District of Columbia, Alaska, Hawaii, Puerto Rico, the Virgin Islands of the United States, and the Pacific Island Areas..
      The ellipsoid used is Geodetic Reference System 80.
      The semi-major axis of the ellipsoid used is 6378137.
      The flattening of the ellipsoid used is 1/298257.

      Vertical_Coordinate_System_Definition:
      Altitude_System_Definition:
      Altitude_Resolution: 1.000000
      Altitude_Encoding_Method:
      Explicit elevation coordinate included with horizontal coordinates

  7. How does the data set describe geographic features?

    CD110.shp
    110th Congressional District (Source: U.S. Census Bureau)

    OBJECTID
    Internal feature number. (Source: ESRI)

    Sequential unique whole numbers that are automatically generated.

    Shape
    Feature geometry. (Source: ESRI)

    Coordinates defining the features.

    STATEFP
    Current state Federal Information Processing Standards (FIPS) code (Source: U.S. Census Bureau)

    Formal codeset
    Codeset Name:FIPS PUB 5-2, Codes for the Identification of the States, the District of Columbia and the Outlying Areas of the United States, and Associated Areas
    Codeset Source:U.S. Census Bureau

    STATENS
    Current state ANSI code (Source: U.S. Census Bureau)

    Formal codeset
    Codeset Name:data are unavailable
    Codeset Source:data are unavailable

    CD110FP
    110th congressional district Federal Information Processing Standards (FIPS) code (Source: U.S. Census Bureau)

    ValueDefinition
    00At Large Representation
    01 to 53Congressional District (in states with more than one district)
    98Non-Voting Delegate
    99No Representation

    CD110IDFP
    110th congressional district identifier, a concatenation of current state Federal Information Processing Standards (FIPS) code, the 110th congressional session code, and the 110th congressional district FIPS code (Source: U.S. Census Bureau)

    Formal codeset
    Codeset Name:FIPS PUB 5-2, Codes for the Identification of the States, the District of Columbia and the Outlying Areas of the United States, and Associated Areas, congressional session code that appears in CDSESSN and the current congressional district code that appears in CDFP
    Codeset Source:U.S. Census Bureau

    NAMELSAD
    Current name and the translated legal/statistical area description for congressional district code (Source: U.S. Census Bureau)

    Formal codeset
    Codeset Name:Use values from the congressional district code (CDFP) field, where value is 01 to 52 without leading zeros and/or the translated legal/statistical area description code for congressional district that appears in LSAD00
    Codeset Source:U.S. Census Bureau

    LSAD
    Current legal/statistical area description code for congressional district (Source: U.S. Census Bureau)

    ValueDefinition
    00Blank
    C1Congressional District (at Large)
    C2Congressional District (prefix)
    C3Resident Commissioner District (at Large)
    C4Delegate District (at Large)
    C5No Representative

    CDSESSN
    110th congressional session code (Source: U.S. Census Bureau)

    Range of values
    Minimum:106
    Maximum:199

    MTFCC
    MAF/TIGER feature class code (Source: U.S. Census Bureau)

    ValueDefinition
    G5200Congressional District

    FUNCSTAT
    Current functional status (Source: U.S. Census Bureau)

    ValueDefinition
    NNonfunctioning legal entity

    NameShort

    SHAPE.area

    SHAPE.len


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?

    U.S. Department of Commerce, U.S. Census Bureau, Geography Division, Geographic Products Branch
    4600 Silver Hill Road, Stop 7400
    Washington, DC 20233-7400
    United States

    301-763-1128 (voice)
    301-763-4710 (FAX)
    tiger@census.gov


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 Divisi, 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?

    Date: 2008 (process 1 of 4)
    TIGER/Line Shapefiles are extracted from the Census MAF/TIGER database by nation, state, county, and entity. Census MAF/TIGER data for the nation, state, county, and entity are then distributed among 58 shapefiles each containing attributes for line, polygon, or landmark geographic data.

    Data sources used in this process:

    • Census MAF/TIGER

    Date: 03-Apr-2009 (process 2 of 4)
    Dataset copied.

    Data sources used in this process:

    Date: 21-Apr-2009 (process 3 of 4)
    Dataset copied.

    Data sources used in this process:

    • \\DBADMIN\C$\CGIA\data\basic_data.mdb

    Date: 21-Apr-2009 (process 4 of 4)
    Dataset copied.

    Data sources used in this process:

    • Server=10.251.138.13; Service=5151; Database=onemap; User=sdeadmin; Version=sde.DEFAULT

  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.

  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.

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

    U.S. Department of Commerce, U.S. Census Bureau, Geography Division, Geographic Products Branch
    4600 Silver Hill Road, Stop 7400
    Washington, DC 20233-7400
    United States

    301-763-1128 (voice)
    301-763-4710 (FAX)
    tiger@census.gov

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

    Downloadable Data

  3. What legal disclaimers am I supposed to read?

    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?

  5. What hardware or software do I need in order to use the data set?

    The TIGER/Line shapefiles contain geographic data only and do not include display mapping software or statistical data. For information on how to use the TIGER/Line shapefile data with specific software package users shall contact the company that produced the software.


Who wrote the metadata?

Dates:
Last modified: 2008
Metadata author:
U.S. Department of Commerce, U.S. Census Bureau, Geography Division, Geographic Products Branch
c/o REQUIRED: The person responsible for the metadata information.
4600 Silver Hill Road, Stop 7400
Washington, DC 20233-7400
United States

301-763-1128 (voice)
301-763-4710 (FAX)
tiger@census.gov

Metadata standard:
FGDC Content Standards for Digital Geospatial Metadata (FGDC-STD-001-1998)
Metadata extensions used:


Generated by mp version 2.9.5 on Tue Apr 21 11:11:23 2009