Route selection doesn't support routes divided into sub relations

bobeeeze commented 1 year ago

Description

Many routes (especially long ones) are represented by a parent relation divided into several sections (sub-relationships). The main route informations are given in the parent relation, because some sub relations may belong to more than one route, and therefore to more than one parent relation.

I've realised that Osmand only displays the sub relations information and doesn't go up the hierarchy. So it doesn't display information about the main route.

I think this is a very important problem, because in France and Spain (two countries I know well) and probably in other countries, there are many long routes divided into several sections. Osmand cannot be used to follow these routes.

How to reproduce

Looking at this route: https://www.openstreetmap.org/relation/14234324 https://hiking.waymarkedtrails.org/#route?id=14234324

This is just an example. There are many routes like this

Actual result

Expected result

Osmand should display the white and red symbol and the text 69 of the GR69 and the route should be in red (osmc:symbol=red:white:red_lower:69:black).

Environment OsmAnd Version: 4.5.10 Android/iOS version: 11 Device model: xiaomi m9t pro

DmitryAlexei commented 1 year ago

Steps to reproduce:

go 43.67763° N, 4.63096° E (Arles, France)
download map or update it (if needed)
enable hiking routes in Configure map > Hiking routes (Colouring according to OSMC)
tap on any shield where route La Rouoto should be present

Actual result:

La Rouoto isn't shown (see OSM relation).
Compare with Waymarked Trails list of available routes

StC-OSM commented 1 year ago

If I remember well, Waymarkedtrails has an inheritance policy that seems appropriate here: sub-relations inherit their parents' attributes unless these attributes are explicitly overridden in the sub-relation.

Actually, the whole community of mappers and consumers (OsmAnd, Waymarkedtrails and the others) would benefit from more explicit conventions about nested relations. Name and ref are two tags that would need more precise operational semantics, in particular.

pyrog commented 1 year ago

Also, if I tape to a route, I could only see the current stage, not the overall route.

vshcherb commented 1 year ago

Possible solutions:

Propagate information to subtracks (easy solution)
Allow to navigate from subtrack to parent track within context menu of the route

osmandapp / OsmAnd