Re: [HOT] Ebola Outbreak Activation
According to the latest report of WHO on Tuesday July 1, the Ebola outbreak killed 467 people, about 759 cases of hemorrhagic fever identified in the three affected countries, Sierra Leone, Guinea and Liberia. This is 129 more deaths than the previous record from a week ago, an increase of more than a third, a sign that the epidemic is distributed after a lull in April. Both MSF and Red Cross are deploying in new areas in Sierra Leone and need our help to map these areas. The HIU unit of the US State Dept, MapBox and Airbus Defense are processing imageries. As these images arrive, more jobs will be created. With this reactivation for the Ebola Outbreak, we need again your participation. The jobs are coordinated from the Task Manager at http://tasks.hotosm.org/#featured/Ebola Pierre ___ HOT mailing list HOT@openstreetmap.org https://lists.openstreetmap.org/listinfo/hot
[HOT] Keeping the data consistency when updating an area with a new imagery
Hi, When we get recent imagery over areas that have already been mapped with Bing imagery, very often it does not have exactly the same georeferencing, and very often we do not have any trace or not enough to fix this. Consequently, either the contributor will offset the new imagery on the vector data, or on the contrary will move the vector data. It results the map becomes less consistent it was before. To solve this, when partnering with GISCorps to map Malakal http://tasks.hotosm.org/job/413 in South Sudan, I had created a grid of offset correction points with the great offset_db plug-in for JOSM http://wiki.openstreetmap.org/wiki/Imagery_Offset_Database so that every contributor could, in two clicks, get the new imagery aligned on the Bing imagery, easily update the data and keep the data consistency. It worked really well. As we will get more and more access to recent imagery, my idea was to find a way to repeat this without relying to the previous action of a single person and spread the use of the offset_db plugin. Recently, in a workshop with various contributors in Burkina Faso, I tested a workflow involving the Tasking Manager and it worked also well. Next step is now to involve the crowd to this process. I created an OSM wikipage both in French and English (any correction by native speakers would be appreciated) : http://wiki.openstreetmap.org/wiki/OSM_Tasking_Manager/Offset_db and created a job for Bossangoa (http://tasks.hotosm.org/job/578) in Central African Republic, because our partners from the HIU kindly provided a recent NextView Imagery. Once you catch the workflow, you will see it is really quick to create offset corrections points and the outcome (the data consistency) are really substantial. Please join! Sincerely, Severin ___ HOT mailing list HOT@openstreetmap.org https://lists.openstreetmap.org/listinfo/hot
Re: [HOT] Keeping the data consistency when updating an area with a new imagery
Thanks Severin for turning the contents of this Burkina Faso workshop into those structured wikipages. Nico On Sun, Jul 6, 2014 at 3:06 PM, Severin Menard severin.men...@gmail.com wrote: Hi, When we get recent imagery over areas that have already been mapped with Bing imagery, very often it does not have exactly the same georeferencing, and very often we do not have any trace or not enough to fix this. Consequently, either the contributor will offset the new imagery on the vector data, or on the contrary will move the vector data. It results the map becomes less consistent it was before. To solve this, when partnering with GISCorps to map Malakal http://tasks.hotosm.org/job/413 in South Sudan, I had created a grid of offset correction points with the great offset_db plug-in for JOSM http://wiki.openstreetmap.org/wiki/Imagery_Offset_Database so that every contributor could, in two clicks, get the new imagery aligned on the Bing imagery, easily update the data and keep the data consistency. It worked really well. As we will get more and more access to recent imagery, my idea was to find a way to repeat this without relying to the previous action of a single person and spread the use of the offset_db plugin. Recently, in a workshop with various contributors in Burkina Faso, I tested a workflow involving the Tasking Manager and it worked also well. Next step is now to involve the crowd to this process. I created an OSM wikipage both in French and English (any correction by native speakers would be appreciated) : http://wiki.openstreetmap.org/wiki/OSM_Tasking_Manager/Offset_db and created a job for Bossangoa (http://tasks.hotosm.org/job/578) in Central African Republic, because our partners from the HIU kindly provided a recent NextView Imagery. Once you catch the workflow, you will see it is really quick to create offset corrections points and the outcome (the data consistency) are really substantial. Please join! Sincerely, Severin ___ HOT mailing list HOT@openstreetmap.org https://lists.openstreetmap.org/listinfo/hot -- Nicolas Chavent Humanitarian OpenStreetMap Team http://hot.openstreetmap.org/ Mobile (FRA): +33 (0)6 52 40 78 20 Email: nicolas.chav...@hotosm.org Email: nicolas.chav...@gmail.com Skype: c_nicolas Twitter: nicolas_chavent ___ HOT mailing list HOT@openstreetmap.org https://lists.openstreetmap.org/listinfo/hot
[HOT] Openaerialmap
Just wanted to say hi to all of you, working on restart of the open aerial map. Jachym P.s. greetings to all other list members as well. Send from cellphone ___ HOT mailing list HOT@openstreetmap.org https://lists.openstreetmap.org/listinfo/hot
