OpenStreetMap logo OpenStreetMap

Changeset When Comment
154675681 over 1 year ago

Hi, you uploaded a few objects like this one with only foreign tags, could you check that?
way/1304965538

154497866 over 1 year ago

So einen ehemaligen Damm kann man als Linie in OSM eintragen, mit dem Tag
historic:waterway=dam

Alle anderen Tags sollten entfernt werden - heutzutage hat das Überbleibsel ja nichts mehr mit einem tatsächlich nutzbaren Damm zu tun.

154563616 over 1 year ago

Please watch out for the correct spelling of tags. It's 'smoothness', not 'smothness'

154385647 over 1 year ago

Hi,
please check the tags you added. "addr:street_address" is not used by anybody else.

154477990 over 1 year ago

Hi,
please check the name tag on this relation:
relation/17879807

154497866 over 1 year ago

Hallo,
du benutzt hier Tags, die es sonst nicht gibt,
pond_system = dam
water = dam

Kannst du erklaeren, was du da erfasst hast, damit wir passende Tags finden koennen?

154500283 over 1 year ago

Hi,
please watch out for the correct spelling of tags. I correct various spelling mistakes in your ref:FR:DREAL / seuil:FR:DREAL tags almost every day.

154466206 over 1 year ago

Hi,
welcome to OSM!
You added many tags here that are not used in any other place. In OSM we have to use the tags that are defined in the wiki or available as presets in the editor - only these can be understood by other mappers and applications.
Could you check the objects you edited and change the tagging?

You're always welcome to ask in the forums in case you need help!

154417881 over 1 year ago

I'd use only one of the two tagging schemes. It's quite obvious that there are two "competing" schemes to every data user - and if there really will be some consensus on tagging, changing the existing objects should not be a big problem.

154449623 over 1 year ago

service:vehicle:tyres and service:vehicle:tyres_repair are different things.
Your edits produced many strange things, e.g. places that repair "oil" or "parts" and tags with spelling mistakes.
Such a change needs proper planning, discussion and approval.

154462746 over 1 year ago

Could you please point us to the mandatory documentation of this import? There are many issues with the tagging scheme that should have been solved beforehand.
E.g. these tags shouldn't be in OSM in their current form:

Latitude = 40.805479
LinkNYC_Site_ID = mn-09-120409
Longitude = -73.965529
addr:housenumber = 2880
addr:postcode = 10025
addr:street = BROADWAY
amenity = wifi;telephone;device_charging_station
wifi = LinkNYC Free Public Wi-Fi

osm.wiki/Import/Guidelines

154442292 over 1 year ago

Please check these objects. They all got a strange tag "srcName", that looks like it shouldn't be in OSM.

154445738 over 1 year ago

Hi,
why did you delete the information that these shops repair Apple products?

154449623 over 1 year ago

Could you point us to the discussion and approval of this large-scale edit of tags? You invented a couple of new tags here, e.g. tyres:repair. What is wrong with the established tags like service:vehicle:tyres_repair?

154417881 over 1 year ago

Hi,
you added par and length information twice here. There's no need to add
disk_golf:length and disk_golf:par - the normal dist and par tags are fully sufficient. The context makes it clear that it's about disk golf.

154399214 over 1 year ago

Hi,
please check your recent edits - there are about 100 "raiway:signal:direction" instead of "railway:signal:direction"

154402721 over 1 year ago

Das kann man sicher ergänzen, aber der eigentlich entscheidende Punkt ist ja, dass man eine App braucht um die Maschine zu bedienen. Ob das dann im Hintergrund über Bluetooth oder Internet läuft ist ja zweitrangig.

154307062 over 1 year ago

Hi,
could you explain the meaning of "maxspeed:tracks"? Is this a misspelling of "trucks"?

154325583 over 1 year ago

Hi,
could you check the city_limit signs like this one? They got a strange tag:
node/47625044

154252483 over 1 year ago

Hi,
this large area you uploaded doesn't have any valid tags. It also seems to be a copy of a boundary that is already in OSM. Could you check and fix this?