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

New Quest: trail_visibility #486

Merged
merged 11 commits into from Nov 10, 2023

Conversation

mcliquid
Copy link

@mcliquid mcliquid commented Nov 6, 2023

Fixes #478

image

@mcliquid mcliquid changed the title First version of trail_visibility quest New Quest: trail_visibility Nov 6, 2023
@mcliquid
Copy link
Author

mcliquid commented Nov 6, 2023

For discussion:

  • Add gravel|fine_gravel|compacted to the filter?
  • Making images bigger? (more than 50%?)

@mnalis
Copy link
Collaborator

mnalis commented Nov 6, 2023

Add gravel|fine_gravel|compacted to the filter?

I wouldn't add them. If they're man made, with those surfaces it's always going to be trail_visibility=excellent.

Maybe gravel (in cases it is caused by e.g. rockslide and not man-made, but isn't marked as rock instead) might be argued to be included, but I'm hoping that there are not many of those and that percentage of them would be covered by that or (sac_scale and sac_scale != hiking). But even of those majority would be for man-made gravel tracks, so better not to include it either.

Anyway users of SCEE can expand the query for themselves as needed, so it is OK as is, IMHO.

Making images bigger? (more than 50%?)

That would make it painful to scroll, probably. I'm however hoping that perhaps better images could be found / taken. That horrible image for example looks more visible than good. And I doubt that even if picture were to take whole screen of mobile phone would fix the issue (even on laptop screen, most of the pics after excellent do not look very different from one another to me)

@mnalis
Copy link
Collaborator

mnalis commented Nov 6, 2023

(FYI @mcliquid I've changed PR text to say "fixes #478" instead of "fix for #478", to use magic keyword which automatically resolves the issue when PR gets merged)

@Helium314
Copy link
Owner

even on laptop screen, most of the pics after excellent do not look very different from one another to me

I agree on this, the images are not particularly helpful for me.
It seems rather tricky to capture something like "Path sometimes invisible, route partly pathless" on a photo and still have it clear in the quest form.

@mcliquid
Copy link
Author

mcliquid commented Nov 7, 2023

Hm, should we remove the images and go with a text only quest form?
I guess it wouldn't be possible to find the "perfect" matching images when I read the latest discussion.

@Helium314
Copy link
Owner

Hm, should we remove the images and go with a text only quest form? I guess it wouldn't be possible to find the "perfect" matching images when I read the latest discussion.

I agree finding good images would be very hard if possible at all.
Maybe text-only is better as in not tempting users to just go by images.

The texts for excellent and good contain markers, which are not mentioned in the other entries. I would be useful to mention them more consistently, or maybe just "no markers" for the best visibility that has no markers any more.

@mcliquid
Copy link
Author

mcliquid commented Nov 8, 2023

I agree finding good images would be very hard if possible at all.

Another user suggested alternative images here, are these possibly more suitable?
https://wiki.openstreetmap.org/wiki/Talk:Key:trail_visibility#Alternative_Pictures

Maybe text-only is better as in not tempting users to just go by images.

Here would be the quest without pictures, only with text. No idea why the last two entries are indented.
https://github.com/Helium314/SCEE/assets/3351668/fed931f8-95ca-457c-b747-a84818b37952

The texts for excellent and good contain markers, which are not mentioned in the other entries. I would be useful to mention them more consistently, or maybe just "no markers" for the best visibility that has no markers any more.

I've added "no markers" to all other items.

@mcliquid
Copy link
Author

mcliquid commented Nov 9, 2023

@Helium314 Can you guide me how to solve the merge conflict with the strings_ee.xml file?

@mcliquid
Copy link
Author

mcliquid commented Nov 9, 2023

@mcliquid
Copy link
Author

mcliquid commented Nov 9, 2023

Can you guide me how to solve the merge conflict with the strings_ee.xml file?

fixed it

@mcliquid
Copy link
Author

mcliquid commented Nov 9, 2023

@Helium314 What do you think, ready to merge?

@Helium314
Copy link
Owner

Quest looks fine now.
Since the images are not used any more they should be removed.

@mcliquid
Copy link
Author

Removed all images and tested the app successfully.

@Helium314
Copy link
Owner

I found some minor things when testing, will add comments to the code

svg reduced from from 19KB to 12KB
@mcliquid
Copy link
Author

@Helium314 Helium314 merged commit 194141a into Helium314:modified Nov 10, 2023
@mcliquid mcliquid deleted the trail_visibility_quest branch November 10, 2023 11:44
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

Successfully merging this pull request may close these issues.

New Quest: How is the trail visibility on this path? (trail_visibility)
3 participants