In addition to the changes proposed here, I would like to make some additional changes to the Thai wiki:
Remove mention of the now finished map raid
I would like to add example photos to several of the sections (for instance, an example of U-Turn implementation)
Add guidance not to connect runways, Pedestrian Boardwalks, Walking Trails, or Stairways to roads. (I realize Waze has improved previous problems with Waze using these for navigation, but based on local experience this still happens on occasion when they are connected to roadways)
No objections.
Adding to it there’s still ongoing discussion, in NL anyway, about Railroad typing & Railroad - Road junctions. About junctions: I’ve seen different solutions, all TR’s green or only TR’s to/from RR red or no junction at all. Myself being Dutch I don’t have experience with the effect of junction nodes at level crossings.
changed raid mention but did not remove it, there is supposed to be an update coming with results.
feel free to supply these. They are currently links to the map so that they are “live,” but I realize that these links may become broken.
In my opinion we should avoid damaging the map to prevents waze bugs, so I would like to have serious proof that this is an unsolved, pressing issue before adding this. Alternative: walking trails are not to be used according to the wiki. Maybe we could move all of these categories to “not to be used.”
In addition, for some people (such as myself), it is helpful to have a graphic representation near the text. That way I can read the description and easily glance back and forth between what I am reading and the example to make sure I am understanding correctly. It becomes more difficult when I have to open a new tab and jump back and forth.
I don’t consider it damaging the map. Waze is currently (and for the foreseeable future) designed for providing driving directions. So items like stairways and pedestrian boardwalks serve no functional purpose, since Waze shouldn’t be using them for routing, and they often aren’t rendered in the app (I’m not 100% what is currently rendered), so they really serve no point. I’ve been around long enough to have seen the “routing onto non-routable segment” bug “fixed” multiple times, and it always seems to come back.
I’d be fine to moving them all to “not to be used”.
I don’t have a strong opinion on this, especially since railroads are not rendered in the app (at least on Android). My opinion is they should be drawn in, and I tend to lean against junctioning them, since if Waze’s routing server glitches or decides the penalty is lower to route onto the tracks rather that stay on roads, it could have fatal consequences. The slightly better granularity on calculating traffic conditions doesn’t seem worth the risk.
Is anybody against adjusting the advice for runways, pedestrian boardwalks, walking trails, and stairways to “don’t use, and certainly don’t connect to roads”?
I wouldn’t mind stronger wording: Do not use non-driveable road types as WT, PB, stairways and runways. Railroads can be used but are not to be connected to drivable types.
