Why not ask your question on the new OpenStreetMap Community Forum?

I'm adding more details to some single-level malls (shop names and locations, mainly), and I'd like there to be paths showing the corridors and entrances/exits. I'd like them to show on most renderers, such as OSMAnd, standard map layer on the website, etc. However, the indoor=corridor tags are not currently shown, and if I try highway=pedestrian, for instance, it complains about lack of names with warnings.

What would be the simplest, most pragmatic way to get useful results (showing paths inside the mall, just to give a general idea for people having never been there) without requiring special renderers?

asked 06 Dec '17, 07:57

voyageant's gravatar image

accept rate: 0%


highway=pedestrian is essentially short for "pedestrianized road", so it's very unlikely to be accurate for an indoor mall.

(06 Dec '17, 16:57) alester

Please use the tags documented in Simple Indoor Tagging, such as indoor=corridor. It's significantly streamlined compared with previous iterations of indoor tagging (which made heavy use of relations, for example) and it's supported in indoor renderers like OpenLevelUp (wiki).

Using a consistent tagging standard gives the best results for the most people, and is therefore the most pragmatic solution – if you consider the long term effects rather than just the immediate benefits.

permanent link

answered 06 Dec '17, 18:35

Tordanik's gravatar image

accept rate: 35%

I do believe the examples discussed here are a halfway stage between standard & indoor tagging. There are multiple places where significant parts of the public highway network for pedestrians passes through covered spaces, and at a minimum fulfil the functional aspects of highway=footway.

Please show a router which will standardly include such covered routes mapped as indoor=corridor. Then I might accept that this is a pragmatic solution which the OP asked for.

Lastly, the usage I describe long pre-dates indoor tagging schemes, and pragmatic solutions must take such factors in account.

(06 Dec '17, 21:21) SK53 ♦

Would it be incorrect and/or counterproductive to add both tags, highway=footway and indoor=corridor? The idea being that the former will be removed once the latter is displayed on standard layers/routers?

(06 Dec '17, 21:38) voyageant

@voyageant: This could be a compromise, but keep in mind that indoor=corridor is intended for area-based mapping. (Which, if you weren't aware of this before, probably makes the tag look even less pragmatic. :P) So unless you're going to use highway=footway on areas, too, the tags will need to go on separate geometries.

@SK53 OSMAnd is listed as supporting indoor=corridor, although I'm not sure if that's actually correct. To be honest, I've been deliberately glossing over the "must show up on standard map and OSMAnd" requirement here because I feel that it's against community norms to base the decision on those factors – tagging for the renderer and all that. Of course, your answer argues that indoor highway=footway can be a decent choice to represent reality, and not just an attempt to get things rendered. I'm not convinced that it's actually a good choice here, but I'll admit that using is not inherently incorrect.

(06 Dec '17, 22:36) Tordanik

Is "indoor=corridor" a solution to the same problem? https://wiki.openstreetmap.org/wiki/Key:indoor links to https://wiki.openstreetmap.org/wiki/Simple_Indoor_Tagging which says "corridors ... are mapped as ... areas"; so it's not actually doing the same job on the map as e.g. highway=footway (though this doesn't of course make highway=footway "correct" or indoor=corridor "incorrect", just different).

(edit: oops - 2 comments composed at the same time; Tordanik addresses some of this above)

(06 Dec '17, 22:41) SomeoneElse ♦

@Tordanik: just looked at my furtive attempts at indoor mapping & see I did use corridor as area. I'm not particularly wild about some of these usages either, but having a representation which gives wildly misleading impressions of pedestrian network connectivity doesn't help either. On the entirely pragmatic level I want accurate timings of how long it will take me to get to the tram stop & the route takes me through the middle of a hospital. :-) Perhaps we can consider this further on the wiki.

(07 Dec '17, 14:10) SK53 ♦

The use of highway=footway for routes inside shopping centres and malls is widespread.

These are often really part of the public realm; and most should be treated as such, even if closed at night. In some cities in North America (Edmonton, Minneapolis come to mind) many pedestrian routes, such as the Minneapolis Skyway, across the city centre (downtown/CBD) are totally enclosed so that much of the main shopping area is of this form.

Additional tags which can be used are tunnel=building_passage and indoor=yes. Opening hours tags could be added to routes which are not open 24/7.

permanent link

answered 06 Dec '17, 11:14

SK53's gravatar image

SK53 ♦
accept rate: 22%


The use of tunnel=building_passage for indoor features is incorrect. The tag is intended for "tunnels though a building" such as this example – never features inside a building.

(06 Dec '17, 18:42) Tordanik
Your answer
toggle preview

Follow this question

By Email:

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



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:


question asked: 06 Dec '17, 07:57

question was seen: 2,420 times

last updated: 07 Dec '17, 14:10

powered by OSQA