...
Exports to the multi table formats KML or GeoPackage, will only export to a single table creating a new or overriding an existing file.
Attachment fields
Attachment fields in Konect can contain more than 1 attachment, so when exported are normalised into their own export files per field. The attachment field files are exported in the same format as the dataset and into the same folder, named the same as the specified dataset file but concatenated with the attachment field’s export name.
...
Photos that are being exported to the same folder over multiple exports will not be overridden if the annotation changes between exports.
Attachment logs
An attachment log file for each attachment field that is exported will also be generated giving the details of how each attachment was dealt with during export. This file is generated in the specified export folder as a CSV file.
Transaction history
The Konect CLI can also export the entire transaction history for a dataset. Queries can be used, but unless a record matched the query through out it’s entire transaction history, it will be missing transactions. For this reason we do not recommending performing transaction history exports on queries. Transaction history exports do not include attachments, or attachment transaction history.
Konect CLI export commands
The Konect CLI has the following data export commands
...
$ konect csvexport -k [API_KEY] -e [ENVIRONMENT_NAME] -d [DATASET_NAME] -f [FILE_NAME] [other parameters and flags]
Konect CLI export parameters and flags
The following are all the parameters and flags available to the Konect CLI data exports.
...