mjaschen / brouter-routingdata-builder

One-stop solution to create routing data files (.rd5) for BRouter.

Marcus Jaschen

👷 Keeping things running at MTB-News.de, Rennrad-News.de, eMTB-News.de and Nimms-Rad.de. Used the last 20+ years to accumulate lots of knowledge of PHP, web technologies, and on how to run Linux servers.

🚵🏻 Riding mountainbikes, roadbikes, and gravelbikes; not necessarily in that order.

🪑 Currently in the process of learning the art of woodworking.

📷️ Creating memories using cameras.

🗺 Hosting bikerouter.de – the best bicycle routing you'll find on this planet. Based on abrensch/brouter and nrenner/brouter-web.

Get in Touch

🔗 marcusjaschen.com

brouter-routingdata-builder's Issues

Update Dockerfile to new build process

BRouter is built with Gradle now. The Dockerfile has to be adjusted to that.

Problem including SRTM-elevation data in generated segment files

Dear all,

I set up the whole segment building process as described in the readme-file. Which worked overall very well.

I am only facing one minor issue: There are no more elevation data within the new segment files. The elevation value is set to -8192 for all way points.

I already modified the PosUnifier.java file for some debugging. The requested filename is correct, I also have the exact same file name in the /tank/brouter/srtm folder. The srtm-files are stored as a zip including .asc data. So this should be as required for the build process.

Are there any suggestions where the underlying problem could be and how a solution could look like?

I am working on Ubuntu 22.04.

Bests and many thanks in advance,
Matthias

Adjust logic to changed PBF parsing behaviour

see

• abrensch/brouter@14b1ece
• abrensch/brouter#555

Until fixed, routing data builder is pinned to abrensch/brouter@11a9843