Suggested Quest: Guidepost

[pigsonthewing]

General

Affected tag(s) to be modified/added: [Tag:information=guidepost] (over 359K instances)

For each guidepost there can be up to 8 tags:

direction_north=*
direction_east=*
direction_south=*
direction_west=*
direction_northeast=*
direction_northwest=*
direction_southeast=*
direction_southwest=*

(see https://wiki.openstreetmap.org/wiki/Key:direction_north etc. )

or if there are more than 8 values, suggest a note.

Checklist

Checklist for quest suggestions (see guidelines):

• [ x] 🚧 To be added tag is established and has a useful purpose
• [x ] 🤔 Any answer the user can give must have an equivalent tagging (Quest should not reappear to other users when solved by one)
• [x ] 🐿️ Easily answerable by everyone from the outside but a survey is necessary
• [x ] 💤 Not an overwhelming percentage of elements have the same answer (No spam)
• [x ] 🕓 Applies to a reasonable number of elements (Worth the effort)

Ideas for implementation

Option 1 [Preferred] Show a compass rose aligned with the map; allow the user to select one or more of eight options, entering text for each selected.

Option 2: show a list of 8 directions, and allow the user to select as many as needed, then for each show a dialogue where text can be entered.

Option 3: Cycle through eight dialogues, each with a "no value" option.

Prompt the user to add a note if there are more than 8 "fingers"

Optional: add a language tag (could suggest default (s) depending on location)

[westnordost]

Can you explain what useful purpose this information has? Is the information used by any app, and if not, can you think of a meaningful use case?

…

On 18 January 2021 12:50:13 CET, Andy Mabbett ***@***.***> wrote: > ### General> > Affected tag(s) to be modified/added: [Tag:information=guidepost] (over 359K instances)> > For each guidepost there can be up to 8 tags:> > direction_north=*> direction_east=*> direction_south=*> direction_west=*> direction_northeast=*> direction_northwest=*> direction_southeast=*> direction_southwest=*> > (see https://wiki.openstreetmap.org/wiki/Key:direction_north etc. )> > or if there are more than 8 values, suggest a note.> > <!-- If the answer is not obvious, please append a short explanation to each item (or, if it is longer, below), explaining the reason. -->> ### Checklist> Checklist for quest suggestions (see guidelines):> - [ x] 🚧 To be added tag is established and has a useful purpose> - [x ] 🤔 Any answer the user can give must have an equivalent tagging (Quest should not reappear to other users when solved by one)> - [x ] 🐿️ Easily answerable by everyone from the outside but a survey is necessary > - [x ] 💤 Not an overwhelming percentage of elements have the same answer (No spam)> - [x ] 🕓 Applies to a reasonable number of elements (Worth the effort)> > ### Ideas for implementation> > Option 1 [Preferred] Show a compass rose aligned with the map; allow the user to select one or more of eight options, entering text for each selected.> > Option 2: show a list of 8 directions, and allow the user to select as many as needed, then for each show a dialogue where text can be entered.> > Option 3: Cycle through eight dialogues, each with a "no value" option.> > Prompt the user to add a note if there are more than 8 "fingers"> > Optional: add a language tag (could suggest default (s) depending on location)> > > > -- > You are receiving this because you are subscribed to this thread.> Reply to this email directly or view it on GitHub:> #2514

-- Diese Nachricht wurde von meinem Android-Gerät mit K-9 Mail gesendet.

[pigsonthewing]

Can be used by foot/ cycle routing apps: "Follow the sign marked 'Anytown 2 miles'"; already used 30,000 times on over 6K objects, according to wiki page cited.

[westnordost]

Makes sense.

An implementation should be option 1. A compass rose that rotates with the map, with tappable directions. Though, a problem here is the size. 8 buttons may get pretty crowded. Especially if labels for the directions are shown.

[ygra]

What can be a bit annoying to enter is that there can be multiple entries per direction, as well as a distance. That may make the UI even more crowded (but that's probably solvable, I guess).

[michaelblyons]

Perhaps a silly idea: "Point your phone the way the arrow points." One big button to confirm. Then we get the direction from the phone's compass, and bring up the destination and distance interface.

…

On April 2, 2021 6:25:33 PM EDT, "Johannes Rössel" ***@***.***> wrote: What can be a bit annoying to enter is that there can be multiple entries per direction, as well as a distance. That may make the UI even more crowded (but that's probably solvable, I guess). -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: #2514 (comment)

[westnordost]

I like it.

[westnordost]

Though probably something like this would be easier

If nothing is tapped yet, instead of the edit text, a hint is shown what to do in this form.

[ygra]

One thing I recently did here was amend existing guideposts with additional information and doing this at home from a photo can be a bit annoying, so the convenience of StreetComplete would be very nice when outside.

However, I couldn't really think of a way to determine that there's still information missing from a guidepost. This quest could also only apply to guideposts that lack any direction information, but it's impossible to determine that information can be added (unless there's a separate quest »Is this guidepost information still accurate«, which might be a good idea as well).

[mnalis]

The main issue I see is that compass on mobile phones (in my experience) is often inaccurate (on each of several mobile phones I've had, both lower and higher end), and sometimes needing recalibrations (doing figure-of-8 with mobile phone or similar) in order to get correct (or any) data.

So I feel confident to use android-provided compass direction only after verifying the direction that I was coming from for reference (which I why I suggested #2209). Using compass as only means for orientation is risky, as SC then might be adding incorrect data (which is IMHO much worse than no detailed data).

[riQQ]

And a fall back is also necessary, as only about ~80% of phones have a compass.

riQQ wrote on 2021-02-19:

Another reason: some devices don't even have a compass, but they do have GPS.

Quick search on Geizhals.de:
2253 phones with Android

• 99.8% have GPS (2248/2253)

• 79.1% have a compass (1781/2253)

[DerDings]

guideposts which are part of a type=destination_sign relation should be excluded. Destinations information is probably included in those relations.

Besides, is there any app which uses the direction_south etc. information?
I think it is very hard to use that information, compared with destination tagged on the road or a type=destination_sign relation clearly defining which road the information belongs to.

[letypequividelespoubelles]

Three ideas for this quests :

• instead of having just the compass, it could be better to help the user to have the compass and in background the local map with the different ways around the guidepost. It could help to point the right direction, and are necessary for the 20.9% of smartphone holders without compass (though I guess it's 20.9% of the different available model that doesn't have a compass, and not of the selled smartphone)
• it could be very annoying to type all the direction, so it might be good to have an auto completion (like for the ATM's operator quest). Moreover, it would reduce typing error. The possible destination for the auto completion could be, for exemple, name of guideposts, peaks, pass, refugee, around this guidepost (maybe 10 km ? )
• what about the indication of time ? In most hiking guideposts, there is the indication of time to go to this destination (or more rarely distance). This information should be in the same quest, as it's very usefull (and even more usefull than just to know the direction).

[pigsonthewing]

guideposts which are part of a type=destination_sign relation should be excluded. Destinations information is probably included in those relations.

They should not, because we want a transcription of what is written on the "finger", nut just the name of the destination.

[pyrog]

When hiking (at least in France) what is useful is the name and elevation of each guidepost, and pictures.

Capturing the details of each directional blade (name with distance and/or duration) seems to me too complicated and unreliable.

It could be possible with an AI with OCR 😅