Down to 1 - let me know when you're done.

A couple of notes:

When you create a permalink for multiple segments, you can pan around the map adding segments. As you move, WME caches the segments you are selecting so there doesn't appear to be a problem. When another editor opens your permalink, the only segments available to select are the ones that are visible in the map display. In this case, you gave a permalink with 8 segments selected, but only one was visible to me and that was the only one selected. The key is to zoom out when you have selected all of the segments so that they are all visible before creating the permalink - like this. When doing this, also avoid creating a permalink that needs a zoom level lower than 4 to include all segments. As you zoom out, the segments will remain selected for you - but street segments can't be selected below zoom=4, so if the zoom level of the permalink is too low, segments may be not be selected when someone else opens them.

The other note is about geometry nodes - the nodes that alter the shape of segments. These 8 segments have highlighted up as having un-needed geometry nodes. This is not a problem as such: it indicates that you may be putting too much effort into making detailed shaping of segments that isn't necessary. There's also the theoretical consideration that the fewer geometry nodes we use, the less processing time it takes for the Editor to work. When map tiles are generated, segment geometry goes through quite a bit of simplification, so very fine detail will be lost anyway. I must admit this used to be one of my own failings in my early editing days: I would spend far too much time trying to create perfect curves and it's something I still fight against today.

Downlocked

The reason for the two private segments is because of a problem that can happen when a main road is paralleled by another access road.

It may happen that Waze will decide to route a driver via the parallel road. If that happens, the driver will likely ignore it and continue on the main road because it's faster. However, phone GPS isn't good enough to detect the difference, so Waze will assume the driver followed directions and took the access road. This increases the speeds recorded for the access road and make it more likely to be chosen in the future. This results in a vicious circle where the access road can become the preferred route all the time for Waze!

The general solution is to make the parallel road private, so Waze will only use it to reach a destination. The only complication can come if the parallel road is legitimately used to access other side roads coming off it. Since there's only one dead end segment here, that complication does not apply.

However, doing it with 2 private segments like is not normal practice and looks odd both in WME and the app. I would advise changing all of Leegate Close to private road. You also need to tweak the angle on the north end of Leegate Close: someone turning in from the north will get a "keep left" instruction instead of a "turn left"; and someone leaving to the north will get no instruction at all.

Meanwhile, I've re-locked the main road

iainhouse wrote:Down to 1 - let me know when you're done.

A couple of notes:

When you create a permalink for multiple segments, you can pan around the map adding segments. As you move, WME caches the segments you are selecting so there doesn't appear to be a problem. When another editor opens your permalink, the only segments available to select are the ones that are visible in the map display. In this case, you gave a permalink with 8 segments selected, but only one was visible to me and that was the only one selected. The key is to zoom out when you have selected all of the segments so that they are all visible before creating the permalink - like this. When doing this, also avoid creating a permalink that needs a zoom level lower than 4 to include all segments. As you zoom out, the segments will remain selected for you - but street segments can't be selected below zoom=4, so if the zoom level of the permalink is too low, segments may be not be selected when someone else opens them.

Thank you, I will try to remember these notes next time. Much appreciated.

The other note is about geometry nodes - the nodes that alter the shape of segments. These 8 segments have highlighted up as having un-needed geometry nodes. This is not a problem as such: it indicates that you may be putting too much effort into making detailed shaping of segments that isn't necessary. There's also the theoretical consideration that the fewer geometry nodes we use, the less processing time it takes for the Editor to work. When map tiles are generated, segment geometry goes through quite a bit of simplification, so very fine detail will be lost anyway. I must admit this used to be one of my own failings in my early editing days: I would spend far too much time trying to create perfect curves and it's something I still fight against today.

Thanks. I used to do the same, but after reading on the wiki and noticing the difference, resolution-wise, between the editor and app the drivers are using to navigate, I realised that perfect geometry would not do that big difference.

Could you please downlock these two segments as well?

Thanks

I'm done now. Thanks.
P.S. I couldn't get the point behind making that last two segments 'Private Road'.

Thanks.
I'm done. The angle to the north has been sorted out.