Yes please only for official sites. We have to be careful to not indicate as an 
helipad if no official sign. In such cases, we use as a convention, leisure = 
common. The GIS specialists can then extract the info and analyze.
regard  
Pierre 

      De : Tom Taylor <tom.taylor.s...@gmail.com>
 À : hot@openstreetmap.org 
 Envoyé le : Dimanche 3 mai 2015 13h10
 Objet : Re: [HOT] Question on Nepal helicopter landing sites mapping
   
I would go with Milo's approach. Leave "aeroway=helipad" for the 
official sites.

Tom Taylor
TomT5454

On 03/05/2015 11:53 AM, Michael Krämer wrote:
> Hi Milo and Sérgio,
>
> thank you both very much for your feedback. I think you gave perfect
> examples of the two different approaches that I
> came across:
>
> Am 03.05.2015 um 17:35 schrieb S Volk:
>> For the other "possible" landing areas as said in instructions, in
>> hilly areas I try to find the higher and larger, clear but not too
>> far from village. Also with some support of helicopters websites as
>> quoted, Helicopters like Chinook may need wider area, but smaller
>> helipoters can land on smaller areas. It depends on conditions that
>> we can't decide from satellite.
>
> Am 03.05.2015 um 17:10 schrieb Milo van der Linden:
>> I have been mapping "aeroway=helipad" in the following way:
>>
>> 1. In JOSM, I draw a line 30m in diameter.
>  > 2. Then I use "Create Circle" and add "aeroway=helipad"
>  > 3. If it doesn't fit in the area  where I drew the line, I use
>  > "Copy" and delete the circle.
>> 4. I then move accross the map seeking potential spots. Once I see
>> one, I press "Paste" to see if the 30m diameter circle fits. If it
>  > does, I leave it there or move it slightly to fit.
>
> So one approach is to have "leisure=common" areas adjusted to the local
> situation. The other approach is to have circles tagged with
> "aeroway=helipad".
>
> Since the two approaches are pretty different I really would like to
> know which one is the preferred one. Once this is sorted out we probably
> shoud align the mapping & tagging for easier extraction and processing.
>
> Thanks,
> Michael
>
> _______________________________________________
> HOT mailing list
> HOT@openstreetmap.org
> https://lists.openstreetmap.org/listinfo/hot



_______________________________________________
HOT mailing list
HOT@openstreetmap.org
https://lists.openstreetmap.org/listinfo/hot


  
_______________________________________________
HOT mailing list
HOT@openstreetmap.org
https://lists.openstreetmap.org/listinfo/hot

Reply via email to