You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Possible values do not show up when tapping into the Advanced field unless typing at least three characters. When the user doesn't have an idea what to search for, it can be tricky to find the desired term assuming it is actually registered in the app.
Some values are likely to be entered twice, e.g. when entering the website name in the Basic information which results in the tag "website", but when searching for "website" in Advanced, the only suggested option is "contact:website".
Opening hours do not allow for special information and formats like (certain) public holidays #11344 or seasonal opening hours under Basic. OsmAnd doesn't assist to enter the right format even in Advanced to solve issues like #7857 and #15072. This can result in showing multiple untitled entries of opening hours in editing mode that were entered in another app as reported in #11390 or false seasonal 24/7 info: #11571
Tell us about the expected behaviour (required)
Compare keys and values from OSM Wiki with the current options in OsmAnd and update the app's keys and values.
Tell us about alternatives you've considered (required)
Entering more values myself but was restricted as I "must be on a branch".
Context (optional)
No response
The text was updated successfully, but these errors were encountered:
I usually avoid the internal OSM editor because of its limited interface, broken suggestion system and non-existing validations. Any other mobile editor (EveryDoor, Vespucci, StreetComple, ...) is way more useful and less error-prone.
Just a hint, not solving any of the above issues.
(I would even drop OsmAnd's editor completely 🤷♂️)
No. Don't remove internal editor. I also use Vespucci quite often, but for simple editing tasks the use of internal editor is faster than changing to Vespucci each time.
OsmAnd only supports only tag that it are embedded i.e. icons / translations.
So yes it's limited but on other hand it also shows what's supported. In case something is missing, it's a good indication that we need to add that tag support.
On the other hand - Templates and Better UX is essential and that what we need to add support and focus.
Also I believe we need to drop OSM Editing Plugin cause it could be nicer integrated into app itself to invite bigger audience.
vshcherb
added
the
Nice to Have
Should be fixed but there is no priority or no possibility to fix it within current horizon planning
label
Dec 5, 2023
vshcherb
changed the title
Improved tag handling by updating keys and suggesting values
OSM Editing doesn't show many OSM tag / values
Dec 5, 2023
OsmAnd is my go-to app for everything related to navigation and OSM mapping. Advanced editing features similarly to the ones found in apps listed by @scaidermern would be amazing!
Describe the idea (required)
For advanced tags, I noticed several keys miss categories like "commerce", bridge types, language and indoor_seating or values like "diet:meat" or "charge_point".
Possible values do not show up when tapping into the Advanced field unless typing at least three characters. When the user doesn't have an idea what to search for, it can be tricky to find the desired term assuming it is actually registered in the app.
Some values are likely to be entered twice, e.g. when entering the website name in the Basic information which results in the tag "website", but when searching for "website" in Advanced, the only suggested option is "contact:website".
Opening hours do not allow for special information and formats like (certain) public holidays #11344 or seasonal opening hours under Basic. OsmAnd doesn't assist to enter the right format even in Advanced to solve issues like #7857 and #15072. This can result in showing multiple untitled entries of opening hours in editing mode that were entered in another app as reported in #11390 or false seasonal 24/7 info: #11571
Tell us about the expected behaviour (required)
Compare keys and values from OSM Wiki with the current options in OsmAnd and update the app's keys and values.
Tell us about alternatives you've considered (required)
Entering more values myself but was restricted as I "must be on a branch".
Context (optional)
No response
The text was updated successfully, but these errors were encountered: