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

Screenshot showing an example Project Dataset

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.

Preparation

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.

Summary

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

2 replies

Trackbacks & Pingbacks

  1. […] 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 […]

Comments are closed.