Disused POI rendering (especially on Android)

I recently edited a POI: a hotel which has been repossesed by the landlord (which is also the reason for me in getting renewed interest in OSM).

I would expect to be able to edit it, in a way in which history and information about the POI would be retained, and yet the fact that the place is permanently closed would be immediately obvious to any OSM user.

I tried to check with Organic Maps and OsmAnd (the most used and open source Android apps for OSM, afaict), but unfortunately this is how it appears:

(I’m a new user, so I’ll have to add further screenshots in replies to this same post)

(You can also see in the latest screenshot how all of the tags are correctly seen as “disused:” by OsmAnd)

There’s no obvious way to realise, no information displayed about the disused status of this building.

I also tried Mapcomplete (through which I uploaded the pictures on panoramax[1]), and it suggests that if a place is closed, because disused, the place should rather be deleted.

OrganicMaps also suggests just deleting a place completely. I haven’t tried yet, because I’m not sure how easy it’d be to undo, but I’m afraid that would just throw away the history and information about the place.

Checking on openstreetmap.org itself is not much better: I can see the detailed tags with fewer clicks/taps, but the place still appear to exist and is not obviously disused at a first glance.

At the risk of stating the obvious: the ideal situation is that when a user tries to find information (and/or a route) to the disused POI, he would be able to see immediately the disused state, and:

  • avoid a wasted trip
  • immediately figure out a fallback

Deleting the place altogether would be suboptimal (it would appear missing, people might accidentally re-add it) and confusing it to the user.

And not showing it as disused (the status quo) means that people realise the issue only when they are in front of the property (which is what happened to me and a bunch of other people).

I might try soon to press some of those other buttons in mapcomplete/organicmaps, but otherwise… Is there really no better solution than modifying the name to add a “(permanently closed)” monicker? Getting multiple Android apps to update their UI will of course take time, but is this a well known gap? Has work to address this in the ecosystem already started?

[1] panoramax tags are actually a similar issue as this one: the main openstreetmap.org doesn’t have any special rendering for its id, but if you open the POI in iD editor, you actually get a link to the panoramax image.

I think Organic Maps updates once a month, you edited the place today, so I guess it will take time to see the edits reflected on that app. Osmand as well, but you can have hourly updates since you’re a mapper.

Adding “(permanently closed)” to the name is not correct btw, the name tag should contain the name and the name only. If you think disused:tourism=hotel isn’t enough, you could add a note=* tag.

4 Likes

I guess it will take time to see the edits reflected on that app

Are you sure about it for OsmAnd?

The last screenshot shows that OsmAnd is already aware of the new tag values.

The last screenshot is the edit mode, it gets the latest data if you are online, even if the offline map is not updated (I just tried myself)

1 Like

I usually change the name=* to old_name=*. The old_name won’t be rendered on the map, but search engines can still support searching for it, and Nominatim does, IIRC.

Interesting, can you share a few OSM links of POI that use old_name (and are disused)? I’d like to understand how they get rendered, if that’s really the better approach.

I tried to use Nominatim to search for disused:tourism places around me (London, UK) but I couldn’t see any.

A quick check on disused | Keys | OpenStreetMap Taginfo shows that less than 10% of the disused values seem to use it as a lyfecicle prefix (the rest use the discouraged “disused=yes” or =no approach)

Use of disused=yes is discouraged for features like shops, roads, parks or museums. See the namespace prefix disused:= instead, for example disused:amenity=, disused:leisure=, disused:tourism=*.

Here is a road that has its name changed. You can still search for the old name with haydnstraĂźe misburg

Here is an ex-pharmacy that is now disused. You can also search for it with waldapotheke misburg, and it will show as vacant shop.

2 Likes

Thank you, but unfortunately…

I know you said

search engines can still support searching for it, and Nominatim does

But I was hoping this would include the commonly used mobile apps. I tried both with Organic Maps and OsmAnd, and neither shows waldapotheke misburg:

(Of course I made sure to download the data for the Hannover region)

OrganicMaps:

OsmAnd:

(Will add it in the next comment, usual new-user restriction)

So, it seems that using old_name is not what I was looking for.

Btw, do you have examples using the disused: lifecycle tag prefix? (I mean, that have been in OSM for > 2 week, so they should appear in every Organic Map)

Sure: Node: 692175892 | OpenStreetMap

Thank you, but I was hoping to see something with either name=foo or disused:name=foo (as well as another prefix use like disused:shop)… Since (I think) that might still be shown on Android apps.

As from the previous example, old_name doesn’t seem to be taken into account by mobile apps.

I understand that you prefer to use old_name, so I assume that to find such an example, it would have to be a POI that you didn’t edit (is there a way to search for such tags in Nominatim? I tried to look it up, and it seems that at least 12 years ago it wasn’t possible)

Any object with name=* will usually be rendered on all maps, no matter the underlying tags. Whether you use was:name, name:was, disused:name or old_name is probably a matter of taste, but community (and usage) consensus is to use old_name for this purpose. If your mobile apps cannot search for old_name, feel free to open up a bug report.

The problem is not that stuff doesn’t show with old_name (though arguably that’s a separate problem), the problem is that stuff is shown but not obviously displayed as disused.

Of course I can also file a bug with the relevant mobile apps, but as shown above: I tested with the most commonly used Android apps, and none seem to behave in a way consistent with the OSM tagging practice.

I’m keen to just use a different app, but my concern is that such an app might not exist. Do you have a recommendation for an app which complies with the way that different OSM communities usually tag stuff?

Replying to whb (cannot add a separate reply because I’m a new user):

Yeah, that’s the way in which I first tried to update the tagging… I switched to other alternatives after I got replies in this thread

@whb do you have examples of an hotel (or a shop, or another similar POI) that uses these tags, since more than 2 weeks? I’d like to confirm how that would be rendered 1

The way the POI in question is currently tagged, no app will display it. However, this assumes that the map data of the app in question is up to date.
In general, I would tag a closed hotel like this:

closed:name=...
closed:tourism=hotel

or

disused:name=...
disused:tourism=hotel

See:
https://wiki.openstreetmap.org/wiki/Lifecycle_prefix

The Overpass API is useful for searching:
https://overpass-turbo.eu/s/237L
edit: Query corrected

1 Like

Different maps and apps will show things in different ways. Here for example is one of mine that shows a pub that is currently closed.

If a particular map or map does something odd you will need to raise that with that map or app. In OSM, tag it as best that you can with accurate information, so that all renderers have a reasonable chance of processing it correctly.

You can see what projects use certain keys by looking at taginfo.

You weren’t suggesting it, but sometimes people add “closed” to the name - this is a really bad idea; so please don’t do that!

1 Like