Get a sneak peek at whats next for Permanent Hazards on our April 7th Office Hours!

Post by marcedli
Let me add some thoughts:

1. In Hungary from the very beginning every railroad is connected to roads with junctions. They were on -5, they are on ground level like in real now.
2. Railroad crosses are VERY VERY VERY dangerous places. The MOST dangerous for the drivers. This immediately shows it's importance I guess, so noone can say "if it's not a real junction then it's not necessary". It IS a junction, because they can collide - the two vehicle types simply cannot turn right/left there.
3. We tested routing with/without junction. We have some very good testing crosses, where we exactly know that if you don't want to wait there for 20 mins, you don't go there. When there is no junction, it's always included in the route. When there is a junction, the server avoids it.

@banished:
I think we should not take "waze fault" or "routing fault" into count when we draw the map. Yeah, one day maybe Waze will route me through the Black Sea and some forests by mistake...but I will not stop drawing lakes, rivers or woods on the map
- Whoever is that blind and dumm that he turns in a RR cross on the track -sorry to say that but- he would have done it without Waze too
- Neither Waze nor map editors driving on the roads, the drivers do. They are in charge of the wheel and pedals, they must decide what they can/should/must do or not from the various 200-300 simultaneous inputs they have (through eyes, ears, experience, etc.).

Waze should detect RR crosses and give higher penalties there (even without any historical speed data) imho. And railroads should be visible in the client too.
marcedli
EmeritusChamps
EmeritusChamps
Posts: 1572
Has thanked: 71 times
Been thanked: 282 times
Send a message

Post by nzahn1
Did we ever resolve the issue of mapping sub-terranean railroads. Specifically thinking of ones that travel under cities.

Haven't found a good reason to have them on the map.
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
Great. Thanks.


Sent from my iPhone using Tapatalk
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
Do we want to include a warning that the Map Problem detection system currently detects junctioned Railroads as routable, and throws an error indicating that the turns should be enabled?

Maybe along with the assumed guidance to ignore the MP and mark as "not identified".
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
voludu2 wrote:Nzahn1, can you propose some text for this?
Will do today, check back later.
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
Yeah, we were just talking in the Mid-Atl about making sure subterranean rail lines aren't on the map. Realistically, by deleting them we aren't losing that much data, and they will be easy to add back later.
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
DRAFT UPDATE to Road-types/USA#Railroad. Changes/additions in red.

This would (edit) NOT 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.
nzahn1
Waze Global Champs
Waze Global Champs
Posts: 1754
Has thanked: 642 times
Been thanked: 776 times
Send a message
Last edited by nzahn1 on Fri Jul 10, 2015 2:40 pm, edited 1 time in total.

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:If we do trust Waze never to route onto tracks, great. Take away the boldface and leave the impression that it is simply best practice.
I have no evidence that the routing prevention will fail, but found a "better safe than sorry" attitude in the forums/chats. I'd be happy to remove the emphasis, and leave it as important as the remainder of the paragraph.
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
Without further objections I will add the following language to the wiki. Bolding can be added at a later date if consensus is reached.
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.
  • 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.
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