Our great sponsors
-
SurveyJS
Open-Source JSON Form Builder to Create Dynamic Forms Right in Your App. With SurveyJS form UI libraries, you can build and style forms in a fully-integrated drag & drop form builder, render them in your JS app, and store form submission data in any backend, inc. PHP, ASP.NET Core, and Node.js.
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
OK, the GitHub page spells it out better [0].
> Self-hostable maps stack, powered by OpenStreetMap.
In addition to listing out some of the required specs (for a localized area) [1]:
> ... generation ... needs ... 8GB of memory ... running ... around 4GB ...
> ... recommend ... 50GB ... disk space
[0] https://github.com/headwaymaps/headway
[1] https://github.com/headwaymaps/headway#system-requirements
What problems did you face with cycling directions?
Regarding the route shapes I can only guess: we use an encoded polyline as default for a very compact response. You can either disable this or use our JavaScript library, or there is a new UI https://github.com/graphhopper/graphhopper-maps
Regarding routing parameters: our custom_model approach is more powerful than simple parameters and still fairly trivially too: https://www.graphhopper.com/blog/2020/05/31/examples-for-cus... See e.g. the several bike examples and see how to get an world wide instance up and running: https://www.graphhopper.com/blog/2022/06/27/host-your-own-wo...
In recent master you can additionally control how elevation influences your route (e.g. prefer or avoid them entirely or steep sections or similar)
I’d recommend taking a look at Maplibre GL JS[0], which is a fully open source map library. It was forked from Mapbox GL JS just before licence change, therefore it’s also fully compatible with the style spec etc.
It’s also actively maintained and has a strong community behind it.
We're in the same boat using Mapbox, we've been debating leaving for the OpenStreetMaps container since we only use them for static images and map display. https://github.com/Overv/openstreetmap-tile-server
Our bill last year was $80k and honestly its right on the cusp of being worth the effort to switch.
I built something along the same lines many years ago, with routing but not geocoding.
https://github.com/stevage/saltymill
Yeah, it's a pain in the arse getting all the bits together. And I wasn't attempting full planet scale.
I'm using OSM Liberty [1] so as far as I know I should be just tracking upstream with most of these issues, but I think some of them might actually be introduced by planetiler [2]. Thanks for giving it such a detailed look though.
I'm using OSM Liberty [1] so as far as I know I should be just tracking upstream with most of these issues, but I think some of them might actually be introduced by planetiler [2]. Thanks for giving it such a detailed look though.