Comment by jameal
1 year ago
Looks interesting! Unfortunately doesn't seem to let me add more than one point on my route. In the console I see
`Error fetching route from Graphhopper Error: Network response was not ok`
I tried a couple times and got this in the U.S. In Europe I picked a couple random points and it worked fine.
I'm getting the same, it's a 400 response.
So far, I've only generated the graph for Europe(using Graphhopper). Even just Europe required 128GB of RAM and around 10 hours of computation time (the entire planet would likely need 384GB of RAM). I plan to add North America on a separate Docker container soon though. I started with Europe because I’m familiar with some of the bike trails here, which makes it easier for me to check if the routing makes sense.
> the entire planet would likely need 384GB of RAM
Unlikely. Even with turn costs enabled 256GB (or less) are sufficient. You could also try to disable CH as for bike often no long routes are required (you could disable them). Here we have written down a few more details: https://www.graphhopper.com/blog/2022/06/27/host-your-own-wo...
5 replies →
You should at least add some kind of error handling so I'm not sitting there like a dope clicking over and over with no result.
1 reply →
Cool project, best of luck! Agree with the other commenter that some kind of error handling or warning re: outside-of-EU availability.