Re: [HOT] Ebola Outbreak Guinea - West Africa, Mapping to support CartONG - MSF-CH - IFRC

[nicolas chavent]

Translating Pierre into French for those mapping in this activation from
French speaking countries and not comfortable with Engliah

Hier (6-Avril), cette activation est entrée dans son 12eme jour : 336
contributeurs, 1,5 millions d'objets modifiés et plus de 140 000 bâtiments
cartographiés.
Ce support massif et constant de la communauté OSM est grandement apprécié
par les travailleurs humanitaires qui font face sur le terrain à une
épidémie très complexe à enrayer et circonscrire

L'imagerie SPOT-6 D'Airbus Imagery dont l'accès et la mise en ligne ont été
assuré par Jean-Guilhem a donné lieu à un projet cartographique listé sur
le Gestionnaire de tâche de HOT et déjà quasi achevé !

Nous enjoignons des mappers expérimentés de la communauté à se porter dans
la même région sur le projet cartographique 497 [1] du gestionnaire de
táche de HOT afin de valider la classification des routes ainsi que les
polygones relatifs à l'usage du sol.
Il s'agit là d'informations importantes pour constituer respectivement de
bonnes ressources de navigation GPS/ordiphones/tablettes (sites
telechargements osmAND et GPS) ou des données de qualité en entrée pour la
préparation d'estimations de population.

Encore une fois merci pour votre engagement et merci par avance pour votre
fidèlité à cette activation

++
Nico

[1] = http://tasks.hotosm.org/job/497

On Mon, Apr 7, 2014 at 6:18 PM, Pierre Béland  wrote:

> Up to yesterday, this Activation has been now running for 12 days, and 336
> contributors added/modified, 1.5Million objects and 140 thousand buildings,
> This constant support of the OSM community is greatly appreciated by the
> humanitarian on the ground facing a very complex epidemy to manage.
>
> From the SPOT-6 Airbus imagery obtained by Jean-Guilhem Cailton friday,
> the Task manager job is mostly completed.
>
> Covering this same region, a new task is for experienced mappers to go
> through and validate Landuse polygons and the road classification. These
> are important both to let prepare good estimates of population and to
> provide good navigation tools for the region (ie. GPS and Android OSMAnd
> downloads).
> See http://tasks.hotosm.org/job/497
>
>
> Pierre
>
> ___
> 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

Re: [HOT] Spot-6 images of Guinée / Northern Liberia available, job 489

[nicolas chavent]

Again and one more time, a huge thanks for your continued work around
imagery Jean-Guilhem

++
Nico


On Mon, Apr 7, 2014 at 8:36 PM, Michael Judex  wrote:

> Hi Jean-Guilhem, thanks for the explanations and the helpful link! As
> always there are a lot of treasures you only need to know where to look...
> (but not easy to find the layers list with my limited knowledge of
> French...) Allow me a wish: to see such meta-information on the wiki page
> of an activation in an webmap (but cant do that by my own).
>
> cheers,
> Michael
>
> Am 05.04.2014 22:17, schrieb Jean-Guilhem Cailton:
>
>  A better answer to your question : on VISOV's Umap used to track news
>> about the Ebola outbreak, boundaries for high resolution imagery layers can
>> be switched on and off (in the layer menu, icon is near top left) (grouped
>> by when they where made available) :
>>
>> http://umap.openstreetmap.fr/fr/map/esov-suivi-epidemie-
>> ebola_6356#10/8.5640/-9.7806
>>
>
>
> ___
> 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

Re: [HOT] Spot-6 images of Guinée / Northern Liberia available, job 489

[Michael Judex]

Hi Jean-Guilhem, thanks for the explanations and the helpful link! As 
always there are a lot of treasures you only need to know where to 
look... (but not easy to find the layers list with my limited knowledge 
of French...) Allow me a wish: to see such meta-information on the wiki 
page of an activation in an webmap (but cant do that by my own).


cheers,
Michael

Am 05.04.2014 22:17, schrieb Jean-Guilhem Cailton:
A better answer to your question : on VISOV's Umap used to track news 
about the Ebola outbreak, boundaries for high resolution imagery 
layers can be switched on and off (in the layer menu, icon is near top 
left) (grouped by when they where made available) :


http://umap.openstreetmap.fr/fr/map/esov-suivi-epidemie-ebola_6356#10/8.5640/-9.7806



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

Re: [HOT] Ebola Outbreak Guinea - West Africa, Mapping to support CartONG - MSF-CH - IFRC

[Pierre Béland]

Up to yesterday, this Activation has been now running for 12 days, and 336 
contributors added/modified, 1.5Million objects and 140 thousand buildings, 
This constant support of the OSM community is greatly appreciated by the 
humanitarian on the ground facing a very complex epidemy to manage.


>From the SPOT-6 Airbus imagery obtained by Jean-Guilhem Cailton friday, the 
>Task manager job is mostly completed. 

Covering this same region, a new task is for experienced mappers to go through 
and validate Landuse polygons and the road classification. These are important 
both to let prepare good estimates of population and to provide good navigation 
tools for the region (ie. GPS and Android OSMAnd downloads).
See http://tasks.hotosm.org/job/497
 

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

Re: [HOT] imagery request coordination tool

[Mark Cupitt]

Here is my GIST I created from geojson,io for The Tharparkar Project. I am
still experimenting with it at the moment

https://gist.github.com/MarkCupitt/36ed71fadce731ea8bde

Cheers

Mark



Regards

Mark Cupitt

"If we change the world, let it bear the mark of our intelligence"

See me on LinkedIn 

*See me on StackExchange *

===
The contents of this email are intended only for the individual(s) to whom
it is addressed and may contain
confidential or privileged information. If you are not the intended
recipient, you must not disclose, copy, distribute,
or use the contents of this email. If you have received this email in
error, please notify the sender immediately and
delete the email and any attachments.
===



On Mon, Apr 7, 2014 at 8:41 PM, Mark Cupitt  wrote:

> Hi All
>
> You may want to check out GitSpatial (http://gitspatial.com/) which
> integrates with http://geojson.io
>
> Cheers
> Mark
>
>
> Regards
>
> Mark Cupitt
>
> "If we change the world, let it bear the mark of our intelligence"
>
> See me on LinkedIn 
>
> *See me on StackExchange *
>
>
> ===
> The contents of this email are intended only for the individual(s) to whom
> it is addressed and may contain
> confidential or privileged information. If you are not the intended
> recipient, you must not disclose, copy, distribute,
> or use the contents of this email. If you have received this email in
> error, please notify the sender immediately and
> delete the email and any attachments.
> ===
>
>
>
> On Mon, Apr 7, 2014 at 7:52 PM, Mikel Maron  wrote:
>
>> Hi
>>
>> > As the specs for a software tool are coming together here I have a
>> suggestion for a very bare minimum measure:
>> >
>> > Use a Github repo and issues for requesting imagery. Each issue should
>> describe the imagery needed with
>> > a http://geojson.io/ polygon describing the extent and should say what
>> resolution is needed / purpose the imagery is needed for.
>> > There is one repo per incident. As soon as someone starts sourcing
>> imagery they should say so on the corresponding issue.
>>
>> Yea, was considering that for a start, GitHub+geojson.io could be a good
>> working proof of concept, at least, if not more. I think one repo per
>> incident might be more than necessary; could probably manage to label
>> issues with tags or milestones to assign them to activations. One maybe
>> simple thing that would make this even more useful for us would be an
>> optional Bing layer on geojson.io; Alex do you think that's possible?
>>
>> Pierre, Andrew, what do you think about adopting this a trail for the
>> continuing Ebola response?
>>
>> -Mikel
>>
>> * Mikel Maron * +14152835207 @mikel s:mikelmaron
>>
>>
>>On Saturday, April 5, 2014 5:35 AM, Pierre Béland 
>> wrote:
>>
>> This is a discussion we already had for Haiyan on the Coordination room
>> with OCHA and Red Cross. For major activations, it would surely be
>> important to have an Imagery monitoring tool that give to various actors
>> the capacity to visualize the same info, add various entries / tickets
>> containing AOI's bbox coordinates. A map could synthetise the various AOI's
>> and imageries available, the possibility of the various actors to comment
>> on a specific task / request would be also important.
>>
>> For Haiyan, while we had many imageries for Tacloban, there were areas
>> where it took a long delay to obtain imagery. To have a better Imagery
>> Monitoring tools would surely have helped.
>>
>> One essential aspect we should not forget, it is important that the
>> coordinators be informed of the various groups that try to find imagery.
>>
>> Pierre
>>
>>   --
>>  *De :* Alex Barth 
>> *À :* Mikel Maron 
>> *Cc :* "hot@openstreetmap.org" 
>> *Envoyé le :* Vendredi 4 avril 2014 21h13
>> *Objet :* Re: [HOT] imagery request coordination tool
>>
>> Mikel -
>>
>> Right on, we need to work on coordinating imagery needs in emergencies.
>>
>> I've been involved a couple of times in the past in sourcing imagery for
>> emergencies and the key challenge for someone who's between the responding
>> community and potential sources like e. g. Digital Globe is to:
>>
>> a) find out what is needed
>> b) find out who is already trying to source what is needed
>>
>> The resulting confusion are me sending out obnoxiously duplicative
>> questions in times where I shouldn't waste people's time.
>>
>> As the specs for a software tool are coming together here I have a

Re: [HOT] imagery request coordination tool

[Mark Cupitt]

Hi All

You may want to check out GitSpatial (http://gitspatial.com/) which
integrates with http://geojson.io

Cheers
Mark


Regards

Mark Cupitt

"If we change the world, let it bear the mark of our intelligence"

See me on LinkedIn 

*See me on StackExchange *

===
The contents of this email are intended only for the individual(s) to whom
it is addressed and may contain
confidential or privileged information. If you are not the intended
recipient, you must not disclose, copy, distribute,
or use the contents of this email. If you have received this email in
error, please notify the sender immediately and
delete the email and any attachments.
===



On Mon, Apr 7, 2014 at 7:52 PM, Mikel Maron  wrote:

> Hi
>
> > As the specs for a software tool are coming together here I have a
> suggestion for a very bare minimum measure:
> >
> > Use a Github repo and issues for requesting imagery. Each issue should
> describe the imagery needed with
> > a http://geojson.io/ polygon describing the extent and should say what
> resolution is needed / purpose the imagery is needed for.
> > There is one repo per incident. As soon as someone starts sourcing
> imagery they should say so on the corresponding issue.
>
> Yea, was considering that for a start, GitHub+geojson.io could be a good
> working proof of concept, at least, if not more. I think one repo per
> incident might be more than necessary; could probably manage to label
> issues with tags or milestones to assign them to activations. One maybe
> simple thing that would make this even more useful for us would be an
> optional Bing layer on geojson.io; Alex do you think that's possible?
>
> Pierre, Andrew, what do you think about adopting this a trail for the
> continuing Ebola response?
>
> -Mikel
>
> * Mikel Maron * +14152835207 @mikel s:mikelmaron
>
>
>On Saturday, April 5, 2014 5:35 AM, Pierre Béland 
> wrote:
>
> This is a discussion we already had for Haiyan on the Coordination room
> with OCHA and Red Cross. For major activations, it would surely be
> important to have an Imagery monitoring tool that give to various actors
> the capacity to visualize the same info, add various entries / tickets
> containing AOI's bbox coordinates. A map could synthetise the various AOI's
> and imageries available, the possibility of the various actors to comment
> on a specific task / request would be also important.
>
> For Haiyan, while we had many imageries for Tacloban, there were areas
> where it took a long delay to obtain imagery. To have a better Imagery
> Monitoring tools would surely have helped.
>
> One essential aspect we should not forget, it is important that the
> coordinators be informed of the various groups that try to find imagery.
>
> Pierre
>
>   --
>  *De :* Alex Barth 
> *À :* Mikel Maron 
> *Cc :* "hot@openstreetmap.org" 
> *Envoyé le :* Vendredi 4 avril 2014 21h13
> *Objet :* Re: [HOT] imagery request coordination tool
>
> Mikel -
>
> Right on, we need to work on coordinating imagery needs in emergencies.
>
> I've been involved a couple of times in the past in sourcing imagery for
> emergencies and the key challenge for someone who's between the responding
> community and potential sources like e. g. Digital Globe is to:
>
> a) find out what is needed
> b) find out who is already trying to source what is needed
>
> The resulting confusion are me sending out obnoxiously duplicative
> questions in times where I shouldn't waste people's time.
>
> As the specs for a software tool are coming together here I have a
> suggestion for a very bare minimum measure:
>
> Use a Github repo and issues for requesting imagery. Each issue should
> describe the imagery needed with a http://geojson.io/ polygon describing
> the extent and should say what resolution is needed / purpose the imagery
> is needed for. There is one repo per incident. As soon as someone starts
> sourcing imagery they should say so on the corresponding issue.
>
> You could easily iterate from such a practice to a more integrated tool.
>
>
> Alex
>
>
>
> On Fri, Apr 4, 2014 at 2:50 PM, Mikel Maron  wrote:
>
>  Hi Everyone
>
> In conversation among the Guinea Ebola activation coordinators, we
> discussed the need and potential for a software tool for coordination of
> imagery requests. I wanted to share that idea here, and maybe we can expand
> on the requirements and possible implementations on list and at the
> technical working group.
>
> We have more options than ever for imagery for activations, and a lot of
> conversations going on at once. What's needed is something to collectively
> coordinate our options, to avoid inevitable crossing of wires.
>
> Such a system would include
> * Make and track Ar

Re: [HOT] imagery request coordination tool

[Mikel Maron]

Hi

> As the specs for a software tool are coming together here I have a suggestion 
> for a very bare minimum measure:
> 
> Use a Github repo and issues for requesting imagery. Each issue should 
> describe the imagery needed with 
> a http://geojson.io/ polygon describing the extent and should say what 
> resolution is needed / purpose the imagery is needed for. 
> There is one repo per incident. As soon as someone starts sourcing imagery 
> they should say so on the corresponding issue.

Yea, was considering that for a start, GitHub+geojson.io could be a good 
working proof of concept, at least, if not more. I think one repo per incident 
might be more than necessary; could probably manage to label issues with tags 
or milestones to assign them to activations. One maybe simple thing that would 
make this even more useful for us would be an optional Bing layer on 
geojson.io; Alex do you think that's possible?

Pierre, Andrew, what do you think about adopting this a trail for the 
continuing Ebola response?

-Mikel

* Mikel Maron * +14152835207 @mikel s:mikelmaron


On Saturday, April 5, 2014 5:35 AM, Pierre Béland  wrote:
 
This is a discussion we already had for Haiyan on the Coordination room with 
OCHA and Red Cross. For major activations, it would surely be important to have 
an Imagery monitoring tool that give to various actors the capacity to 
visualize the same info, add various entries / tickets containing AOI's bbox 
coordinates. A map could synthetise the various AOI's and imageries available, 
the possibility of the various actors to comment on a specific task / request 
would be also important.
>
>
>For Haiyan, while we had many imageries for Tacloban, there were areas where 
>it took a long delay to obtain imagery. To have a better Imagery Monitoring 
>tools would surely have helped. 
>
>
>One essential aspect we should not forget, it is important that the 
>coordinators be informed of the various groups that try to find imagery.
> 
>Pierre 
>
>
>
>
> De : Alex Barth 
>À : Mikel Maron  
>Cc : "hot@openstreetmap.org"  
>Envoyé le : Vendredi 4 avril 2014 21h13
>Objet : Re: [HOT] imagery request coordination tool
> 
>
>
>Mikel -
>
>
>Right on, we need to work on coordinating imagery needs in emergencies.
>
>
>I've been involved a couple of times in the past in sourcing imagery for 
>emergencies and the key challenge for someone who's between the responding 
>community and potential sources like e. g. Digital Globe is to: 
>
>
>a) find out what is needed
>b) find out who is already trying to source what is needed
>
>
>The resulting confusion are me sending out obnoxiously duplicative questions 
>in times where I shouldn't waste people's time.
>
>As the specs for a software tool are coming together here I have a suggestion 
>for a very bare minimum measure:
>
>
>Use a Github repo and issues for requesting imagery. Each issue should 
>describe the imagery needed with a http://geojson.io/ polygon describing the 
>extent and should say what resolution is needed / purpose the imagery is 
>needed for. There is one repo per incident. As soon as someone starts sourcing 
>imagery they should say so on the corresponding issue.
>
>
>You could easily iterate from such a practice to a more integrated tool.
>
>
>
>
>Alex
>
>
>
>
>
>On Fri, Apr 4, 2014 at 2:50 PM, Mikel Maron  wrote:
>
>Hi Everyone
>>
>>
>>In conversation among the Guinea Ebola activation coordinators, we discussed 
>>the need and potential for a software tool for coordination of imagery 
>>requests. I wanted to share that idea here, and maybe we can expand on the 
>>requirements and possible implementations on list and at the technical 
>>working group.
>>
>>
>>We have more options than ever for imagery for activations, and a lot of 
>>conversations going on at once. What's needed is something to collectively 
>>coordinate our options, to avoid inevitable crossing of wires.
>>
>>
>>Such a system would include
>>* Make and track Area of Instance boundaries.
>>* Form for standard set of questions when requesting imagery (ie justifying 
>>humanitarian need)
>>* Show available Bing imagery for those areas.
>>* Show available imagery from other providers.
>>* Links to associated tasking manager jobs.
>>* Comments/interaction on each AOI, so coordinators and imagery providers can 
>>stay informed of progress.
>>* Flexible permission/visibility.
>>
>>
>>Look forward to hearing from those interested on this idea!
>>Mikel
>> 
>>* Mikel Maron * +14152835207 @mikel s:mikelmaron
>>___
>>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

Re: [HOT] HOT Tech WG Meeting X+10

[Dražen Odobašić]

A short reminder, HOT Tech WG meeting is today at 17:00 UTC

http://www.timeanddate.com/countdown/generic?p0=1440&iso=20140407T17&msg=HOT%20Tech%20WG%20Meeting%20X%2b10

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