First question :)

I recently mapped the interior stores of Golden Square Shopping Centre in Warrington's town centre. All was well and good, even when I had finished. It's been a day since, and since then, suddenly when I zoom in, the interior walls have completely disappeared. I can't think of something I may have changed that made that happen.

The Grand Arcade in Wigan doesn't have this problem, but only its corridors are mapped as the main building, rather than the whole enclosing footprint of the building. So I figured that may be the issue, and that something had newly changed in how things are rendered. Except that the streets in Warrington town centre that I've also mapped in the exact same fashion, with enclosing buildings mapped before inner shops, don't have this issue.

I think this change is ugly enough to be a problem, as I find it harder to visually navigate. And I'm expecting the way I mapped it to be scrutinized, but until this point it was functionally and visually good in my opinion. Now it just looks like precisely placed points for each store instead of areas.

Any help as to something I've done wrong, if it fixes the issue, thanks for in advance.

asked 15 Aug, 23:53

Falsernet's gravatar image

Falsernet
1112
accept rate: 0%

service: Golden Square Shopping Centre

(People find it easier to answer if you give them some links to the map and data.)

(16 Aug, 09:32) TZorn

Hi Falsernet.

I tend to believe that what you are experiencing is just a temporary glitch or caching issue.

Nevertheless, I'm wondering about a few things.

You have mapped the complet building in a relation of an outer line and that small oval cut-out. That's fine. But then you have tagged each individual shop also as a building. So basically you are saying there are a lot of small wall-to-wall buildings inside a huge building. This is not what we usually do (at least as far as I know, mapping practices might differ in your area).

If you explicitly want to map walls and the like take a look at the Simple Indoor Tagging scheme.

To describe vertical relationships you need to apply the layer key. So for example the rooftop car park needs to get a higher layer than the shops. You have applied the level key but that is not sufficient. The layer key governs how things are rendered and how routers connect features. It just shows the sequence of how objects are stacked. The level key is basically there to provide orientation and labeling in terms of actual building floors.

There are also a lot of small errors like implausible opening hours, overlapping objects, etc. Mapping such complex structure I would highly recommending you switching to the JOSM editor. It offers much more possibilities and a better validation than the iD editor.

permanent link

answered 16 Aug, 10:01

TZorn's gravatar image

TZorn
11.1k554205
accept rate: 15%

Good to know, regarding it being temporary.

The oval cut-out is part of the corkscrew car park entrance. (It would be a pig to map as a service road - instead I opted to put the car park entrance point as where you enter the corkscrew from the road; navigation inwards is very simple in real life as long as you drive slowly enough not to crash inside.)

I'll be sure to investigate simple indoor mapping! The issue though, with putting the car park above the shops in layer, is that it will cover them up and make many of the stores being mapped useless to begin with; I'm not aware of a UI that uses OSM data that lets you select a floor, but I assume it'd use the level tags to select specific floors.

As for opening hours, I thought I'd been quite diligent with the specific shops when I added opening hours, based on data from businesses' own websites. If you remember a specific example of the hours being 'implausible', I'd like to hear so I can fix it, unless I'm misunderstanding what you mean by implausible. Perhaps I messed up the mental conversion from 12hr to 24hr clock.

(16 Aug, 17:37) Falsernet

It's of course unfortunate when a car park covers up other features. But that's the case with many things (buildings on top of an underground station, shops on top of other shops in a multi-storey shopping center, a bridge on top of riverside restaurants etc.). You shouldn't count too much into what the standard map on openstreetmap.org shows. Don't map for the renderer is one of OSM good practices. Instead you should map the reality and different data consumers (maps, routers, apps, ...) can decide how to interpret them and what do display and what not.

(16 Aug, 20:46) TZorn
1

cont...

Take a look at OpenLevelUp to see the levels you have mapped (seems strange there are a few L3 objects but no L2 ones).

The opening hours of Game are not well tagged. Feed the string into the Opening Hours Evaluation Tool to see why you should use , instead of ;`.

To find more problems like the opening hours one use some quality assurance tool like Keep Right or the built in JOSM validator.

(16 Aug, 20:47) TZorn
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:

×2
×190
×179

question asked: 15 Aug, 23:53

question was seen: 276 times

last updated: 16 Aug, 20:47

powered by OSQA