[Script] WME Validator v2021.3.5 (+ PLACES BETA)

[Poncewattle]

User control panel, user groups, select Map Editor - Level 2, join it, then select it as your default group.

[Poncewattle]

Ding. Yup. That's exactly what's happening. Well that mystery is solved!

(Learn something every day!)

Does that destroy the traffic history data on the segment too? The ID number doesn't change at least.

[Poncewattle]

I find it now somewhat critical that this indication remain in Validator so I can troubleshoot and report problems with enabled or disabled dead-end roads.

Right now the validator reports it as a (yellow) warning if the u-turn is enabled to get around the bug documented in the wiki that says "Due to a bug in Waze, we need to make sure that Waze thinks that a U-turn is not allowed on a dead-end, even though in reality it must be." (which was before they hid it from us of course):

https://wiki.waze.com/wiki/Map_Editing_ ... nd-streets

What I am inferring from what I hear you saying is, iff Waze ever fixes that bug, then the validator should then be changed to report it as an error for the OPPOSITE condition -- if the u-turn is in fact disabled, since after the bug is fixed the u-turns in most cases should in fact be ENABLED.

Am I understanding this right?

[Poncewattle]

my position is that it absurd for routing to depend on some setting that we can inadvertently change

Oh good, because that's what I've been paranoid of myself. I've been told "don't do that" but I end up doing "it" as a side effect of doing other things, and if I didn't have the validator installed, I wouldn't even know I'm changing "it" at all because it's hidden now.

[Poncewattle]

Hmm, I was going to bring up Franconia Notch in NH as an example of a two-way Interstate but I see it's an Interstate classified in Waze as a major highway and not a freeway.

https://www.waze.com/editor/?env=usa&lo ... s=64617804

[Poncewattle]

Sir berestovskyy, might want to keep an eye on this thread:

https://www.waze.com/forum/viewtopic.php?f=276&t=111469

If attaching railroads to roads becomes accepted, then that check should probably be disabled.

[Poncewattle]

'Non-drivable connected to drivable': excluded Railroads

Why?

See this post:

https://www.waze.com/forum/viewtopic.php?f=276&t=111469

Doesn't sound like it's settled yet though.

[Poncewattle]

Validator is flagging Brg as invalid street name, but it's listed in TTS table as valid for bridge

[porubcan]

Hello all,

I apologize if this was already answered, but I haven't found answer on forum or wiki.
I started to search for more information due to WME Validator pointed an error "More than one segment connected to roundabout node A"

Roundabouts have few principals:
The first one, each node on the roundabout can only be connected to no more than one segment.
Each connection has a spectrum that exists in order to notify the Client on how to define the message (Go straight, exit through the 2nd / 3rd / 4th exit).

so few details about the roundabout in play. photo first (click on preview to get large image, there is streetview on the right side):
[ img ]
detail on the angle the roads are connected on streetview

if you are entering the roundabout from south (selected segment), it is not possible to exit immediately to the right. for those direction there is separate lane.
in current solution, the turn from segment entering roundabout to the outbound segment is disabled, what causes, that for this particular entrance the exit is not counted but for all other inboud segments the exit is counted. in my opinion this is correct setup, but the wiki states otherwise.

what would you think? is this an error? should it be treated different way?

thanks for your help.

[porubcan]

Does this roundabout give the correct turn instructions?

Yes, it gives correct turn instructions (take Xth exit for all combinations)
I just wondered that there is strict statement in wiki without further explation and without any exceptions.