hholzgra / maposmatic-hiking-atlas

Create a local hiking atlas booklet using the MapOSMatic API

maposmatic-hiking-atlas

Create a local hiking atlas booklet using the MapOSMatic render API, OverpassAPI queries, and GPX track information for hiking route relations from WayMarkedTrails.

Demo output PDF

For now this is just a quick and dirty proof of concept tool to test the render API, it works on my computer, and your mileage may vary.

Prerequisites:

• PHP >= 7.x
• Pear package HttpRequest2
• LaTex with pdfpages package
• only tested on Linux

To run this:

• look up the OSM relation ID for your citys admin boundary polygon
• edit the header part of the wanderatlas.php file
• run php wanderatlas.php
• wait ... this will roughly need one minute per route if the server is otherwise idle
• find the result in my-atlas.pdf

maposmatic-hiking-atlas's Issues

WayMarkedTrails GPX track downloads are broken

The URL for downloading GPX data for a route has changed, it is now

https://hiking.waymarkedtrails.org/api/v1/details/relation/...relation-id.../geometry/gpx

Use pdfLaTeX and pdfpages package to stitch together the atlas

Right now the individual pages just get stitched together using the pdfunite command, which gives only minimal control over the result.

What I'd rather have is a document that at the very minimum contains:

• page numbers
• a table-of-contents page

and maybe later also, as a separate page per map:

• route description text extracted from OSM hiking relaions
• a height profile of the route
• info about POIs along the way, like restaurants ...

Do not wait for individual requests, file all in parallel

There is no need to wait for each individual render request, we can submit them all right away as there are no cross-dependencies and then wait until all have completed (or actually just wait for the last one) before stitching them all together

Make paper size configurable

Right now Din A4 paper size is hard coded into the script at several places, this should be configurable to at least also allow for "Letter" format ...

Alternative frontend(s)

Right now it is required to edit the script to configure the atlas, and the only true choice is that of a city name and its administrative boundary OSM id.

A more interactive frontend should allow to:

• select a city name

• OR: select a bounding box

• OR: a center point and area dimension

• select or exclude found routes

• add some extra meta data to e.g. put on the front page