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

Nudge users to use aerial imagery #2066

Open
danieldegroot2 opened this issue Aug 3, 2024 · 1 comment
Open

Nudge users to use aerial imagery #2066

danieldegroot2 opened this issue Aug 3, 2024 · 1 comment

Comments

@danieldegroot2
Copy link
Contributor

danieldegroot2 commented Aug 3, 2024

When creating a POI and/or improving the POI position accuracy

  • add an explicit notice in the location step to tell users to check for available imagery.

On desktop, there should be enough width to add a text on the left/right side, along the lines of
('Do not copy information from copyrighted maps.')
'Check the layer menu (bottom left). Choose a proper aerial imagery layer (top left in menu).'
'Place the POI as close as possible to its actual location.'
'You can always improve the object's location later (in the object's detail pane) if needed.'

Or, especially for mobile, it could also be a short hint (i.e. '<= Tip: Add an aerial imagery layer').

If it is too repetitive, it could be limited to the first (few) additions.

These changes may further prevent POI in the middle of a road/car park if it is located inside a building or on the side of the road/car park.
(adding blindly based on default basemap); example where I modified one https://overpass-api.de/achavi/?changeset=154774401

@pietervdvn
Copy link
Owner

In previous, long forgotten version, the add-new-point flow used aerial imagery by default instead of a basemap. The problem with this flow however is that only a few areas have good-enough areal imagery and that people found the sudden switch confusing.

I'm also afraid that adding many pieces of text is gonna clutter the UX more and, TBH, most people won't read it anyway.

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

2 participants