SimonPoole's Comments
| Changeset | When | Comment |
|---|---|---|
| 179706364 | Hi, while acknowledging that Arpitan/Francoprovençal can be spoken in these regions, it would seem unlikely that you would know all these names 1st hand knowledge. Could you please disclose from where or how you are sourcing these names? |
|
| 179795628 | gain the boundary doesn't exist anymore and has zero priority. Fixed anyway, the issue was the old boundary being geometrically incompatible with the current correct one. There is and was a real issue with the lake itself in that part of the water area was tagged (not glued) on the admin boundaries, I've redrawn that as a fix for the municipalities for which we've fixed the admin boundaries of, but it is a latent problem for Neuchâtel itself. |
|
| 179779065 | Postal code boundaries are not useful in Switzerland and in general we have not mapped them. Breakage of this specific one was not unexpected as the surrounding municipality were very broken (high priority to fix) and I haven't arranged a current source for it yet. |
|
| 179740482 | Neither boundary actually exists anymore since many years and should simply be deleted, or at least the misleading tags removed. |
|
| 179762625 | Again a typo this was actually work on Mettembert. |
|
| 179366575 | You are jumping to conclusions. Yes, the person doing the import added a small number of (unnamed) peaks at the time. This is weird as we had no such data and the dataset didn't include it (the relevant POI/peak data from swisstopo wasn't open data back then). Some of these peaks were later edited and relocated. The rest were added much later, without reference to topology or the border, and the simple explanation, applying Occam’s razor, of why they were joined to border is accidental gluing. |
|
| 179366575 | Yes this was on purpose, as ungluing from all other non-border elements (for obvious reasons).. The border was originally imported from swisstopo (the same source as from where we are updating it now) with no reference to peaks etc. While legally, as in the contract between IT and CH, it might be defined with reference to peaks we would need for the peaks to be at the location used when that happened. In any case it is clear that the current location of the peaks in OSM doesn't directly define the border so it doesn't make sense to include them. |
|
| 179604216 | Leimbach naturally. |
|
| 178739239 | Because the relevant tags were empty. |
|
| 178880696 | Genau, und deshalb hat es nichts mit den administrativen Grenzen zu tun. Nochmals: ob Wasserflächen zu dem Gemeindegebiet dazu gehört oder nicht wird vom jeweiligen Kanton bestimmt. Aktuell ist es so, dass im Kanton Thurgau sie nicht dazu gehören. Wie man auch leicht and den Nachbargemeinden sieht, daran halten sich sowohl die swisstopo wie auch das BfS, und auch wir. |
|
| 178880696 | PS: der Zonenplan ist von 2019. |
|
| 178880696 | Das offensichtliche Problem, dass du auf eine Quelle verweist dass du im Changeset nicht angegeben hast, mal ausser Acht gelassen: du kannst dich gerne mit swisstopo, das BfS und den Kanton Thurgau streiten., aber aktuell sind die alle der Meinung, dass du nicht recht hast. |
|
| 178880696 | Dieses Changeset vermischt viel zu viel verschiedene Sachen speziell wenn du gleichzeitig an Grenzen arbeitest (wie dir auch schon gesagt worden ist), und macht es schwierig genau nachzuvollziehen was du geändert hast. So oder so, du hast die Grenzen von Gottlieben verschlimmbessert, der Rheinanteil gehört nicht zur Gemeinde, die Grenze verläuft am Ufer entlang (wie du leicht aus den verwendeten Daten von swisstopo sehen kannst). |
|
| 177454566 | Es gibt keine Anzeichen dafür, dass der Inhalt von standseilbahnen.ch offene Daten sind, falls du eine Erlaubnis hast sie zu nutzen dokumentiere das bitte. |
|
| 177500898 | Ohne vorherige Diskussion so grossflächige Änderungen zu machen ist ein Unding. Genau so wie dein vorheriger Edit. Bei diesem ist besonders schlimm, dass man die einzelnen Änderungen auch nicht nachvollziehen kann und wieso du sie jeweils gemacht hast, da viel zu viel Gemeinden betroffen sind. Für den ursprünglichen Import wurden die Grenzverläufe vereinfacht deshalb sind so oder so Abweichungen von swisstopos Datensatz zu erwarten. |
|
| 177441447 | While the licence situation is not totally clear, assuming it is the standard swisstopo open data licence you need to provide attribution (you did read the licence before you copied the data?), and our agreement with swisstopo in such cases is that we provide it on the contributors page. |
|
| 177441447 | PS: you would need to add the specific source to the contributors page if we do decide to keep them. |
|
| 177441447 | Please refrain from adding more of these routes until the community has come to a consensus. Thank you. See https://community.openstreetmap.org/t/ski-routes-import/138798 for the discussion. |
|
| 176697614 | ||
| 176697614 | Two small things: the bfs number should be 2056 and the postal code is likely wrong too (shouldn't be set). Moutier got a new number too. |