Closed pyrog closed 1 year ago
pelderson
commented
2 years ago I support this idea! For Analysis, I use the URL to the object, no problem there. For PLanner, I often create a short dummy route and use the output link instead of a URL with coördinates. That's clumsy, and with any application update the itinerary link stops working.
vmarc
commented
2 years ago The "position" query parameter has been added to the url of the map pages. The url with the position parameter is updated when panning the map or zooming in or out.
For example:
node page without position parameter (node in center, zoom level 18)
node page with position parameter (same node, but panned and zoomed out)
route page without position parameter (positioned to fit route bounds)
route page with position parameter (same route, but panned and zoomed out)
network page without position parameter (positioned to fit network bounds upon first access, otherwise previous position from browser local storage)
network page with position parameter (same network, but panned and zoomed in)
The planned route is now included in the "plan" query parameter in the planner url.
For e.g. documenting nodes, display a specific place on knooppuntnet… it will be useful to handle coordinates in URL.
Something like WaymarkedTrails:
Or BRouter:
Note:
URL could be without langage, so the map choose the user langage https://knooppuntnet.nl/map/hiking#node=60726576
Even shorter https://knooppuntnet.nl/hiking#node=60726576
This is examples based on other OSM apps. It should be adapted to current analysis URLs:
These URLs are similar to what I am looking for
… but it's not possible to specify the exact view and it's not possible to easily copy/paste the URL from the map