Changeset: 119118784
Fix Niedersachsen Wadden Sea national park boundary based on exact coordinates/shapes defined in law
Closed by JeroenvanderGun
Tags
created_by | JOSM/1.5 (18387 nl) |
---|---|
source | https://www.voris.niedersachsen.de/jportal/?quelle=jlink&query=WattenmeerNatPG+ND&psml=bsvorisprod.psml&max=true&aiz=true |
Discussion
-
Comment from Hb-
Please see §3 of the law. The park boundary is defined on the map first. The German Digital Maps have centimeter accuracy. The maps reflect geodetic points (Grenzpunkte/-steine).
The coordinates are secondary information. They only have meter accuracy.
Example: For point 135 From https://www.umweltkarten-niedersachsen.de/Download_OE/GSG/NPW_Aussengrenze.zip the shape file delivers point 135 at 5930447.934, 448733.311. This is a geodetic point on the boundary of Landkreis Wesermarsch. The Anlage of the law has 5930448, 448733.
This edit used the nautic coordinates E08° 13,605' N53° 31,227' and placed the node at 5930447.011, 448733.526.So the concept of this edit does not reflect the law.
-
Comment from JeroenvanderGun
The original point 135 before this edit was about 16 meters off, my edit reduced the error to less than 1 meter (assuming my QGIS correctly converts your shapefile to WGS84).
Feel free to further improve the coordinates of the points (if the license is compatible with OSM licensing or specific permission has been obtained or copyright exceptions apply).
My edit added reference numbers to all edited nodes, so that should make further editing easier.
-
Comment from Hb-
The edit was indeed an improvement. Referencng the Number to each node is also good. But noting the law as source seems difficult, according to the reasons given before.
In the later edit https://www.openstreetmap.org/changeset/119123573 the nodes 20 to 23 seem to be completely misplaced near Wilhelmshaven. They should be South of Borkum.
-
Comment from JeroenvanderGun
These nodes 20-23 are from Anlage 6 (the part of the national park excluded from the UNESCO world heritage), which unfortunately has separate numbering.
Ways (11)
- 267577187, v8
254959442, v10254959443, v7254959446, v15254959447, v11254959448, v8267631257, v3267646990, v91016517398, v31036621247, v21042071324, v2
Relations (2)
Nodes (1-20 of 37)
- 1
- 2
- 40 (9623970599), v1
- 13 (9623970600), v1
- 11 (2607238152), v3
- 10 (2607238154), v3
- 12 (2607238156), v2
- 14 (2607238198), v2
- 15 (2607238208), v2
- 16 (2607238236), v2
- 17 (2607238244), v2
- 135 (2607238320), v3
- 24 (2607238375), v2
- 136 (2607238381), v3
- 25 (2607238449), v2
- 26 (2607238469), v2
- 27 (2607238487), v5
- 140 (2607238510), v3
- 139 (2607238546), v2
- 137 (2607238559), v3
- 56 (2607238632), v2
- 28 (2607238673), v4
Welcome to OpenStreetMap!
OpenStreetMap is a map of the world, created by people like you and free to use under an open license.
Hosting is supported by Fastly, OSMF corporate members, and other partners.
https://openstreetmap.org/copyright | https://openstreetmap.org |
Copyright OpenStreetMap and contributors, under an open license |