GISDATA.NEW_road_interstate_250k

Metadata also available as

Frequently-anticipated questions:


What does this data set describe?

    Title: GISDATA.NEW_road_interstate_250k
    Abstract:
    U.S. National Transportation Atlas Interstate Highways represents rural and urban interstate highways. U.S. National Transportation Atlas Interstate Highways is part of the National Highway Planning Network version 2.1 published by the Bureau of Transportation Statistics as part of the National Transportation Atlas Databases for the United States. NBII-SAIN (ed.) created this dataset by clipping ESRI 2002 intrstat.shp. to the southern and eastern states. NBII-SAIN website: (<http://sain.nbii.gov/>).
    Supplemental_Information: Largest scale when displaying the data: 1:250,000.

  1. How should this data set be cited?

    Bureau of Transportation Statistics, and Environmental Systems Research , Inc. (ESRI), 20020401, GISDATA.NEW_road_interstate_250k: ESRI Data & Maps 2002, Environmental Systems Research Institute, Inc. (ESRI), Redlands, California, USA.

    Online Links:

    • Server=rainbow.sunsite.utk.edu; Service=5151; User=gisdata; Version=SDE.DEFAULT

    Other_Citation_Details: Location: ESRI Data & Maps 2002 (CD 2) \usa

  2. What geographic area does the data set cover?

    West_Bounding_Coordinate: -109.048009
    East_Bounding_Coordinate: -67.781285
    North_Bounding_Coordinate: 46.847812
    South_Bounding_Coordinate: 25.749138

  3. What does it look like?

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

    Calendar_Date: 1997
    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 (1343)

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

      Horizontal positions are specified in geographic coordinates, that is, latitude and longitude. Latitudes are given to the nearest 0.000000. Longitudes are given to the nearest 0.000000. Latitude and longitude values are specified in Decimal degrees.

      The horizontal datum used is D_WGS_1984.
      The ellipsoid used is WGS_1984.
      The semi-major axis of the ellipsoid used is 6378137.000000.
      The flattening of the ellipsoid used is 1/298.257224.

      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?

    GISDATA.NEW_road_interstate_250k
    The lines represent a comprehensive network database of interstate highways within United States from the principal arterial highway system and National Highway System. (Source: Bureau of Transportation Statistics)

    OBJECTID
    Internal feature number. (Source: ESRI)

    Sequential unique whole numbers that are automatically generated.

    ROUTE_NUM
    Feature geometry. (Source: ESRI)

    Coordinates defining the features.

    DIST_MILES
    A composite field of the primary sign route that identifies the type, sign route number that can include a directional indicator, and a qualifier. The first character identifies the type, the following characters up to but not including a blank identify the sign route number that can include a directional indicator, a blank, and the last character identifies the qualifier. (Source: Bureau of Transportation Statistics)

    ValueDefinition
    Type, represented by the first character.(blank) - not signed, I - Interstate, U - U.S. route, S - State route, O - Off-Interstate business marker, C - County route, T - Township, M - Municipal, P - Parkway or Forest route marker, N- None of the above.
    Sign route number (can include a directional indicator), represented by all the following characters up to but not including a blank.Any combination of: AZ, 09, N, S, E, W.
    A blank space.This separates the sign route number from the qualifier.
    Qualifier, represented by the last character when preceded by a blank.(blank) - No qualifier, not signed, or not applicable; A - Alternate route; B - Business route; P - Bypass; S - Spur; L - Loop; F - Proposed (future); D - Temporary (detour); T - Truck route; N - None of the above.

    DIST_KM
    The length of the road feature in miles. (Source: Bureau of Transportation Statistics)

    Calculated lengths for the features.

    SHAPE
    The length of the road feature in kilometers. (Source: Bureau of Transportation Statistics)

    Calculated lengths for the features.

    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?

    Members of the Geographic Information Systems Laboratory, Pellissippi Research Institute, The University of Tennessee, Knoxville.

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

    Environmental Systems Research Institute, Inc. (ESRI)
    c/o Data Team
    380 New York Street
    Redlands, California 92373-8100
    USA

    909-793-2853 (voice)
    909-793-5953 (FAX)
    info@esri.com

    Hours_of_Service: 8:00 a.m.5:30 p.m. Pacific time, MondayFriday
    Contact_Instructions:
    In the United States Please direct all inquiries regarding software/data pricing and consulting services to your local ESRI Regional Office. For support, you may contact Technical Support by telephone (voice) between 6:00 a.m. and 6:00 p.m. Pacific time, Monday through Friday, by dialing 909-793-3774; facsimile (fax) available at 909-792-0960; electronic mail (e-mail) support@esri.com; or visit <http://support.esri.com>; ESRI holidays excluded.

    Outside the United States Please direct all inquiries regarding software/data pricing, sales, support, and consulting services to your local ESRI International Distributor. This information can be found at <http://gis.esri.com/intldist/contactint.cfm>.

    For other questions or comments, you may contact ESRI headquarters by e-mail, telephone, or fax or write to us.


Why was the data set created?

U.S. National Transportation Atlas Interstate Highways provides a comprehensive database of interstate highways from the nation's principal arterial highway system and the National Highway System. The data is generalized to improve draw performance and be used effectively at a national level.


How was the data set created?

  1. From what previous works were the data drawn?

    BTS - NHPN (source 1 of 1)
    Bureau of Transportation Statistics, 1997, National Highway Planning Network: National Highway Planning Network Version 2.1, Bureau of Transportation Statistics, Washington, DC, USA.

    This is part of the following larger work.

    Bureau of Transportation Statistics, 1997, National Transportation Atlas Databases: National Transportation Atlas Databases 1997, Bureau of Transportation Statistics, Washington, DC, USA.

    Type_of_Source_Media: CD?ROM
    Source_Scale_Denominator: 100000
    Source_Contribution: Attribute and geospatial data

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

    Date: 1997 (process 1 of 5)
    The general processing steps for the creation of the National Highway Planning Network: - Conflation of attributes for rural highways from [National Highway Planning Network V1.1, Bruce Peterson, Oak Ridge National Laboratory, 1992] to [USGS Digital Line Graph (DLG-3, 1978) Series] road alignments using R-MATCH software developed by the Geographic Information Systems Group, University of Tennessee. - Digitizing and conversion of state supplied digital and map data. Line work geodetically controlled to match [USGS Digital Line Graph (DLG-3, 1978) Series] line work. -Integration of conflated version of [National Highway Planning Network V1.1, Bruce Peterson, Oak Ridge National Laboratory, 1992] and assimilated State Data into a comprehensive topologically integrated network database. States edge matched. -Integration of supplemental State Data into the National Highway Planning Network Version 2.

    Note: "National Highway Planning Network Version 2 Machine Readable Data Files" prepared by the Federal Highway Administration, Office of Environment and Planning (HEP-11), Washington DC, 1994

    Additionally, the data was "clipped" to the southern and eastern states with ArcMap 8.2.

    Person who carried out this activity:

    NBII-SAIN

    Data sources produced in this process:
    • BTS - NHPN

    Date: 27-Jul-2000 (process 2 of 5)
    The following steps were performed by ESRI: Extracted data set from the National Highway Planning Network v2.1. Extracted all interstate highways, and then generalized. Removed unneeded attributes. Converted to North American Datum of 1983 (NAD83). Recalculated any attributes based on length. Created ArcGIS layer file (.lyr). Created ArcView legend file (.avl). Created projection file (.prj). Ran ArcView Avenue request ExportClean, and created spatial indices.

    Data sources used in this process:

    • BTS - NHPN

    (process 3 of 5)
    Metadata imported.

    Data sources used in this process:

    • S:\Library\ParentDataSets\ESRIDATA\usa\intrstat.shp.xml

    (process 4 of 5)
    Metadata imported.

    Data sources used in this process:

    • C:\WorkSpace\road_interstate_250k.xml

    (process 5 of 5)
    Dataset copied.

    Data sources used in this process:


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

  1. How well have the observations been checked?

  2. How accurate are the geographic locations?

    The original positional accuracy of the data set had a maximal positional error of 80 meters, and then it was generalized (tolerance unknown). The positional accuracy is unknown.

  3. How accurate are the heights or depths?

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

    After processing, the data set is checked for drawing display and number of records and file sizes compared with source materials. NBII-SAIN (ed.) created this file by clipping from the merged boundaries of three TN counties (Hamilton, Marion, and Sequatchie), two AL counties (Dekalb and Jackson), and three GA counties (Dade, Walker, and Catoosa) using the ESRI 2002 intrstat.shp. NBII-SAIN website: (<http://sain.nbii.gov/>).

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

    No duplicate features are present. The shapefile is exported using Avenue request ExportClean. This request verifies and enforces the correctness of shapes.


How can someone get a copy of the data set?

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

Access_Constraints: Access granted to Licensee only.
Use_Constraints:
The data are provided by multiple, third party data vendors under license to ESRI for inclusion on ESRI Data & Maps CD?ROMs for use with ESRI® software. Each data vendor has its own data licensing policies and may grant varying redistribution rights to end users. Please consult the redistribution rights below for this data set provided on ESRI Data & Maps CD?ROMs. As used herein, ?Geodata? shall mean any digital data set consisting of geographic data coordinates and associated attributes.

The redistribution rights for this data set: Public domain data from U.S. government is freely redistributable with proper metadata and source attribution.

The terms and conditions below apply to all the data sets provided on the ESRI Data & Maps CD?ROMs.

Proprietary Rights and Copyright: Licensee acknowledges that the Data and Related Materials contain proprietary and confidential property of ESRI and its licensor(s). The Data and Related Materials are owned by ESRI and its licensor(s) and are protected by United States copyright laws and applicable international copyright treaties and/or conventions.

Limited Warranty and Disclaimer: ESRI warrants that the media upon which the Data and Related Materials are provided will be free from defects in materials and workmanship under normal use and service for a period of ninety (90) days from the date of receipt.

THE DATA AND RELATED MATERIALS ARE EXCLUDED FROM THE LIMITED WARRANTY, AND THE LICENSEE EXPRESSLY ACKNOWLEDGES THAT THE DATA CONTAINS SOME NONCONFORMITIES, DEFECTS, OR ERRORS. ESRI DOES NOT WARRANT THAT THE DATA WILL MEET LICENSEE'S NEEDS OR EXPECTATIONS; THAT THE USE OF THE DATA WILL BE UNINTERRUPTED; OR THAT ALL NONCONFORMITIES, DEFECTS, OR ERRORS CAN OR WILL BE CORRECTED. ESRI IS NOT INVITING RELIANCE ON THIS DATA, AND THE LICENSEE SHOULD ALWAYS VERIFY ACTUAL DATA.

EXCEPT FOR THE LIMITED WARRANTY SET FORTH ABOVE, THE DATA AND RELATED MATERIALS CONTAINED THEREIN ARE PROVIDED "AS-IS," WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.

Exclusive Remedy and Limitation of Liability: The entire liability of ESRI or its licensor(s) and Licensee's exclusive remedy shall be to terminate the Agreement upon Licensee returning the Data and Related Materials to ESRI with a copy of Licensee's invoice/receipt and ESRI returning the license fees paid to Licensee.

IN NO EVENT SHALL ESRI AND/OR ITS LICENSOR(S) BE LIABLE FOR COSTS OF PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOST PROFITS, LOST SALES, OR BUSINESS EXPENDITURES, INVESTMENTS, OR COMMITMENTS IN CONNECTION WITH ANY BUSINESS; LOSS OF ANY GOODWILL; OR FOR ANY INDIRECT, SPECIAL, INCIDENTAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES ARISING OUT OF THIS AGREEMENT OR USE OF THE DATA AND RELATED MATERIALS, HOWEVER CAUSED, ON ANY THEORY OF LIABILITY, AND WHETHER OR NOT ESRI OR ITS LICENSOR(S) HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. THESE LIMITATIONS SHALL APPLY NOTWITHSTANDING ANY FAILURE OF ESSENTIAL PURPOSE OF ANY EXCLUSIVE REMEDY.

Third Party Beneficiary: ESRI's licensor(s) has (have) authorized ESRI to (sub)distribute and (sub)license its (their) data as incorporated into the Data and Related Materials. As an intended third party beneficiary to this Agreement, the ESRI licensor(s) is (are) entitled to directly enforce, in its own name, the rights and obligations undertaken by the Licensee and to seek all legal and equitable remedies as are afforded to ESRI.

In the event that the data vendor(s) has (have) granted the end user permission to redistribute the Geodata, please use proper proprietary or copyright attribution for the various data vendor(s), and provide the associated metadata file(s) with the Geodata. In compliance with FGDC metadata standards, ESRI has attempted to practice proper metadata methodologies by providing any data source information, descriptions, and file names to assist in this effort.

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

    Environmental Systems Research Institute, Inc. (ESRI); ESRI International Distributors
    380 New York Street
    Redlands, California 92373-8100
    USA

    800-447-9778 (voice)

    Contact_Instructions:
    In the United States, contact the ESRI Telesales staff at 800-447-9778 for more information about our software and data.

    Outside the United States, please direct all inquiries to your local ESRI International Distributor. This information can be found at <http://gis.esri.com/intldist/contactint.cfm>.

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

    Offline Data

  3. What legal disclaimers am I supposed to read?

    See use constraints.

  4. How can I download or order the data?

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

    To use this data requires software that supports ArcView® GIS shapefiles.


Who wrote the metadata?

Dates:
Last modified: 08-May-2003

Metadata author:
Environmental Systems Research Institute, Inc. (ESRI)
c/o Data Team
380 New York Street
Redlands, California 92373-8100
USA

909-793-2853 (voice)
909-793-5953 (FAX)
info@esri.com

Hours_of_Service: 8:00 a.m.5:30 p.m. Pacific time, MondayFriday
Metadata standard:
FGDC Content Standards for Digital Geospatial Metadata (FGDC-STD-001-1998)

Metadata extensions used:


Generated by mp version 2.7.3 on Wed Jul 30 16:02:44 2003