Hi,
could you check these nodes? They got the tag "navigatinaid" instead of "navigationaid".

Jan

Hi,
you uploaded 59 nodes with very strange tags - they dom't look lime they belong into the database, e.g.
node/3667974021
Could you fix these?
Jan

Hi,
28 seems right, I don't know why I read / wrote 50.
Thanks for taking care!
Jan

Hi,
you added 4 nodes with the tag "traffic_sign:s" - this looks like a mistake. Could you check it? Example:
node/4564258644

Cheers, Jan

Hi,
could you check this way? I don't know what "biv = yes" means.
way/577322675

Jan

Hi,
you used the tag "socket:combo" here - this type of socket is new. Could you check which one it actually is? osm.wiki/Key%3Asocket

Hi,
in your edits I found the tags "working", "working ", "Working" and "Working ". Please make sure you use only lower case letters and no spaces in the key.
The same holds for the values, "Pole" should be "pole". Could you have a look and fix these issues?

Thanks, Jan

Hi,
could you explain the meaning of this way? It doesn't have any valid tags.
Jan

Hi,
you uploaded another 281 ways with the tag "landcouver" - this should be "landcover". Could you have a look and fix this?

Thanks, Jan

Hi
you uploaded 50 ways with only foreign tags which looks like a mistake.
way/577831441
Could you have a look and fix this?

Cheers, Jan

Hi,
you're using the tags "maxspeed:backward:type" and "maxspeed:forward:type" here - usually the order is "maxspeed:type:backward", because 'type' is a sub-key and 'backward' is a suffix. Would you have a look and change it to the common order?

Thanks, Jan

I fixed it in changeset/57912710

Hi,
you invented 3 new tags "DTP ", "DTP", "Dtp" here. Could you explain what these mean?

Please keep in mind that OSM tags are case sensitive and whitespace matters.

Jan

That means it is an import of data? The source is not "knowledge"?
Please read osm.wiki/Import/Guidelines

Also, the tagging has to be revised, tags like
object_id, type = AUTRE, horaires:FR, longitude, latitude should not appear in OSM and have to be removed or adapted to the established tagging scheme.
Names are _never_ written in capital letters. Some of them where mapped correctly before your change.
The description tag is not a place for extended advertising for the object.

Hi,
could you check your preset / default values / scripts? There is a typo: "glacier:e1e_bottom" instead of "glacier:ele_bottom" (a "one" instead of the letter L)

Cheers, Jan

What are we going to do with the existing
res_num, pa_id, Res_num, RES_NUMBER, PA_ID tags? Delete?

Hi,
on these 182 ways you added the tag "landcouver" - this should be "landcover". Could you have a look and fix this?

Thanks, Jan

Barriers like this exist almost everywhere. As you describe there are many different kinds of obstacles that hinder users of one or more specific kinds of vehicles. I fully agree that this is important information to include in OSM, but I'm sure that you need a much more specific tagging with many more options. A simple 'inclusive' is not very useful because very few ways are really inclusive and can be used by ansolutely everyone.

"inclusive" is not actually a "speaking tag" - it could be anything. What is the exact width when you start using this tag? what about bicycles with trailers?
I would recommend to stay with the established tagging schemes: You can always use a "maxwidth" tag - this carries a lot of information and should be supported by most routing codes.

Hi,
you used the tag "inclusive = no" on several barriers, what is the meaning of this tag?
Jan