Monthly Archives: July 2013

Announcement of Smap Release – July 2013

Yep we missed a release in June this release contains 2 months of changes. New Features:

  1. Exporting of surveys to Openstreetmaps.  Refer to http://blog.smap.com.au/?p=310 for details.
  2. Block submission of new results.  On the template management screen you can block or unblock a survey by clicking the checkbox next to the survey name.  This could be used where you have completed a survey and are analysing the results, however additional results are being submitted by someone who is demonstrating or testing the survey tool.
  3. Reports can be accessed by external systems through a reporting API. Download from here.
  4.  Reports can be embedded in WordPress blogs (or any other container that support the oEmbed standard).
  5. The bounding box of the area covered by a report is now shown rather than just showing a point for the report.
  6. Maps can be included in reports.
  7. The text that describes a graph or map has been improved. The text for a map now describes all the layers on the map.
  8. Validation on loading of templates.  The converted database friendly question names are now checked for duplicates.  Hence if you had a question named hdm0.1 and another hdm0x1. Then these would be reported as duplicates and the template would not be loaded. The reason that they are duplicates is that characters that are not accepted by the database as column names are converted into “x”.
  9. The XLS file that was submitted as a survey template can be downloaded from the template management page.
  10. Survey templates can be downloaded as a PDF.  This feature uses the Links Codebook code from Nafundi which has been modified to be accessible via a web service rather than on the desktop.
  11. Assignments of tasks are shown in a table as well as on the map.

The July version of the Smap server can be downloaded from here.

 

 

 

Exporting Surveys to Openstreetmap

I have added a new option to the Smap Server that will export a survey in OSM format. The following video shows this being used to add house numbers to Openstreetmap.

The survey from that video is defined in an XLSForm template reproduced below:
osmsurvey

This survey will collect the street name, odd or even, country, city, postcode in the top level form. It then collects the house numbers and their locations in a repeating group.  Some of the top level fields are copied into each house record using the “calculate” type.

I have adopted a couple of naming conventions for surveys that are destined to be exported to osm.

  1. Any question name that starts with an underscore, such as _country, is not exported.
  2. If the question name starts with “addr_”, then that is changed to “addr:”. The reason for this is that XLSForm did not seem to support the use of colons inside names but they are used in OSM key values.

I completed the survey twice to get the house numbers for a street called Jewell Crescent. When the results are exported the OSM file looks like this:

[code language=”xml”]

























































[/code]

After loading into Openstreetmap it looks like this.

This new functionality is in the source code now. It will be included in the next production release of Smap on Sunday 28th of July, after which the server can be downloaded from here.
Other Thoughts

  1. Currently option names map to OSM values.  This is quite restrictive as ODK does not allow these names to have spaces.  I will probably add an option to the export function that, if set, will use the option label to set the OSM value.
  2. You can export any survey to Openstreetmap.  Most of the time these won’t have been designed to be loaded directly as the demo was.  However it can still be useful to get the data into JOSM and then manually copy information into new OSM nodes.  For example if you have a survey with information on health clinics.

Connecting Openstreetmap to Smap

It may be time that Smap returned to its Openstreetmap roots  and created an application that can synchronise relevant data between Smap and OSM.

Data in Smap is accessible by a REST API which returns geoJSON.   Albeit that this sample is for a published report, live data normally requires a user id and password to access. The report that consumes this sample data url can be viewed here.  There is also a set of REST API calls that return details of available projects (collections of surveys), surveys, forms, questions and options. The Smap server is open source available at http://code.google.com/p/smap-suite/ and is easy to install on a linux server. Data can be collected with odkCollect, fieldTask or enketo Forms. All data is stored in Postgis and location for each survey record can be recorded as a point, polygon or linestring.

Possible objectives for the application would be:

  1. Get locations and attribute values from OSM to use in assigning a task for someone to conduct a survey at that location. http://www.youtube.com/watch?v=zuJlWIoSEhA
  2. Allow a user to transfer survey results into OSM either updating existing elements or creating new ones.  The first step would be to define the matches between OSM tags and Smap columns. The second step would be to manually process each record in Smap and apply a create or update operation on OSM.

 

 

 

 

 

 

Connected Arabic fonts in Android 2.3

I’m working with a customer that is conducting a survey in Iraq using Samsung Galaxy Y Duos (android 2.3) and fieldTask. Later model phones (android 3+) worked well with Arabic but not these earlier versions. Even after rooting the phones and installing new fonts it still didn’t connect the characters.  See below a screen shot using Dr Ben Ox Arabic fonts which seemed to give the best results.
arabic2 (1)

Fortunately there is an Arabic reshaping library available from https://github.com/agawish/Better-Arabic-Reshaper/ which can be used with these old phones. I added ArabicReshaper.java and ArabicUtilities.java from this library to the odkCollect library that performs survey completion in fieldTask. I then modified the “QuestionWidget.java”, “SelectOneWidget.java” and “SelectMultipleWidget.java” files in odkCollect to call the “reshape” function when setting the text. See line 12 below.

[code language=”java” highlight=”11,12″]
protected void addQuestionText(FormEntryPrompt p) {
String imageURI = p.getImageText();
String audioURI = p.getAudioText();
String videoURI = p.getSpecialFormQuestionText(“video”);

// shown when image is clicked
String bigImageURI = p.getSpecialFormQuestionText(“big-image”);

// Add the text view. Textview always exists, regardless of whether there’s text.
mQuestionText = new TextView(getContext());
// mQuestionText.setText(p.getLongText()); smap
mQuestionText.setText(ArabicUtilities.reshape(p.getLongText())); // smap
mQuestionText.setTextSize(TypedValue.COMPLEX_UNIT_DIP, mQuestionFontsize);
mQuestionText.setTypeface(null, Typeface.BOLD);
mQuestionText.setPadding(0, 0, 0, 7);
mQuestionText.setId(QuestionWidget.newUniqueId()); // assign random id

// Wrap to the size of the parent view
mQuestionText.setHorizontallyScrolling(false);

if (p.getLongText() == null) {
mQuestionText.setVisibility(GONE);
}

// Create the layout for audio, image, text
mediaLayout = new MediaLayout(getContext());
mediaLayout.setAVT(p.getIndex(), “”, mQuestionText, audioURI, imageURI, videoURI, bigImageURI);

addView(mediaLayout, mLayout);
}
[/code]

This improved the display significantly:
SC20130708-172712

This Arabic version of fieldTask is available for download from http://dev/smap.com.au. There are other widgets that could have this functionality added and presumably the arabic text typed by an enumerator in a text field should also be reshaped. These additional changes will be made on an as needs basis. The preferred option is to get a phone that supports Arabic fonts natively which would be a better option than having to root the phones to install new fonts.

Map with locations shown by OCHA icons

This is another test of embedding a Smap report into WordPress. Here is the report now.

The major change since the last test report is more space for the meta information and the creation of automatic commentary on the report.  For example the lines:

  1. Shows the location of responses to the question ‘Select type’ in survey ‘ocha’ grouped by the responses to the question Record location
  2. Shows the percentage of responses that selected each option in the question ‘Problems’ in survey ‘speed’ grouped by the responses to the question Set Location

These were automatically generated to describe the two layers of data on the map.  I think they could be clearer though.  The final line “Comment provided by DME manager” was typed in when the report was created in Smap and before it was published to WordPress.

Embedding into WordPress is a great way to publish reports as you can add supporting material.  For example here is a tweet.

Anyway for more information contact me at Smap Consulting.  neilpenman@gmail.com

 

Smap Reports API version 1.0 Released

The API can be used to retrieve report data from a Smap server.  This version is out of draft however it will evolve with feedback from the Speed Evidence project team and the Ushahidi developers who are creating a Portal that will consume the API.  Hopefully it should be fully implemented in Smap releases from the 1st of August.

Download from here.

The API will allow the proposed Speed Evidence Portal to present survey data alongside relevant community information submitted using SMS messages.

Statistical Analysis of Public Tweets to Provide Early Notification of Emergency Events

CSIRO have been developing software for monitoring social media.  Last monday I went to Canberra to talk to Ron Jones who is responsible for business development of these products.  We met, near his office on the ANU campus, at the Purple Pickle cafe.

We discussed two products but I am going to focus on the Emergency Situation Awareness application (ESA) for this blog post since its very relevant to the work that Smap Consulting does. The title of this post is a quote from a video produced by CSIRO showing how ESA works.

My understanding is that ESA analyses the frequency of occurrence of key words or hashtags in tweets over a period of several months. Then if there is a deviation from the background level of a word during a 2 minute window an alert will be created at one of 4 levels depending on the amount of deviation; green-blue-purple-red.  Here is a screen shot from the video showing alerts for the word storm around about the time a tropical storm hit Brisbane.

alerts

 

The second column is the date and time that the alerts began, the third column the duration that an elevated alert level was maintained and the 4th column the number of alerts during that period. ESA has an API that allows an external system to interrogate the statistical server.

This would be a great tool to integrate with Smap and Ushahidi to get a better picture of the situation after a rapid onset emergency.  ESA could be used to identify new events while Smap can be used to provide an assessment of that event.  The results can then be shown on a tool such as the Speed portal, further filtering the “firehose” of information that emergency workers can be subjected to.

Getting this tool applied to rapid onset emergencies in developing countries would require a little bit of effort and cash. For example currently only tweets in Australia are monitored.  Possibly we would need a server for Africa or Asia etc. However it looks very promising to me.

 

Smap API

I have been working on a project to allow reports from Smap to be added to a portal that provides an assessment of the situation in the first 72 hours after a rapid onset emergency. This is for World Vision’s Speed Evidence project, Ushahidi are writing the portal.

These new reports support oembed so they can be inserted into a wordpress blog such as this one. Here is a report containing a map.

The above report is a map from the Smap analysis dashboard showing:

  1. A select multiple question on problems grouped by an arbitrary set of hexagonal polygons.  The colours represent the relative percentages of interviewees who reported safety concerns in the hexagonal area.  Red indicates a very high percentage blue a very low percentage. Green is somewhere in the middle. (It follows the Red – Orange – Yellow – Green – Blue scale).
  2. A select one question on type of refugee camps in the area

Here is another report containing a graph showing the problems reported grouped by the gender of the person reporting the problem.

Finally here is a report containing a table.

This table shows the average age of the people who reported each problem.

This capability is still beta and will be released in 2-3 weeks.  Some of the work that still needs to happen includes:

  1. Setting the size of the report so it doesn’t leave whitespace when embedded in wordpress or another container
  2. Better legends and descriptions of the content of the report generated directly by the Smap server.