NCDOT Roads

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

Frequently-anticipated questions:


What does this data set describe?

Title: NCDOT Roads
Abstract:
A GIS layer depicting a detailed statewide roads network for the state of North Carolina. This data file was created from multiple sources, including Department of Transportation data (NCDOT), US Census (TIGER) and local government data, to create a detailed GIS roads layer that would meet the Geographic Information Coordinating Council's (GICC) State Mapping Advisory Committee (SMAC) content standard for street centerlines and that could be used as a base for geocoding addresses.
Supplemental_Information:
Various road data and information was gathered from a number of sources to create this GIS layer. Roads data was gathered from federal (TIGER), state (NCDOT) as well as county and city agencies within the state to create this data set. Data and attributes were combined, deleted, and added to create a statewide roads file that met SMAC content standards and was capable of being used as a geocoding source for addresses within the state.
  1. How should this data set be cited?

    The North Carolina Department of Transportation Geographic Information Systems Unit, 200708, NCDOT Roads: The North Carolina Department of Transportation Geographic Information Systems Unit, Raleigh, North Carolina.

    Online Links:

    • www.nconemap.com

  2. What geographic area does the data set cover?

    West_Bounding_Coordinate: -84.421467
    East_Bounding_Coordinate: -75.418430
    North_Bounding_Coordinate: 36.615121
    South_Bounding_Coordinate: 33.733389

  3. What does it look like?

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

    Calendar_Date: Aug-2007
    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?

      This is a Vector data set. It contains the following vector data types (SDTS terminology):

      • String (736356)

    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.001877
      Ordinates (y-coordinates) are specified to the nearest 0.001877
      Planar coordinates are specified in meters

      The horizontal datum used is North American Datum of 1983.
      The ellipsoid used is Geodetic Reference System 80.
      The semi-major axis of the ellipsoid used is 6378137.000000.
      The flattening of the ellipsoid used is 1/298.257222.

      Vertical_Coordinate_System_Definition:
      Altitude_System_Definition:
      Altitude_Datum_Name: National Geodetic Vertical Datum of 1929
      Altitude_Distance_Units: feet
      Altitude_Resolution: 0.000100
      Altitude_Encoding_Method:
      Explicit elevation coordinate included with horizontal coordinates

  7. How does the data set describe geographic features?

    ISRN_v2_MMM2007_Roads
    Statewide road network (Source: The North Carolina Department of Transportation Geographic Information Systems Unit)

    Shape
    Feature geometry. (Source: ESRI)

    Coordinates defining the features.

    RdTxt
    Road Text (Automatically created from the Concatenation of PreDir + RdName + RdTyp + SufDir.) (Source: NC Geographic Information Coordinating Council (GICC), State Mapping Advisory Committee (SMAC), Road Data Content Standards Group - "Geographic Data Content Standard for Transportation Roads Data")

    Values differ by feature.

    PreDir
    Road Prefix Domain (Source: NC Geographic Information Coordinating Council (GICC), State Mapping Advisory Committee (SMAC), Road Data Content Standards Group - "Geographic Data Content Standard for Transportation Roads Data")

    ValueDefinition
    <BLANK>None
    EEast
    WWest
    NNorth
    SSouth
    NENortheast
    NWNorthwest
    SESoutheast
    SWSouthwest

    RdName
    Road Name (96500 Unique Names for the entire state. q To avoid confusion the period "." is not used for a value inside this field. The only exception is for initials like "A.O. Smith" and the space after the last period is required to allow automatic case determination. Do not place a period with Mrs, Jr, Dr, Rev, St, Sr, & SS. q NC, US and SR must be followed by a space. q Some ramps are defined with from and to road name. (Source: NC Geographic Information Coordinating Council (GICC), State Mapping Advisory Committee (SMAC), Road Data Content Standards Group - "Geographic Data Content Standard for Transportation Roads Data")

    Values differ by feature.

    RdTyp
    Road Type for the Road Name. (Source: NC Geographic Information Coordinating Council (GICC), State Mapping Advisory Committee (SMAC), Road Data Content Standards Group - "Geographic Data Content Standard for Transportation Roads Data")

    Values differ by feature.

    SufDir
    Post Directional Suffix (Source: NC Geographic Information Coordinating Council (GICC), State Mapping Advisory Committee (SMAC), Road Data Content Standards Group - "Geographic Data Content Standard for Transportation Roads Data")

    Values differ by feature.

    LngPreDir
    Long Version of Road Prefix (PreDir - assigned by automated process) (Source: NCDOT GIS)

    Values differ by feature.

    LngRdTyp
    Long Version of Road Type (RdTyp - assigned by automated process) (Source: NCDOT GIS)

    Values differ by feature.

    LngSufDir
    Long Version of Road Suffix (SufDir - assigned by automated process) (Source: NCDOT GIS)

    Values differ by feature.

    LowLeft
    Lowest address on the left side of the street segment (Source: County addressing unit)

    Values differ by feature.

    HighLeft
    Highest address on the left side of the street segment (Source: County addressing unit)

    Values differ by feature.

    LowRight
    Lowest address on the right side of the street segment (Source: County addressing unit)

    Values differ by feature.

    HighRight
    Lowest address on the right side of the street segment (Source: County addressing unit)

    Values differ by feature.

    ZipLeft
    Five-digit zip code on the left side of the street segment (assigned by automated process) (Source: County addressing unit)

    Values differ by feature.

    ZipRight
    Five-digit zip code on the right side of the street segment (assigned by automated process) (Source: County addressing unit)

    Values differ by feature.

    Zip4Left
    Additional four-digit zip code on the left side of the street segment (assigned by automated process) (Source: County addressing unit)

    Values differ by feature.

    Zip4Right
    Additional four-digit zip code on the right side of the street segment (assigned by automated process) (Source: County addressing unit)

    Values differ by feature.

    CityLeft
    Municipal Boundary Name on the left side of the street segment (assigned by automated process) (Source: NCDOT GIS)

    Values differ by feature.

    CityRight
    Municipal Boundary Name on the right side of the street segment (assigned by automated process) (Source: NCDOT GIS)

    Values differ by feature.

    IsInCity
    Is set to "1" if center of the road is inside the Municipal Boundary (assigned by automated process) (Source: NCDOT GIS)

    ValueDefinition
    1center of road is inside the municiapal boundary
    0center of road is not inside the municipal boundary

    County
    County Name (assigned by automated process) (Source: NCDOT GIS)

    Values differ by feature.

    State
    State Abbrevation Name (assigned by automated process) (Source: NCDOT GIS)

    Values differ by feature.

    DateAdd
    Last date that a change occurred to this record. (Field not populated by NCDOT) (Source: County addressing unit)

    Values differ by feature.

    RdOwner
    Maintenance Provider (assigned by automated process) (Source: NC Geographic Information Coordinating Council (GICC), State Mapping Advisory Committee (SMAC), Road Data Content Standards Group - "Geographic Data Content Standard for Transportation Roads Data")

    Values differ by feature.

    Ser_Class
    Service Class (assigned by automated process) (Source: NC Geographic Information Coordinating Council (GICC), State Mapping Advisory Committee (SMAC), Road Data Content Standards Group - "Geographic Data Content Standard for Transportation Roads Data")

    Values differ by feature.

    Sr_Num
    SR Number from the state road system (assigned by automated process) (Source: NCDOT GIS)

    Values differ by feature.

    Rte_Name
    State Road Name from the state road system (assigned by automated process) (Source: NCDOT GIS)

    Values differ by feature.

    Rte_Num
    Eight Digit State Road Number from the state road system (assigned by automated process) (Source: NCDOT GIS)

    Values differ by feature.

    CFCC_Code
    Census Feature Code (assigned by automated process with limited results) (Source: NCDOT GIS)

    Values differ by feature.

    SpeedLmt
    Estimated Speed Limit assigned to road (assigned by automated process) (Source: NCDOT GIS)

    Values differ by feature.

    MileTrv
    Miles Traveled for this line segment (assigned by automated process) (Source: NCDOT GIS)

    Values differ by feature.

    MinuteTrv
    Minutes Traveled for this line segment (assigned MileTrv / SpeedLmt) (Source: NCDOT GIS)

    Values differ by feature.

    OneWay
    Oneway direction indication (assigned by automated process and is incorrect for many divided roads) (Source: NCDOT GIS)

    Values differ by feature.

    FID
    Internal feature number. (Source: ESRI)

    Sequential unique whole numbers that are automatically generated.


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?

    NC Department of Transportation Geographic Information Systems Unit
    c/o GIS Unit
    GIS Help Desk
    3401 Carl Sandburg Ct
    Raleigh, North Carolina 27610
    USA

    919-212-6000 (voice)
    919-212-5999 (FAX)
    gishelp@dot.state.nc.us

    Hours_of_Service: 8am to 5pm, M-F
    Contact_Instructions: Phone or e-mail.


Why was the data set created?

These data were created to assist governmental agencies and others in making resource management decisions through use of a Geographic Information System (GIS). A detailed roads layer is recognized as a base cartographic layer for location analysis.


How was the data set created?

  1. From what previous works were the data drawn?

    USGS75_QUADS (source 1 of 3)
    Survey, US Geological , Unknown, 7.5 Series USGS Quad maps: US Geological Survey, Reston, Virginia.

    Other_Citation_Details: Published map series
    Type_of_Source_Media: paper
    Source_Scale_Denominator: 24000
    Source_Contribution:
    Data was originally acquired through digitizing of USGS 7.5 quad maps with scales of 1:24,000 and refined and updated using 1993 and 1998 DOQQ's.

    County Data (source 2 of 3)
    Various, Unknown, County roads: Various, Various.

    Type_of_Source_Media: CD-ROM
    Source_Scale_Denominator: 2400
    Source_Contribution:
    Local county roads data was obtained on cd-rom from individual counties within the state.

    TIGER files (source 3 of 3)
    U.S. Census Bureau, 2005, TIGER Line Files: TIGER/Line File 2005, U.S. Census Bureau, Washington, DC.

    Type_of_Source_Media: CD-ROM
    Source_Scale_Denominator: 2400
    Source_Contribution: TIGER streets line file

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

    Date: Unknown (process 1 of 3)
    Data was collected from local county governments, Census Bureau, and internal. Manipulated and adjusted to fit NCDOT Routing and Geocoding needs.

    Person who carried out this activity:

    North Carolina Department of Transportation Geographic Information Systems (GIS) Unit Programming & Analysis Section
    c/o GIS Unit
    3401 Carl Sandburg Ct
    Raleigh, North Carolina 27610
    USA

    (919) 212-6000 (voice)
    (919) 212-5999 (FAX)
    gishelp@dot.state.nc.us

    Hours_of_Service: 8am to 5pm, M-F
    Contact_Instructions: Phone, Fax or e-maill
    Date: Aug-2007 (process 2 of 3)
    Road and street data were compiled from various sources to create this data file. NCDOT road data, individual county streets and address data, and federal TIGER/Line files were reviewed for each of the one hundred North Carolina counties to create the most accurate file. Attribute fields were manipulated to concur with the State Mapping Advisory Committee (SMAC) standards and populated using existing data, by NCDOT staff. Each county street layer was visually QC'd by staff and were then edgematched and joined to create one statewide streets data file.

    Person who carried out this activity:

    North Carolina Department of Transportation GIS Unit
    3401 Carl Sandburg Court
    Raleigh, NC 27610
    USA

    919-212-6000 (voice)
    919-212-5999 (FAX)
    gishelp@dot.state.nc.us

    Hours_of_Service: 8 am to 5 pm, M-F
    Contact_Instructions: Phone or email
    Date: 02-Apr-2008 (process 3 of 3)

    Person who carried out this activity:

    North Carolina Center for Geographic Information and Analysis
    c/o David Giordano
    Database Administration
    301 N. Wilmington Street, Suite 700
    Raleigh, North Carolina 27601-2825
    U.S.A.

    (919) 733-2090 (voice)
    (919)715-0725 (FAX)
    dataq@ncmail.net

    Hours_of_Service: 8am to 5pm
    Contact_Instructions: Phone and electronic mail preferred
  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?

    Attribute data has been verified by NCDOT GIS Unit staff.

  2. How accurate are the geographic locations?

    There are no measurement, precision, spatial, or data schema standards assigned to this data set.

  3. How accurate are the heights or depths?

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

    Dataset is complete to our knowledge. If an omission or error is located, it is corrected by NCDOT GIS Unit staff.

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

    There are no measurement, precision, spatial, or data schema standards assigned to this data set.


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 North Carolina Department of Transportation shall not be held liable for any errors in this data. This includes errors of omission, commission, errors concerning the content of the data, and relative and positional accuracy of the data. This data cannot be construed to be a legal document. Primary sources from which this data was compiled must be consulted for verification of information contained in this data. This data may not be resold.

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

    NC Department of Transportation Geographic Information Systems Unit
    3401 Carl Sandburg Ct
    Raleigh, North Carolina 27610

    919-212-6000 (voice)
    919-212-5999 (FAX)
    gishelp@dot.state.nc.us

    Hours_of_Service: 8am to 5pm, M-F
    Contact_Instructions: E-mail and phone
  2. What's the catalog number I need to order this data set?

    Data can be obtained by request

  3. What legal disclaimers am I supposed to read?

    The North Carolina Department of Transportation shall not be held liable for any errors in this data. This includes errors of omission, commission, errors concerning the content of the data, and relative and positional accuracy of the data. This data cannot be construed to be a legal document. Primary sources from which this data was compiled must be consulted for verification of information contained in this data. This data may not be resold. NCCGIA is charged with the development and maintenance of NC OneMap and, in cooperation with other mapping organizations, is committed to offering its users accurate, useful, and current information. Although every effort has been made to ensure the accuracy of information, errors and conditions originating from physical sources used to develop this dataset may be reflected in the data supplied. The user must be aware of possible conditions and bear responsibility for the appropriate use of the information with respect to possible errors, original map scale, collection methodology, currency of data, and other conditions specific to certain data. NCCGIA does not support secondary distribution of this dataset without its current, compliant metadata record. The use of trade names or commercial products does not constitute their endorsement by NCCGIA or North Carolina State Government.

  4. How can I download or order the data?

  5. Is there some other way to get the data?

    none

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

    ESRI Software


Who wrote the metadata?

Dates:
Last modified: 02-Apr-2008
Metadata author:
NC Department of Transportation
c/o GIS Unit
GIS Help Desk
3401 Carl Sandburg Ct
Raleigh, North Carolina 27610
USA

919-212-6000 (voice)
919-212-5999 (FAX)
gishelp@dot.state.nc.us

Hours_of_Service: 8am to 5pm, M-F
Contact_Instructions:
E-mail: gishelp@dot.state.nc.us Phone: 919-212-6000
Metadata standard:
FGDC Content Standards for Digital Geospatial Metadata (FGDC-STD-001-1998)


Generated by mp version 2.9.5 on Wed Aug 27 10:31:27 2008