Hot answers tagged osrm
Solved by himself : Adding ?compression=false to the request query will output unencoded data. A proof that smeagol and gollum can work together. ( what is compression, my precious? )
Same problem - instructions on OSRM github are incomplete. I've fixed it by: sudo apt-get install libosmpbf-dev
Instead of avoiding compression you can fix the real problem. If you have lots of points (which is the case for routing) and you send them as normal json numbers you have a big response and a problem. To reduce that size one could embed a binary form of the point list into the json. OSRM is doing this via googles algorithm, of course there are other ...
You try to use the unstable version from the develop branch. We recently removed the dependency for OSMPBF.
The costs you mention are from the Workshop (not the documentation and they are pretty much arbitrary. They were just set like this to give an example how to modify costs depending on road classes. OSRM defines its "costs" in the profile files in the profiles directory, for example for car: ...
OSRM does not use a database, but tuned data structure that are sometimes (falsely) called index. The process to go from raw OSM data to actual query processing is a multi-step process, i.e. extract, prepare, route. As Mapperz said, it is possible to query a SQL data base for additional data during the extraction process. To query OSRM for routes from your ...
Switch to a 64 bit kernel installation of Linux and your problems should be fixed.
Question A: How many requests can I send until I get blocked? There is not a fixed limit. It is recommended to use a valid user-agent that you register before hand. This way it is less likely to get blocked. So write an Email to OSRM (infoATproject-osrm.org), explain them what you want to do, and give them the name of your user-agent. In your python code ...
Only top voted, non community-wiki answers of a minimum length are eligible