berestovskyy wrote:dknight212 wrote:In London we use this type of construction to work the time based operation of our congestion charge.[...]is it possible to prevent these types of segments being raised as issues?
It's not a problem to suppress the "Overlapping segments" either for lvl 6 locked segments or if one of the overlapping segments has a time based restriction.
Please note that Validator users have the "Exclude non-editable segments" option set by default, so low-level users do not see those errors since the segments have lvl 6 lock.
Please discuss the options I mentioned above with the other CMs and let me know shall I exclude lvl 6 locked segments, segments with restrictions, both or neither.
SuperDave1426 wrote:Ok, thanks. I wonder if he can be persuaded to add State Managers, at least within the states they manage....
PesachZ wrote:Take a look at the link which started this discussion, the satellite and street view images both confirm that it is a two way street on both sides of the barricade.
Unless you feel there should be a 5 meter segment at the do not enter sign? But that becomes an unnecessary hack, and an added node just to make validator happy. (Maybe not just to appease validator, as it could also allow the client to display the blockade)
crazycaveman wrote:If you have the experimental road layer enabled and the legacy roads disabled, no roads will be displayed because the experimental layer does not yet get enabled through a permalink. Might be best to enable the roads layer before running a scan so you don't have to enable them with every permalink to follow
Users browsing this forum: No registered users