To Do - Colorado

If you are mapping this region, please update the wiki with where you are working! I don't "own" the state of Colorado, just trying to create something so we all can coordinate better. Contact me if you have questions or feel free to update the wiki as you see fit!

Jenni

This page is intended to cover the rest of Colorado not in the Denver Metro area, including the other metro areas as identified here

Metro areas

Freeways

Major Highways / aka US Hwy

This section should include the major US Highway routes listed here

Minor Highways / aka State Hwy

This section should include the major State Highway routes listed here

Rural areas

Map editing guidelines

(or: Let's Just Do This Once), pulled from Boston metro To-do pages

Other Items (not listed below)

• Only split a road into 2 lanes if there is greater than a 20' median, e.g. 2 or more lanes could fit inside. Anything smaller should be a single road, even if there is a physical barrier (this will help with U-Turns, and will make it easier to edit the map in the short and long term).
• Note that in the old editor, there's also a feature allowing a mid-road line, which may help on roads with a physical barrier but not a lot of lanes.

Interstates/Major/Minor Highways

Due to issues with automatically generating shields on Highways with directionality, it appears to be MOST EFFECTIVE to add directionality, e.g. "I- 70 E" as the first step!

• eliminate unnecessary junctions: mid-segment, other than where the city changes or speed limit changes, get rid of 'em. (Important exception: don't make segments too long, because traffic analysis is per-segment. Perhaps keep it less than 1km per segment?)
• confirm lane directionality (note: one-way roads do not have center dividers)
• connectivity between highway segments
• road type is correct
• finalize geometry (remember to preserve Alt Names when changing geometry)
• naming: preserve TIGER base map naming as requested by Waze (common name, followed by US/State Hwy numbers and other aliases)

Ramps

• eliminate unnecessary junctions
• geometry matches aerials
• directions correct (note: one-way roads do not have center dividers)
• road type set to "ramps"
• street names should match existing signage; e.g.:
  • "Exit 20: Boston / Brighton / Cambridge"
  • "to I-90 W / Worcester"
• when a ramp segment has no sign of its own (e.g., after two ramps merge), borrow from the names of the "upstream" ramps, which should be similar if not identical
• check & correct all connectivity among ramps & roads--critical for proper routing

Helpful tip: if a ramp (or any other type of road) segment has no name, the client will display the next non-empty name in line. For example, suppose you have a two-way ramp segment. You can't name it as either an on- and off-ramp, because traffic (and navigation) will be using it for both. The solution is to leave the name blank, which will cause the names of adjoining segments to be displayed.

Wiki editing info can be found here. Sounds scary but it's easy Just watch this short video.