ChillyDL's Comments
| Changeset | When | Comment |
|---|---|---|
| 147581936 | what exactly did you do where? The scope of your mass edit is much wider than Germany. Discussion is one thing, but where is your documentation? |
|
| 146761711 | Hello Michael Collinson,
I know there is more to it and I am sure you have reason to not put those object under historic=archaeological_site to begin with. But would you agree to use the archaeological_site=industrial or =building, repectively, which have come to replace site_type= and are widely in use? |
|
| 145743834 | Interessant mit der Ausnahmeregelung. Das erlaubte Verlassen der Wege ist also kein Indiz.
Ich setzte die NSG-Grenze wieder zurück. Danke für die Hinweise! |
|
| 146163293 | Hallo Yorvik Prestigitator,
|
|
| 145743834 | Ja, das ist widersprüchlich. Die Karten auf den Infotafeln vor Ort geben die Grenzen des Naturschutzgebietes so an, wie ich sie wegen der On-the-Ground-Regel eingetragen habe. Siehe z. B. hier:
Für diese engeren Grenzen spricht auch, dass offensichtlich die Regeln für Naturschutzgebiete wie "Wege nicht verlassen" z. B. auf dem Sandberg nicht gelten, wie man an Informationstafeln fern der Wege und auch an dem Foto auf der Website des Berliner Senats sieht, das du verlinkt hast. |
|
| 145728782 | Laut Website des Einkaufszentrums ist der Laden nach wie vor da:
|
|
| 145728782 | Hallo,
|
|
| 145508035 | Hallo ma-rt-in,
|
|
| 144469743 | I am suprised, too. McDonalds themselves are not aware of WiFi in all their branches: "Do All McDonald's Have Free Wi-Fi?
Regarding Germany, Telekom, who privide the WiFi at McDonalds, specify: "Die schnellen Internetzugriffe per WLAN stehen Ihnen [...] flächendeckend an fast allen [!] Raststätten der Autobahn Tank & Rast Holding GmbH oder McDonald's Restaurants [!] [...] zur Verfügung."
Telekom also only speaks of restaurants, not of the many Mc-Donald's take-aways. |
|
| 144050831 | Hallo puma515,
|
|
| 143966704 | lift_gate. Danke. Habe ich geändert.
|
|
| 141656723 | The signes refer to the "Legge prov.le n. 10 - 8/5/1990" |
|
| 141656723 | Hello Anonix,
|
|
| 140652763 | Hello Ydel,
So I replaced this in your edit. You might not want to use them any longer.
|
|
| 140324475 | Hallo Paul Kessler,
|
|
| 117580648 | Hallo Shaun das Schaf,
|
|
| 139189031 | We seem to have slightly different views on what is an improvement. Good that we can agree on adding fortification_type=castle to the dozen of archaeological_site=fortification that I converted from archaeological_site=castle two days ago.
|
|
| 139189031 | I am not too happy with fortification_type=castle either due to its vagueness, but actually, vague this object is.
|
|
| 139189031 | I can see how annoying you must find it to interfere with what you would like your map to look like. It is just that, in any case, this is a no longer visible, archaeological site, and it should be tagged with the according tags for such. archaeological_site=castle is not helpful, unspecific as it is. I do not favour its introduction – or expansion of use beyond the odd occurrence, if you want so. |
|
| 139189031 | Hello,
Since nothing is left of this castle to be seen (aerial imagery shows a plain meadow), mapping may be questionable in the first place, but if mapped, the tagging scheme needs to be under historic=archaeological_site. Given that the structure has completely disappeared and given the relatively short time that castles in the other meaning of the term as non-defensive “stately home” have existed, it is not plausible that the former structure has been anything than a defensive fortification. So I specified this, not removing information, but adding information by being more precise. There isn’t yet a clearly established tagging scheme for former, now archaeological stately homes, palaces, and the like. Because of the ambiguity of the term, it should certainly not be archaeological_site=castle. |