Hello jptolosa87. At way/525752102 you have tagged `j=..`. What should it be? `name`? #newkey #typo

Hallo Seandebasti. Bei node/1404631447 hast du ein `inscription_note` hinterlassen. Laut https://taginfo.openstreetmap.org/keys/inscription%3Anote würde man hier wohl den Doppelpunkt als Trenner bevorzugen ;-) #newkey

Hello aharvey. You have add a lot new fitness_station subkeys. Had you looked on https://taginfo.openstreetmap.org/keys/fitness_station#values before? Have you documented this new subkeys in the wiki? ;-) #newkey

Hello swimdb. At node/540536383 you have tagged `ewbsite` instead of `website`, right? #newkey #typo

Hello mentaken. At node/5115550443 you have tagged `currency:euro=yes` instead of `currency:EUR=yes`, have a look at https://taginfo.openstreetmap.org/search?q=currency ;-) #newkey #typo

Hello Johnny. At way/525970539 you have added the misspelled `corssing=yes` although there is already a correct `crossing=yes`?! #newkey #typo

Hello Mappernerd. At node/5115501467 you have tagged `Card Factory=driveway`. What is it for? Just a typo? Wrong key? #newkey

Hello NochEinJannik. At node/5115249917 you have tagged `camera: angle`. I think the blank after the colon is unnecessary ;-) #newkey #typo

Hello baradam. At way/526024979 you have tagged some new (so far unkown) keys: `areasqkm`, `fdate`, `ftype`, `permanent_` and `reachcode`. Do we really need this attributes in the database? Also `fcode`, `st_area_sh` and `st_length_`? #newkey

Hallo Protoxenus. Bei way/113498641 hast du `agricultural:maxweight` getaggt. Sollte es nicht umgekehrt sein, siehe https://taginfo.openstreetmap.org/keys/maxweight%3Aagricultural ;-) #newkey

Hello Bharat Raj Bhat. At way/525818579 you have tagged `addr:palce` although there is already `addr:place`? I think you should review it. #newkey #typo

Hello mas90. At way/525887313 you have tagged `aaddr:hamlet` instead of `addr:hamlet`, right? #newkey #typo

Hello Ankesh Sharma. At way/525831926 you have tagged `#CiscoOps=yes` and `#ankessha=yes`. I think this has nothing to do with an OSM Element. Should it be changeset comments instead? #newkey

Hallo Iris L. Wolltest du vielleicht `opening_hours` (osm.wiki/DE:Key:opening_hours) anstelle von `Öffnungszeiten` taggen? ;-) #newkey

Hello cat_crash. In the last days, you have edited way/396714343 a lot. Also you have introduced a lot of new (so far unknown) keys (e.g. additional_amenities, own_parking, pets_allowed, ssync:osm). All this with a "new editor", or what is "Services_OpenStreetMap/0.1" and "Mapk.In"?! #newkey

Hmm, at taginfo addr:housenumber_1 and addr:street_1 would have more than thousand usages, so i think you were right in version #5 of this building. So why did you changed this? The problem is the same, i think no navigationapp would read addr2:* nor addr:.._1.
So, i asked you for the different entrances.

Hmm, gute Frage. `layer` habe ich bisher immer nur so verstanden, dass wenn zwei oder mehr OSM Elemente "übereinanderliegen" zu bestimmen, welches höher und welches tiefer liegt, und zwar unabhängig davon, auf welcher "Ebene" man sich befindet. `level` drückt dann eher den Bezug auf die Bodenfläche bzw. bei Gebäuden des Erdgeschosses aus. Es gäbe aber da ja auch noch osm.wiki/DE:Key:location mit dem Wert "underground", was aber bisher halt nur für Rohre und Leitungen verwendet wird. Deshalb würde ich persönlich und subjektiv immer noch zu `level=-1` tendieren.

Hello lansion. At way/525087297 the chars `b` and `t` at `mbt:scale:uphill`are switched, right? #newkey #typo

Hello SomeoneElse. At way/525251037 there are some typos: `maxsspeed` and `surce:name` ;-) #newkey #typo

Hallo geocodec. Bei way/234539450 wollte wohl das `a` bei `lyer` nicht, oder? Aber sag mal, da es ein building ist, wäre dann nicht eher `level` angebracht? ;-) #newkey #typo