I remember there are cases to use dummy segments on dumbell rounabouts where in the US. A bit lazy to find it out
Personally, I will treat this as a single roundabout. I did check on Google it treats it as single roundabout too. However, Nokia map treats it as normal road so it only gives 'go straight, turn left, etc.' instruction.
Tim mentioned the road sign. I checked on the street view, there is no roundabout sign after you entered the roundabout. So it's better to treat it as single one.
As it is a bit big roundabout, we may lost court the number of the exit. Maybe we can change this segment (click here) to ramp and name it 'Exit to Grange Park' as road sign. I have tried this in my area and mentioned in this thread.

btw, should we report there area is old aerial map

sorry guys, the examples I've seen were in the UK. The third case is more like your case. (Tim, I think it is your area, right?)
1) https://world.waze.com/editor/?zoom=8&l ... TTTFTTTTFT
2) https://world.waze.com/editor/?zoom=7&l ... TTTFTTTTFT
3) https://world.waze.com/editor/?zoom=5&l ... TTTFTTTTFT

A solution I've seen elsewhere (can't find reference, sorry) is to make this as two roundabouts, but make one segment of each non-drivable and invisible. With appropriate turn directions and road types, you can make the junction look and navigate correctly in the client.

Caveat: I've not tried this myself.

Personally, I would consider these to be two joined roundabouts with a partial restriction.
What would Google do? (it attemps to treat them as two roundabouts, but fails).
What do the local signs look like?

While the keep left/right instructions are perhaps not ideal, they do mostly work in generic cases such as this.

leo_lau wrote:Personally, I will treat this as a single roundabout. I did check on Google it treats it as single roundabout too.

I disagree. Depending on the route, Google gives two roundabout instructions. Where it doesn't is where it's messed up.

leo_lau wrote:sorry guys, the examples I've seen were in the UK. The third case is more like your case. (Tim, I think it is your area, right?)
1) https://world.waze.com/editor/?zoom=8&l ... TTTFTTTTFT
2) https://world.waze.com/editor/?zoom=7&l ... TTTFTTTTFT
3) https://world.waze.com/editor/?zoom=5&l ... TTTFTTTTFT

The first example is one that timbucks did following a discussion here.

That third example is up by me, yes, though I haven't turned it into a regular roundabout because I think it's too complicated. The various ramps and splits are carefully names so that it should give sensible "keep left/right" instructions.

There's also this partial roundabout which is part of a pair of dumbells, which I may convert. Problem is, the other one is a different shape, so they can't be considered 1 roundabout.

Timbones wrote:A solution I've seen elsewhere (can't find reference, sorry) is to make this as two roundabouts, but make one segment of each non-drivable and invisible. With appropriate turn directions and road types, you can make the junction look and navigate correctly in the client.

Caveat: I've not tried this myself.

The question is would the majority of people understand it correctly if it said (in the case above) "at the roundabout [continue straight/take the second exit] and then at the roundabout take the second exit" - I'm a person who would take the continuation across the dumbbell as being the second exit, not the bridge across the motorway