"The other option would be add a parameter to the query api (includeuuids=true/false). Then for query types that we want to support, when we see this parameter we add another query column to the output. The JSON writer would automatically pick this up and include it in the output (so would the other formats csv, shp). "

We should support all the query types that make sense to keep things consistent. The types Vulcan needs at the moment are observation, patrol and patrol observation queries.

An updated 6.2.3 Connect war file with this change made would be needed for them to keep testing their integration on their example servers.