Get a sneak peek at whats next for Permanent Hazards on our April 7th Office Hours!
Post by nzahn1
Also, can we talk about the abunant number of boxes at the top of this page:

Code: Select all

{{mbox
| type = critical
| text = The contents of this page were completely revamped starting 19 April 2014, to incorporate an entirely new set of guidelines for map editing. All US editors should familiarize themselves with the contents of this page. Please see [http://www.waze.com/forum/viewtopic.php?f=276&t=85397 this topic] for details.
}}
{{UpdatedBanner
|majorDate    = 1/14/15
|majorDesc    = Clarify when to use PLR vs Private Road for apartment complexes, trailer parks, schools, universities, etc.
|majorForum   = http://www.waze.com/forum/viewtopic.php?f=276&t=124820}}
nzahn1
Waze Global Champs
Waze Global Champs
Posts: 1754
Has thanked: 642 times
Been thanked: 776 times
Send a message

US Global Champ | MAR Coordinator | iOS Beta | WME Beta | Localizer
WME Profile | E-mail | MAR Forum | MAR Wiki | MD Twitter

Post by nzahn1
Timbones wrote:
nzahn1 wrote:Without further objections I will add the following language to the wiki. Bolding can be added at a later date if consensus is reached.
First, it provides drivers with visual orientation relative to railroad and light-rail tracks.
...except that the app doesn't [yet] show railroads on the map for [ordinary] users. It might be worth mentioning this, and that railroads will [hopefully] be shown in the future.
That was existing language on the page, but I'd be happy to modify it, if there is consensus.
nzahn1
Waze Global Champs
Waze Global Champs
Posts: 1754
Has thanked: 642 times
Been thanked: 776 times
Send a message

US Global Champ | MAR Coordinator | iOS Beta | WME Beta | Localizer
WME Profile | E-mail | MAR Forum | MAR Wiki | MD Twitter

Post by nzahn1
DwarfLord wrote:One last comment, I would suggest substituting "underground transit systems" or "underground rail lines" for "underground railroads". The latter term has a connotation in American history.
Minor change effected.
nzahn1
Waze Global Champs
Waze Global Champs
Posts: 1754
Has thanked: 642 times
Been thanked: 776 times
Send a message

US Global Champ | MAR Coordinator | iOS Beta | WME Beta | Localizer
WME Profile | E-mail | MAR Forum | MAR Wiki | MD Twitter

Post by PesachZ
CBenson wrote:
AlanOfTheBerg wrote:
Poncewattle wrote:It'd be nice if WME would just hide the turn arrows for railroad junctions, like it now hides the u-turn selection for dead-ends. I know turn restrictions are not-applicable now but there's just something a bit unsettling about potentially seeing a green turn arrow onto a railroad line, even if it's ignored.
I think this was mentioned before, and it's a decent idea. It has been added as #225 to
The more I see this of this discussion the more I think this should be expanded. In addition to not displaying turn arrows on non-routable segments, we shouldn't have the option to assign house numbers or add restrictions to non-routable segments. Its just asking for trouble to be able to assign characteristics that only have a routing function to a few random non-routable segments.

Of less importance, if the guidance is "Always select 'None' for the city name" then the in the ideal world, you wouldn't be able to assign a city to a non-routable segment. Similarly, if the guidance is always "Set railroad to 2-way directionality" then why have other options.
This is off topic.

However there are legitimate reasons for house numbers and cities etc. On Mon routable segments (sometimes). I have several areas where there a legal addresses on 'streets' with signed names. However these streets are not open to vehicular traffic. If you wanted to navigate to one of those houses, but couldn't add house numbers to those segments, it would be impossible. Currently I have these as non drivable segments, disconnected from the drivable network, named correctly with house numbers. When searching for a route Waze takes you to the closest drivable segment (usually the entrance to the street, and displays the pin in the correct place.

Sent using Tapatalk for Android 4.4.2
PesachZ
Wiki Master
Wiki Master
Posts: 4516
Has thanked: 1365 times
Been thanked: 1572 times
Send a message
Last edited by PesachZ on Tue Oct 21, 2014 10:47 pm, edited 1 time in total.
https://s.waze.tools/gc.pngNYhttps://j.mp/1xPiWC8https://j.mp/1C9mUY2
Formal Mentoring, Wiki
Useful Wiki pages
URs & etiquette | WME | Editing Manual | Quick-Start Guide | Best Map Editing Practices | Junctions
State specific Wiki | Forum

Post by PesachZ
I vote for Alan's suggestion. Its closer to reality which makes it easier to adapt and improve in the future. If the infrastructure is in place (I.e. junctions) that might in incentivise the devs to build features which capitalize on that, e.g. RR X-ing alerts.

Sent using Tapatalk for Android 4.4.2
PesachZ
Wiki Master
Wiki Master
Posts: 4516
Has thanked: 1365 times
Been thanked: 1572 times
Send a message
https://s.waze.tools/gc.pngNYhttps://j.mp/1xPiWC8https://j.mp/1C9mUY2
Formal Mentoring, Wiki
Useful Wiki pages
URs & etiquette | WME | Editing Manual | Quick-Start Guide | Best Map Editing Practices | Junctions
State specific Wiki | Forum

Post by PesachZ
kentsmith9 wrote:Just saw my first MP on a Junctioned RR. Waze had a driver locked onto the RR that ran parallel to the road next to it. The driver turned left across the RR and the MP claimed the driver was on the RR and turned left against the restricted turn.

I thought Waze would NOT route onto a RR or would not even assume you could be on a RR? Did I miss something somewhere?
It might still snap; lock drivers to RR to harvest speed data from wazers on the train, and avoid that data getting dumped on adjacent roads.

Sent using Tapatalk for Android 4.4.2
PesachZ
Wiki Master
Wiki Master
Posts: 4516
Has thanked: 1365 times
Been thanked: 1572 times
Send a message
https://s.waze.tools/gc.pngNYhttps://j.mp/1xPiWC8https://j.mp/1C9mUY2
Formal Mentoring, Wiki
Useful Wiki pages
URs & etiquette | WME | Editing Manual | Quick-Start Guide | Best Map Editing Practices | Junctions
State specific Wiki | Forum

Post by PesachZ
nzahn1 wrote:DRAFT UPDATE to Road-types/USA#Railroad. Changes/additions in red.

This would fall under the new Global Wazopedia approval scheme:
The "Railroad" road type serves three purposes in Waze. First, it provides drivers with visual orientation relative to railroad and light-rail tracks. More importantly, in the common case where passenger-carrying tracks lie parallel with roads, mapping the tracks allows Waze to recognize spurious speed data from people Wazing on the train and prevent it from corrupting speed data for the adjacent road. Finally, when a railroad crosses a drivable road segment at grade (same elevation) the routing server can better determine delays at that crossing.

{{As of|2015|2}} the automated [[Map Problems in Waze Map Editor|Map Problem]] search algorithm will identify suspected errors at railroad crossings. It is common to see the “restricted turn might be allowed” error where a railroad crosses a drivable segment nearby to where another drivable segment also crosses. These kinds of map error should be marked as “Not Identified” so that they are not shown again at that location. Do not enable turns at railroad crossings.
I wanted to add a note about mapping subterranean railroads to the guidelines too:
  • Do not map railroads below ground, as they do not serve any of the three purposes outlined above. This is especially true in urban areas where underground railroads are common, and their appearance on the map would be confusing to drivers.
  • Set the elevation just as you would a drivable segment. When tracks junction a road on the ground, the Elevation should be set to Ground.
Sounds good to me.

This is a USA page, and as such does not need to follow the global scheme. You will need consensus from USA editors.

Sent using Tapatalk for Android
PesachZ
Wiki Master
Wiki Master
Posts: 4516
Has thanked: 1365 times
Been thanked: 1572 times
Send a message
https://s.waze.tools/gc.pngNYhttps://j.mp/1xPiWC8https://j.mp/1C9mUY2
Formal Mentoring, Wiki
Useful Wiki pages
URs & etiquette | WME | Editing Manual | Quick-Start Guide | Best Map Editing Practices | Junctions
State specific Wiki | Forum

Post by PesachZ
Even if we trust Waze we also have to trust other editors. There's a possibility the RR may be accidentally switched to say walking trail by a new editor. The restricted arrows represent a fail safe. And in such a critical navigation decision, redundancy is good.

Sent using Tapatalk for Android
PesachZ
Wiki Master
Wiki Master
Posts: 4516
Has thanked: 1365 times
Been thanked: 1572 times
Send a message
https://s.waze.tools/gc.pngNYhttps://j.mp/1xPiWC8https://j.mp/1C9mUY2
Formal Mentoring, Wiki
Useful Wiki pages
URs & etiquette | WME | Editing Manual | Quick-Start Guide | Best Map Editing Practices | Junctions
State specific Wiki | Forum

Post by PhantomSoul
What if we piloted it in a small area to observe its effects?
PhantomSoul
Local Champ Mentor
Local Champ Mentor
Posts: 1757
Has thanked: 311 times
Been thanked: 511 times
Send a message

Post by PhantomSoul
While I get putting a junction into the crossing road at an at-grade railroad crossing to capture any traffic pattern due to passing trains, I'm not sure that actually junctioning in the railroad itself adds any value to the map. Safety issues aside (I would seriously question why a person who tries to turn into a railroad even has a drivers license), the established process is to not junction railroads into roads, which would take considerable effort to change, between updates needing to be done on the map and evangelizing the new practice to both current and new editors. Seems like an awful lot of work to do something only because Waze said we could.

Just because we can do something doesn't necessarily mean we should. Don't we have better-return things to work on?
PhantomSoul
Local Champ Mentor
Local Champ Mentor
Posts: 1757
Has thanked: 311 times
Been thanked: 511 times
Send a message