Hi,
I found 70 Relations with the tag "lavels". Seems like a typo. Could you check that?
Cheers, Jan

Hi Leon,
please check for spelling mistakes in keys. E.g. I found "building:levela",
"building;levels" and "bulding:levels"
in this changeset.
Cheers, Jan

Hi,
these tags are still in the database. can they be converted to something useful or be deleted?
Also, I found several invalid multipolygons that do not have an "outer" way.

Hi,
can you really recycle glasses in this container? node/4317394839

Or should it be recycling:glass = yes?

Cheers, Jan

Hi,
can all these foreign tags be deleted?

KECAMATAN DUSUN SELATAN
Keterangan Pemda
Kondisi Baik
Kriteria Kantor
Latitude 1° 42' 31.047" S
Longitude 114° 52' 19.305" E
NAMA_KAMPU Buntok Kota
Nama_Fasil Kantor Bappeda
X_UTM 263260.0
Y_UTM 9811014.0

Hi,
you used the tag addres = construction. As an address (note the double s) can not be constructed - do you mean building=construction?
Cheers, Jan

Hi,
I found the tags maxheight:lane:2 and maxheight:lane:3 in this changeset. This kind of tagging is not used in other places.
Usually the :lanes suffix is used osm.wiki/Lanes
e.g.
maxwidth:lanes=value1|value2|value3
listing the maxheights for each lane from left to right. Maybe you want to adapt your tagging to this scheme?
Cheers, Jan

Bei solch seltenen Keys kannst du dich leider nicht auf keepright verlassen. Dieser Check auf falsche Schreibweisen funktioniert mit reiner Statistik - und die ist bei seltenen Keys leider nicht aussagekräftig genug. Danke fürs Korrigieren ;-)

Hi,
bitte bei der Schreibweise aufpassen, "health_specialty:*" hat ein 'i'. (nicht specalty)
Und, in einem anderen Changeset: Es gibt kein ":type:" im Namen. Es sind etwa 40 Tags von dir mit diesen Schreibfehlern. Kannst du da einen Blick drauf werfen?

Hier kannst du schauen, was anderswo verwendet wird:
http://taginfo.openstreetmap.org/keys/health_specialty#similar

Hi,
did you want to add these foreign tags on 361 ways or was it a mistake?
E.g. way/431093868
LUAS_KM2=0.0
LUAS_KM2_2=0.0
OBJECTID=0
OBJECTID_2=0
PENDUDUK_2=0.0
PENDUDUK_J=0.0

Cheers, Jan

Hi,
this paragraph explains it quite well:
traffic%20sign=*?uselang=en-US#As_part_of_a_way
traffic_sign=stop says "There is a stop sign in this place", it does not give any information about the direction, so we have to assume it affects both directions.
traffic_sign:forward=stop says "There is a stop sign here, but only in forward direction"
That is, use traffic_sign if the sign is there in both directions, _or_ use traffic_sign:forward / traffic_sign:backward if it is in one direction only.

Hi,
could you check this tagging?
building:evel =3
on way way/67317511
Looks like a typo but I can't correct it without knowing the building.
Cheers, Jan

Hi,
why did you revert my changes? I.e. turn:hgv:lanes to turn:lanes:hgv? The transportation mode is always listed after the main key and before a suffix like :lanes or :forward.
Jan

Hi,
I found it because of the typo. And I didn't know about this century-tagging scheme before, so I just asked.
Cheers, Jan

Hi,
you used the tag "startdate=C17". What is the meaning of that?
way/138893496

Jan

Hi,
you added the tag "Operator" to this beach. There was already a tag "operator" with a different value. Could you check that? In OSM, keys do not use capitalization.

Cheers, Jan

Hi,
the tagging of 8 stop signs seems to be wrong:
traffic_sign=stop, traffic_sign:foward=*
I think it should be traffic_sign:forward=stop
e.g. node/4291855623
Cheers, Jan

Hi,
this commit created almost 10,000 new nodes which are not part of any way and have no tags. I guess it was an error? Can they be deleted?
Cheers, Jan

Hi,
I found 243438 nodes created by you that have no tags and are not part of any way or relation. Can these nodes be deleted?
Jan

Hallo,
du hast an den Gleisen incline-Tags angebracht, allerdings haben sie keine validen Werte, z.B. ±3.9%. Entweder 3.9% oder -3.9%, aber nicht mit ±.
Kannst du das korrigieren? Woher kommen diese Informationen eigentlich?
Jan