Get a sneak peek at whats next for Permanent Hazards on our April 7th Office Hours!
If you think you've found a bug on the website which isn't specifically an App or Map Editor problem, or have a request for new or modified feature of the Community, Forums, or Waze website, use this forum.

Post Reply

Default turns when adding new roads

Post by sgtgary
I am sure this has probably been submitted before, but maybe not... I can't find it on a search

When adding a brand new road on Waze, the turns are all defaulted to off. Joining other roads requires that you go and choose the turns that are permitted. This is a nightmare for my growing end of Omaha because people are adding roads at a pretty good pace but I'm having to go and fix hundreds of turns that aren't permitted (you notice them when the GPS routes you all over the neighborhood to get somewhere).

I would love either:
1. an easy way to identify the roads without turns permitted on the map view
2. a default setting that lets all roads turn when a new road is connected. It's easier to disable a turn then.

Just an idea :)
sgtgary
Posts: 64
Has thanked: 166 times
Been thanked: 10 times

POSTER_ID:10820224

1

Send a message
Nebraska State Manager
US Plains Editor
Twitter: @sgtgary

Post by txemt
You'd be surprised how quickly you could clean that up with QW.
txemt
Posts: 4774
Has thanked: 25 times
Been thanked: 919 times
Send a message
Just wazeting my time to help you waze your route smoothly.

Post by txemt
kodi75 wrote: It doesn't seem worthwhile to research whether to 'hard-allow' them all - unless there is a UR that draws me to that area or it affects a major intersection, right?
Why not?
txemt
Posts: 4774
Has thanked: 25 times
Been thanked: 919 times
Send a message
Just wazeting my time to help you waze your route smoothly.

Post by txemt
More points when editing. :)

You can be proactive and hit the new subdivisions before the other wazers do. There's a lot of brand new subdivisions I've placed based on satellite imagery as well as other sources for those neighborhoods. I try to beat the people moving into those neighborhoods, so they can find directions to their new homes without any problems.
txemt
Posts: 4774
Has thanked: 25 times
Been thanked: 919 times
Send a message
Just wazeting my time to help you waze your route smoothly.

Post by sgtgary
Thanks! Unfortunately, many of these subdivisions were done recently and before I was a member... and they're all goofy on the turns. So I've been *trying* to go and find turns not marked and fixing them the best I can. It's a lot of work to fix those when they're not obvious on the map. ;)
sgtgary
Posts: 64
Has thanked: 166 times
Been thanked: 10 times
Send a message
Nebraska State Manager
US Plains Editor
Twitter: @sgtgary

Post by Kuhlkatz
CBenson wrote:The problem is that my experience is with base mapped roads and you are assuming a situation where an editor has laid out the area. So yes I think you are correct. But there are plenty of segments around here (although admittedly fewer all the time) that have never been touched by an editor at all as they were base map imports.
Ah, that provided the 'Lightbulb moment' - :idea:
Being basemapped, NA likely had most of the map looking this way initially. I was referring to and also 'assuming' that it was a newly laid out area, seeing that it was already named etc.

I tend to forget that not everyone started with a blank slate, as I am only relating to what I see day to day. In INTL server case, except where basemapped, that would boil down to sloppy editing 99% of the time. In your case that's the norm for untouched areas, and unfortunately the first poor sod that drive those segments are blamed for the mess, as it now contains his name ;)
Kuhlkatz
Waze Local Champs
Waze Local Champs
Posts: 917
Has thanked: 32 times
Been thanked: 146 times
Send a message
Carel Cornelius
AM : Centurion & Sandton, ZA
CM & Coordinator, South Africa
(HTC One, Android 5.0.2, v7.19.401.51)
[img]https:///DwNb3R[/img]
South African Wiki Waze Wiki Map Editing

Post by Kuhlkatz
CBenson wrote:Did I miss something? I thought that waze did still automatically override soft restrictions (including directionality such as unknown).
I was referring to one thread that included Tony's comment as below. Not sure that it was this particular one, but I do find this interesting.

http://www.waze.com/forum/viewtopic.php ... 11#p340911 :
bgodette wrote: on Tue Jan 15, 2013 6:53 pm
TonyG-UK wrote: wrote:
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.
In the same thread gerben also said :
gerben wrote:* 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.
So based on this, if a new area is layed out and the names added as a seperate pass, or as I prefer, lay out and name the full-length streets first and then connect them afterwards, can we assume they were edited at least once more after the initial creation, so technically speaking their directionality *would* remain fixed, even if it is incorrect.

I'm not disputing anything or trying to pick fights here, I'm just curious about why some of you first-generation editors (read "old hands at this") prefer to leave sections like these, when a QW clean-up is fairly quick, especially if someone knows the area.
I personally prefer to QW junctions while I create a section, so I know it's 'fixed'. Afterwards, red arrows when viewed with 'Connectivity Arrows' (Shift-Z) draws attention when zoomed out, and can be quickly verified as a valid turn restriction or not. To spot an invalid turn restriction here is going to be impossible if not cleaned up.
CBenson wrote:I thought hard restrictions were by definition manually created (although frequently unintentionally by editing a segment property without properly setting the restrictions).
So, as far as turn restrictions go, if they are never explicitly set using Q/W on the junction or clicking any arrows with the segment highlighted, only the allowed 'soft' ones are in place and no hard restrictions should exist for the segment / junction pair ?

What I am trying to get at is this : Do we know for sure that sections left like this would not generate auto-MPs due to intact 'soft' restrictions allowing everything, and having no other explicit restrictions set, or would it be better to spend a few minutes and take the precautionary approach ?

I assume someone would have been swamped with MPs, but it more than likely would require regular drives over the area as well to provide any results that could generate MPs.
Kuhlkatz
Waze Local Champs
Waze Local Champs
Posts: 917
Has thanked: 32 times
Been thanked: 146 times
Send a message
Carel Cornelius
AM : Centurion & Sandton, ZA
CM & Coordinator, South Africa
(HTC One, Android 5.0.2, v7.19.401.51)
[img]https:///DwNb3R[/img]
South African Wiki Waze Wiki Map Editing

Post by Kuhlkatz
CBenson wrote:I've got to disagree here. A quick once over to see if road markings includes one way arrows somewhere before mass QWing is much more likely to produce URs and MPs than the existing soft turn restrictions. Unless of course you get lucky and there are in fact no one-ways or other turn restrictions there.
Someone familiar with the area should be able to correct that fairly quickly. In most populated neighborhoods, one-ways and fancy turn restrictions will not exist apart from the main arteries through them. If it's near a CBD or an industrial area, it may be a different story.

I understand that the auto-directionality and soft turn restriction overrides should not be happening any more in the back end, even though there has been isolated recent reports where this still seemed the case.

It still does not make sense why soft turns are still allowed by default when a junction is created, yet the default for the 'hard' restrictions still deny everything.
A few trips through there would maybe not affect routing due to the soft settings, but with the new automated MP system, each junction traveled through a few times will potentially create an auto-MP as the hard restrictions do not match.
Kuhlkatz
Waze Local Champs
Waze Local Champs
Posts: 917
Has thanked: 32 times
Been thanked: 146 times
Send a message
Carel Cornelius
AM : Centurion & Sandton, ZA
CM & Coordinator, South Africa
(HTC One, Android 5.0.2, v7.19.401.51)
[img]https:///DwNb3R[/img]
South African Wiki Waze Wiki Map Editing