Thanks Tim.
Is routing still broken for segments ≤15 m long? If so, it’d be nice to have a highlight for segments equal to or less than 15 m in length.
Is that different than the feature which disallows routing on short segments (10m) to prevent u-turns?
Observed on Chrome. Don’t know for FF.
It looks like there is a mistake between Toll and Locked features in 1.6 as:
-
When selecting Lock, it displays locked segments with a Dash
-
When selecting Toll, it displays toll segments with a Red
The black line on the locked segments indicates that it is locked at a higher level than yours. Segments locked at your level and below are highlighted in red with the transparency increasing as the lock level decreases.
The toll highlight is dashed instead of solid. I hadn’t realised until now that there was a colour conflict. In the UK, at least, I think we may lock all toll segments anyway to prevent inexperienced editors changing them. The toll highlight “takes precedence”, so a locked, toll segment is dash-highlighted. I don’t know if there are any colours left to split them!
Tim - might you want to re-jig the order of the checkboxes so that “Toll” is above “Locks” on the menu?
The “Locked” option now displays 2 colors: red = locked but editable by you; black = locked at a higher level.
The “Toll” option shows blue dashes for unlocked toll segments, and red dashes for locked toll segments even if “Locked” option is off.
Hope that makes sense.
via mobile
Hi Tim, if i use lock flag and editor filter, to check edit of wazer with rank lower than mine, no highlight is shown.
Is it possibile display the lock highlight of that editor only ? Regards
Marco
Hey!
Is it possible to change the Red locked color in a color that flashes? Maybe green or something like that. Because it’s hard to see if a Major is locked (lower level) or not.
Nice tool!
Or… Is it possible to tell us what to change withing the script to be able to that?
Thanks
I shall consider adding this in a future version when I have time.
Meanwhile, the easiest solution is to (temporarily) disable the Road layer with Shift+R. Then the highlights are easy to see.
Search the code for “#f40”. That line, and the previous line with “#f00” are the two red colours used for locked roads. You’ll probably want to change the “#f00” one, as the second is not used.
Thank you, Tim.
Hi, first thanks for your extension, very useful.
I had an idea :
Now segments have a rank, so I thought it could be interesting to highlight roads with a high rank (for example only level 5 roads), it could show the skeleton of an area.
If you are interested I can send you a modified version of your script including this feature.
The script already highlights locks based on the road rank (if not locked) or the user rank (for locked segments). Are you asking that there be a selector for minimum locking level?
Yes it’s something like that when you want to be sure that roads are locked with the good level or for editors with lower level they can know if they will be able to edit some roads without checking every segments one by one. (if you create a new road starting from a locked road, it is very disapointing when you finally cannot save because your starting road is locked with a big level and have to cancel everything.)
The script already adjusts the width or opacity of the highlight according to lock level I thought?
Oh I didn’t notice it, so you can forget my idea unless we find a reason to see lower level rank.
Tim, it’s easy to edit the script today to show all Roads and include Soft Turns with the node highlighting, but would it be possible in a future update to add something in the GUI for this, maybe “Show all node highlights” or something, so we don’t have to edit the script?
I’m afraid not. The script is deliberately coded to only show turn issues on major roads to encourage responsible editing.
Confused, why would showing on other streets be irresponsible? Only thing I could think of is it would possibly show too much information, distracting some editors?