We are only going to implement this on Connect for connect queries. If users want to get the uuids they will have to pass an additional parameter to the query api (something like includeuuids=true). This will only be applicable for some queries types (observation and waypoint queries types).

Added a "includeuuids=true" parameter the query API.

This option has been added to the following query types. If supplied for other query types it is ignored.

• All Data Observation Queries
• All Data Incident Queries
• Patrol Incident Queries
• Patrol Observation Queries
• Asset Incident Queries
• Asset Observation Queries
• Entity Incident Queries
• Entity Observation Queries
• Survey/Mission Incident Queries
• Survey/Mission Observation Queries

Supported in csv, geojson, and shp output formats

For Incident Queries:

• a single Waypoint UUID column will be added that is populated with a string representation of the UUID (eg. 70c6985ee08f4853b5ef51a80296239e)

For Observation Queries

• a Waypoint UUID column is added and populated with the string representation of the waypoint uuid
• an Observation UUID column is added that is either null (if there is no observation for the waypoint) OR the string representation of the observation uuid

Note: this it is possible to add patrol_uuids, mission_uuids etc if required. We just need to know the list of requirements.

As a part of this work I also update the geojson export so it doesn't truncate attribute names anymore.

Working as expected in 6.1.a4