In iD geht das so weit ich weiß nicht. Mit JOSM ist es kein Problem, du kannst beliebig Daten in/aus lokalen Dateien speichern und laden, so dass du sie siehst, sie aber nicht auf dem Server landen.

Hi,
you might want to change 149 times 'souuce' to 'source'.
Cheers, Jan

Such external reference numbers are usually not part of the data in OSM. Please write a description in the Wiki so that every mapper can understand what they are.
Also consider to use an established format for the keys, such as ref:capad.
Actually, there are already some objects with a capad number using the tag "ref:capad2014_osm" - adhering to this scheme would be beneficial for all data users.

Hi,
you introduced some new tags on several national parks. Could you explain their meaning?
AUTHORITY = WA_DPAW
PA_ID = WA_31362
RES_NUMBER = WA31362

Thanks, Jan

Hi,
dann war shop = coffee (verkauft Kaffeebohnen) nicht richtig, es hätte amenity = cafe (schenkt Kaffee aus) sein müssen.

Wir haben keine Möglichkeit, zwei so verschiedene Dinge an einem Knoten zu taggen. Deswegen würde ich hier vorschlagen, zwei getrennte Punkte anzulegen für Cafe und Radwerkstatt. Dass die dann am Ende im gleichen Raum sind und vom gleichen betrieben werden, ist egal. Dann erscheint der Punkt auch richtig auf allen Karten, die solche POIs explizit anzeigen.

Hallo,
du schreibst "Als Quelle für den Umriss der Passage und alle indoor-Räume usw. diente der Plan, der an einigen Eingänge steht"

Dass ein Plan öffentlich aushängt heißt nicht, dass er frei verwendbar ist. Hast du die Lizenz überprüft, bzw. eine Genehmigung durch den Hersteller des Plans?

Hi,
could you check this road? It got the tag "ones = yes".
way/44098440

Jan

Hallo,
ist das richtig, dass dieser Kaffeeladen jetzt ein Fahrradladen ist?
Und was heißen denn diese beiden Tags:
service:bicycle:cake yes
service:bicycle:coffee yes
Gruß, Jan

Hi,
this waterway got a strange tag, could you check that?
way/574814527

Jan

Hi,
you used the tag "w2g = yes" on several objects, could you explain what it means?

Thanks, Jan

Hi,
this way got several access tags, which aren't right. Could you explain what the actual access rules are? I guess it can easily be tagged with access:conditional=*

Thanks, Jan

Hi,
it looks like something went wrong here, there are several peaks with strange tags like
elevation=717.98
hj_name=露積峰
index_no=3485
lon=126-58-38.35
lot=37-39-12.28
type=표고점
These don't look like they should be in OSM. Could you check that?

Jan

For JOSM I only know about the "LaneAttributes" preset which helps a bit to quickly enter the most important attributes.

Hi,
you introduced a huge number of new tags in this changeset, which have not been used in any other place and which are not documented. Please spend some time reading the Wiki to find out how these features have to be mapped so that they can be understood by software and are for example shown on maps.

House:code 1A20
addr:Distirct Mbeya vijijini
addr:Village Njelenje
adults 4
cash_access Commerce;MPESA
cash_deposit Commerce
electricity no
fence no
head_household yes
house:rooms 6
house_member 5
house_rent no it is not for rent
livestock yes
livestock_type Pig
number_houses_compound 2
other_energy tochi na koroboi
roofing:colour silva
roofing:condtition kutu
roofing:material Iron sheet
roofing:style Others

I also missed a clear description, so I made my own. In general the order of almost everything is
key
[:subkey]
[:hgv|:bicycle|...]
[:lanes]
[:forward|:backward|:both_ways]
[:conditional]
[:start|:end]=*

osm.wiki/User:Mueschel/DestinationTagging

Yes sure, if this is a documented tag, feel free to use it.

Hi,
sorry, I don't speak Hungarian.
The two objects had the tag "url:", not "url:miserend".

Hi,
I saw that you added some destination signs here. One remark: You used the tags destination:to:arrow and destination:to:symbol while the usual order is destination:arrow:to and destination:symbol:to

Cheers, Jan

This changeset was reverted in changeset/57657580

Kannst du etwas hierzu sagen:
note/1340960

Gruß, Jan