GIScience / GIScience/ors-map-client
Instructions for walking profile too detailed
- Dominant language
- JavaScript
- Stars
- 145
- Forks
- 39
- PR merge metrics
- No merged PRs in 30d
Description
When using the walking profile (maybe others as well), the instructions are very detailed. This probably is due to the high count of segments in the graph, so if you had a circle with 7 segments, it wouldn't say "walk around the circle", but "walk 3 s, walk 2 s, walk 2 s" and so on.


The examples show what is meant. The used segments belong to different paths, so they are included in the instructions. Sometimes it is a street side switch, this could/should be included as an instruction. Maybe it also helps if all instructions under 2/3/4 s are disregarded or merged with the adjacent ones (would make sense in second example).
Also for HEAL. Suggestion from HEAL team is to disable instructions, but I think they should be kept
Contributor guide
No contributing guide indexed for this repository
Research direction
Reproduce the walking-profile examples shown in the issue, including the HEAL case, and trace how route segments become turn instructions in the client. Compare circle segments, street-side switches, and very short instructions against the expected merged or retained guidance; done means the displayed instructions are less fragmented without disabling them.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100