| … on Update: Missing Persons Data | |
| … on Biggest gap in this whole digi… | |
 | patrick on Hey @Caleb, Here are some desi… |
 | caleb on Hey @Caleb, Here are some desi… |
<a href="http://haiti.ushahidi.com/"><img src="http://sitroom.ushahididev.com/wp-content/uploads/help-haiti.png"></a>
<a href="http://haiti.ushahidi.com/help" title="Support Haiti Disaster Relief"><img src="http://sitroom.ushahididev.com/wp-content/uploads/btn-submit-report.png" /></a>
<a href="http://haiti.ushahidi.com/reports/submit" title="Submit a Report"><img src="http://sitroom.ushahididev.com/wp-content/uploads/btn-donate.png" /></a>
Ushahidi Situation Room Feed
Again, thanks to the InSTEDD team for providing this technology situation report for Haiti. This is an overview of the last 24 hours worth of work within the community.
Download the Word Doc:
Haiti Technology Community Situation Report – 17 Jan 2010
Read it online below:
(More …)
Update from InSTEDD. They’re working on a what they’re calling “SMS 2 Geo” project for getting much more accurate geodata on incoming messages and reports. More information that is forthcoming, and they’ll need some help with UI and UX for that once the initial core coding is done.
If you want to help, get in touch with Luke Beckman: beckman@instedd.org
Reuters and InSTEDD are using 4636 too for messages, whereas at Ushahidi we’re handling the incoming ones and the database: http://www.reuters.com/article/idUSTRE60G16420100117
Anyone who texts into us will also receive from them.
Currently InSTEDD team in Haiti is setting up 5-10 local SMS gateways for outgoing SMS, just waiting on SIMs
Courtesy of the good folks at InSTEDD, here is a comprehensive situation report on the tech communities activities through 1/16/2010.
Download it as a Word Document:
Technology Community SitRep Haiti 6 Jan 2010
View it online below:
(More …)
InSTEDD’s most recent Situation Report that covers communications, mapping, coordination, medical and missing persons information as it pertains to the tech community working on the Haiti response.
Technology Community Situation Report 15-Jan, 2009 as of 2359 hours
Prepared by Luke Beckman, National Response Liaison, InSTEDD, +1-650-740-5853, Beckman@instedd.org
Download it as a Word Document here:
InSTEDD_SitRep_15-Jan-2009
Read it online below:
(More …)
InSTEDD kindly mentions the emails I have been sending. There is now an updated wiki with a more comprehensive information here – http://inventory.ict4peace.org/Haiti+Earthquake+-+January+2010
An older one, but good to catch up on if you’re new to the project
InSTEDD’s team of Luke Beckman and Nico di Tada are creating situation reports for both their organization and SOUTHCOM. These are comprehensive reports of the ongoing technical groups working on the Haiti earthquake response, and cover everything from mapping to communications to gaps where there are still needs to be addressed.
It’s available here as a Word document for download:
Summary_for_USSOUTHCOM_on_Open_Source_1-14-10a
Read it online below…
(More …)
Situation Report from the InSTEDD team:
Ushahidi is working on getting a Haiti shortcode (4636, being arranged by Digicel and paid for supposedly by US State Department. Should be up and running by morning 16-Jan) to get MOs. MTs won’t probably work. They have no details on how they are going to get the messages yet.
Original envisioned process was as follows:
1. Put word out that people on the ground can send [Name location status/message]
2. SMS submitted, with varying levels of structure/detail. SMS responds with information. For all messages, there will be a tinyurl that has more info on Haiti recovery.
3. Enters database
4. Passed to a mechanical turk type outfit for structuring/tagging
5. Message is structured in the database
6. Gets passed off to orgs (via Sahana) for action
————
WE MUST HAVE THE SENDER’s number
What Ushahidi will have:
- URL is 4636.ushahidi.com
- Ability to tag and structure SMS messages (note from nico: not sure what they mean with “structure”)
- Structure= family name, given name, geotag, category of report (note from nico: same here)
- Ability to re-expose feed via geoRSS
- Data can also be output in the SMS table
- When the SMS comes in, they will see where it needs to go and deal with it on main page.
What we need from them by priority:
1 – an RSS with the sender’s number as the author of the rss item
2 – make the previous rss a Geo-RSS with the location of the sender
3 – have the crowd-sourced tags as RSS tags.
4 – Have them parse the “register” or “registre” + mobile phone and relaying that to us somehow. (Juan, any ideas on something easy for them/us?)
What we (InSTEDD/Manas) need to do ASAP:
Related to MOs
0 – Switch the EIS EC2 instance to the biggest one we can get. We can’t afford timeouts or overloads.
1 – Make sure the RSS importer recognizes the author as a mobile phone number and adds it to the list of registered phones.
2- Paginate that list (Juan, I think it’s not being paginated, and it’s gonna get big very quick).
3- Code: if the incoming item is a mobile phone number and it has a geo location, add that as the location of that citizen. (Juan, if they send us the lat/lon, we are loosing the clustering thing, we might need to reverse geo lookup to cluster them, we will see when we get there, but be ready and respond quickly)
4 – Re-test tags into Riff from RSS tags.
5 – Provide support for whatever relaying method of invitees Ushahidi gives us.
Related to MTs
1 – To Juan: It’s going to be a while probably until we get a way of broadcasting MT’s, we can test Clickatell tomorrow, but we need to figure out a way of round-robin between several LGW.
Just heard from Nico of InSTEDD and the AlertNet team of Reuters on the ground. They are about to deploy a citizen based- well networked, Emergency Information Service. They say that if the 200 shortcode is going to happen, that is the most needed thing on the ground. They will be ready to use that shortcode in the morning.
Eddy is discussing. 
Eddy 7:37 pm on January 19, 2010 Permalink |
This is a fine, detailed and highly specific post. Please know how appreciated that is. Keep up the great work everyone.