GeoGig and plugin: Analysis of current functionality and limitation

[MarkusHesse42]

Open points:

• Supported field types (uuid, vectors of data, ...)
• Export to postgres (differential export...)
• Differential import from postgres
• Error handling (should work, to be tested)
• ...

First results on field types:

Type	Import	Export Geopkg
boolean	OK	Failed
bigint	OK	OK
character varying	OK	OK
date	OK	OK
real	OK	OK
text	OK	OK
numeric	OK	OK
bigint[]	OK	OK
timestamp	OK	OK
uuid	OK	Failed

Summary: Import to geogig works for all tested field types. Export to GeoPackage fails for boolean and uuid.
I created the following issues on the geogig bug tracker for these problems:

• boolean: Table with boolean field not exported to GeoPackage locationtech/geogig#407
• uuid: Table with uuid field not exported to GeoPackage  locationtech/geogig#408

Further basic limitations are:

• There is no real delta export of changes from geogig to postgres (GeoGig: Implement (differential) export to postgis #17)
• Created GeoPackages are not indexed and lead to problems in QGis (Export to GeoPackage does not create a spatial index locationtech/geogig#409)
• Tables without geometry cannot be exported to GeoPackage for use in QGis (Export of table without geometry fails locationtech/geogig#399)