One way to do it is probably to mark it as an address with no business information. Or I can name it, but put in parentheses the status (not open yet or closed down). I could also leave a note for someone to update this information later.

Another route for if it's not yet open would be to just leave this data out and I (or someone else) will need to add it later when it's open. What I'd like to do is use construction=yes, but I assume it'll still show up on the map and be confusing to people who don't know it's not open.

Please advise on the best path to take. If it's shut down but all the business markings are still there, I assume we just leave out/remove this data right?

asked 25 Jan '19, 01:25

Pluto%20is%20a%20Planet's gravatar image

Pluto is a P...
31113
accept rate: 0%

3

The given answers give excellent advice about how to handle these cases. I'd just like to add that putting a status into the name would be considered very wrong.

(25 Jan '19, 16:41) alester

  1. For a POI that is not yet to be constructed, do not add it on OSM.
  2. For a POI that its construction is in progress, add your data, but prefix the POI type key with construction: lifecycle prefix. This prefix will prevent your not-yet-open POI from displaying on the maps/applications in an inappropriate way.

    For example (node-type POI):

    construction:shop=convenience
    name=7-Eleven
    

    Which, once open for business, you can remove the prefix; turning it into:

    shop=convenience
    name=7-Eleven
    

    In case you have other information (like phone=*, opening_hours=*), you may add them if you wish. (May the verifiability be with you) Applications, as far as I figured, would not take them seriously if the POI is in construction or closed down.

    If said POI is also building-in-construction (way-type POI), consider adding building-specific building=construction, construction=* combo too; for example:

    building=construction
    construction=retail
    construction:shop=mall
    name=Zen
    

    Which, once open for business, you can turn it into:

    building=retail
    shop=mall
    name=Zen
    
  3. For a POI that recently went out of business, prefix the POI type key with disused: . This will remove it from most maps/applications display.

    • If the sign is still there, you can leave other data intact.
    • If the sign is removed, then you can remove other information that is specific to the closed business. Leave other standing information, like address, and disuse-prefixed shop type, intact.
      • Note: If locals still know or call it by the old name, you might consider changing name=* key into old_name=* instead of removing it outright.
    • If the POI is also a building, keep those building-related tags intact.

    For example, a bottled gas shop, that is also a building:

    building=retail
    shop=gas
    name=Wang Gas
    opening_hours=08:00-16:00;PH closed
    addr:housenumber=123
    addr:street=Merry Street
    

    When it's out of business:

    building=retail
    disused:shop=gas
    name=Wang Gas
    opening_hours=08:00-16:00;PH closed
    addr:housenumber=123
    addr:street=Merry Street
    

    When its sign is taken down:

    building=retail
    disused:shop=gas
    addr:housenumber=123
    addr:street=Merry Street
    

P.S. If the POI is not just closed down, but also in a very bad shape (e.g. windows/walls falling down), consider using abandoned: prefix in place of disused:.

P.P.S. If the entire block or building got torn down, then you can just remove all information/sub-POIs inside it. (Also consider marking the area with landuse=brownfield if you see fit) Don't forget to note the fact on edit summary when saving your edit too, or otherwise people would think you were vandalizing the map.

permanent link

answered 25 Jan '19, 04:18

Nutchanon%20Wetchasit's gravatar image

Nutchanon We...
260157
accept rate: 50%

edited 25 Jan '19, 12:09

In practice people do all those things.

For new stuff I would say mapping the address is a good way to handle it, and then maybe add a note stating when the business is opening (a note on the osm website preferably vs a note= tag). People use the notes as todo items, so it should eventually get fixed up.

For a closed business that still has signs and such, I think removing the key tag (probably shop= or amenity=) is a good way to do it. It's still identifiable by the name, it just doesn't offer services. If the signs are gone, the name can come off.

permanent link

answered 25 Jan '19, 03:12

maxerickson's gravatar image

maxerickson
11.5k1077161
accept rate: 30%

I don't know if there is a standard way to tag future things but this is what I do:

  • Use the construction: prefix for the future tags. For example construction:name=futurename, construction:amenity=restaurant, construction:website=http://website.for.new.business
  • I add a fixme tag with a description of the situation. For example fixme="Was the xyz restaurant, is currently being remodeled to become the abc restaurant, expected opening spring 2019". The use of the fixme tag helps me remember to check back from time to time to see if they are now open. And if I don't do it, then some other mapper may see the fixme tag and do the check.

For businesses that have gone away, I change the place to shop=vacant and add a description="Used to be the xyz store, now empty." If/when another business opens in that location then I update everything to the new business and drop anything that refers to the old business (OSM is supposed to be for current data).

permanent link

answered 25 Jan '19, 03:20

stf's gravatar image

stf
8.7k971139
accept rate: 18%

3

shop=vacant sells ... vacants? ;-) Not a good tag for a renderer which just renders all shops - but does not know this exception.

(25 Jan '19, 06:35) aseerel4c26 ♦

Got a point, but I found it in the wiki https://wiki.openstreetmap.org/wiki/Tag:shop%3Dvacant as well as near the bottom of https://wiki.openstreetmap.org/wiki/Key:shop

(25 Jan '19, 08:40) stf

shop=malls don't sell shopping centres either. the disused prefix covers too many eventualities to identify shops which don't CURRENTLY have a tenant. It has the merit of being duck tagging: people actually talk about empty or vacant shops (which is more than I can say for malls). It also assumes the only use case for shop is to find things to buy, which is not the case.

(25 Jan '19, 16:48) SK53 ♦
1

@stf: Both of those places in the wiki also add some words of caution, though, which I agree with. Given how many shop values there are, and how many keep being added, it makes data consumers' work easier if they can just treat all shop=* tags as shops. After all, shop=* is defined as "a place selling retail products or services".

(25 Jan '19, 17:42) Tordanik
1

@SK53: at least a shop=mall IS a kind of collection of shops. A shop=vacant is not a shop (it is just a place suitable for a shop and looking like a shop) - but would still show up in a simple rendering which just displays all shop=* (see Tordanik). Even the featured humanitarian layer displays a shop=vacant with a shop icon. And iD, too.

Duck tagging? It may look like a (closed) shop, but it does not sell like a shop. So, imho it fails the test for a shop. Ducks quack and shops sell. ;-)

(25 Jan '19, 20:15) aseerel4c26 ♦
Your answer
toggle preview

Follow this question

By Email:

Once you sign in you will be able to subscribe for any updates here

By RSS:

Answers

Answers and Comments

Markdown Basics

  • *italic* or _italic_
  • **bold** or __bold__
  • link:[text](http://url.com/ "title")
  • image?![alt text](/path/img.jpg "title")
  • numbered list: 1. Foo 2. Bar
  • to add a line break simply add two spaces to where you would like the new line to be.
  • basic HTML tags are also supported

Question tags:

×861
×23
×3

question asked: 25 Jan '19, 01:25

question was seen: 932 times

last updated: 25 Jan '19, 20:27

powered by OSQA