-
Notifications
You must be signed in to change notification settings - Fork 4
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
Encourage/enable edits to OSM #179
Comments
Tagging as v3 issue for now, with reference to the first two options. The third, if we decide to do it, is probably a bigger issue out of scope for v2. I think we could usefully mention OSM data with a link to https://osm.org in v2 though, maybe in the about page. |
This is done. Great! Will test out now.. |
Ah no, closing as inactionable. We link to OSM from the About page in the sketch tool and on all relevant layers in the browse tool. There are much larger open questions about how to collect feedback from users about things they see that look wrong and validate that and funnel it back into OSM. |
Aha. Just tested for one of the OSM layers in York. Great that it jumps to the relevant OSM way on that layer, it's a bit sudden and does not give warning. UX experience that I guess would be less surprising would be to click on an entity, see some info, including maybe 'View in OSM' and possibly streetview, and then explicitly have one more click. |
Overall: agree re wider questions that need some thought. |
Just labelled this as 'wontfix' for now, can pick up later in this / other issues if it jumps up the priority list. |
This is a meta issue split out from conversation in #177.
Need: OSM data is imperfect. The more users know about it and know how to edit it, and the more they actually edit it to improve it, the better ATIP data, and all evidence derived from OSM data, will be.
There are many options from simple to complex including:
The text was updated successfully, but these errors were encountered: