Closed rugk closed 4 years ago
Can you give example of OSM element where address is missing and it would be useful to add it?
I hoped @stefanw could explain what data may be needed/adjusted in a better way. I only wanted to spark the idea here, and do not have insides into the data that is there and what things are missing.
So I'd like to forward that question to @stefanw.
I can think of the following situations which may occur and where people may argue that this is not really a missing information:
And in cases where nothing of above applies, the correct solution is to map address on building (or optionally on node places within building outline), what is already supported by SC.
Overall, I am not convinced that it really is worth implementing.
Okay, this stefanw also did not describe it here, so I'll close it.
Hmm, maybe someone else from @okfde like @arnese maqy be interested in improving the data for TopfSecret in this app? (Please refer to the history of this ticket?)
I know they are busy.
Sorry for not reacting earlier.
This is basically about POIs (like restaurants) lacking address tags. Right now we have to reverse geocode the restaurant node without addresses to get an address.
Here is an example. There is a nearby house number address node, but the amenity:restaurant
node does not have address tags. I'm sure there could be a solution for this.
@westnordost Could you reopen this for the discussion?
No, because what has been written before still applies
Am 14. September 2020 22:32:23 MESZ schrieb rugk notifications@github.com:
@westnordost Could you reopen this for the discussion?
General
Affected tag(s) to be modified/added: obvious Question asked: Is this the correct address?
/Is here a restaurant?Checklist
Checklist for quest suggestions (see guidelines):
Background
FragDenStaat and Foodwatch started the campaign "Topd Secret". They use the German freedom of information act to request information about official hygienic reports. But the details are off-topic here. During this campaign, they encountered a problem of the OSM data. To quote them:
translated:
Solution
So maybe we can fix that problem/data with StreetComplete.
Because they also describe they have implemented a reverse-geocoding and thus limited the cases for potential quests to the quest list here, which has a website version. Or wait, no, this list, lists addresses that are not listed in OSM, not addresses with missing address tags…
However, that may also easily fit into a quest, i.e. "Does this restaurant exist here?" and then just yes/no, which adds the restaurant.Okay, no, this can hardly be verified without seeing OSM nodes nearby, so forget it.So maybe we should limit this to confirming addresses? (after you've got them from reverse geocoding) @stefanw, would this help? In this case, we just need the list of node and (reverse geocoded) addresses. This can then be presented to the user and they can just "confirm" or "deny" that the address matches. (They also detect deleted restaurants this way…)
Ideas for implementation
Element selection: specific
amenity
andshop
tags, filtered by data above?Metadata needed: possibly no country restriction, as the case itself (no clear address) can happen worldwide, but we may start with Germany first anyway, as we have data there.
Proposed GUI: show the name of the restaurant and the address that we suspect below. If missing, offer input fields. Let the user confirm the address?
/ccing @stefanw from @okfde