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?f=10&t=36644&p=340911#p340911
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.