OpenStreetMap logo OpenStreetMap

Changeset When Comment
135953851 over 2 years ago

This import created a large amount of data quality issues. E.g.:

- messed up geometries like this:
way/1160297576

- wrong 'name' tags. This tag is just for an actual name, not for descriptions

- mispelled keys like:
Accessibility button
Door Handle
Floor Type
Floor type
Note
Pull/Push
Push/Pull
Reference
door type
fLOOR TYPE
push/pull
reference
solid

- no link to the mandatory documentation of the import
- no proper source of the data

Please read and follow our import guidelines:
osm.wiki/Import/Guidelines
Please read and follow our Organized Editing guidelines:
https://wiki.osmfoundation.org/wiki/Organised_Editing_Guidelines

135959366 over 2 years ago

This import created a large amount of data quality issues. E.g.:

- messed up geometries like this:
way/1160297576

- wrong 'name' tags. This tag is just for an actual name, not for descriptions

- mispelled keys like:
Accessibility button
Door Handle
Floor Type
Floor type
Note
Pull/Push
Push/Pull
Reference
door type
fLOOR TYPE
push/pull
reference
solid

- no link to the mandatory documentation of the import
- no proper source of the data

Please read and follow our import guidelines:
osm.wiki/Import/Guidelines
Please read and follow our Organized Editing guidelines:
https://wiki.osmfoundation.org/wiki/Organised_Editing_Guidelines

136011609 over 2 years ago

You're right, somebody changed the recommended tag a month ago. But this one is not used anywhere, compared to the old 'repair=yes' that is used 720 times on shop=tyres. 'service:vehicle:tyres_repair' is also used, but only 120 times.

135830742 over 2 years ago

Hi,
the 'indicates' and 'text' tags on these route_markers are not used in other places. I suggest to use the same syntax as on destination signs:
direction_east and similar:
direction_north=*

135789681 over 2 years ago

Hi,
the tag 'tree_ref' is not used in any other place. You can use a plain 'ref' tag - it's obvious that it's the ref of a tree because of the natural tag.

135841218 over 2 years ago

Welcome to OSM!
I found tags like
warehouse3 = yes
admin = yes
on several objects.

Please use only tags that are described in the OSM Wiki or are available in the presets of your editor.
This is necessary to make sure that every other user can understand the data.

As the most important tag, these objects should have a building = * to describe what kind of building they are.

135828454 over 2 years ago

I deleted the nodes.
It seems an import of these nodes is not necessary at all. Those that I checked already exist in OSM.

If there are some missing, the best place is to start with an import documentation as described in the guidelines.

135828454 over 2 years ago

Welcome to OSM,
You uploaded many nodes without proper tagging.

In OSM we have to follow a couple of rules how imports of external data need to be done. See
osm.wiki/Import/Guidelines

Please read and follow these guidelines. For now I suggest to revert this changeset.

135819438 over 2 years ago

My mistake is fixed, thanks for pointing it out.

135819438 over 2 years ago

Hi,
I edited these ways because the side of parking was not tagged correctly.

There was a very recent rework of the parking tag scheme for highways:
osm.wiki/Street_parking

parking:right:fee is the recommended tag since a few months.

135792094 over 2 years ago

Hi,
could you check the 'ref' of this relation, something went wrong there:
relation/15819532

135778498 over 2 years ago

Hallo,
einer dieser Wege hat einige fremde Tags und eine Relation für das Naturschutzgebiet fehlt auch.
Kannst du da noch nachbessern?

135794189 over 2 years ago

This import created a large amount of data quality issues. E.g.:

- messed up geometries like this:
way/1160297576

- wrong 'name' tags. This tag is just for an actual name, not for descriptions

- misspelled keys like:
Accessibility button
Door Handle
Floor Type
Floor type
Note
Pull/Push
Push/Pull
Reference
door type
fLOOR TYPE
push
push/pull
reference
solid

- no link to the mandatory documentation of the import
- no proper source of the data

Please read and follow our import guidelines:
osm.wiki/Import/Guidelines
Please read and follow our Organized Editing guidelines:
https://wiki.osmfoundation.org/wiki/Organised_Editing_Guidelines

135726827 over 2 years ago

Hi,
what do these ways represent? They don't have any common tag.
Please check the wiki and the presets in the editors for common tagging schemes.

135722280 over 2 years ago

Hi & welcome to OSM!
I noticed that you added several tags to schools that are not used by other people.
For example:
Estudiante
Padres Procesadores
Personal Obrero
administrativo
docentes

This might be a good description of the object,
but is not usable in OSM - no software can understand
it.
Please have a look to the documented tags in the wiki and use only these - only well-defined tags can be understood by other mappers and can be shown on maps and in applications.

135755578 over 2 years ago

Hi,
you uploaded many ways without any proper tag, e.g.
way/1169137738

What is the purpose of these ways, what is the source of this data?

135642771 over 2 years ago

I reverted this changeset and all its uploaded nodes that should never have appeared in OSM. Grab needs to improve their QA routines, including misspellings of common tags!

135601000 over 2 years ago

I reverted this changeset and all its uploaded nodes that should never appear in OSM. Grab needs to improve their QA routines, including misspellings of common tags!

135596392 over 2 years ago

This import created a large amount of data quality issues. E.g.:

- messed up geometries like this:
way/1160297576

- wrong 'name' tags. This tag is just for an actual name, not for descriptions

- mispelled keys like:
Accessibility button
Door Handle
Floor Type
Floor type
Note
Pull/Push
Push/Pull
Reference
door type
fLOOR TYPE
push/pull
reference
solid

- no link to the mandatory documentation of the import
- no proper source of the data

Please read and follow our import guidelines:
osm.wiki/Import/Guidelines
Please read and follow our Organized Editing guidelines:
https://wiki.osmfoundation.org/wiki/Organised_Editing_Guidelines

135597357 over 2 years ago

This import created a large amount of data quality issues. E.g.:

- messed up geometries like this:
way/1160297576

- wrong 'name' tags. This tag is just for an actual name, not for descriptions

- mispelled keys like:
Accessibility button
Door Handle
Floor Type
Floor type
Note
Pull/Push
Push/Pull
Reference
door type
fLOOR TYPE
push/pull
reference
solid

- no link to the mandatory documentation of the import
- no proper source of the data

Please read and follow our import guidelines:
osm.wiki/Import/Guidelines
Please read and follow our Organized Editing guidelines:
https://wiki.osmfoundation.org/wiki/Organised_Editing_Guidelines