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

Improve ski run property merging #100

Open
russellporter opened this issue Jan 19, 2023 · 0 comments
Open

Improve ski run property merging #100

russellporter opened this issue Jan 19, 2023 · 0 comments
Labels
enhancement New feature or request

Comments

@russellporter
Copy link
Owner

If there are multiple sources of ski run properties (way & relations) these are flattened into a single representation to allow for a simpler UX.

The current approach treats all data sources equally. For example: run difficulty is merged by taking the easiest value from the available sources.

A somewhat common case for nordic ski trails is a longer trail, tagged as a relation has piste:difficulty=easy, but one of its ways may be tagged as piste:difficulty=intermediate.

In the case currently we show the whole trail as easy. However, the ways data should be closer to the ground truth, given relations work at a higher level.

The improvement would be to treat the way data as primary, and only fall back to the current strategy if the way doesn't have a difficulty value.

@russellporter russellporter added the enhancement New feature or request label Jan 31, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant