mueschel's Comments
| 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:
- wrong 'name' tags. This tag is just for an actual name, not for descriptions - mispelled keys like:
- no link to the mandatory documentation of the import
Please read and follow our import guidelines:
|
| 135959366 | over 2 years ago | This import created a large amount of data quality issues. E.g.: - messed up geometries like this:
- wrong 'name' tags. This tag is just for an actual name, not for descriptions - mispelled keys like:
- no link to the mandatory documentation of the import
Please read and follow our import 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,
|
| 135789681 | over 2 years ago | Hi,
|
| 135841218 | over 2 years ago | Welcome to OSM!
Please use only tags that are described in the OSM Wiki or are available in the presets of your editor.
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.
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,
In OSM we have to follow a couple of rules how imports of external data need to be done. See
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,
There was a very recent rework of the parking tag scheme for highways:
parking:right:fee is the recommended tag since a few months. |
| 135792094 | over 2 years ago | Hi,
|
| 135778498 | over 2 years ago | Hallo,
|
| 135794189 | over 2 years ago | This import created a large amount of data quality issues. E.g.: - messed up geometries like this:
- wrong 'name' tags. This tag is just for an actual name, not for descriptions - misspelled keys like:
- no link to the mandatory documentation of the import
Please read and follow our import guidelines:
|
| 135726827 | over 2 years ago | Hi,
|
| 135722280 | over 2 years ago | Hi & welcome to OSM!
This might be a good description of the object,
|
| 135755578 | over 2 years ago | Hi,
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:
- wrong 'name' tags. This tag is just for an actual name, not for descriptions - mispelled keys like:
- no link to the mandatory documentation of the import
Please read and follow our import guidelines:
|
| 135597357 | over 2 years ago | This import created a large amount of data quality issues. E.g.: - messed up geometries like this:
- wrong 'name' tags. This tag is just for an actual name, not for descriptions - mispelled keys like:
- no link to the mandatory documentation of the import
Please read and follow our import guidelines:
|