Can SurveyCTO capture GPS coordinates/geo-location data?


SurveyCTO has very robust support for capturing geo-location data/GPS coordinates. To capture GPS coordinates, you just need to add a geopoint field in your survey. When surveyors arrive at that field, they will see a button they can tap to capture the GPS coordinates of their location.

The field will record the following information: their longitude, latitude, altitude, and the accuracy, in meters, at the time the GPS coordinate was captured.

You are also not limited to solitary GPS coordinates. You could place a geopoint field in a repeat group, or make use of the geotrace or geoshape field types to map the boundaries of an area.

You can read more about collecting GPS data here.

SurveyCTO also has functions you can use on captured geopoints to obtain additional data:

1. distance-between(): Use this function in a calculate field to automatically calculate the distance, in meters, between two different GPS coordinates captured in your survey.

2. area()Use this function to calculate the area, in meters-squared, enclosed by 3 or more GPS coordinates captured in your survey form. For example, this function would be useful if you wanted to calculate the area of a plot of land. This works on a repeated geopoint field or a geotrace or geoshape field.

3. short-geopoint(): Use this function if you want a field that only contains the longitude and latitude information and does not include the altitude and accuracy data captured in the original geopoint field.

To get details on how to use each of the above functions and their full syntax, please read this help guide.

And don't forget! After you've captured your geolocation data, you can use SurveyCTO's integrations with Google Earth or with any other system via Zapier or Google Sheets as an intermediary. 


Functions and operators referenced in this article: distance-between(), area(), short-geopoint(). For a full list of SurveyCTO functions and operators, please read this help guide.

Do you have thoughts on this support article? We'd love to hear them! Feel free to fill out this feedback form.


Article is closed for comments.