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

[Kevin Kenny]

That sounds good for the wooden (!) helipad visible in
https://binged.it/2gdSX38 , too.  That's no longer in regular use, and the
H has been removed from it, because the fire tower visible to the southwest
is no longer staffed. It's still viable for an emergency (and sees an
occasional flight to maintain the solar-powered radio repeater that's still
located on the tower).

I don't want to map that one until I've climbed up there with GPS. There's
rather a lot of topography, and Bing often hasn't corrected for squint
angle in that part of the world. I particularly suspect that it might be
off because the platform looks a little askew from being rectangular.

On Tue, Nov 22, 2016 at 7:07 PM, Blake Girardot <bgirardot at gmail.com> wrote:

> On Tue, Nov 22, 2016 at 8:33 AM, Tom Pfeifer <t.pfeifer at computer.org>
> wrote:
> > 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.
>
> This is exactly right to my understanding and tagging. My
> understanding and as I have mapped in the past a aeroway=helipad is
> for a known built up permanent for the most part landing area. I
> mapped a lot of these in Nepal.
>
> > There is already "emergency=landing_site" defined and used 1800 times
> that
> > seems to fit the purpose of Blake exactly?
> >
> > https://wiki.openstreetmap.org/wiki/Tag:emergency%3Dlanding_site
>
> This does sound like exactly the right tag for what we are planning on
> mapping.
>
> > 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
> >
> >
> >
> > _______________________________________________
> > Tagging mailing list
> > Tagging at openstreetmap.org
> > https://lists.openstreetmap.org/listinfo/tagging
>
> _______________________________________________
> Tagging mailing list
> Tagging at openstreetmap.org
> https://lists.openstreetmap.org/listinfo/tagging
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/tagging/attachments/20161122/60c32a97/attachment-0001.html>