Query about use of elevation

While looking at some roads close to home, I noticed that the following sections of the ringroad are elevation 2 while all other surrounding ones are elevation gorund:

https://www.waze.com/en-GB/editor/?env=row&lon=-1.58973&lat=53.77927&layers=933&zoom=5&segments=123168739,123168723,145969536,146524314,189941514,231375050,232276391,123168701

Does the elevation in this case really matter? Will it affect routing in any way?
Or does it only come into play when on road crosses another via bridge or tunnell?

Cheers,

Esky.

Elevation does not affect routing in any way.

It used to be the case that, if 2 segments with the same elevation crossed without a junction, Waze would generate a Map Problem suggesting that there should be a junction there. However, a large numbers of such crossing segments appear in complex junctions and I never see any such MPs, so I’m quite sure that this mechanism is no longer in operation.

With the release of the last client version but one, Waze started rendering elevations on the livemap and the client, leading to some strange results showing up. Waze have said this was an accident - elevations are not yet supposed to be rendered. They have advised us not to worry about elevations at the moment.

Having said that, I don’t see it does any harm to correct wrong elevations, against the day when they will be rendered deliberately. Don’t, however, go about adding junctions to segments so you can “create” bridges/tunnels where one segment crosses another. It’s entirely possible that Waze will work out a way to render these without small bridge segments: until they work that out, there’s no point adding them.

Iain,

thanks for the explanation. Good to know they’re not causing ant issues.

That being said … they do play havoc with my OCD ! Do you mind doing the honours and setting the elevation to ‘ground’.

Thanks in advance.

Esky.

I used to remove bridge segments whenever I saw them, setting the level to “ground” and merging them with the segments each side. However I’ve now realised that there is sometimes good reason for having separate bridge segments.

Sometimes only a bridge, and not the rest of the road, may be closed. Most often this happens when a railway passes over or under the road, when Network Rail may close the bridge. If the rest of road contains likely destinations, e.g. if it is a residential road, it’s much better to close just the bridge on Waze. So it’s a great help if there’s a bridge segment already; please don’t get rid of them.

On the other hand, for purpose-built roads with no houses or other likely destinations along them, I still think it’s fine to get rid of separate bridge segments. Any closure to such a road is likely to be for a complete stretch between roundabouts or other junctions. And since you when you want to put a closure onto the spreadsheet you have to list all the segments, the fewer the better!

Done :mrgreen: