[Script] WME Add-Ons V0.45 ==> Features moved in WME Toolbox

[rottielover]

@davipt

@rottielover

http://www.waze.com/wiki/index.php/Automatic_map_updates_and_the_locking_of_roads

Which advises, in part: “…It will change the directionality of a road, enable turns, and reportedly it will change the geometry or layout of a road.
This can cause map errors, especially in areas where there are few wazers. One wazer who always travels one way down a road may change a correctly recorded two-way road into one-way.”

I was once curious about this one so we have setup a certain remote and not used one-way segment as two-way and have, two guys, driven there every day for some weeks to test it. It never changed to one-way. It may apply if the road becomes automatically two-ways because of people driving both ways, and later become one-way if people starts driving only one way, but after setting it manually to two ways it never changed. And obviously it wasn’t locked.

Anyway we’re not arguing against each other here, if we are all in this thread we all surely know the power of this script and the amazing help it provides, as well as dangerous damages it can potentially do. And I see no issues for a entire small town to be set as two-ways (even all directions), and I have plenty of cases like those, but personally I do prefer people to drive there and have waze automatically learn the directions and the position of the road. Mostly because of lazyness and having other more important fixes to do

Agreed, I don’t feel this is an “argument”, I enjoy discussion, I try and learn something new everyday!

Example, today I found out what the NbWays column was (btw, Is there more documentation somewhere?)

The other thing to keep in mind as well is that the map needs to function. In a few of these towns I was getting “crazy” routing, because the basemap import was just “all jacked up” (no other term for it)…

Thanks all!

[rottielover]

@davipt

or then filter by each speed and see areas where people surely cross the limits. o.O

Why does that matter?

[CBenson]

@davipt

@TonyG-UK

@davipt

What do you mean fallacy? No of course I can’t find the exact sentence on the wiki,

Then you shouldn’t say the Wiki says so, cause it probably doesn’t.

It’s hard to search stuff on the wiki and forum. I do remember my discovery started with this post, but can’t recall where I jumped from there on.

So what are you arguing about? What I wrote in the wiki on unknown directionality is here: http://www.waze.com/wiki/index.php/Creating_and_Editing_street_segments#Road_Direction Is there some dispute regarding how unknown direction roads function? Or is this discussion about soft one-way roads?

[gerben]

@rottielover

Please see my post above, according to the page I linked in the wiki, Two-Way roads can be changed to one way, if wazers always drive down the same way. (possible in these small towns)

There have been some bugs with this, but nowadays, once a segment is edited in WME, it’s direction is no longer updated by the automatic process, so this will not happen anymore*.

• Unfortunately, during the infrastructure change a lot of roads did not get this ‘internal directionality lock’ when edited. This was fixed somewhere in december, so only for very recently edited roads you can be sure that the directionality will not be updated by any automatic process.

[skbun]

Currently, using the ‘select’ button in ‘Segment list’ will select all segments in view, whether or not you have permission to actually modify them. Could you please modify this routine to add a test for seg.isAllowed(seg.PERMISSIONS.DELETE)), as you do for surpressing junctions?

If you are near the border of your editing rights and need to make changes there - or are near segments with locks higher than your editing level, this will mean that only segments will be selected that you actually have permission to work with.

If for some reason someone needed to select all segments regardless of permissions (I can’t imagine why, but let’s say they did), this can be done in play mode.

[bgodette1]

@TonyG-UK

No. I’ve had a street go from two-way to one-way, simply because I was the only person driving down it, and I always drove in the same direction.

This is no longer the case as of about a month or so ago. Prior to that it was possible for some segments to still be under automatic direction updating even after having been manually edited. This now no longer happens once the segment has been edited again.

To reiterate, as of about a month ago, editing any property of a segment will now cause direction on that segment to become fixed.

The Wiki page here about locked roads is currently inaccurate. Locking segments hasn’t had any influence on connectivity ever since turn locks were separated out more than a year ago, and has been controlled by fwdTurnsLocked and revTurnsLocked since.

@davipt

Also routes will prefer segments manually set to two-way over segments marked as unknown?

There’s a routing time penalty for Unknown direction. Waze claimed 30 seconds per segment, real world testing indicates ~4 minutes.

[kentsmith9]

@bgodette

The Wiki page here about locked roads is currently inaccurate. Locking segments hasn’t had any influence on connectivity ever since turn locks were separated out more than a year ago, and has been controlled by fwdTurnsLocked and revTurnsLocked since.

I started a Wiki thread here to discuss the change since I am not 100% certain I know what should be changed.

(Edit: We have completed that thread discussion.)

[Olestas]

Hmm… not installing in Chrome by drag and drop into extentions. How do you install it?

[fvwazing]

Save the script as a LOCAL file and drag and drop that one.

[Olestas]

Hmm… have done this precisely 2 times before this post, and it refused. Now it worked…

[Olestas]

Suppress extra - should not include similar segments which have restricted turns in between.

[robin1979]

@olestas

Suppress extra - should not include similar segments which have restricted turns in between.

They shouldn’t be connected as such then - this behaviour is okay like it is now.

[Olestas]

Illogical.
But why it joins segments which have changing one-way and two-way road types? Should not do this.

[robin1979]

@olestas

Ok. But why it joins segments which have changing one-way and two-way road types.

That’s kind of weird construction as well. But that’s actually a WME bug then. This script doesn’t really do anything you’re not allowed to do with WME itself.

[Olestas]

So… maybe it is somehow possible to avoid joining segments with different types in anything?

[HandofMadness]

@robin1979

@olestas

Suppress extra - should not include similar segments which have restricted turns in between.

They shouldn’t be connected as such then - this behaviour is okay like it is now.

For gated entrances in private communities where only residents can open the gates. You restrict the turn in so Waze doesn’t direct guests through those limited access gates. If you separate the segment, you’ll get missing road problem reports due to residents driving through the gate. For whatever reason, Waze is more likely to generate an auto report for that vs driving against the turn restriction.

[CBenson]

@shawndoc

For gated entrances in private communities where only residents can open the gates. You restrict the turn in so Waze doesn’t direct guests through those limited access gates. If you separate the segment, you’ll get missing road problem reports due to residents driving through the gate. For whatever reason, Waze is more likely to generate an auto report for that vs driving against the turn restriction.

I get plenty of auto reports for driving against turn restrictions. But the bigger issue I have with this recommendation is that it doesn’t always work especially for large private campuses. Waze will route through the restricted turn if the route through the main gate is too much longer.

[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).

[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.

[bgodette1]

@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.