Hi All,

I'm having some issues getting disused airfield runways to show in the renderer. They are often used as highways, footpaths or are used for various sundry other uses. Being large visible areas I want to include them in the map but simply tag them in a way that has the map render them but accurately reflects the fact they are just big areas of open concrete.

I originally tired marking them as disused:aeroway=runway but anything disused doesn't get rendered so I reverted to simply adding a centre line marking it as such and then defining the area the concrete takes up. (Area in Question)

I tried tagging them as area=yes/area:highway=unclassified/highway=unclassified to denote the fact they are used for vehicular access but as a "road" don't fit any pre-defined classification.

This works, but the buildings that are build upon part render below the concrete area which I understand it because it's defined as a a highway and thus always gets rendered on top.

So my question is:

a) Is there a better set of area:* tags I can use to define large areas of concrete that should be rendered on the map? b) If I should use area:highway, I believe I can make the buldings "part" of the area so they rendered above? How should I set-up the relationship?

asked 19 Nov '18, 16:13

NeilJed's gravatar image

accept rate: 0%

You probably need to flip around your thinking. Rather than focusing on the way you want things to look in one particular rendering and trying to find tags that get you the look you want (known in the OSM community as "tagging for the renderer"), you should be focusing on finding the most appropriate tags to represent reality and leaving it up to each data consumer/renderer to determine how they want to show things. Otherwise, you may get things to look the way you want in the one rendering, but the underlying data may cause unexpected rendering issues for other renderers or be unusable by some data consumers.

As for the best tags to use, disused:aeroway=runway is most likely the best tag for the entire runway. If there are parts of it now being used for other purposes like roads or footpaths, you could map those as distinct objects over the disused:aeroway object or break that object up and tag the pieces separately.

permanent link

answered 19 Nov '18, 23:00

alester's gravatar image

accept rate: 30%


Thanks for the response.

Yes, I was aware I may have fallen foul of "tagging for the renderer". I have placed a centre line down the path of each runway and marked it as disused:aeroway=runway and done similar for the entire area around the airfield. Naturally neither of these show up in the default map view.

The issue is that there is no hard boundary as to which areas are used for what and sometimes it varies on events. So basically it's multipurpose. In some ways I wish there was a generic "paved area" type that covers this.

I'll have a think and try to come up with solution that works but abides by the tagging schema. Mostly this was prompted by someone I know was organising an event on an old runway and was trying to show the location on an embedded map and the fact the runways weren't shown was causing some problems for people getting there.

(20 Nov '18, 14:03) NeilJed

Since you are talking about disused airstrips and touristic? / hobby? events taking place there - I guess things like drag races or a big outdoor book or art market? - I think tagging them as highway=pedestrian, area=yes is the most appropriate. People are likely walking around a lot on the former tarmac, and it is likely used as just one big plaza or square.

Tagging them with anything suggesting they are "normal" roads for cars (e.g. highway=unclassified/tertiary/secondary) is thus not sensible.

(21 Nov '18, 20:52) mboeringa
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: 19 Nov '18, 16:13

question was seen: 260 times

last updated: 21 Nov '18, 20:52

powered by OSQA