[Script] WME Add-Ons V0.43

[bz2012]

suggested addition: 'fix broken nodes'.
Would be similar to 'suppress extra junctions' in that it would look at all nodes in the current screen but it would run the 'junction node fixer' on all revcons, softcons and u-turn nodes.

Has the potential to fix many problems without any down-side that I can see, off hand.

[davipt]

Chances are 100 to 1 that someone will come along and remove the TR, destroying that brittle arrangement. Insert a stretch of parking lot road instead and name it "Residential access only" (so the next editor has a clue at least).

If it's residential access only shouldn't it be a private segment? Or is it a public mostly building parking street that goes parallel to a main street and waze tends to route through it because probably the main street has more junctions?

[bgodette]

suggested addition: 'fix broken nodes'.
Would be similar to 'suppress extra junctions' in that it would look at all nodes in the current screen but it would run the 'junction node fixer' on all revcons, softcons and u-turn nodes.

Has the potential to fix many problems without any down-side that I can see, off hand.

Down side is you're leaving any turn restrictions that should or should not be set unable to be updated by user drives. So unless you're going to guarantee that all turn restrictions are correct, this is a massively bad idea.

[bz2012]

suggested addition: 'fix broken nodes'.
Would be similar to 'suppress extra junctions' in that it would look at all nodes in the current screen but it would run the 'junction node fixer' on all revcons, softcons and u-turn nodes.

Has the potential to fix many problems without any down-side that I can see, off hand.

Down side is you're leaving any turn restrictions that should or should not be set unable to be updated by user drives. So unless you're going to guarantee that all turn restrictions are correct, this is a massively bad idea.

Won't WAZE continue producing Problem Reports when it sees drivers taking turns against arrows and down wrong way segments, asking us to check the area and verify things?

Granted, WAZE may stop (if it still currently does) changing the turn restrictions without asking for editor verification.
But that may be a good thing because drivers sometimes make illegal turns and people using WAZE in ways not intended like walking or biking can make WAZE 'think' the turn restrictions are wrong and change them, causing drivers to later be routed over illegal turns.

Also, it is my understanding that a 'forbidden turn' is not really absolutely forbidden, the route is just given a low priority, WAZE still seems to send people along it, as evidenced by all the recent 'route not taken' reports in which drivers are being sent the wrong way down one way segments and down dead end streets. These sometime seem somewhat related to 'nearby [within a few miles?!!!] revcons, soft turns or u-turn nodes.

Might it not be best to remove these 'things' that are currently being blamed for the bad routes so that the REAL problems underlying the crazy routing can finally be tracked down and fixed?

[fvwazing]

Chances are 100 to 1 that someone will come along and remove the TR, destroying that brittle arrangement. Insert a stretch of parking lot road instead and name it "Residential access only" (so the next editor has a clue at least).

If it's residential access only shouldn't it be a private segment? Or is it a public mostly building parking street that goes parallel to a main street and waze tends to route through it because probably the main street has more junctions?

Maybe it should be called "Closed for guests"?
The way I understood the problem is that a certain area has limited access - so every entry should be private road. Of these roads some are more restricted than others - they are closed for guests, but open to residents. PLR would stop creating a route through those gate but suppress MapErrors from happening. Wasn't that what the OP wanted?

[bgodette]

suggested addition: 'fix broken nodes'.
Would be similar to 'suppress extra junctions' in that it would look at all nodes in the current screen but it would run the 'junction node fixer' on all revcons, softcons and u-turn nodes.

Has the potential to fix many problems without any down-side that I can see, off hand.

Down side is you're leaving any turn restrictions that should or should not be set unable to be updated by user drives. So unless you're going to guarantee that all turn restrictions are correct, this is a massively bad idea.

Won't WAZE continue producing Problem Reports when it sees drivers taking turns against arrows and down wrong way segments, asking us to check the area and verify things?

So you're going to scan 100% of NA every day?

Granted, WAZE may stop (if it still currently does) changing the turn restrictions without asking for editor verification.
But that may be a good thing because drivers sometimes make illegal turns and people using WAZE in ways not intended like walking or biking can make WAZE 'think' the turn restrictions are wrong and change them, causing drivers to later be routed over illegal turns.

It requires a statistically significant number of events to open a soft restricted turn.

Also, it is my understanding that a 'forbidden turn' is not really absolutely forbidden, the route is just given a low priority,

Only if the turn is soft and the alternatives are worse.

WAZE still seems to send people along it, as evidenced by all the recent 'route not taken' reports in which drivers are being sent the wrong way down one way segments and down dead end streets.

That's only evidence of Waze running against the entire drive history to generate those automated problems, which has been covered many times.

Might it not be best to remove these 'things' that are currently being blamed for the bad routes so that the REAL problems underlying the crazy routing can finally be tracked down and fixed?

Only if you're willing to say all turn restrictions in that area are correct, otherwise no.

Again, it's a really bad idea as it prevents a number of automated systems from working. So unless you want to take ownership of rechecking that area every few days, don't do it.

[bz2012]

WAZE still seems to send people along it, as evidenced by all the recent 'route not taken' reports in which drivers are being sent the wrong way down one way segments and down dead end streets.

That's only evidence of Waze running against the entire drive history to generate those automated problems, which has been covered many times.

If that is true, then the small amount of traffic along some busy roads where I have seen those warning pop up, makes absolutely no sense.

I would expect to see numbers of 'did not take' in the thousands, considering the number of GPS tracks I have seen in some of those places or are you saying that the misdirections took place several years ago, when the maps were first drawn and WAZE is ignoring all the proper routing that has taken place since then?

And exactly where has this been 'covered many times'? I didn't find satisfactory explanations in the 'sea of orange' thread . Is there another thread covering the topic in more depth?


And, lets assume that there are sufficient reasons NOT to automate fixing soft-cons.
I don't see that the argument applies equally to rev-cons and u-turn nodes. Don't those need fixing in any case?

[gdu1971]

Hello,
minor update:
WME-Addons V0.42
- Save snap dist parameter in user settings
- StreetId regexp improvment for France
- Path for new beta-editors in manifest (NA and INTL)
- Improved layout for segment list options
Submit a bug or request an improvment:
https://code.google.com/p/wme-addons/issues/list
Download urls remain the same (first post of this thread)

[cybernissart]

Hi Gilles,

Can you detail the changes done by the Clean Roundabout feature ?
It looks like every RP need a clean action, as it seems to modify them.
Is it removing street name and similar ? Changing some soft turn ?

As per my Suggestion posted on SVN page, I asked if possible to enable a 'Suppress Extra Jonctions' on roundabout as well, as some are having extra nodes, or we introduce lots when changing RP from Y mode to straight street node.
As manipulation of Roundabout is very sensitive, it would greatly help to clean junctions as well to improve them.

[gdu1971]

Hi Gilles,

Can you detail the changes done by the Clean Roundabout feature ?
It looks like every RP need a clean action, as it seems to modify them.
Is it removing street name and similar ? Changing some soft turn ?

As per my Suggestion posted on SVN page, I asked if possible to enable a 'Suppress Extra Jonctions' on roundabout as well, as some are having extra nodes, or we introduce lots when changing RP from Y mode to straight street node.
As manipulation of Roundabout is very sensitive, it would greatly help to clean junctions as well to improve them.

Hello,
The clean roundabout algorithm is quite simple for now:
- detect if selected segment is part of a roundabout else exit
- detect all parts of the roundabout
- for each node of the roundabout, check segments which are not part of it and get cityID road Type and level
- Get the first cityID, highest street type and level found on those segments
- apply CityID if found, highest street type and highest level +1 on all roundabout segments (level +1 is just a cosmetic issue for the client and editor)
improvments planned are :
- put algorithm in a loop when more than one roundabout is selected
- adapt algorithm with the wiki rules http://www.waze.com/wiki/index.php/Roundabout to choose the right higher road type