Skip to content
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

Render parent relation name rather than child relation name for routes #329

Open
StC-OSM opened this issue Oct 6, 2024 · 0 comments
Open

Comments

@StC-OSM
Copy link

StC-OSM commented Oct 6, 2024

Some routes (hiking, cycling, etc) are made of relations within relations, sometimes up to 4 to 5 levels of them. Often, each relation has a name only to indicate that it is a part of the parent relation.

When rendering, it is generally more appropriate to render the name of the parent relation. See for instance two images for parent relation 14900298 and its child relation 8413154, one from mapy.cz and the other from freemap.sk; the former corresponds more to what is usually expected on a map ("Voie de Vézelay" rather than "Voie de Vézelay, Brienne - Bar sur Seine" ; note that Tour des deux Bar is another route that goes through the same way there)

Capture d’écran 2024-10-06 à 10 38 50 Capture d’écran 2024-10-06 à 10 38 29

I have not checked how mapy.cz decides that a child relation corresponds to a route section, but it is plausible that they use the same criteria as what Waymarkedtrails states in its documentation: children relations with the same network tag are considered as sections of the parent relation. I wondered if you could consider using a similar rule.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant