Currently users are able to export their maps into a .geopkg file containing the geo data and style information. When they import the .geopkg file it will create a brand new dataset for the user. However in some cases the data they are exporting may be synchronization datasets or referenced via Postgres FDW and the user may wish to retain these properties. We would like to create a new .carto.geopkg file which store these data storage attributes following the geopkg spec per http://www.geopackage.org/spec/#extension_metadata.
In order to facilitate writing and reading this information during export and import respectively a library to write the metadata should be created.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
Context
Currently users are able to export their maps into a .geopkg file containing the geo data and style information. When they import the .geopkg file it will create a brand new dataset for the user. However in some cases the data they are exporting may be synchronization datasets or referenced via Postgres FDW and the user may wish to retain these properties. We would like to create a new .carto.geopkg file which store these data storage attributes following the geopkg spec per http://www.geopackage.org/spec/#extension_metadata.
In order to facilitate writing and reading this information during export and import respectively a library to write the metadata should be created.