Web search: routes without length, uphill and downhill, wrong length in the route card
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 48/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Active
- Domain
- full-stack, web-dev
Research direction
The issue identifies server search results and the web route row and card as the areas to change, but names no files or tests. Start by tracing how route search results are assembled on the server and consumed by the web map, then compare the route details shown in the Android example. Done means search rows show route length, uphill and downhill before the place, and route cards show lengths in km.
Written by the indexing model from the issue text.
Description
Problem
Found in osmandapp/OsmAnd#25940 (W-TC-01…03): search "Tatranska magistrala" on https://test.osmand.net/map/#12/49.0830/19.6120.
-
The route row shows no route length, uphill and downhill, only the distance from the map center: web
Foot · Východná · 21.8 km, Android shows a line with the length, uphill and downhill icons before the place:⇆ 50.2 km ↑ 2.46 km ↓ 2.91 km · Východná. -
The route card shows the length as metres: the 50.2 km route shows
0.1 km, the 22.2 km route shows0 km.
Fix
- Server: send uphill and downhill of routes with the search results.
- Web: show length, uphill and downhill in the route row as on Android: a line with the length, uphill and downhill icons before the place.
- Web: show the route length in the card in km.
- Dominant language
- MDX
- Stars
- 63
- Forks
- 431
- Avg merge
- 17h 10m
- Merged PRs (30d)
- 124
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from osmandapp/web
-
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
Maintainers usually reply within 1 day
-
Enlarge click area for selecting track lines in mapPossibly taken @Dima-1 claimed this 17 days ago. OpenNice to have
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
osmandapp/web#2057 · 2 comments · 1 assignee ·
Maintainers usually reply within 1 day
-
Difficulty 3/5 1-2 days Newbie friendliness 67/100
Maintainers usually reply within 1 day
-
Difficulty 3/5 1-2 days Newbie friendliness 55/100
Maintainers usually reply within 1 day
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Maintainers usually reply within 1 day
-
Add "append" and "prepend" slots for vue-vuetify extended renderersPossibly taken @simeyc claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
eclipsesource/jsonforms#2668 ·
Maintainers usually reply within 1 day
-
enhancement good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
andy1924/notch-player#11 ·
-
feature request
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
openlayers/openlayers#17736 · 1 comment ·
Maintainers usually reply within 1 day
-
enhancement Website
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
OWASP/OWASP-Hunting#96 ·
Maintainers usually reply within 1 day