[HOT] Fwd: [OSM-talk] HOT Fiji & 180th Meridian

[Mike Thompson]

Blake,

Thanks!  That is very helpful!

Mike

On Tue, Feb 23, 2016 at 3:52 PM, Blake Girardot <bgirardot at gmail.com> wrote:

>
> Hi Mike,
>
> Ideally, and typically we map in response to support organizations on the
> ground who request the map data from us for emergency relief and they
> provide us their priority areas. No one contacted us in this case and asked
> us for map data or provided priority areas so we did not officially
> activate.
>
> One of the community members (JGC) has been reviewing news and social
> media to determine impacted areas and I am working on a tasking manager
> project to support his suggested first priority area now (Koro Island).
>
> In this case the mapping we do will probably be used during the remainder
> of the relief phase and just as importantly for the recovery efforts,
> knowing what used to be where and planning during reconstruction (and used
> in insurance claims to cover reconstructions believe it or not).
>
> But without direct contacts on the ground we will be "mapping in to the
> blue" and will publish our resulting data sets on HDX (
> https://data.hdx.rwlabs.org/group/fji?sort=metadata_modified+desc) as
> well as using the HOT Export Server to generate gps device maps with
> building foot prints for relief workers.
>
> I expect the first Fiji project to come out shortly for Koro Island, which
> is small and only about 500-1000 buildings.
>
> The follow on Fiji projects will probably cover the north shore of Viti
> Levu as well as the small islands between Koro and Viti Levu.
>
> Since it is not an official HOT activation, it moves a little more slowly
> as we find people with the time to handle the process of reviewing damage
> reports, existing data sets, existing mapping, imagery and making TM
> projects.
>
> So I think the answer is we are supporting, but without any ground
> contacts it takes us a bit longer to get ramped up.
>
> Regards,
> Blake
>
> On 2/23/2016 10:44 PM, Mike Thompson wrote:
>
>> What is the reason we are not supporting Fiji in the wake of Winston? is
>> it because their are somewhat well off and do not need our help? I ask
>> not just out of curiosity, but because I am likely to be asked at one of
>> the upcoming mapathons.
>>
>> Mike
>>
>> On Sat, Feb 20, 2016 at 8:21 PM, Blake Girardot <bgirardot at gmail.com
>> <mailto:bgirardot at gmail.com>> wrote:
>>
>>
>>     Hi,
>>
>>     I am not sure what mapping HOT can do to support Fiji after the
>>     typhoon, but this message to OSM-Talk is informative.
>>
>>     If anyone is reviewing mapping or starts mapping there the below
>>     linked to wiki page seems important to review.
>>
>>     Thanks to Richard <ricoz.osm at gmail.com <mailto:ricoz.osm at gmail.com>>
>>     for pointing it out.
>>
>>     Regards,
>>     Blake
>>
>>
>>     -------- Forwarded Message --------
>>     Subject: [OSM-talk] HOT Fiji & 180th Meridian
>>     Date: Sat, 20 Feb 2016 21:10:26 +0100
>>     From: Richard <ricoz.osm at gmail.com <mailto:ricoz.osm at gmail.com>>
>>     To: talk at openstreetmap.org <mailto:talk at openstreetmap.org>
>>
>>     Hi,
>>
>>     not sure what the situation on Fiji is but if there is any
>>     HOT effort keep an eye on the
>>
>>     https://wiki.openstreetmap.org/wiki/180th_meridian
>>
>>     Luckily most tools were improved over the past few months
>>     but keep in mind that there may be remaining problems and
>>     fairly new or experimental versions of some tools are
>>     required.
>>
>>     Richard
>>
>>     _______________________________________________
>>     talk mailing list
>>     talk at openstreetmap.org <mailto:talk at openstreetmap.org>
>>     https://lists.openstreetmap.org/listinfo/talk
>>
>>
>>
>>     _______________________________________________
>>     HOT mailing list
>>     HOT at openstreetmap.org <mailto:HOT at openstreetmap.org>
>>     https://lists.openstreetmap.org/listinfo/hot
>>
>>
>>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/hot/attachments/20160223/47e2883b/attachment.html>