|
|
| Line 31: |
Line 31: |
|
| |
|
|
| |
|
|
| |
| ==== True Elevation ====
| |
| In Michigan, an expanded implementation of the general guidance for [[Creating_and_editing_road_segments#Road_elevation|elevation]] and [[Overpasses,_Underpasses_and_Bridges|overpasses, underpasses, and bridges]], has been adopted and follows Illinois rules. Please refer to the these sections for additional guidance.
| |
|
| |
| ''True Elevation'' refers to layers of road decks supported above and below the terrain (ground) with open space between them. In essence, any road segment which a bird, such as a hawk, could fly underneath should be elevated above ground level. The inverse condition applies to tunnels or multi-level underground segments where your average groundhog could tunnel between them.
| |
|
| |
| ''What is an overpass?'' An overpass is a general term for any road, walkway, railroad, bridge, or other mapped structure crossing over an impediment such as a waterway, natural formation, or another road, walkway, railroad, or bridge. In our mapping context it can also be conceptualized underground where tunnels crossing over, or under, one another.
| |
|
| |
| ===== Elevation =====
| |
| Apply these points to the use of true elevation:
| |
| :* All roads when not supported above or tunneled below the terrain are set to ground elevation unless otherwise noted.
| |
| :* If a road segment is supported above the terrain or another road segment, the elevation of the segment should be set one higher (+1) than the segment or terrain (ground) immediately beneath.
| |
| :* The elevation of road segments completely or transitionally sub-surface should be negative and one less than (-1) the surface, tunnel, or level immediately above.
| |
| :* Ramps are to be set to the lower elevation of the roadways to which they junction unless passing over or under other segments.
| |
|
| |
| ===== Segmentation =====
| |
| When creating segments to implement this guidance, please observe these precepts:
| |
| :* Create junction nodes for elevation purposes at the point the physical change in elevation occurs unless otherwise specified.
| |
| <!--
| |
| :* Use existing junction nodes when within 500 feet of an elevation change. ''For example, do not create new junction nodes for elevation purposes at an interchange when ramps junction with the main road within 500 feet of the physical overpass.''
| |
| :* Do not create an elevated overpass less than 150 feet in length (with a strong preference for 200 feet).
| |
| -->
| |
| :* Do not cut a segment within 200 feet (60m) of an existing junction.
| |
| :* Do not create a segment less than 200 feet (60m) in length.
| |
| :* Underground segments should be cut at least 50 feet (15m) before, or after, the entrance to the subterranean section.
| |
| :* Check the tunnel option for any underground segment.
| |
|
| |
| ===== Culverts =====
| |
| A ''culvert'' is a tunnel allowing a stream or open drain to pass under a roadway. Under normal circumstances these are not to be mapped. However, an elevated segment for a culvert may be created to support real-time closures (due to significant flooding or repair) when '''all''' these conditions are met:
| |
| :* The culvert is of significant construction requiring multiple day closures to repair or has major flooding potential.
| |
| :* The culvert not located near the center of the segment.
| |
| :* The segment is heavily populated by potential destinations and a route to the wrong end of the segment would result in a un-routed detour of more than one mile.
| |
| <!---- DO NOT MODIFY BELOW ------ DO NOT MODIFY BELOW ------ DO NOT MODIFY BELOW ---- | | <!---- DO NOT MODIFY BELOW ------ DO NOT MODIFY BELOW ------ DO NOT MODIFY BELOW ---- |
| ------------------------------------------------------------------------------------- | | ------------------------------------------------------------------------------------- |
NOTE: Michigan follows the GLR road locking standards for all roads
County Highways versus County Roads
- Michigan has an "intercounty" highway system in addition to locally maintained county roads. In both cases, naming conventions should follow highway naming by state.
- Numbered county highways are prefixed with A through H based on geography. Naming convention should be "CR-[Letter Prefix][#]" (i.e. "CR-D19"). In all cases, local signage should be used to designate a primary name, while the county highway designation could be an alternate name if appropriate. While these roads could conceivably be classified higher, the lowest road type used should be Minor Highway regardless of appearance or functional classification.
- A small number of counties maintain numbered county roads that are not part of the statewide A-H highway system. These roads should be named CR-[#] (i.e. "CR-388") and would typically appear as Primary Street, Street, or even Dirt Road.
State Numbered Highway Naming
The following proposal for a new national state highway naming standard is currently under review by the GLR State Managers.
Primary Street Name: Use whatever name is in common usage in that area. (Check business addresses, GIS, etc).
If the commonly used Primary Street name is not the state's Numbered Highway name (Example: M-59), include an alternate street name with the Numbered Highway name.
When to include a City Name on a State Numbered Highway:
- Primary Street Name: No City Name
- Alternate Street Names: No City Names
- divided roadway with limited access:
- Primary Street Name: No City Name
- Alternate Street Names: No City Names
- all other mH/MH Numbered State Highways
- Primary Street Name: Include a city name in locales that use city names.
- Alternate Street Names that use a state Numbered Highway name (Example: M-59): No City Name
Functional Classification
Michigan follows the Waze Functional Classification (FC) standard for determining what Road Type to use for all paved roads.
