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

Improved documentation about using GPX notes feature. #679

Open
meiphoo7-Mae opened this issue Oct 13, 2024 · 0 comments
Open

Improved documentation about using GPX notes feature. #679

meiphoo7-Mae opened this issue Oct 13, 2024 · 0 comments

Comments

@meiphoo7-Mae
Copy link

Use case

In the area where I tag there are a lot of projects that will a take a long time before they're completed. So I wanted to try the GPX notes feature to store notes for my personal use (instead of notes that end up publicly on OSM). In the app this is called 'Allow creating custom quests' and it says amongst other things 'Note that you'll need to enable custom quests'.
So I followed that suggestion and created a custom quest.

Now there are several problems:

  1. If I create a note, no matter if it is GPX or OSM, as soon as it is saved the note disappears immediately. Under Settings > Quests, I found the option 'Show all notes' which I've activated. When I select the option Settings > Notes > 'Get GPX notes and attached photos and tracks', I can see that my freshly created GPX note is in the file so the note is indeed present. I know that OSM hides notes for the user that created the note but I assume SCEE is not prone to that.
  2. When creating a custom quest, as mentioned above, something has to be put in the field 'Filtering details'. How is one supposed to know what should be put here, given the fact that any documentation is completely non-existent both here and on OSM wiki? Pressing the white 'i' in the blue box opens a text about element selection but still it remains unclear what the name of the GPX-note element is.
  3. Typing things in the field mentioned above, makes me almost want to throw my phone against the wall because literally after each character that is typed or deleted an annoying message pops up with something like 'ERROR' that covers up the keyboard. Is it really necessary to show that dozens of times?
    And even when the app is killed the message remains popping up until it is apparently done with things.

Proposed Solution

Can certain features be documented in a manner that is understandable for a general public?
A solution for remarks 1) and 2) above also works for me.

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