Benandjerry (talk | contribs) (Created page with "==== Ramps 200px|Ramp.png ==== right|300px|RoadPicN2.jpg right|300px|HBlue.png The following are to be classified...") |
Benandjerry (talk | contribs) No edit summary |
||
| (One intermediate revision by the same user not shown) | |||
| Line 5: | Line 5: | ||
The following are to be classified as {{Ramp}}. | The following are to be classified as {{Ramp}}. | ||
*Roads which connect roadways to other roadways as part of an [[Limited Access Interchange Style Guide|interchange]] | *Roads which connect roadways to other roadways as part of an [[Limited Access Interchange Style Guide|interchange]]. | ||
*Roads connecting freeways and highways with [[Rest areas]], parking areas, and service plazas (e.g., "to Service Area"). | *Roads connecting freeways and highways with [[Rest areas]], parking areas, and service plazas (e.g., "to Service Area"). | ||
The following are '''not''' to be classified as {{Ramp}}. | The following are '''not''' to be classified as {{Ramp}}. | ||
Latest revision as of 06:34, 4 November 2015
Ramps 
The following are to be classified as Ramp .
- Roads which connect roadways to other roadways as part of an interchange.
- Roads connecting freeways and highways with Rest areas, parking areas, and service plazas (e.g., "to Service Area").
The following are not to be classified as Ramp .
- At-grade connectors, unless they fit into one of the exceptions (see article).
- Turn lanes.
Ramp names do not appear on the client application map, but do appear in the text for routing directions. Entrance and exit ramps often contain a lot of text which is duplicative of roads already in the area, so this text is suppressed until the user actually needs it. This is also the reason for using the ramp type for named MUTI and jughandle segments—the text is needed for effective navigation instructions but would needlessly clutter the ramp.
Information on how to lay out ramps and set the proper angles from the main road can be found in the Junction Style Guide.