If you are sure that my edit is wrong and against local habits, please feel free to revert it. I'm not insisting, my comments are just to back up my decision with the usage documented in the Wiki.

private=permit is documented for street parking and was part of the proposal accepted with 98% approval.
"parking:side:private=* is in use as an addition to specify [private] more precisely, e.g. parking:side:private=residents"

"must be applied for by a resident"

But that's clearly what is described in the Wiki. I won't get a permit by going to some place, filling a form and paying a fee. I need to be a resident in the area, or need to be invited by one. That's exactly what access=private, private=permit is intended to mean.

Hi,
it's an old changeset, but there are 4 remaining nodes with an early railway:signal tagging scheme. Could you have a look and see if you can update them to the currently used scheme?

Example:
node/2867547653

Die Tags an diesem Gebäude existieren seit einer Ewigkeit, aber viele davon sind ausschließlich hier in Verwendung. Sind diese Daten noch aktuell, oder gibt es eine Möglichkeit das auf "normale" Tags umzustellen?
way/267201439/history

Hi,
please don't add parking tags that apply to different sections of a way with "_1" - these can't be used by any software as long as it's not known in which part of the way which restriction applies.
The only viable way is to split the way as necessary, even if this results in many short segments.

Hi,
could you check your additions? I found about 30 objects with strange tags like this one:
way/1148090613

Also, there are many with capital letters in tags like 'Yes'. OSM is case sensitive, so these have to be lower case 'yes'.

Thanks for the reply!
The problem is that the tag with the '.' is not defined and not supported by any software. I suggest to either separate the two thing on separate objects (which might be difficult in this case), or simply add both numbers to the normal "ref:GB:nhle" tag, separated with a semicolon.

Hi,
you added the tag "parking_lane_both = *" to many streets - this doesn't fit to the common scheme of tagging of parking lanes. Could you have a look and fix this?
The full documentation is
osm.wiki/Street_parking

Hi & welcome to OSM!
I see that you used some tags that are not used in other places, especially on this node:
node/12476340274

In OSM we have to use a well-defined set of tags to allow all the software tools to understand the data and e.g. show it on maps.
Please use only keys that are documented in the Wiki or are available as presets in your editor.

For detailed information like on this node it is in general better to add a link to the website, wikipedia or wikidata. OSM is not really suited as a directory of people working at a place.

Hallo,
hier ist wohl einiges schiefgegangen. Alle diese Knoten (und noch ein paar Dutzend mehr) haben 40 fremde Tags, die nicht in OSM auftauchen dürfen. Außerdem fehlt die notwendige Angabe einer Quelle und die nötige Dokumentation eines Imports, siehe
osm.wiki/Import/Guidelines

That's not necessary. The villages are tagged as nodes or areas, so it's always possible to search for snowmobile paths near them, e.g. like this

https://overpass-turbo.eu/s/1WDC

Thanks for the reply!

So, adding this as tags like
bålsjön = yes
was a mistake then? Or are the cities some kind of operator of the trail? Then it could be tagged as
operator = bålsjön

Hi,
you used some tags that are not used in other places:
Could you explain what they mean?

bålsjön
vågdalen
Vågdalen

Please check this import, all the ways are missing tags.

基石 = 礦物課1097號
基石 = 市11

Done.

There are two more nodes with a strange tag I can't fix:
node/12468292272
node/12468292274

Hi,
if you like, I can just change the tags, that's not much work.

Hi,
you added a couple of tracks with a strange "sud=d" tag. Please have a look.