Hi Gareth. I’ve connected both of those. :mrgreen:
I do have a few notes 
- I’ve tweaked the geometry on Beech Grove. One of the angles was almost exactly 45°, which means we literally don’t know what instruction Waze will give - could be turn or keep or nothing. By tweaking all 3 angles to approx 120° you will get “turn” instructions - probably best for an unclear junction with no road markings. The Junction Angle Info script is a great help here.
- Beech Grove should be abbreviated to Beech Gr.
- This segment is only joined at one end. When you create a new segment and try and join both ends to an existing segment, only one end will join - you can’t split a segment twice in one “action”. The best way is to make the loop using 2 segments. This also helps because…
- …Waze can’t handle a loop made of 2 segments. Routes are send to the client as a list of junction nodes. If there are 2 or more single segments joining the same pair of nodes, strange things can occur. Think “crossing the streams”. :lol:
- This bit is even worse! The loop is made of a single segment, which just confuses the editor. The segment you tried to connect to the loop hasn’t actually connected and probably won’t. Delete the loop and just extend the other segment across that parking area in a single line. With a car park that small, the app can’t tell exactly where you are anyway - not close enough to use the loop properly.
- Lastly, I see a few segments around there being highlighted as “simplifiable” by WME Toolbox. This isn’t necessarily a problem - it indicates that the segments have geometry nodes that aren’t really contributing significantly to the shape. You have to remember that the segments get drastically simplified when the map is generate for the Waze app. If you’re drawing very smooth & accurate geometry, it may be very satisfying to you (I’m the same), but you’re probably spending time on it that you don’t need to. Have a look at the A19 just to the north there. You’ll see that it hardly follows reality precisely - but it makes little difference by the time you see it in the app.
Hi,
Thanks for that; really great information. All taken on board. It’s interesting to get background on how the app handles the information.
Corrects made.
I know what you mean about making sections match reality; I find it really cathartic to make mapping very accurate, even if this means I have been going overboard! Will back off a bit…
Gareth