Over the past week I built a project to let people self-host an entire maps stack so they don't have to send data to the big G. Right now it includes a base map, geocoder and directions server. Currently only bicycle directions are supported, and I'm only hosting tiles for Seattle because I'm unemployed and can't afford to host data for the whole planet. Check it out!
https://github.com/ellenhp/headway
Ultimately I'd like to really focus on transit routing (not implemented) but I'll probably throw a driving mode in there too.
Compared to self-hosting an existing project, it is much easier to bring up a new Headway instance:
`make Seattle.up` will bring up a new instance on 8080.
See https://www.openstreetmap.org/copyright
ellenhp: Why not start with the attribution toggled open, or some alternative way to highlight the map data's provenance?
edit: Attribution is now shown toggled open at page load, resolving this issue.
Currently travelling so will investigate further when somewhere appropriate (may be cached on my phone, something specific to mobile web, etc).
For a single solution to geocoding and autocompletion, there's Pelias: https://pelias.io/
OTP is actually really fantastic and it might be a better choice than valhalla's multimodal especially if it can handle GTFS realtime. Thank you for the reminder that it exists!!!
would love to have IPv6 support. It should be on default by now, if there aren't any issues hindering support.
[1] https://github.com/onthegomap/planetiler
(Your build example says the tiles are 99GB, and their normal tier is $0.023/GB)
I guess the part of the cost that people actually care about is the bandwidth. How do you suggest dealing with that part of the problem?
Deleted Comment
Google maps, organic maps, osmand+, I still have to double check what crazy suggestion it has made. Single track gravel roads over a perfectly safe alternative a lot of the time.
I have the avoid unpaved roads options ticked... it would be great to have some machine learning magic take a look at a street view picture and decide if there is grass growing up the middle of the road and add a weighted chance of needing to reverse 200 metres when there is other traffic
I haven’t looked into the code yet, but I’m especially interested in the routing bit.
As a cyclist I’m almost always disappointed by google, apple, and Valhalla. The cycling directions from these systems are usually better than nothing, but almost always have one or two dangerous or ridiculous segments.
I’ve never tried to solve it myself, only day dreamed.
Any insights?
Getting bike routing right is really challenging, partly because often there genuinely isn’t a good route, and partly because standards and infrastructure (and OSM mapping practice!) differ from country to country. I love the challenge and the feedback from users when it works well, but it’s a massive task.
It’s anecdotal, but definitely better than what I’m seeing with Val halla / google / apple.
Can you share any details about how your route finding works?
Have you tried the OSRM bike config? (The one you find in https://github.com/Project-OSRM/osrm-backend/blob/master/pro...)
As for Street View, while I haven't looked into getting it into OsmAnd, Mapillary has an official plugin and while its coverage isn't really comparable, it does often have newer images and often saves me an app switch if I just need to see anything in a general area.
I did know about Mapillary. I'll check if its coverage got better.
What's your use case?
Navigation when driving my car: not every month, not many times per year. After all I know the roads, I don't need somebody to tell me where to turn. When I do, it's usually the last km, when the chances to miss an intersection are higher. On main roads or close to home, not so much.