/pdirections is the endpoint for our public client that is restricted to ors internal usage.
It has the exact same functionality as the directions endpoint.
The conversion of the route works as you discovered.
We use the geometry points of the track and generate waypoints in defined intervals that can be specified with the deviation tolerance.
The smaller the value the more points are generated.
(it should only be possible to generate 50 waypoints maximum, but i somehow ****** up the implementation i just realized )
The generated points are send to our directions endpoint and a route is generated.
It is currently not possible to generate a route for an exact geometry with our backend.
So the closest you can get is:
- import route
- generate waypoints
- adjust waypoints until it represents your route