Change configuration so all roads are available to all vehicles

Maps Website
1

I’m learning to use the new maps client, and am trying to compare route times and lengths.
In my test case, there is the long way around on highways, or the short way over a mountain road. The client will let me route a bike over the mountain road, but not a vehicle, even though I know for a fact that the road is passible.

For my purposes I need to be able to include all roads, for all vehicle types, as possibilities. I have spent considerable time making adjustments in the ors-map-filters.js with no affect.

What is the appropriate way to change the configuration for this purpose?

2

Hey @MoltenLight

The client is responsible for sending the parameters/filters according to what is supported by ORS API. In this case, the restriction is related to the routing engine (our API) and not the client. So I guess you would have to run a local instance of our back-end/API in order to achieve your purpose.

3

Thanks for the insight.
I’m working on Windows 10. I have installed Docker, and built the server, using this batch file:

set pwd=C:\Project\openrouteservice-js
docker run -dt ^
  --name ors-map-server-8095 ^
  -p 8095:8095 ^
  -v %pwd%/graphs:/ors-core/data/graphs ^
  -v %pwd%/elevation_cache:/ors-core/data/elevation_cache ^
  -v %pwd%/conf:/ors-conf ^
  -v %pwd%/us-west-latest.osm.pbf:/ors-core/data/osm_file.pbf ^
  -e "JAVA_OPTS=-Djava.awt.headless=true -server -XX:TargetSurvivorRatio=75 -XX:SurvivorRatio=64 -XX:MaxTenuringThreshold=3 -XX:+UseG1GC -XX:+ScavengeBeforeFullGC -XX:ParallelGCThreads=4 -Xms1g -Xmx2g" ^
  -e "CATALINA_OPTS=-Dcom.sun.management.jmxremote -Dcom.sun.management.jmxremote.port=9001 -Dcom.sun.management.jmxremote.rmi.port=9001 -Dcom.sun.management.jmxremote.authenticate=false -Dcom.sun.management.jmxremote.ssl=false -Djava.rmi.server.hostname=localhost" ^
  openrouteservice/openrouteservice:latest

It appears to have completed successfully and showed up in Docker Desktop as “running”.
The issue is I can’t connect to it.

Previously I had done: npm run dev , and then was able to connect the New Maps Client using: http://localhost:8080/#/

As you can see above, I changed the port in the build to 8095, and then tried to connect:
http://localhost:8095/#/
http://localhost:8095/
http://localhost:8095/ors
http://localhost:8095/ors/v2
http://localhost:8095/ors/v2/directions

Nothing will connect.
I see references to tomcat, but am assuming that doesn’t apply to Windows.

Thanks

4

Hey @MoltenLight

In this case, I ask you to post your question in the category related to ORS back-end, so the people that are more involved with it can potentially help you.

5

If you want to run the app on a localhost:port
you need to only change the port of your machine, not the one inside docker.
-p port-on-your-machine:port-within-docker
if the app is exposed inside the docker on port 8080, you need to leave the second value on 8080.

However as @amon mentioned, this is a backend issue and has to do with the way graphs are built.
Not all ways are included in the graph for every profile due to tags such as bycicle:no or car:no.