nextcloud / nextcloud/maps

[Bug]: OSRM routing does work only for car mode

Open
#1,126 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

0. Needs triage bug
Dominant language
JavaScript
Stars
598
Forks
113
PR merge metrics
No merged PRs in 30d

Description

⚠️ This issue respects the following points: ⚠️
Bug description

I am not sure if this is a bug, but in OSRM settings when I set all OSRM server urls to https://router.project-osrm.org/route/v1 then on maps routing I can choose from 3 modes (car, bike, foot), but each of those works the same (like always just for car). Even more weird is when I set in settings the url just for bike and foot, then those remaining modes work different, like something in between car and bike/foot, but still different when comparing to public OSRM demo.
I would like to use this server, since selfhosting OSRM with its requirements seem like large overkill for usage like once or twice a week.

Steps to reproduce
  1. set all OSRM server urls to https://router.project-osrm.org/route/v1
  2. try routing in different modes
  3. observe that each mode gives the same output, telling me to go on bike/foot via highway.
Expected behavior

Each mode gives slightly different results if there are better routes for bike or on foot.

Installation method

Other

Operating system

RHEL/CentOS

PHP engine version

Other

Web server

Apache (supported)

Database engine version

PostgreSQL

Is this bug present after an update or on a fresh install of the server?

None

Is this bug present after an update or on a fresh install of the app?

None

Are you using the Nextcloud Server Encryption module?

Encryption is Disabled

What user-backends are you using?
  • Default user-backend (database)
  • LDAP/ Active Directory
  • SSO - SAML
  • Other
Configuration report

No response

List of activated Apps
Enabled:
  - activity: 2.19.0
  - admin_audit: 1.17.0
  - assistant: 1.0.1
  - breezedark: 26.0.0
  - bruteforcesettings: 2.7.0
  - calendar: 4.5.0
  - checksum: 1.2.2
  - cloud_federation_api: 1.10.0
  - contacts: 5.4.0
  - contactsinteraction: 1.8.0
  - dashboard: 7.7.0
  - dav: 1.27.0
  - event_update_notification: 2.2.0
  - extract: 1.3.6
  - federatedfilesharing: 1.17.0
  - federation: 1.17.0
  - files: 1.22.0
  - files_archive: 1.1.3
  - files_pdfviewer: 2.8.0
  - files_reminders: 1.0.0
  - files_rightclick: 1.6.0
  - files_sharing: 1.19.0
  - files_trashbin: 1.17.0
  - files_versions: 1.20.0
  - files_zip: 1.4.0
  - firstrunwizard: 2.16.0
  - gpxpod: 5.0.12
  - integration_openai: 1.0.13
  - integration_reddit: 2.0.1
  - keeweb: 0.6.13
  - logreader: 2.12.0
  - lookup_server_connector: 1.15.0
  - maps: 1.1.1
  - metadata: 0.19.0
  - music: 1.8.4
  - news: 23.0.0
  - nextcloud_announcements: 1.16.0
  - notes: 4.8.1
  - notifications: 2.15.0
  - oauth2: 1.15.1
  - password_policy: 1.17.0
  - photos: 2.3.0
  - privacy: 1.11.0
  - provisioning_api: 1.17.0
  - recommendations: 1.6.0
  - related_resources: 1.2.0
  - richdocuments: 8.2.0
  - serverinfo: 1.17.0
  - settings: 1.9.0
  - sharebymail: 1.17.0
  - spreed: 17.1.0
  - support: 1.10.0
  - survey_client: 1.15.0
  - suspicious_login: 5.0.0
  - tasks: 0.15.0
  - text: 3.8.0
  - theming: 2.2.0
  - translate: 1.1.6
  - twofactor_backupcodes: 1.16.0
  - twofactor_totp: 9.0.0
  - updatenotification: 1.17.0
  - user_status: 1.7.0
  - viewer: 2.1.0
  - weather_status: 1.7.0
  - workflowengine: 2.9.0
Disabled:
  - circles: 27.0.1 (installed 24.0.0)
  - comments: 1.17.0 (installed 1.14.0)
  - encryption: 2.15.0
  - files_external: 1.19.0
  - forms: 3.3.1 (installed 3.3.1)
  - integration_homeassistant: 0.0.2 (installed 0.0.2)
  - systemtags: 1.17.0 (installed 1.14.0)
  - user_ldap: 1.17.0
Nextcloud Signing status

No response

Nextcloud Logs

No response

Browser Console

No response

Additional info

No response

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by inspecting the Maps routing integration and the OSRM settings that supply the server URLs, then compare how the car, bike, and foot modes are sent to the service. Reproduce the three steps with the public OSRM endpoint and verify that each mode produces mode-specific routing rather than identical results.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
api, web-dev
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.