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

[nidnarb]

Anyway possible to get validator to stop saying roads that have a period are invalid. Example G.5 Rd NE, Q.1 Rd NE, T.7 Rd NE etc..

Thanks!

Sent from my Nexus 6P using Tapatalk

Do you have any permalinks for these roads, should they really have a period in the name? This is a check which is specific to USA and checks that names are in accordance with our recommended abbreviations.

Yes in Douglas and Grant County in WA have periods in the street name. When its a parralel road from the main one. Example G Rd NW, streets between that and F Rd NW would be something like G.7 Rd NW or G.3 Rd NW. I have confirmed from County GiS and one person who lives in the area thats how the streets are named. These are the same streets where i have the issue with TTS. Here is a PL of one of the road signs in that area. https://www.waze.com/editor/?env=usa&lo ... lter=false

Here is another PL of a road example at intersection. https://www.waze.com/editor/?env=usa&lo ... lter=false

If you need any other info let me know.

[nidnarb]

Part of the reason for the check is to avoid TTS issues. We may have to do something to accomodate here, or work around.

Well it does look like you got the TTS fixed. now the roads say the right name. Before they said ten zero 2 road north east. Now it says ten point 2 road north east. So hopefully you guys can get validator to work around this. Thanks again!

[Nimbus-]

In Chrome - Validator seems to be preventing the left pane from scrolling, making the other tools unusable.

As a temporary fix, I've toggled it to move to the bottom. But now I can't hide the bubble blimp at the bottom.

[Nimbus-]

Is that the Chrome Extension version or the Script version?

The Chrome Extension.

[no1ne]

there is a typo in the report

Filter: duplicate segments, non-drivables and streets, non-editable segments and mjnor issues are excluded from this report.

[no1ne]

I think check for WMETB: Simple segment shouldn't ignore roundabout segments

[no1ne]

oops my mistake i mean should

[no1ne]

Is it why the how to fix show a link to a forum topic with a form to fill


Via Tapatalk

[no1ne]

Rule Walking Trail elevation = -5 is arbitrary. I did not see where anyone came forward to explain why he cares.

I did, two pages ago. "Some communities have been using Walking Trails at elevation -5 to signify railroads as a matter of editor policy."

That isn't an explanation of the error. Of what is this a useful check?

note an error, a warning or a SLOW
some country used to set railroad as Walking Trail elevation = -5
and An Important Change in the Client Display is to come (soon? )

I can't fathom any reason an actual walking trail would be set to elevation -5.

As a matter of editor policy, all non-drivable road types (including railroads, runways, boardwalks, stairs, and walking trails) have elevation set to -5 per established convention. -5 indicates that the segment is not to be attached to the drivable roadways "to prevent false system reporting that think the roads should be connected.".

[no1ne]

In this case, there is no way that Waze failed the routing

I disagree for the reason stated in the split thread.

I desagree with you
- Your exemples are quite old, the most recent is from nov 2013
- At the last meet-up i attend ( Praha and Ra'anana ) Ehud always told us that we must not adapt the map to match strange routing engine behaviours it's waze work to fixe them
- first it was said to split in two, one of the segments sharing same end point , now some says it must be in three

For me it's a wast of time
but i'm may be wrong so please pm me a link if there is another topic in the champs forum
If not perhaps it would be worse opening one asking waze point of view via redviper26