Downloading layer as Geopackage provides a file with .x extension

[severinmenard]

Cf screenshot:

If you manually replace .x by .gpkg, the file opens well in QGIS and is well interpreted as a gpkg, so basically the export format is good, only the extension goes wrong.

For a test: https://ifl.francophonelibre.org/mapstore/#/viewer/openlayers/375

[landryb]

fwiw, trying to repro, i see that even if logged in to georchestra, there's a WPS call made to geoserver that triggers a 401 auth:

https://ifl.francophonelibre.org/llg/ows?service=WPS&version=1.0.0&REQUEST=DescribeProcess&IDENTIFIER=gs:DownloadEstimator,gs:Download

the headers sent by geoserver all seem to have the right information for the returned file name:

Content-Disposition: attachment; filename=osm_cohesion_biomedical.gpkg
Content-Type: application/xml;charset=UTF-8
Content-Length: 321

but it seems in addition to the file, it also sends an xml error (the 321 bytes):

<?xml version="1.0" encoding="UTF-8"?><ows:ExceptionReport xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:ows="http://www.opengis.net/ows" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" version="1.0.0" xsi:schemaLocation="http://www.opengis.net/ows https://ifl.francophonelibre.org/llg/schemas/ows/1.0.0/owsExceptionReport.xsd">
<ows:Exception exceptionCode="NoApplicableCode">
<ows:ExceptionText>java.io.IOException: Error occurred creating table
Error occurred creating table
Unable to map tags_hstore( org.geotools.data.postgis.HStore)</ows:ExceptionText>
</ows:Exception>
</ows:ExceptionReport>

im not much sure that mapstore is the problem here ? @pierrejego ?

[landryb]

i suppose that you installed https://docs.geoserver.org/latest/en/user/community/geopkg/ to get geopackage format ? it doesnt seem supported by default in geoserver.

[Gaetanbrl]

Thanks @landryb for this reply. GS 2.17 geopkg extensions seems fully installed.

In addition, geopkg seems correctly working when i create export from geoserver directly (preview menu). Something seems wrong between MS2 and geoserver.

[severinmenard]

Any update from GeoSolutions about this bug?

[tdipisa]

@severinmenard this is an old problem. I don't remember it fully in detail, but you might find this issue helpful. Ensure your MS configuration is correct maybe, here the online documentation of the tool that we have updated working on the linked issue.