You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am trying migrate osrm backend setup from windows 10 with docker desktop CH algorithm to windows server 2022 (Azure VM).
Since docker desktop is not supported in server version of windows I am using windows binaries (v5.16.0)
My pbf file has merged data of few continents of size 48 GB.
my data preprocessing steps are completed, I have completed this using MLD steps, I did not faced any errors in extraction, partition and customize processes. but in extraction, I encountered one warning message few times for different node ID's saying "Turn is a u turn but not classified as a u turn".
After completion of preprocessing I have hosted them using osrm-routed, but I am not getting expected results it is giving result like this:
{
"code": "NoRoute",
"message": "No route found between points"
}
it is giving correct result for some coordinates and for other coordinates it is giving No route found message.
I am trying migrate osrm backend setup from windows 10 with docker desktop CH algorithm to windows server 2022 (Azure VM).
Since docker desktop is not supported in server version of windows I am using windows binaries (v5.16.0)
My pbf file has merged data of few continents of size 48 GB.
my data preprocessing steps are completed, I have completed this using MLD steps, I did not faced any errors in extraction, partition and customize processes. but in extraction, I encountered one warning message few times for different node ID's saying "Turn is a u turn but not classified as a u turn".
After completion of preprocessing I have hosted them using osrm-routed, but I am not getting expected results it is giving result like this:
{
"code": "NoRoute",
"message": "No route found between points"
}
it is giving correct result for some coordinates and for other coordinates it is giving No route found message.
I tried this:
http://localhost:5000/route/v1/driving/-2.2892203985804755,53.604017274352515;-1.8842546987176998,52.52374243277772?overview=false
but got same error as mentioned above, but in my old setup with same data and OSRM-API is giving correct results
Please help me to solve this issue.
Thanks
The text was updated successfully, but these errors were encountered: