another one set backwards for the country. there are also some missing one-way on entry exit roads you could have set, please fix.

This is in the wrong sense for the country, please fix.

Not all road loops are roundabouts, turning loops exist too. And you have made the only entrance/exit way one-way. Please fix this and be more careful.

You have set junction=roundabout and source=Bing when Bing (nor any other imagery I can see) shows a roundabout at all. This history of this way shows it was created with a comment (in Italian) which seems to translate as 'try inserting roundabout' which is not convincing. If it were real, you should have noted that it has oneway=-1 and reversed the sense. Please stop blindly adding junction=roundabout to any road loop you can see.

Do you know this is one-way? and a roundabout? If it is, you have left it backwards. Please stop blindly adding junction=roundabout to any road loop you can find.

Only a few of these are roundabouts, and a couple of these you left set in the wrong direction for the country. I have fixed the worst of these.

Do you know that the road along west side of the spanish square is one way - or any of this square? And did you see the history of the french road, with junction=roundabout and oneway being repeatedly added and deleted?

One circular way in USA set backwards, one car park outline? set as roundabout? Needs more care.

Do you know that this road loop is definitely one-way, a roundabout? And is it really in the reverse direction to normal for the country?

The change I made was to correct the text "Saintsbury's", please feel free to improve the map further.

Yes - was thinking of high priority road terminating at lower, this is the other way around - will go with primary, thanks.

If the error was a 'sudden highway type change' (osm.wiki/Osmose/issues#1090) or equivalent, then there was something to be done. With a couple of minor roads connecting to the roundabout, the roundabout can usefully be set as primary_link.

This is a geographically huge changeset, not helpful to others trying to work out what you have done. Please use smaller changesets with specific comments on your intentions.
Do you think the A614 really turns into a minor road at the M18 roundabout before becoming primary again? What was the error message you thought you were fixing?

Why add direction=clockwise? Is is really reverse direction to default?

Hi Vincent,
It's considered best practice for roundabouts, yes mostly for routing, so that 'taking the first exit' rather than 'turning left' is used. There are nearly no roundabouts where this is not done, even when geometrically awkward - only exception is where a 'bypass' route exists and a no-left-turn turn restriction may be wanted on the route via the roundabout. But the 'bypass' route is only mapped if theres a physical separation of the ways.
regards, Clive

Noticed you've added some underpasses under the A6 in this changeset and in changeset/46813168. At the moment the tagging (railway=subway) implies the track of a underground train running on the surface! Suggest you use the tags of the adjacent pathways and add tunnel=yes for the underpass parts. You can also use the Bing imagery layer as well as any gps data you have to ensure you get the best possible accuracy of locations. regards Clive

I suspect it is over-penalising a route from a secondary to a primary road via a minor way, even though it seems short and obvious. Trying with 'fuel efficient' route option (ie. short route) OsmAnd gets the right turn, it's only the 'fastest' route with the problem. For now, I've removed the no-U-turn, and trying/proposing setting the two cross-ways at the junction (which were minor ways) as secondary link (ie. extensions of Vic.Pk.Rd), so turns don't need to pass over minor ways. Looks reasonable, but would have to wait for next month's update to see any effect, and of course it (may) destroy the test case if it should rather be reported.

Hi, If turning right from the southbound Welford Rd into Knighton Jnct Ln or the pub is ok then this new turn restriction can't remain. The specific routing problem was in (expecting to) turn right from Victoria Park Rd to northbound Welford Rd - OsmAnd app's router gives left turn then U-turn which is silly. Thought I would find a mis-set turn restriction at that junction but there are none, so router must be over-prioritising main road usage. If dual carriageway goes further south that would probably discourage it from the stupid route. Thanks, Clive

A few months ago I saw that Keep right error flag at the Furzefield Chase railway bridge, and wasn't sure from imagery whether the footpath went under the bridge or not, so created a Note, which has been answered today saying that the path crosses the road. But I see you made the opposite fix a few days ago. Are you sure the path goes under the bridge, or should the path connection to the road be reinstated and the bridge (probably) shortened as per the Note response?

For me, it's not (just) an access to a private property or business, and it's certainly not private as driveways often are. It may be a dead end for car drivers, but for walkers its a significant through route connecting to the footpath beyond - in the absence of service=driveway_and_footpath, it needs to be something else, be it a lane or an 'unspecified' service road.