ChillyDL's Comments
| Changeset | When | Comment |
|---|---|---|
| 141656723 | about 2 years ago | The signes refer to the "Legge prov.le n. 10 - 8/5/1990" |
| 141656723 | about 2 years ago | Hello Anonix,
|
| 140652763 | over 2 years ago | Hello Ydel,
So I replaced this in your edit. You might not want to use them any longer.
|
| 140324475 | over 2 years ago | Hallo Paul Kessler,
|
| 117580648 | over 2 years ago | Hallo Shaun das Schaf,
|
| 139189031 | over 2 years ago | 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 | over 2 years ago | I am not too happy with fortification_type=castle either due to its vagueness, but actually, vague this object is.
|
| 139189031 | over 2 years ago | 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 | over 2 years ago | 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. |
| 139175543 | over 2 years ago | Hello jcphal,
I fixed it at a tumulus South East of Pierrefiche today. |
| 138537809 | over 2 years ago | Sorry for the inconvenience. This was a global quality assurance edit, identical for about 120,000 POIs: “site_type=” has been removed where there was a “archaeological_site=” tag with the same value. To track the changes, you can find the documentation here (step 2):
|
| 136654664 | over 2 years ago | Danke!
|
| 136116051 | over 2 years ago | Hello MichaelCollinson, I see you mapped four historic=archaeological_site as site_type=fort. "fort" is not really in use for archaeological sites, so I changed the value to "fortification".
|
| 134765232 | over 2 years ago | Hello Lutalica_1974,
|
| 134483706 | over 2 years ago | Ich glaube, der Verein sollte besser als Node in dem Gebäude getaggt werden und nicht als das Gebäude selbst, oder? |
| 131806091 | almost 3 years ago | All well, let's do it like this.
|
| 131806091 | almost 3 years ago | I did not decide on their status as archaeological sites. They were not tagged as such, but used the deprecated `site_type=industrial` where other objects in the area use `historic=industrial`. The situation in this case was that in the Yorkshire Dales and North Pennines, a tagging as `historic=industrial` is fairly common, introduced by a user about three years ago. It does not have a documented definition, and it doesn't seem fitting well within other "historic" values because it doesn't tell what it actually is/was, like you write. But this being the local scheme – albeit not always consequently in its details –, I used this scheme with 6 objects to keep local consistency. This makes sense to me, but I can undo this with these objects. For a more comfortable view of the changeset, see Achavi:
|
| 131806091 | almost 3 years ago | Hello SomeoneElse,
The tag changes in these 16 objects were mainly the removal of redundant "site_type=" tags, occasionally with other details added like from aerial photography. Since this is not a mass nor a automated edit but simple database quality assurance in a mere dozen cases, I saw no need for a discussion. |
| 133791312 | almost 3 years ago | Hello zolt d,
|
| 133586774 | almost 3 years ago | Hallo cayenne11,
|