Keywords
Theme:
FWGOVERNMENTALUNITS, FWTRANSPORTATION, FWROADS
Theme:
Boundaries
Theme:
Line Feature, Feature Identifier, Census Feature Class Code (CFCC), FMCSA, Hazardous Material Route, Point/Node, TIGER/Line, Latitude/Longitude, Vector, TIGER/Line Identification Number (TLID)
Place:
United States, Puerto Rico, State
Stratum:
ground
Temporal:
2006, 2007, 2008
Description
Abstract
The Federal Motor Carrier Safety Administration (FMCSA) Hazardous Material Routes were developed using the 2004 First Edition TIGER/Line files. The routes are described in the National Hazardous Material Route Registry (NMHRR). The on-line NMHRR linkage is http://hazmat.fmcsa.dot.gov/nhmrr/index.asp
With the exception of 13 features that were not identified with the Tiger/Lines, Hazmat routes were created by extracting the TIGER/Line segments that corresponded to each individual route. Hazmat routes in the NTAD, are organized into 3 database files, hazmat.shp, hmroutes.dbf, and hmstcnty.dbf. Each record in each database represents a unique Tiger/Line segment. These Tiger/Line segments are grouped into routes identified as character strings in the ROUTE_ID field in the hmroutes.dbf table. The route name appearing in the ROUTE_ID is assigned by FMCSA and is unique for each State [this sentence could be deleted - it doesn't add a lot to it]. The hmstcnty.dbf table allows the user to select routes by State and County. A single shapefile, called hazmat.shp, represents geometry for all routes in the United States.
Purpose
In order for the public to be able to view the Hazardous Material Routes reported to FMCSA, the data is being released in ESRI shapefile format for use in a GIS system.
Supplementary Information
The data provided is in the native Latitude/Longitude coordinate
system inherited from the TIGER/Line data.
_________________
Status of the data
On going
Data update frequency:
While this is a preliminary release, updates will be released
when available.
Time period for which the data is relevant
Publication Information
Who created the data: Federal Motor Carrier Safety Administration, Research and Innovative Technology Administration's Bureau of Transportation Statistics (RITA/BTS), Volpe NTSC
Date and time:
2008
Publisher and place:
Research and Innovative Technology Administration's Bureau of Transportation Statistics (RITA/BTS), Washington, DC
Series name: FMCSA Hazardous Material Routes
Series issue: None at time of this release.
_________________
Data storage and access information
File name: hazmat
Type of data: vector digital data
Location of the data:
http://hazmat.fmcsa.dot.gov/nhmrr/index.asp
http://www.bts.gov/programs/geographic_information_services/
Data processing environment: Microsoft Windows XP Version 5.1 (Build 2600) Service Pack 2; ESRI ArcCatalog 9.1.0.722
Accessing the data
Data format: ESRI Shapefile
Size of the data: 14.752 MB
Data transfer size: 14.752 MB
How to decompress the file: No compression applied. However, if using digital transfer online option, note access instructions.
Access instructions: NTAD is available for download at www.bts.gov/programs/geographic_information_services. The NTAD DVD can also be ordered from the online bookstore at www.bts.gov.
Available media: DVD
Constraints on accessing and using the data
Access constraints:
None
Use constraints:
Acknowledgment of the Research and Innovative Technology Administration's Bureau of Transportation Statistics (RITA/BTS) National Transportation Atlas Databases (NTAD) 2008 would be appreciated in products derived from these data.
Details about this document
Contents last updated: 20080519
at time 09350200
Contents last reviewed: 2008
Who completed this document
Geospatial Information Program
Research and Innovative Technology Administration's Bureau of Transportation Statistics (RITA/BTS)
mailing address:
Washington, DC 20590
United States
(202) 366-3282 (voice)
answers@bts.gov
Standards used to create this document
Standard name: FGDC Content Standards for Digital Geospatial Metadata
Standard version: FGDC-STD-001-1998
Time convention used in this document: local time
Metadata profiles defining additonal information
ESRI Metadata Profile: http://www.esri.com/metadata/esriprof80.html
Horizontal coordinate system
Geographic coordinate system name: GCS_WGS_1984
Details
Geographic Coordinate System
Latitude Resolution: 0.000001
Longitude Resolution: 0.000001
Geographic Coordinate Units: Decimal degrees
Geodetic Model
Horizontal Datum Name: D_WGS_1984
Ellipsoid Name: WGS_1984
Semi-major Axis: 6378137.000000
Denominator of Flattening Ratio: 298.257224
_________________
Bounding coordinates
Horizontal
In decimal degrees
West:
-124.216232
East:
-71.051495
North:
49.000758
South:
26.111954
In projected or local coordinates
Left: -124.216232
Right: -71.051495
Top: 49.000758
Bottom: 26.111954
_________________
Lineage
FGDC lineage
Process step 1
Process description: Hazardous Material Routes are extracted from the Census TIGER/Line files. This is the preliminary release.
Source used: NMHRR
Process date: 2006
Process step 2
Process description: RITA/BTS has normalized the original HazMat table in an effort to increase efficiencies in data storage and retrieval. The original table contained the following fields: FID (Primary Key), Shape (geometry), TLID, FEDIRP, FENAME, FETYPE, FEDIRS, CFCC, STCNTY, RouteID, RouteType. After studying the table it was found that the STCNTY, ROUTEID and ROUTETYPE fields could be separated from the hazmat table and placed into related tables. Below are the processes taken to normalize the data.
First the primary key field (FID) was duplicated within hazmat table. The field was named PK and now acts as the primary key for the table. Then the table was run through a program that identified which records were duplicates. For each duplicate record the appropriate Primary Key was assigned.
Next the hmroutes table was created. The RouteID and RouteType fields were placed in this table along with FK field. The FK field was populated with the PK values of the hazmat table and will serve as the foreign key field. The ROUTEID field was a concatenation of the State Abbreviation, the Route Type and the Route Number. The table was run through a program that parsed and stored the state abbreviation, the route type and route number into separate fields.
Then the hmstcnty table was created. The STCNTY field was placed in this table along with FK field. The FK field was populated with the PK values of the hazmat table and will serve as the foreign key field. The STCNTY field was a concatenation of the State FIPS and the County FIPS codes. The table was run through a program that parsed and stored the state FIPS and county FIPS into separate fields.
Finally the duplicate records in the hazmat table were deleted.
Process date: 2006
Who did this process
Geospatial Information Program
Research and Innovative Technology Administration's Bureau of Transportation Statistics (RITA/BTS)
mailing and physical address:
1 202 366 DATA (voice)
1 202 366 3640 (fax)
answers@bts.gov
Sources
Source 1:
National Hazardous Material Routes
(NMHRR)
Media: CD-ROM
Contribution: Geographic and cartographic information (line segments) selected from the Census TIGER/Line database.
Currentness of this source
_________________
Spatial data quality
Horizontal positional accuracy
Accuracy is inherited from the TIGER/Line files:
The Census Bureau uses Global Positioning System (GPS) coordinates at road centerline intersections to evaluate the horizontal spatial accuracy of source files that may be used to realign road features in the TIGER database and test the horizontal spatial accuracy of the road features in the TIGER/Line files. The test compares a survey-grade GPS coordinate to its associated road centerline intersection in the TIGER file. The test is based upon an independent collection of GPS coordinates for a random sample of road intersections from a centerline file that meet certain criteria. The points are referred to as the sample points and are gathered through a private contractor working for the Census Bureau. Since
the collection method uses survey-quality GPS-based field techniques, the resulting control points are considered "ground truth" against which the TIGER road centerline intersection coordinates are compared. The distances between the coordinates are calculated and the Census Bureau determines the Circular Error 95% (CE95). That is, the accuracy of the file in meters with 95% confidence. The CE95 can be calculated from the mean and standard deviation by using the formula: mean of differences plus (2.65 times the standard deviation). CE95 results reported for each file tested are determined using a spreadsheet with embedded statistical formula. The use and applicability of the spreadsheet and its embedded formula have been verified by Census Bureau statisticians. The basis of the calculation is the use of the root mean square error (RSME). This is the method as stated in the U.S. Government's Federal Geographic Data Committee
Standard FGDC-STD-007.3-1998, Geospatial Positioning Accuracy Standards.
Part 3: National Standard for Spatial Data Accuracy. The results of using this measure of accuracy are in compliance with Federal Spatial Data requirements.
In terms of the Census Bureau application, the dataset coordinate values
are those taken from the centerline file and the coordinate values from
an independent source of higher accuracy are those acquired through the
Census Bureau's contractor. Refer to the 2004 First Edition TIGER/Line metadata for each county or statistically equivalent entity for information on the spatial accuracy of features in that county. Please note that the horizontal spatial
accuracy, where reported, refers only to the realigned road features identified as matched to the positionally accurate source file with that accuracy. It is not the spatial accuracy of the TIGER/Line file as a whole.
_________________
Spatial data description
Vector data information
ESRI description
hazmat
ESRI feature type: Simple
Geometry type: Polyline
Topology: FALSE
Feature count: 145005
Spatial Index: TRUE
Linear referencing: FALSE
SDTS description
Feature class: SDTS feature type, feature count
hazmat:
String, 145005
Details for hazmat
Type of object: Feature Class
Number of records: 145005
Description
FMCSA Hazardous Material Routes in GIS Format
Source: Federal Motor Carrier Safety Administration
Attributes
FID
Definition: System generated primary key; a unique identification number for the feature
Definition Source: ESRI
Shape
Definition: Internal Arcview Generated Attribute
Definition Source: ArcView
TLID
Data type: Number
Width: 10
Definition: The Tiger Line Identification number
Definition Source: Census TIGER/Line
FEDIRP
Data type: String
Width: 2
Definition: Feature direction prefix
Definition Source: Census TIGER/Line
FENAME
Data type: String
Width: 30
Definition: Feature name
Definition Source: Census TIGER/Line
FETYPE
Data type: String
Width: 4
Definition: Feature Type
Definition Source: Census TIGER/Line
FEDIRS
Data type: String
Width: 2
Definition: Feature Direction Code
Definition Source: Census TIGER/Line
CFCC
Data type: String
Width: 3
Definition: Census Feature Class Code
Definition Source: Census TIGER/Line
PK
Data type: Number
Width: 9
Definition: Primary Key
Definition Source: RITA/BTS
VERSION
Data type: String
Width: 2
Definition: Version of the database
Definition Source: RITA/BTS
_________________
Overview
Hazardous Material Route files contain data describing Line Features.
The data/attributes describing the lines include coordinates, feature identifiers (route id and route type), CFCCs (inherited from TIGER/Line and used to identify
the TIGER/Line characteristic of a feature) and secondary feature name (Street name: inherited from TIGER/Line)
The hazmat table stores the basic spatial data for the Hazardous Materials information. The hmroutes tables stores the routing information and the hmstcnty table holds the state and county information. All of the data are not stored in a single table because it is inefficient.
To integrate the hmroutes table with the hazmat table you must create a relationship between the two. This relationship is defined by hazmat's PK field and the hmroute's FK field. More specifically for each PK value in the hazmat table there are one or more FK values in the hmroutes table.
To integrate the hmstcnty table with the hazmat table you must create a relationship between the two. This relationship is defined by hazmat's PK field and the hmstcnty's FK field. More specifically for each PK value in the hazmat table there are one or more FK values in the hmstcnty table. For information on how to create a relationship between tables search for the term "relate" in the help file of your GIS application.
Overview citation
hmstcnty
OID - The primary key and a unique identification number for the record
FK - The foreign key. This field is used to link this table and the related features of the hazmat table
StFIPS - The State FIPS code for the related feature
CntyFIPS - the county FIPS code for the related feature
hmroutes
OID - The primary key and a unique identification number for the record
FK - The foreign key. This field is used to link this table and the related features of the hazmat table.
STATEABBR - Abbreviation of the state in which the related hazmat feature occurs
ROUTE_ID - The original route identification code presented by Highways. It's a concatenation of the State Abbreviation, the Route Type and the Route Number.
STATEABBR - The two letter state abbreviation
ROUTE_TYPE - The route type of the related hazmat feature
ROUTENUM - the route number of the related Hazmat feature.