Service Description: This dataset represents the locations of tunnels for roads within the continental United States, Alaska and Hawaii.
Homeland Security
Use Cases: Use cases describe how the data may be used and help to define and clarify requirements.
1) In the event of a threat against tunnel infrastructure, this dataset may be used to locate tunnels needing protection.
2) In the event of a general threat against the transportation industry, this dataset may be used to contact the transportation industry to apprise them of the threat.
3) An accident has occurred at a tunnel and emergency medical personnel / rescue personnel must quickly deploy to the tunnel.
4) A resource for emergency route planning purposes.
5) A resource for situational awareness planning and response for federal government events.
Service ItemId: 63cc6040f0e940969dac5311243625ee
Has Versioned Data: false
Max Record Count: 2000
Supported query Formats: JSON
Supports applyEdits with GlobalIds: False
Supports Shared Templates: True
All Layers and Tables
Layers:
Description: Tunnels in the United States According to the HSIP Tiger Team Report, a tunnel is defined as a linear underground passageway open at both ends. This dataset is based on the U.S. Department of Transportation's National Bridge Inventory (NBI). Records in the NBI that are attributed as "Tunnels" were extracted by TGS and were located using a combination of ortho imagery, topographic DRGs, NAVTEQ streets, and NAVTEQ railroads. Two points were captured for each tunnel, one at each tunnel opening. A line was then created either by tracing the NAVTEQ street / railroad, or, if there was not a NAVTEQ street / railroad coincident with the tunnel, then by a straight line joining the two points. For some tunnels, the NBI contains two records, one for the road through the tunnel and one for the road on top of the tunnel (if any). In these cases, both have been captured in this dataset. Features in this dataset that are over tunnels have a [RECTYPE] of "1", while features that are in tunnels have a [RECTYPE] of "2". Presumably, this was done because both roads could be blocked if the tunnel was destroyed. In some cases, the NBI only represented a tunnel with a record of type = "1" (over). In these cases, the following rules were applied: 1) If there was no road running through the tunnel, the road on top of the tunnel was captured. For example, if a mine conveyor runs through the tunnel and a county highway runs on top of the tunnel, the county highway was captured. 2) If a road ran through the tunnel, then this road was captured and the [RECTYPE] was changed to "2". The "feature carried" and "feature intersected" fields were also changed to be consistent with the feature actually captured. According to the U.S. DOT: "Our reporting requirements do not extend to tunnels, therefore, any info we have should be considered incomplete."
Copyright Text:
Spatial Reference: 102100 (3857)
Initial Extent:
XMin: -13606974.1977606
YMin: 4557752.91680066
XMax: -13602604.9841371
YMax: 4561186.16617869
Spatial Reference: 102100 (3857)
Full Extent:
XMin: -13605181.1075
YMin: 4558903.1435
XMax: -13604275.4662
YMax: 4559908.6906
Spatial Reference: 102100 (3857)
Units: esriMeters
Child Resources:
Info
SharedTemplates
Supported Operations:
Query
ConvertFormat
Get Estimates