KC-Guardrail (talk | contribs) No edit summary |
Nimper2000 (talk | contribs) (Updated visual examples of TE on livemap) |
||
(6 intermediate revisions by 4 users not shown) | |||
Line 9: | Line 9: | ||
=== Functional Classifications === | === Functional Classifications === | ||
Kansas uses the Functional Classification rules outlined in the [[ | Kansas uses the Functional Classification rules outlined in the [[Road types]] page | ||
The table below shows a cross reference for the minimum road types in Kansas. Keep in mind that these are only minimums, and may need to be upgraded based on the qualities defined on the [[Road types|road type guidelines]] page. | |||
<br /> | |||
<center> | |||
{|border="1" cellpadding="2" | {|border="1" cellpadding="2" | ||
|- align="center" | |- align="center" | ||
Line 40: | Line 41: | ||
|{{Street}} | |{{Street}} | ||
|} | |} | ||
</center> | |||
<br /> | |||
======**Kansas numbered state highways should be set to a minimum of Minor Highway.**====== | |||
<br /> | |||
=== Lock Levels === | |||
Kansas uses lock levels common among the [[USA/Plains]] region. | |||
<br /> | |||
{{Lock Standard State|KS}} | |||
<br /> | |||
==='''True Elevation'''=== | |||
'''''NOTE: If you have any questions, please seek guidance from a Kansas State Manager or one of the Plains Region Leadership team.''''' | |||
The Plains Region uses the concept of True Elevation (TE) to better represent segments in relationship with its surroundings/ground level. Most segments should have an elevation of Ground unless they pass over another segment, waterway, or natural feature. '''True Elevation applies to both drivable and non-drivable segments'''. | |||
= | '''Definitions''' | ||
''Bridge'' | |||
*Segment travels over another segment (also known as Overpass). | |||
*Segment travels over a large river or large body of water. | |||
*Segment artificially elevated to pass over large ground level objects and large natural features. | |||
''Tunnel'' | |||
A tunnel is any road segment that is underground and thus the GPS reception is inconsistent. | |||
'''Examples''' | |||
*Simple Interchange | |||
*More Complex Interchange (requiring junctioning of ramp segments to maintain ground elevation) | |||
*Major Circular Interchange | |||
*Complex Interchange | |||
*Raised Freeway (over preserve area) | |||
'''Visuals''' | |||
Below are two images showing the difference in Live Map rendering when True Elevation is not applied and then when True Elevation is applied. Take note on the shading along the edge of the segment when True Elevation is used and how it is missing when it is not. At the time of this writing (August 2022) the Waze app does not show this different shading. | |||
{| class="wikitable" | |||
![[File:KS_NoTE_Ex.png|400px|thumb]] | |||
![[File:KS_TE_Ex.png|400px|thumb]] | |||
|- | |||
!'''Segment over water without True Elevation''' | |||
!'''Segment over water with True Elevation''' | |||
|} | |||
'''Implementation''' | |||
*Elevations of overlapping segments should be set relative to each other, with the lowest segment as Ground (unless that segment is a tunnel). | |||
*Only elevate/lower the actual bridge/tunnel section of the road. | |||
*Bridges should be cut at the start/end of the bridge where the land falls away. You can usually see guardrails at the start/end of the bridge section. Also the pavement type may change (Asphalt to Concrete for example). | |||
**Do not '''cut segments''' for elevation purposes if the bridge starts/stops within 60m/200ft of an existing junction. | |||
**Maintain some uniformity for display purposes when determining where to make the splits. | |||
**Elevated bridge segments should be 15 meters (50 feet) or greater. Bridges smaller than 15 meters, such as over a creek or box culvert, most likely should not be elevated. Check with SER Leadership before elevating sub-15-meter bridge segments. | |||
*Only set elevation as low/high as necessary. For example, no segment should be Elevation +2 unless it passes over another segment with Elevation +1. | |||
*Tunneled segments shall have lower elevation relative to ground and ''Tunnel'' should be checked. | |||
*Only segments that are actually '''underground''' should have negative elevation. | |||
*Tunnels should be cut at least 15m/50ft before and after the tunnel, to allow time for the GPS to regain signal. | |||
*'''The use of common sense is paramount in using True Elevation.''' | |||
<!---- DO NOT MODIFY BELOW ------ DO NOT MODIFY BELOW ------ DO NOT MODIFY BELOW ---- | <!---- DO NOT MODIFY BELOW ------ DO NOT MODIFY BELOW ------ DO NOT MODIFY BELOW ---- |
Latest revision as of 22:11, 3 August 2022
State Highway Naming
Kansas highways are named as K-### (e.g. K-7, K-7 N). This includes their related business, loops, and spurs. (e.g. K-7 BUS) This shortened version takes up less space on the map screen and is announced correctly as "Kansas Highway ###" while navigating with the Waze app.
County Road Naming
County roads with the name designation of "County Road ###" are named as CR-### (e.g. CR-110). This shortened version takes up less space on the map screen and is announced correctly as "County Road ###" while navigating with the Waze app.
Functional Classifications
Kansas uses the Functional Classification rules outlined in the Road types page
The table below shows a cross reference for the minimum road types in Kansas. Keep in mind that these are only minimums, and may need to be upgraded based on the qualities defined on the road type guidelines page.
KDOT Classification | Waze Road Type |
---|---|
Interstate | Freeway |
Other Expressway | Major Highway |
Other Principal Arterial | Major Highway |
Minor Arterial | Minor Highway |
Major Collector | Primary Street |
Minor Collector | Primary Street |
Local Road | Street |
**Kansas numbered state highways should be set to a minimum of Minor Highway.**
Lock Levels
Kansas uses lock levels common among the USA/Plains region.
In Kansas we have a set minimum standard for locking roads based on segment type. Any road of a certain segment type must be locked at least to the rank (level) in the chart below. Roads may be locked higher for protection and special situations (areas with construction, tricky design, frequent mistakes, imaging inaccuracies, and the like), but should not be locked lower.
A great time to implement these locks is while bringing the road types of an area into compliance with the current US road type standards (FC and highway systems). Lock the roads based on type after they've been set to current US road type standards.
Segment Type | Statewide |
---|---|
Freeway | 4 |
Ramp | Highest rank of connected segments |
Major Highway | 3 |
Minor Highway | 3 |
Primary Street | 2 |
Street | 1 |
• • • • Ferry • • • • | 5 |
|-|-|-|-|-|-|-|-|-| Railroad |-|-|-|-|-|-|-|-|-| | 2 |
True Elevation
NOTE: If you have any questions, please seek guidance from a Kansas State Manager or one of the Plains Region Leadership team.
The Plains Region uses the concept of True Elevation (TE) to better represent segments in relationship with its surroundings/ground level. Most segments should have an elevation of Ground unless they pass over another segment, waterway, or natural feature. True Elevation applies to both drivable and non-drivable segments.
Definitions
Bridge
- Segment travels over another segment (also known as Overpass).
- Segment travels over a large river or large body of water.
- Segment artificially elevated to pass over large ground level objects and large natural features.
Tunnel
A tunnel is any road segment that is underground and thus the GPS reception is inconsistent.
Examples
- Simple Interchange
- More Complex Interchange (requiring junctioning of ramp segments to maintain ground elevation)
- Major Circular Interchange
- Complex Interchange
- Raised Freeway (over preserve area)
Visuals
Below are two images showing the difference in Live Map rendering when True Elevation is not applied and then when True Elevation is applied. Take note on the shading along the edge of the segment when True Elevation is used and how it is missing when it is not. At the time of this writing (August 2022) the Waze app does not show this different shading.
Segment over water without True Elevation | Segment over water with True Elevation |
---|
Implementation
- Elevations of overlapping segments should be set relative to each other, with the lowest segment as Ground (unless that segment is a tunnel).
- Only elevate/lower the actual bridge/tunnel section of the road.
- Bridges should be cut at the start/end of the bridge where the land falls away. You can usually see guardrails at the start/end of the bridge section. Also the pavement type may change (Asphalt to Concrete for example).
- Do not cut segments for elevation purposes if the bridge starts/stops within 60m/200ft of an existing junction.
- Maintain some uniformity for display purposes when determining where to make the splits.
- Elevated bridge segments should be 15 meters (50 feet) or greater. Bridges smaller than 15 meters, such as over a creek or box culvert, most likely should not be elevated. Check with SER Leadership before elevating sub-15-meter bridge segments.
- Only set elevation as low/high as necessary. For example, no segment should be Elevation +2 unless it passes over another segment with Elevation +1.
- Tunneled segments shall have lower elevation relative to ground and Tunnel should be checked.
- Only segments that are actually underground should have negative elevation.
- Tunnels should be cut at least 15m/50ft before and after the tunnel, to allow time for the GPS to regain signal.
- The use of common sense is paramount in using True Elevation.