Waze forum

Right, I was talking about the description of the issue, is it will be fixed ? highlighting help but not 100%, since it's highlight only major issues and it's not always clear about where is the issue.
Thanks.
 

I will like to see the type of road connected to the A junction?
Is there an variable that expands the type of conected segment?

The temporary Date() workaround was published in WME Validator Localization for Brazil, while waiting for a new update.

ifaesfu wrote:I found the update: https://greasyfork.org/scripts/3895-wme ... ration-fix

There is NOT UPDATE. This is an workaround.

In my tests, this NULL elevation is false positive, due WME-ToolBox problems with new WME data model.
If I disable toolbox, this problem disappears. And elevation is always correctly saved, regardless of what is shown.

I think that service road check would not be nice: when the service road type is removed, soon (?), then staff is run the search/replace "service road" by street type. So, the change may be transparent, without need to search, manually edit, and change this type in WME.
Perhaps, this check can be placed in the localization package, to be applied and used by all editors;
I think that checks #44, #45 and #50 are more important to restore.

The goal of validator is checking and do alarm in real problems.
In actual environment, what is the real problem with "service roads"? Resp. Nothing !

Sure. There is no problem with service roads. But there a problem due a bad mapping and wrong application of service road. I agree. Put the check.

When I update and save any segment, the custom ${elevation} /[^0]/ alarm, until I click in segment again, or refresh all. Tested in green custom.

SuperMedic wrote:Is there a way to provide an access function that returns an array or object of all of the segments that have been found?
I.e.
[{id:345346,lat:-72.4948583,lon:36.2849201},...]

https://greasyfork.org/pt-BR/scripts/53 ... data-store