-
-
Notifications
You must be signed in to change notification settings - Fork 367
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
Where to draw the line what appears in shop overlay and what not? #5152
Comments
Related #5065 (comment) and following comments. So, in that regard, since hotels, motels, ... generally do not occupy shop spaces but rather either are purpose-built (many hotels) or occupy otherwise residential/office space, they are not included in the list. It should not be surprising to not find these POIs in the shop overlay, given its name. Retirement homes, hospitals, schools etc. are also not included. |
Fair enough, I can continue using EveryDoor for these POIs. But I'd like to point out that nowadays Churches are also included in the Shop Overlay. As are Kindergartens/Preschools and Corporate Offices. None of these are Shops and follow similar occupation patterns in dense metropolitan areas as Guest Houses, BnBs, and small hotels. An example where this would have been useful is the changeset https://www.openstreetmap.org/changeset/138065994 in which I switched to EveryDoor to verify a Guest House and removed another. In the latter case the space was repurposed as a shop again. I earlier added the seemingly missing shop (and created a duplicate POI) in SC and only later discovered in ED that it already existed but just wasn't shown in SC when I checked that street. |
Hm, well as written, a line has to be drawn which POIs to include and which not somewhere, right? |
Probably, but it does needs some work to draw that line, as OSM tagging is a kind of a mess. Probably it would be easiest to copy it from project that has already put in the work to do it? For example, Every Door has AFAICT, basically it has a whitelist/blacklist list of See all e.g. Maybe @Zverik would be interested to have that inclusion/exclusion lists for "amenities vs. micromapping" transformed into some generic language-independent format like JSON, so it can then easily be shared by multiple independent projects? Or perhaps a flag might be introduced into |
I am just going to tag @tyrasd here too because IMO such a distinction of shops/amenities/places vs. micro-mapped things would be useful for any consumer of id tagging presets: All editors, but also general-purpose renderers, I'd say. So it sounds useful to have this information directly in the presets themselves, no? As for naming, I'd suggest "place" vs "furniture": As far as definition goes, I guess what (most?) places have in common is that you can go inside. |
makes sense to me.
Most, but not all. For example, I'd consider |
When gathering statistics locally, I’ve used the rule of thumb that a POI is something that a user might want to search for, thus anything that typically has a name. From that I would exclude roads and boundaries, but otherwise this heuristic has worked well for me. I include bus stops, art installations, and ATMs (named after the operator) based on local custom, which might differ in other places. |
True, good observation. But of course, Also, as far as I know, it is not possible to search for iD presets that could have a name, because the |
To me (and Every Door mostly), POI is a venue manned by people or providing paid services. So, shops, churches, vending machines and parcel delivery machines, but not post boxes or garbage bins. |
If we don’t count post boxes and garbage bins as POIs, how could we ever hope to match Overture’s advertised POI count? 😛 The reality is probably that the true definition of a POI depends on the audience: what a consumer considers a POI may differ from what a government considers a POI, and a data vendor would have their own definition too. So I think there’s some room for StreetComplete to have its own opinion. |
Well all of these are POI. POI are tagged points. Traffic lights, trees, stop signs can be considered POI. What I meant are things to pay special attention to, which most likely have opening hours, payment options, names obviously, can be located inside buildings etc etc. |
I don’t think anyone here is referring to OSM’s technical definition of a POI. We’re all grasping at a real-world definition of a POI but finding that there are multiple definitions. This may be why some non-user-facing systems use alternative terms like “facility” and “venue” that they can define for their own purposes. For a user-facing purpose, “POI” is still somewhat more intuitive. I happen to like the elegance of “whatever someone would want to see in search results, other than a plain address”. But if this is only determining what someone can add using StreetComplete, then maybe the criteria shouldn’t be strictly about whether it’s a POI anyways. |
True, but the clash of meaning is still unfortunate. So definitely worth to explicitly clarify it in this discussion. And using non-ambiguous word might be better idea even for end-users (as you mention in “facility” and “venue” examples).
Or "something user might want to enable audio announcement for in navigation app". e.g. you may want your navigation app to announce "You'll be passing fast food McDonalds in 100m" or "You'll be passing Hotel California in 100m" or "You'll be passing petrol station in 100m" (depending on whether you're needing food or rest or fuel, of course) but you don't really want it to announce "You'll be passing street lamp" or "You'll be passing waste basket" (or even "You're passing housenumber 42" ) |
I came to this issue because I wanted to map a Hostel/Hotel too - would be very cool to have this option. I like @mnalis approach here #5152 (comment) |
The new comment/description for what is a "shop" (now "place") is the following:
So, while the list of things included in this overlay has been extended by things that are purpose-built - schools, universities, stadiums, hotels, guest houses, hostels, motels, police stations, fire brigade stations, bowling alleys, hospitals, cinemas, conference centers, townhalls, etc., what is still omitted are things that are rather like landuses, such as parks, gardens, golf courses, but also marketplaces, miniature golf courses, zoos, theme parks, military bases etc. So, some things that may be called "places" are still missing from this overlay even though they can be entered, but I found it weird to add it into this category, or what do you think? Here's a list of things I skipped:
See changes here: 6eb6ddf |
Also ping @mnalis because I updated the list of things that should be classifed as "shop" (now "place"). |
… for new Places as requested in streetcomplete#5152 (comment)
… for new Places as requested in #5152 (comment)
Use case
Hotels, Bed & Breakfasts, etc. can't be added (and verified) via the app. Admittedly they aren't really shops but neither are some other amenities like kindergartens. Small guest houses are often located where small shops could be and it would be useful if one could just add them like the rest without switching apps.
Proposed Solution
I think these types of amenities should be available:
The text was updated successfully, but these errors were encountered: