It's reserved for future use, see https://github.com/Project-OSRM/osrm-backend/issues/2512
Yes, at the moment you have to start one server per profile and dispatch with a HTTP server in front of it. If you use e.g. the node-osrm bindings [1] you can build a single express/koa HTTP server doing this dispatching internally. Feel free to edit the Wiki if you stumble over such issues :) Cheers, Daniel J H 1 https://github.com/Project-OSRM/node-osrm On Wed, Mar 8, 2017 at 3:35 PM, Jäger, Frank (KRZ) <[email protected]> wrote: > Hallo, > while my first routing-service with osrm-backend now is running on my > server, I'm thinking to serve another profile. > > The documentation > https://github.com/Project-OSRM/osrm-backend/blob/master/ > docs/http.md#general-options > ... seems to have the profile-name in the URL. > > /{service}/{version}/{profile}/{coordinates} > > I wonder if {profile} points to the foldername, or to the filename? > No, nothing. It's just a trap! > > https://router.project-osrm.org/route/v1/foot/8.602208,52. > 248399;8.630159,52.241298?steps=false&alternatives= > false&geometries=geojson&overview=full > is just the same as > https://router.project-osrm.org/route/v1/banane/8.602208, > 52.248399;8.630159,52.241298?steps=false&alternatives= > false&geometries=geojson&overview=full > > The value of "profile" after "/v1/" has no function. Only the > service-port of the service maps to the computed profile, I think. > > So, for a second routing-profile I have to start a second service on a > another port? Is this true? > > It would save a lot of time for beginners like me to write this > information into the documentation. > It costs a lot of testing to get out of this "trap". > > > Greetings > Frank > > > _______________________________________________ > OSRM-talk mailing list > [email protected] > https://lists.openstreetmap.org/listinfo/osrm-talk > >
_______________________________________________ OSRM-talk mailing list [email protected] https://lists.openstreetmap.org/listinfo/osrm-talk
