Hi,
could you check this kerb?
node/11109129468
It has several tags that are not used in other kerbs:
counter = slope: <= 5%
description = Incline: 11%
top = landing: >=60"
two_sided = yes

Welcome to OSM!

These edits look like you dumped a local data set into the OSM database. Unfortunately this is not the correct way to import external data and make it usable within OSM.
Please have a look at our import guidelines:
osm.wiki/Import/Guidelines

I'll revert these additions for now so that you can first sanitize the data and then reimport it following the mandatory guidelines.

Please don't try to start discussions in 'description' tags.
I removed "maxweight:7.5" because such a tag doesn't exist. There can't be a value inside the key.
The correct form for conditionally different weight restrictions is maxweight:conditional = * @ *

Hi,
could you check this node, it got two ref tags, which one is correct?
node/12850724601#map=19/59.339660/18.037133

Thanks for the explanation. It seems the city map can't be accessed from Germany...

The current tagging is a bit unfortunate, because e.g. 'shoulder' is not used with forward/backward, but always with left/right. But maybe the city comes up with better signage quicker than we can find a proper tag :)

Hi,
'mobile_bakery' is not yet in use in other places.
Have a look for "street_vendor", which also covers this type of amenity traveling around:

street_vendor=yes

Hi,
I don't fully understand the tagging of this way:
way/1207542763

What's the difference in both directions (apart from the traffic signs)? In one direction you tag it as segregated, in the other as pedestrians need to use the shoulder, but the surface is the same everywhere. Do you have a photo of the way?

Welcome to OSM!
Something went wrong here: Instead of editing existing objects, you uploaded a whole new set, duplicating the existing data.

Please only use the integrated download function of JOSM. Don't try to download e.g. a GeoJSON file elsewhere and open it in JOSM - it will result in this kind of duplicated data.

Hi,
please check this node, it got a strange tag:
node/12830021694#map=19/51.267525/-0.282896

Thanks for the reply. I already fixed the tags that where added up to now. Just make sure your presets / auto-completion get updated.

Hi,
please check your tagging:
It's "axle", not "axel".
and the full tag should be
"maxaxles:hgv"

Hi,
could you check this parking? "maxstay" should be a time, not a price.
way/1383240422

Hi,
you added two memorials with a huge amount of text in the tags. Is all this text in the various languages actually present on the memorial? If not, it shouldn't be in OSM - a link to Wikipedia or Wikidata containing all the details about the person is sufficient.

It's described in the wiki page about ferry routes:
route=ferry
Are you familiar with bus routes? The mapping scheme is almost identical.

You can just draw one way and create two relations using this way.

This separates the two types of ferry without drawing anything twice.

Hi,
please check the wiki for common socket:* tags - the ones you used here are not used in any other place.

Hi,
you used tags like "level:1-2=residential" to mark the use of different parts of two buildings.
Usually, this is mapped using two building:part=yes objects with their respective building:use tags. Could you have a look at this tagging scheme?

Hi,
these ferries got a huge amount of tags that are not used in other places and are very unlikely to be used in any kind of software.
I'm convinced that there are enough standard tagging options for this kind of information.
Most importantly, the prefixes 'public_boat' and 'private_boat' need to be removed. There's no need to have the information of two different services on the same way - just separate them into to ways. That would make the information a lot more clear immediately.

Hi,
you introduced a new tag here: "bikestreets" - what does it mean?

Hi,
you introduced a new tag "mayoral" here - what does it mean?