Retrieving Submissions Geodata
Submissions' geodata, one form field per submission, in GeoJSON format. If no particular field path is supplied, the first non-repeat geopoint/geotrace/geoshape field is used. No particular ordering is implied.
You can use an OData-style $filter query to filter the submissions.
Path parameters
The numeric ID of the Project
The xmlFormId of the Form being referenced.
Query parameters
An OData-style $filter query to filter the submissions by.
Impose a limit on the number of submissions to extract geoinformation from.
Extract geoinformation from the specified field. At most one field can be specified. If no field is specified, the first geofield not part of any repeatgroup is extracted from.
Response
OK
Submission geodata, in GeoJSON format. Geodata is grouped by submission. Submissions are represented as a GeoJSON "feature".
When the provenance of the geodata (the form's field path) is not evident from the request, the origin field path of the geodata will be denoted in a fieldpath property in the feature's GeoJSON properties object. This is the case in when no fieldpath query parameter is present, as in that situation the first geopoint-, geotrace-, or geoshape-field (not in any repeatgroup) of the form is used. And thus as forms get revised, what is the first geo-type field (not in any repeatgroup) may change; without the fieldpath extra information, the data provenance would be unclear.