Section outline

    • Introduction

      Now your maps are prepared and you have planned the points of interest to visit, you're almost ready to go to the field.

      In the field you will collect a large amount of data. The data needs to be collected and organised in such a way that they can be used in interpretation and further processing after the fieldwork.

      For every observation, experiment or measurement in the field, at least the following information must be recorded:

      • Location i.e. where was the data collected.
      • Date, time i.e. when was the data collected.
      • Descriptive data i.e. all observations and/or measured values.


      If you work in a team it is also important to add the name of the observer. This can be useful as a contact to ask additional information that was not recorded on field forms, but also to correct for systematic biases in observations. This can be for example the case with vegetation cover estimates.

      Hardcopy field forms

      Traditionally we use field forms to note our field observations or interview responses. Prior to the fieldwork you can prepare a standard data form that you can print as a field book. Alternatively you can use a plastified sheet with numbered observation information to collect. These numbers can be noted in a notebook.

      It is recommended to use notebooks at A-5 or A-6 format with a hard cardboard cover, which can be comfortably carried in the field without wearing or damaging.

      The produced fieldmaps are used in combination with the field forms. Field maps are in particular useful to directly indicate the location in the field where the observation was made. The observations locations are indicated on the fieldmap by a number and a symbol.

      The numbers used on the fieldmap are also recorded in the fieldbook or data forms, together with the collected information. Furthermore the fieldbook should provide general information, which may be worthwhile to recall at a later stage.

      Some more recommendations for using a fieldbook:

      • Always use a pencil to write in fieldbooks, data forms and on fieldmaps. The ink from a pen will stain during rainfall and render your observations unreadable.
      • For each day in the field, add a record in the fieldbook describing the general weather conditions. This can be important during the interpretation stage of the study and essential if you later need to look for satellite images for certain clear dates.
      • Make different forms for different types of observations. For example separate forms for geological and geomorphological observations.
      • When collecting samples, also label the sample with the number of the field location. Possibly write the location, date and time also on the sample. An extended number coding may be used if multiple samples are taken at one location. Use a water-proof ink marker to label samples.
      • Make sure that the date/time on devices are synchronized. In this way you can easily link for example pictures taken in the field to the field observation form for that location.
      • When you make an observation, also note the GPS coordinate. Although the coordinate is stored in the GPS, it's good to have a backup on the field form.
      • Note that the uncertainty in elevation measured with a GPS can be 3 times higher than in the X and Y coordinate. It is therefore recommended to use a calibrated barometric altimeter or DGPS if you need a high accuracy.
      • Make sketches of what you see in the field to make interpretation afterwards easier.


      Field data collection app

      Nowadays, however, it's quite easy to create your own field data collection app, without programming.

      Input is a simple survey app allowing users to capture data in field. Forms and data preparation can be done in QGIS software and synchronised with the Input app using the Mergin plugin and repository.

      Input is not aimed to be a full GIS/mapping application. It is designed with simplicity, ease of use and seamless data synchronisation in mind.

      A typical workflow for using Input consists of the following steps:

      1. Preparing project: user loads background and survey layers, set up the forms, apply styling to the layers, set up map themes and define the layers to be used for survey purpose.
      2. Data/project transfer: once the project set up, users need to transfer data to the device. This can be achieved through Mergin.
      3. Working with Input: map navigation, data editing, including filling the forms, viewing existing data and uploading the changes back to Mergin.


      Test your app before going to the field. You can still make changes to the design and add/remove/adjust fields and widgets in the form. If you work in a team, make sure that you do a test with the entire team before leaving to the field.


      Backups!

      Fieldwork data is very valuable and it is therefore important to keep a double administration the field observations. For hardcopy fieldbooks it is good practice to copy the field observation at the end of each field day. Obviously, the copied data are not to be taken into the field and kept in a safe, dry place during the fieldwork. An additional copy in a digital document is also recommended and, if set up in a good way, this can make processing of the data easier after the fieldwork.

      As with notebooks in the field, also with digital field forms it is very important to make backups! If you have an internet connection in the field it is recommended to regularly synchronize your collected data with the cloud. If you only have an internet connection in the base camp for the fieldwork, don't forget to synchronize to the cloud when you're back from the field. If you don't have internet at all, it is very important to save your collected data to backup disks/USB sticks. This is also recommended if there is internet. In that case you'll have the data on your phone, in the cloud and on a backup disk/USB stick.


      Tutorials