I am building some small private project currently using the standard openrouteservice directions API.
However, I would like to have some more control over some of the routing specifics, for example, which waytypes should be used for cycling navigation or for hiking which SAC scales should be included in the routing.
I know that this is not possible with the public API, but I am planning to run my own instance of ORS either way.
My question is, if there are already any resources or even guides on how to go best about creating your own directions routing profile? What exactly and where things need to be updated?
I’ve already looked in the forum, but couldn’t find specifics tbh.
Any help/pointer is appreciated!
there are a few posts that deal with in a bit more detail this e.g.:
If you run your own, you will be fine with adjusting existing values.
for hiking sac scale adjust:
for cycling regular or mtb (both extend CommonBikeFlagencoder): e.g.
which waytypes are usable is definde in the getAccess method in those files.
This is evaluated during graph build though.
So if you change something don’t forget to rebuild the graphs (best just remove the existing ones)