Post Reply

[PAGE UPDATE] Forest Service Roads - Editor discretion

Post by DwarfLord
In local discussions regarding Forest Service roads, a concern emerged that editors are not being sufficiently warned about the hazards of effectively doing a copy-paste from MVUMs into the Waze map. I'd like to suggest two changes to the Forest Service Roads article, as follows:

1. MOVE the Editor discretion section from being a minor subsection of Maintenance Levels to its own major section immediately below Maintenance Levels.

2. CHANGE the text of the Editor discretion section to read as follows:
Proposed updated Editor Discretion section wrote: Always exercise caution when mapping roads found on an MVUM, particularly through roads! MVUMs may be inaccurate or out of date, and roads may vary in quality over seasons depending on the climate (rain/snow). Particularly, some roads in Maintenance Level 3 may have attributes that are closer to Off-Road / Not Maintained than Street.

Before mapping a road, compare the MVUM with recent aerial imagery (and with Street View and anecdotal visitor reports if possible) and verify that the road remains drivable. Vegetation growing not just between the tracks but in them often signifies an abandoned road. Some roads may be permanently closed with boulders or solid fencing placed at their endpoints. Don't map these, even if they appear on the MVUM! Mapping or completing abandoned roads may have severe unintended consequences. For example:
  • If the road is mapped as a through road, even one with high penalties, Waze may attempt to route emergency traffic over it when primary roads have been closed. Waze could endanger lives by offering impassable roads as escape routes! Ideally editors responding in an emergency will identify and close all relevant through roads, but the more roads involved, the greater the response effort, and the more likely something will be missed.
  • Any road's presence on the Waze display could encourage Wazers to try it and potentially get stuck.
  • Even if not used for routing, mapped roads serve an orientation purpose. Drivers passing a "road" that is shown on their display but no longer looks like a road (overgrown, permanently fenced off or blocked, etc.) may be disoriented by the inconsistency.
When selecting road type, besides considering the recommendations in this article, also take other nearby roads into account. For example, if another road nearby appears to be in much better condition and more heavily used, and it is mapped as Street type with the "Unpaved" attribute, should you use the identical type for a little-used parallel road? In fact, do circumstances suggest the better nearby road may have replaced the road you are mapping? A more-heavily penalized road type may be appropriate for the road you're considering, or perhaps the road should not be mapped at all.

Also consider the Wazer population likely to be traversing the area. Is it a heavily-touristed area where many Wazers are likely to be driving ordinary passenger vehicles or RVs? Or is it more remote, where Wazers are likely to be better prepared for rough roads?

Using discretion when deciding whether and how to map Forest Service roads can dramatically improve Wazers' driving experience.
DwarfLord
Wiki Master
Wiki Master
Posts: 2512
Has thanked: 1065 times
Been thanked: 1451 times

POSTER_ID:16850907

1

Send a message

Post by DwarfLord
As support appears unanimous (if pretty thin) for the above update regarding editorial discretion when copying map data from an MVUM to the Waze map, I'm planning to make it live tomorrow (Sunday).
DwarfLord
Wiki Master
Wiki Master
Posts: 2512
Has thanked: 1065 times
Been thanked: 1451 times
Send a message