mueschel's Comments
| Changeset | When | Comment |
|---|---|---|
| 153745120 | I use Taginfo to create a list of new keys - many of these are spelling mistakes. And it happens that here we got the first and only "departures_2" in the database. |
|
| 153745120 |
You're right that the separator should be a ; (I fix it in a minute), and the Su/PH statement should also be last to not be overwritten by school holidays. The syntax with a slash is documented in the formal specification:
|
|
| 153713086 | Hallo,
|
|
| 153586117 | Thanks for the explanation! On top of your edit I also added opening hours and access tags to mark the relevant period. |
|
| 153658280 | Hi,
|
|
| 153617070 | That's not about hierarchy between contributors, but hierarchy between tags: Major tags vs. minor information: Semicolons are bad in major tags (e.g. building or amenity), but are very well suited for minor and diverse additional information. Existing tags vs. new tags:
|
|
| 153586117 | Hi,
|
|
| 153617070 | You asked about this last week in the forums. Kovoschiz gave a long explanation how a single "charge" tag is the common way and too detailed price information on hotels is not wanted (check also all the up votes those posts got!). |
|
| 153556699 | Hi,
1) Die übliche Reihenfolge im Key ist
2) "bus" kann nicht hinter dem @ stehen - Fahrzeugarten kommen direkt in den Key: maxweight:backward:conditional = none @ destination
|
|
| 153445561 | That happens to many people. In this case it could have been something akin to a training area so I had to ask. |
|
| 153445561 | Hi,
|
|
| 153440266 | Hi,
date_visite
They all should be "check_date" or "survey:date". You also use "light_source" which should be "lit". |
|
| 153357742 | Hi,
|
|
| 153387228 | access=psv is not an official tag.
Do you know which charging system they use? Maybe we can add a socket tag as well. |
|
| 153387228 | Hi,
|
|
| 153222441 | The objects are still there. E.g. this
|
|
| 153261047 | Hi,
|
|
| 153247685 | hi,
|
|
| 153257040 | Hi,
|
|
| 153242149 | Hallo,
|