[Tagging] How might we best map emergency helicopter landing zones?

Tom Pfeifer t.pfeifer at computer.org
Tue Nov 22 13:33:11 UTC 2016

aeroway=helipad should be used only for built-up infrastructure, not for 
emergency places that have a different use normally.

An emergency landing place is nothing but a predefined clear space, it 
could be a soccer pitch or a big lawn in a park in normal situations.

There is already "emergency=landing_site" defined and used 1800 times 
that seems to fit the purpose of Blake exactly?


On 22.11.2016 14:02, Andrew Errington wrote:
> I tag them as aeroway=helipad, and it looks like this:
> http://www.openstreetmap.org/#map=16/35.2932/127.5317
> There are a lot of them in the mountains of Korea.  Usually marked out
> with a pattern of white stones embedded in the ground.
> Would like to know if there's a better way, or if doing it this way is
> wrong.  Or right.
> Thanks,
> Andrew
> On Nov 22, 2016 8:41 PM, "Blake Girardot" <bgirardot at gmail.com
> <mailto:bgirardot at gmail.com>> wrote:
>     Dear friends,
>     I have worked with folks doing ground surveys of helicopter landing
>     zones during emergency response.
>     These are ground truthed locations, observed by active search and
>     rescue helicopter pilots collecting the basic minimum critical ground
>     survey items for an HLZ for their aircraft type.
>     They collect the data and provide it in the public domain and I would
>     like to map it.
>     I think the vast majority of the items collected are already well
>     supported in OSM, trees, light poles, ground type, area, grade,
>     landuse.
>     What would be the best way to map this data? Does it need its own
>     namespace? Just map  regular OSM tagging and render the data myself
>     custom?
>     I think issues of does the data belong in OSM are separate issues, I
>     am just interested in how to map it and tag it well. I would be
>     mapping nothing but ground truthed data that we already map every day,
>     trees and light poles and ground type, landuse. It is publicly
>     available data (CC0).
>     Other data could and should be added specific to HLZ's so we will need
>     to discuss any non traditional tags that I would like to see be used
>     for the HLZs mapped.
>     Cheers,
>     Blake

More information about the Tagging mailing list