I have a question about best practices in storing geolocated form data from the ODK Central API.
User story: I am retrieving form submissions with a
geopoint field from KoboToolbox and ODK Central APIs, and storing those in a GeoJSON-like format with the form fields stored in a
properties array, and
coordinates in a
The KoboToolbox API offers a special metadata
_geolocation field for submissions, which appears to inherit any geolocation data captured during form entry. This makes it quite straightforward to store Kobo submissions in a GeoJSON-like format: I simply pass the
_geolocation_ value to
However, from what I can tell it doesn't appear that the ODK Central API provides any special geolocation fields for submissions. So unless I'm wrong, it seems that I would need to iterate through the fields returned by the Submission XML endpoint to find anything resembling valid lat/long pairs. This isn't ideal and could run into edge cases, so I wanted to ask:
- Is there currently a more straightforward way to retrieve geolocation data using the ODK Central API that I might have missed?
- Are there any plans in the pipeline to add a geolocation field to submission metadata along the lines of what the KoboToolbox API offers?