Skip to main content

I received a geopackage named "test.GPKG". When I set up a reader I select OGC GeoPackage as format and browse for the dataset. I select "test.GPKG" and click "Parameters" to select the tables. But then I get a error message that no such file exists. FME does not recognise the extension when written in capital. In the message FME is looking for "test.GPKG.gpkg".

 

Solution: rename dataset to extention with lowercase letters. Like "test.gpkg". Then the tables are shown.

 

Question: Is this behavior wanted? Or should FME also recognise the extension written in uppercase letters?

 

Freek

Hi @vega1979​ , it seems that the OGC GeoPackage Encoding Standard requires file extension is ".gpkg", so I think the behavior - FME won't acknowledge ".GPKG" as an appropriate file extension - is intentional.

ogc-geopackage-encoding-standard-file-extension


The lower case is an OGC Standard.

The funny thing is that if you have an upper case extension and you declare it small case in the reader it just works. Both normal reader and FeatureReader have this behavior.


Hi @vega1979​ , it seems that the OGC GeoPackage Encoding Standard requires file extension is ".gpkg", so I think the behavior - FME won't acknowledge ".GPKG" as an appropriate file extension - is intentional.

ogc-geopackage-encoding-standard-file-extension

Hi @Takashi Iijima​, thank you very much for your answer. It is clear that the lower case extension is intentional. I contacted my client to look in to this. What application do they use that is causing the uppercase extension.

Thanks.


The lower case is an OGC Standard.

The funny thing is that if you have an upper case extension and you declare it small case in the reader it just works. Both normal reader and FeatureReader have this behavior.

Hi @caracadrian​ , good to see you have the same experiance as I did. Thanks for conferming it OGC standard.


Reply