OpenStreetMap

The “Brand” and [“Wikidata(https://wiki.openstreetmap.org/wiki/Wikidata) tags can be really helpful in this case. Unfortunately, you would have to add these tags manually. On the bright side, it will help with editing lots of these warehouses at the same time. Best of mapping, Tomodachi94

I would suggest all Currys PCWorlds have a carphone warehouse after the change (if they do not already) they are all the same company so maybe the shop tag for Carphone warehouse can die completely

Things will change so quick now in retail It will be difficult to keep up with the closures in the next 6 months/year. At least in the UK there are some major high traffic areas areas that are so future proofed by existing mapping they will look complete.

https://www.openstreetmap.org/#map=17/53.46543/-2.34846

I wouldn’t bother tagging Carphone Warehouses within Currys PC World at all, other than perhaps an additional shop=mobile_phone node. We don’t tag their KnowHow repair brand separately, after all. (Similarly, Morrisons call their fresh produce section “Market Street” yet we don’t tag it separately.)

In similar situations I would do something along the lines of operator=Currys PC World and indoor=yes, however I don’t think this is technically the correct use for indoor.

@Richard I don’t know any details about Carphone Warehouse, but if the opening times are different I would argue for a separate node. This is how I do it with cafes inside Morrisons stores, typically named “Market Street Cafe”.

For outlets/concessions of one brand mapped within a larger store of a different band, if I was adding the address to an OSM object for the former, I would typically include the name of the larger store in the addr:housename=* tag. This then leads to a sensible address, when you compile the various addr:* tags. For example:

• Tiny Town Post Office (name)
• Co-op Daily (addr:housename)
• Main Street (addr:street)
• Tiny Town (addr:city)
• TT1 1AA (addr:postcode)

So I’d use that for the Carphone Warehouse outlets, adding a addr:housename=Currys PC World to the Carphone Warehouse node. (I’ve already done this for a few of them I spotted, which will allow me to automatically remove false positives from https://osm.mathmos.net/ghosts/ when Carphone Warehouse gets added to that tool next month.)

@Robert Whittaker that does make sense in terms of addresses, but I don’t think a client of OSM data can reliably use it. At least not without special casing for Post Offices, Carphone Warehouse, cafes in supermarkets, etc and that is not scalable.

A client needs to be able to say “Carphone Warehouse is located inside Currys PC World” but “name is located inside addr:housename” is far to generic.

My suggestion of operator=Currys PC World and indoor=yes is wrong. It’s an incorrect use of both tags, operator is a legal company that runs the node, it would line up sometimes but it’s not reliable.

I like the idea of is_in or rather is_in:store however it seems is_in is deprecated. So I guess my argument is that we need a new tag for this case.

@Richard I’ve still not found a source that says all the Currys PC World stores are 3-in-1 stores. The press release sort of implies it, but not completely. But once we see what rebranding happens, you may well be right, only one POI is needed in this case. Then I’d recommend alt_name=Currys;PCWorld;Carphone Warehouse shop=electronics;computer;mobile_phone with a name that matches the rebrand.

I have asked Currys, and they tell me not all Currys PC World’s currently have a Carphone Warehouse in store, and that it wouldn’t necessarily be the case that every outlet ended up having one once the Carphone Warehouse branches have closed.

I’ve used location=indoor do describe shops (as a separate node) inside other shops, but I think I’m the only one—indoor=yes is more common.