Mappt User Story: Building Market Linkages for Smallholder Farmers in Uganda

Innovations for Poverty Action (IPA) is a research and policy nonprofit that discovers and promotes effective solutions to global poverty problems. IPA brings together researchers and decision-makers to design, rigorously evaluate, and refine these solutions and their applications, ensuring that the evidence created is used to improve the lives of the world’s poor.


A project enumerator collects data from a respondent using Mappt on a Samsung-SM231 in a rural village in Uganda

Laza Razafimbelo is a research associate at IPA in Uganda. He works on the “Market Linkages for Smallhold Farmers in Uganda” project. Prices of staple foods like maize, beans, and rice vary substantially in Sub-Saharan Africa, depending on the season, country, and region. Addressing the imbalance in food supply and increasing farmer income may require a multi-pronged approach that tackles multiple barriers at once. The project is evaluating the impact of contract farming services and a mobile technology-enhanced trader alerts system on food markets across Uganda.

Why did you need to use a  Geographic Information System (GIS) in the project?

Laza: In planning the project, it was decided that a Geographic Information System (GIS) was required for 2 reasons;

  1. As a management tool, we needed to use it to keep track of the data collection process.
  2. As part of the project, we wanted to map the road to our study areas and collect information along the route.

Why did you need Mappt?

Laza: Mappt is the best road mapping app we could find on the market after testing several. It has a great support and sales team. One may be tempted to use the bunch of free apps on the market, but this made the difference and the quality of data from Mappt is incomparable to other applications.

What problems were occurring before Mappt?

Laza: Internet coverage is a big problem. The internet is not always guaranteed since we mainly work in the rural area of Uganda. We  found that paper materials were messy and inaccurate. We tried to collect some of the data (travel time, etc)  manually, but the data was inconsistent due to the inaccuracy.

How did you use Mappt?

Laza: We were using Mappt to help us to add the transport cost into our analysis. With Mappt, we were mapping the main commercial routes of our study areas. With the same tool, we also collected other data such as road quality type, travel time, etc. We subscribed to 9 licenses for a period of 2 months and we managed to collect all the different data that we wanted using only one tool – Mappt.

Why did you choose Mappt over other software?

Laza: We chose Mappt for a number of reasons – cost efficient, ability to work offline, brilliant attribute features and vector layers, good GPS coordination system and great support and sales team.

So how did the project turn out?

Laza: We are done with the data collection and will start the analysis.

What was the most valuable thing about Mappt?

Laza: Reliable tool (never got a bug), great support and sales team.

Final question – would you recommend Mappt to others? Why?

Laza: We highly recommended Mappt for any mobile GIS work for its reliability and the great team behind it. We have tried a lot of other apps but Mappt is way better.


Collecting field data using Mappt under the shade of a mango tree in rural Uganda


Try Mappt today by downloading it from the Google Play Store


Using Mappt to Collect Data in the Field, Part 3 of 3

This is the final installment in our 3-part series, which has been offering a simple user story that could form a workflow basis to be adopted by new or existing Mappt users.

If you haven’t read them, take a look at part 1, “Preparation,” here and part 2, “In the Field,” here.  Part 1 dealt with preparing your tablets and datasets, while part 2 covered importing, updating and exporting job data while in the field.

Returning to Base

Once you return to base, you will want to get your captured data off the tablet.

Within Mappt, this can be achieved by selecting a layer and then exporting the layer to email. Your tablet will then present a list of installed apps that will offer to transmit the data for you. This will include apps that are not email-centric, but are otherwise great options for sending data. For example, if you have Google Drive or other cloud-based storage solution installed, you will be able to upload your data there.

Google Drive (and other cloud-based storage apps) provide great ways to collaborate on data and combine datasets.

Another option is to simply email the data, perhaps to a team leader or other staff member responsible for coordinating data changes.

Screenshot of the Open From Google Drive button in Mappt

You can also export the data to a removable flash card and copy the files to the computer where you may have tools for integrating back into the project.

A final option is to plug your tablet into a computer via the USB cord and copy the files that way.


Integrating the data back into your project datasets is a matter of much greater discussion, involving concerns such as conflicts, merging, authority, etc. and will not be covered here.  As suggested above, this may be something that is handled by a nominated member of your team, using tools designed specially for this purpose.


We hope that the topics covered in this 3-part series have provided some tips on developing your own workflows.  Be sure to post your thoughts in the comments, as we love hearing user stories!

Using Mappt to Collect Data in the Field, Part 2 of 3

This is part 2 in a 3-part series that offers a simple User Story that could form the basis of a workflow to be adopted by new or existing Mappt users.

If you haven’t already, we suggest reading part 1, “Preparation” here, which discussed preparing your tablets and datasets for work in the field.

In the Field

When performing your duties in the field, you will import your Project Datasets into Mappt to assist in locating assets and referring to job information.  As suggested in phase 1, project datasets should not be edited; instead, data captured in the field should be logged into smaller, job template datasets.

When commencing a job, a new template should be imported and updated as the job progresses.

A good job template will allow you to easily capture new data while providing the structure necessary to capture quality, error-free data.  For Shapefiles, this would mean that the job template contains a pre-defined set of attributes, guiding the user to enter relevant data into the correct places.

If your work is conducted in an Internet-connected area, you may consider hosting and distributing your datasets over Google Drive via a shared folder.  Doing this will allow your administrative teams to provide consistently accurate datasets to your team, without the need to redistribute datasets via email or other manual methods.

Custom offline imagery can be loaded to assist with navigation in combination with the tablet’s GPS hardware. If your imagery is high-quality and correctly geo-referenced, you can use the imagery to position features on the map with a high degree of accuracy. This is perfect for when the GPS hardware is not accurate enough.

Thematic Mapping (previously known as Classifications) can be applied to larger datasets to locate features with certain attributes.  For example, consider a dataset containing markers that represent assets to be inspected, with an INSPECTED YES/NO attribute, indicating whether the asset requires inspection.  Using Thematic Mapping, the markers could be styled green to highlight the markers to be inspected, providing an easy method to visually indicate work to be done.

thematic mapping

Completing the Job

Once data has been obtained and the job complete, any captured data layers can be exported to the local storage of the tablet before moving on to the next job.

In phase 3, we will outline some options for retrieving the recorded data from the tablet for re-integration back into the project.

Using Mappt to Collect Data in the Field, Part 1 of 3

In the Mappt cave we are always interested in the workflows and procedures our customers employ when using Mappt in the field.

We find that most of these workflows consist of the same base necessities, regardless of the industry-specific nature of the work.

Over the next couple of posts, we will outline a simple 3-phase User Story that could form the basis of a workflow to be adopted by new or existing Mappt users. This workflow is presented from the perspective of managing a small team of Mappt users for a particular project, but applies equally to one Mappt user performing a single job.

The phases are:

  • Preparation
  • In the Field
  • Returning to Base

This post will cover phase 1, “Preparation,” with posts for phase 2 and 3 coming in the following weeks.


The Preparation Phase would involve gathering the relevant datasets and imagery to be deployed to the tablets. Ideally, the datasets and other files created during this phase would be deployed to the tablets just once, and remain relevant for the duration of the project.

One suggestion is to categorise your data into these groups:

Project Datasets

Project datasets (Shapefiles, ECW files, etc) that are relevant to the project as a whole. For example, a dataset for a project involving inspection parks may contain a spatial database of all parks to be inspected throughout the course of the project.

Screenshot showing an example Project Dataset

In this example, the Project Dataset consists of all of the parks to be inspected by field staff.

Job Templates

Job Templates are generally near-empty Shapefiles or Mappt Project files whose main purpose is to act as a template for data entry. This allows data to be collected in a uniform way, which is then exported on a per-job basis for re-integration into project datasets back at base.

Screenshot showing an example Job Template.

Note that as in the example above, Job Template Shapefiles must have at least one dummy feature defined; an empty Shapefile can not exist.  Once imported into Mappt, this dummy feature can be deleted.


The focus in the Preparation Phase is to create datasets that will require minimal manual handling or administrative intervention once the project commences. These datasets are deployed to tablets before the tablets are issued to staff.

This is especially useful for projects that require long-term disconnection from the Internet, whereby all relevant datasets can be copied to the device back at base, before transporting the tablets to the remote location.

Tune in next week for Phase 2: In the Field

GPS Tips and Tricks in Mappt for Android

One of the most-used features in Mappt is the ability to capture location data from internal or external GPS devices. With Mappt, users can record their movements throughout an area, turning this GPS-captured information into features.  These features can then be manipulated and annotated, then ultimately exported as Shapefile or KML, to be sent via email or uploaded to cloud-based technologies.

Based on the feedback we’ve received from Mappt users “in the field,” we’ve decided to highlight some tips and tricks when working with the GPS functionality in Mappt.

Image of a Baboon Sitting on a Cliff

Clearly lost, this baboon ponders the power of Mappt’s GPS capabilities.

Tip #1: “Walking Out” an Area

Did you know that, when you are in “polygon drawing mode” or “line drawing mode,” you can drop a new vertex at your current location? This is handy for “walking out” an area when you are in the field.  In the image below, I took a casual stroll around a sand pit, adding vertices at my current GPS location to a polygon as I went.

Partially-drawn polygon being mapped from the user's movements.

A partially-drawn boundary of the sand pit, using points dropped at my GPS position.

The resulting polygon is a bit messy, being subject to GPS inaccuracies, but could easily be tidied up within Mappt, or exported and tidied up on a desktop machine.

Polygon Created by "Walking Out" the Boundary

The completed polygon.

This minor feature provides a range of applications, from mapping boundaries as demonstrated above, to measuring paths or areas, to simply logging landmarks as markers on a map.

Tip #2: Take a Break on Large Trips

Mappt is capable of handling captured GPS paths with tens of thousands of vertices, but eventually performance will degrade under such weight.  We recommend pausing, saving then restarting the GPS tracker every hour or so, which will split your path into smaller segments.  These can later be stitched back together if necessary.  This will also allow you to hide unimportant segments using the visibility toggle button, which reduces the workload on Mappt and promotes responsiveness.

Screenshot of a segment of a captured GPS path with over 7000 points

Mappt will remain responsive, even when working with captured GPS paths with thousands of points

The rate of vertex collection will depend on several factors, such as speed and overall GPS activity, so you may want to experiment with the amount of time between saves.

Tip #3: Ditch the GPS and Use High-Res Imagery For Increased Accuracy

This tip may seem a bit out of place in a blog post about GPS tips, but it all falls under the category of georeferencing features in Mappt.  If you have high-res and accurately-georeferenced imagery of your remote location loaded into Mappt, you can use visual inspection of your surroundings to accurately place features on to the map. For example, you could determine your location by picking a nearby tree or rock formation and finding it in your offline imagery loaded into Mappt.  You can then be sure that a feature placed at that location in Mappt will have reasonable geospatial accuracy (as long as the georeferencing of the imagery is accurate!).

Tip #4: Mappt Will Continue to Capture GPS Data in the Background

As long as you leave the GPS tracking enabled within Mappt, it will continue to capture GPS data, even if you minimise or switch to another app.

Screenshot of the Mappt Background Service notification area item

Mappt will put an item in the Notification Area to let you know it is capturing GPS data.

Note that if you exit Mappt from within the menu (Menu -> Exit Mappt), Mappt will shut down the GPS and stop capturing points before it exits.