-
-
Notifications
You must be signed in to change notification settings - Fork 981
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Parse the 'description' tag of routes in the same way as you parse them of objects #18611
Comments
OsmAnd~ 4.6.0#1135m, released: 2023-12-01
Osmand does not also display other tags commonly used in OSM:
|
xmd5a2
added a commit
to osmandapp/OsmAnd-resources
that referenced
this issue
Dec 14, 2023
xmd5a2
added a commit
to osmandapp/OsmAnd-resources
that referenced
this issue
Dec 14, 2023
cepprice
added a commit
that referenced
this issue
Dec 19, 2023
alex-osm
added a commit
that referenced
this issue
Dec 19, 2023
Display route tags automatically #18611
cepprice
added a commit
that referenced
this issue
Dec 19, 2023
This was
linked to
pull requests
Dec 19, 2023
Chumva
added a commit
that referenced
this issue
Dec 20, 2023
Group translatable keys, expand on click #18611
To test:
|
Review
|
Review - 2Missed units
Missed Description
|
29.03.2024 Review
|
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the idea (required)
I noticed that OsmAnd displays the 'description' tag for objects (this is a description of the object with a limit of 240 characters on OSM). But the same 'description' tag OsmAnd does not parse routes.
By default, OsmAnd does not highlight routes, to see the routes, select your profile (in the upper left corner, for me it’s a pedestrian) and scroll to the very bottom of the list and mark the display of routes, their coloring will appear on the maps (something like https://graphhopper .com/maps/?profile=car&layer=TF+Outdoors).
When choosing a route, see https://www.openstreetmap.org/relation/15004011 for an example. OsmAnd does not display a description of the route. This is very poor and does not give any idea: what kind of route/description it is, what its length is, its starting point and finish.
Add tag parsing for routes: "description"; "distance"; "from", "to".
Tell us about the expected behaviour (required)
https://www.openstreetmap.org/relation/15004011
another example:
https://www.openstreetmap.org/relation/9591689
Tell us about alternatives you've considered (required)
N/A
Context (optional)
No response
The text was updated successfully, but these errors were encountered: