SimonPoole's Comments
| Changeset | When | Comment |
|---|---|---|
| 184309757 | BTW see https://community.openstreetmap.org/t/municipality-borders-qa-and-fixes/142018 for the discussion on the topic. |
|
| 184309757 | See https://www.dsantini.it/dbsn/boundaries/#16.2/45.996337/7.908877 (on the swisstopo site you can switch to a number of elevation layers that are fairly clear on where the peak is). As said swisstopo has a dataset of all border points that contains information on if and what kind of marker is at the location. |
|
| 184309757 | ||
| 184314894 |
The nearest border point is at (11818) is located at 45.9959316, 7.9890881 (a bolt). The peak is at 45.995930, 7.989075 a meter away. And yes expecting your complaint I looked at every single one, checked border points, position of the peak etc. (leaving out the arguments on what being "on the border" even means topologically). |
|
| 183351645 | Nur nochmals zum klarstellen, die Gebäuden heissen weder Zürcherstrase noch Zürcher Strasse noch Zürcher-Strasse. Strassennamen Variationen gehören wenn schon an die -Strasse- nicht an die Gebäude. Tendenziell (wie schon wiederholt im Forum besprochen) bin ich dafür für den addr:street Wert in der Adresse den "amtlichen" Namen zu verwenden, wenn der richtig auch als official_name oder alt_name etc auf der Strasse eingetragen ist, sollte mit der Suche alles. funktionieren. |
|
| 183351645 | Die Lösung ist jeweils auf der -Strasse- den official_name zu setzen wenn der Wert in den Adressen vom Wert des name Tags der Strasse abweicht. Es ist sowohl die Lösung mit dem wenigsten Aufwand wie auch der die Realität am besten abbildet (sprich der Name auf dem Strasenschild entspricht nicht dem im GWR, es gibt durchaus Strassen die 3-4 verschiedene Schreibweisen vor Ort haben und irgendwi muss man vernünftig mit dem umgehen). |
|
| 123784932 | In changeset/183428891#map=12/46.9031/7.9344 behoben. |
|
| 183227820 | ||
| 182823202 | Hallo Stefan, nur zur Info: du hast in diesem Changeset aus Versehen einen Knoten der Raron - Niedergestein Grenze verschoben, siehe https://matrix.to/#/!SKrlcOagVFDvtqOndy:matrix.org/$17791748467107wcfMp:matrix.org Habe ich bereits behoben in changeset/182864295#map=13/46.34019/7.80410&layers=N Gruss |
|
| 181522883 | That should have been replaced Magden boundary with swisstopo 2026 boundary geometry. |
|
| 181501409 | PS the other two edits look OK as far as I've checked. |
|
| 181501409 | Hi, in this changeset you changed the municipality boundary of Biel/Bienne to a walking route. I've undone the change, but what did you actually want to map? |
|
| 181254930 | This was Birrwil not Beinwil |
|
| 180266917 | Behoben in changeset/180302859#map=14/46.99641/6.77879 (sprich gerade verwendet). Der Grund lag drin, dass ich da an der falschen Grenze war und deshalb dort nicht weiter gemacht habe (ne Abzweigung verpasst), aber vergessen hatte, dass ich den Ersatz schon wegen einer historischen Grenze (sprich was das es nicht mehr gibt) schon gesplittet hatte. |
|
| 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. |