The red flag would be expected, the blue unneeded flag I'm asking to be fixed so it considers turn restrictions and allowed U-turnsTaco909 wrote:I don't think turn restrictions were ever enough to avoid a flag... in fact, it would result in a "red" inbound/outbound connectivity warning flag rather than the "blue" extra node flag.PesachZ wrote:Adding an extraneous segment would stop the validator flag, but That adds two nodes instead of one into the database. I think Validator should compare segment properties across a junction, an not deem it unnecessary if it is separating two segments which different properties, (i.e. lock levels, elevation, name, alt name, type), as well as any turn restrictions including allowed u-turns.
The connectivity flag could be avoided by the addition of the one-way segment and enabling the u-turn.
I thought that lock level was enough to avoid the extra node flag. Elevation and name are unless something changed on elevation lately.
Lock level didn't do it for me here
Sent using Tapatalk for Android 4.4.2
Re: [Script] WME Validator 1.1.1 / 30.08.2014