The geotrace question type in XLSForms and rtSurvey enables respondents to capture a series of connected points on a map, creating lines or paths. This feature is particularly useful for mapping routes, boundaries, or linear features in spatial surveys.

Basic XLSForm Specification

typenamelabel
geotraceriver_pathTrace the path of the river

For more details on the basic geotrace question type, see the XLSForm specification.

Uses

Geotrace questions are commonly used for:

  1. Mapping routes or paths taken during field surveys
  2. Tracing linear features like roads, rivers, or boundaries
  3. Capturing the extent of linear infrastructure (e.g., pipelines, power lines)
  4. Recording travel paths in transportation studies
  5. Defining transects in ecological surveys

Best Practices

  1. Ensure the device has location services enabled and permissions granted.
  2. Provide clear instructions on how to trace the path and what features should be included.
  3. Consider using satellite imagery or base maps to help respondents accurately trace paths.
  4. Be mindful of the potential complexity of traces and their impact on data size and processing.

Example Usage

Here’s an example of how you might use a geotrace question in a survey:

typenamelabelhint
geotracehiking_trailTrace the path of the hiking trailStart at the trailhead and end at the summit

rtSurvey Extensions

While the basic XLSForm specification for geotrace questions is straightforward, rtSurvey may offer additional features or customizations:

  1. Integration with offline maps for remote areas
  2. Options to set minimum and maximum number of points for the trace
  3. Ability to edit or refine traces after initial drawing
  4. Support for automatic tracing at set intervals during movement

(Note: The specific extensions available in rtSurvey for geotrace questions would need to be confirmed and detailed here.)

Data Format

Geotrace data is typically stored as a string of space-separated coordinate pairs, similar to geoshape but without the closing point:

  lat1 lon1; lat2 lon2; lat3 lon3; ... latN lonN
  

For example:

  38.253094215699576 21.756382658677467; 38.25021274773806 21.756382658677467; 38.25007793942195 21.763892843919166; 38.25290886154963 21.763935759263404
  

Considerations for Analysis

When using geotrace questions, consider:

  1. How the geographic data will be visualized and analyzed (e.g., GIS software)
  2. The potential need for data cleaning or simplification of complex traces
  3. Privacy and data protection measures for handling detailed spatial data
  4. Integration with other spatial data sources for comprehensive analysis

Limitations

  • Tracing accurate paths on small mobile screens can be challenging.
  • Complex traces may require significant storage and processing capacity.
  • Continuous GPS usage for automatic tracing can quickly drain device batteries.
  • There may be privacy concerns associated with collecting detailed path data.
Was this page helpful?