How to deal with GDAL options like GPKG spatial index

[eoudejans]

We have observed that every commit GPKG recreates the spatial index, and that creating a spatial index is the default behavior. And for large domains there can be a lot of tiles that will be committed on a per-tile basis. This behavior can be explained by the nature of the dataset type: a sql database that can be used by multiple users at once. For our applications however it is seldom necessary, and not used by the GeoDMS engine.

Turning the GPKG spatial index off can be done using:
parameter<string> GDAL_LayerCreationOptions: ['SPATIAL_INDEX=NO']

However if the user decides to do use the spatial index, the best strategy is to use it after the GeoPackage is created.

To this end a new GDAL_XYZ config setting could be introduced: GDAL_AfterCreationOptions: ['SPATIAL_INDEX=YES']. Which consists of by GeoDMS defined options that can better be performed after creation, like spatial index.

[eoudejans]

gdal will be called with default options, unless the user overrules these options.

[eoudejans]

To be implemented: issue specific warnings in case of possible performance penalties. For instance the GeoPackage spatial index creation on a per-commit basis.