Quite sure. Sorbus aria is a taxonomically outdated synonym of Aria edulis.

Sorbus is a taxonomic mess that has been considerably revised over the last decade.

https://www.treesandshrubsonline.org/articles/aria/aria-edulis/

"You must not delete the work of other contributors."

Oh dear. Oh dear, oh dear, oh dear.

I did NOT "delete" the work of other contributors. I replaced it with better tagging. To quote the wiki:

"The following closed ways should be treated as linear features:

* "barrier=*, for thicker hedges or walls or detailed mapping defined using an area add area=yes
* "highway=*, see 'Highway areas' below for more details"

Those highway=footway and area=yes tags have highway=footway lines within them.

osm.wiki/Key:area:highway

That tagging which I correctly used is describing the shape of a pavement area. The linear highway=footway ways through the area tagged with area:highway are the ones used for routing.

The combination that you want to use occurs 456,857 times, whereas area:highway is used 349,749 times.

So get off your high horse and actually look at tagging use reality instead.

Easy. That's the correct Latin binomial for it. Sorbus aria is an outdated binomial name for Aria edulis.

https://www.treesandshrubsonline.org/articles/aria/aria-edulis/

Technically yes.

However it's correct, even if a bit redundant. It's certainly better than Quercus n. sp. which means a botanically undescribed species of the quercus genus which is a tad unlikely next to the Peripherique in Paris!!!

Le problème ? Platanus n'est pas une espèce. C'est un genre. Le genre est le niveau supérieur à l'espèce. Il existe de nombreuses espèces chez Platanus. Par exemple, Platanus orientalis et Platanus occidentalis. En français, Platane d’Orient et Platane d’Occident.

Il s'agit d'espèces d'arbres différentes mais toutes deux font partie du genre Platanus.

Pour Plantane il est correct d'utiliser genus:wikipedia:fr.

They mostly are and I intended them to be. Looks like some escaped being sorted out. I will remedy this.

Except that those central pedestrian refuges are large enough to mean that it should be recorded as two carriageways for the distance through the Place des Ternes.

Why do you think I altered it in the first place?

Oh and the give way on node 12532433232 now makes absolutely no sense with the way you left it. You've also managed to get Avenue des Ternes crossing a pedestrian refuge without a corresponding pedestrian crossing node.

I likely would have picked it up with Osmose in any case, but yes it can trivially be resolved. Tilia cordata as a species has Tilia as a genus. That's why Osmose has picked up the problem.

The fault is not my edit. The fault is the current genus tag of Malvales nothing of the sort. Malvales is actually an order rather than a genus. Very much higher up the taxonomic tree.

Simple. No such thing as the combination of Acer and hippocastanum. It was nonsensical information and it was not at all clear what the correct combination should be.

Aesculus hippocastanum as you have added on the other hand is a valid combination and useful information.

D'accord.

Mais l'espece Platanus × hispanica, ou Platanus hispanica est un platane. Vous avez crée cette point avec species=Platanus hispanica.

https://www.warwickdc.gov.uk/download/downloads/id/839/bye-laws_for_pleasure_grounds_sydenham.pdf

Pretty sure that's where I got it from: bylaws made by the local council that run the park.

Too late. I'd already updated to the alpha by the time you posted that comment. I'll have a hunt around using Overpass and see if I can get rid of those buggy tags.

Where on earth did this come from?

It is NOT a roundabout. It is a signal-controlled crossroads junction.

As has been said before, OSM is NOT an appropriate place to put short-term closures of roads. Beyond that this edit is based on a source of One.Network, which so far as I am aware does not have a licence which is compatible with OSM. So the edit is bad on two points, not just one.

Oh definitely a typo. Good catch.

I'll fix it after finishing this reply.

This edit is utterly wrong. Canal towpaths are NOT "designated" for cyclists. Designated means a legal right from public law to do something. A Traffic Regulation Order in the UK. That is not what the Canal and River Trust allows on its towpaths.

Cyclists are allowed on the towpaths through the permission of the Canal and River Trust only. That is a permissive tagging situation. Hence the previous, correct tagging.

Please reverse this changeset.

Well in that case it was tagged incorrectly. If it's no longer used by passengers then it is disused and should have been tagged as such.

This has now been corrected.

Lots and lots and lots of incorrect tagging for renderer in this changeset.

Bus routes do NOT have names as you have tagged them. The names you have tagged are classic tagging for the renderer. The bus services have a reference, whether numeric, alphabetic or alphanumeric. They have a starting stop. They have an ending stop. They have stops they go via. All of those can be and are tagged in the Marineo route relations around Boulogne.

Properly configured software reads those tags to show details for the bus route. I removed the name tags for a reason. Tagging for the renderer is that reason. Now you have incorrectly added them back.

I'm going to remove them again to stop the tagging for the renderer.

No. Wrong.

You do NOT deliberately or negligently create impossible geometries like your edit did. Your edit left a slip-road that is impossible to access.

Guess what? It shows up on the iD validator as an error. There's a reason for that.

It's one thing to accidentally create an impossible geometry. That happens to all of us on occasion. Same as sometimes accidentally breaking a big relation and causing an area to "flood" or similar.

Your attitude to this changeset on the other hand says to me that you have done this deliberately or negligently rather than accidentally. When the situation was pointed out to you by me your response was to arrogantly dismissed the issue. Even taking aside bus route relations, which have a tendency to be broken by the careless because they don't show up directly on the map or in validators of editors like iD there is the issue of the slip road to the A446.

That slip road shows up on the main map render. The error shows up in the iD validator as an unreachable road. The slip road going from the A446 to the former roundabout is showing as closed on One.Network until 16th September. The slip road you have disconnected from things is showing as open on that website!

So if One.Network shows the length of road as open that would indicate it can be accessed from somewhere. That would indicate it is likely the new route up from the south is now open.

So if you did a "site observation" you would have been able to see whether that were true and mark things up accordingly. But you didn't. You just went in, plonked an edit in place and didn't sort out the consequences of that edit properly.

I've had the "benefit" of your edits before as I recall. The A452 junction at Park Drive and Princes Drive in Leamington for example. This one I don't think I will be able to easily sort out as my chances of going through that area in the near or even medium-term future are low.

Do your edits properly and stop being negligent of the consequences and arrogant when those consequences are pointed out to you.

If you're going to do things like this then make sure you create geometries that are actually valid. This has left an utter mess with the sliproad leading from the junction to the A446.

You have also broken some bus route relations with this edit as well.