Skip to main content
Question

OGCGEOPACKAGE Reader doesn't recognise extension in capital .GPKG

  • January 31, 2022
  • 4 replies
  • 54 views
V

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

4 replies

takashi
Celebrity
  • takashiCelebrity
  • January 31, 2022

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

Why not inspect features with Visual/Data Preview and Feature/Record Information before writing them into a destination dataset?
caracadrian
Contributor
Forum|alt.badge.img+23
  • caracadrianContributor
  • Contributor
  • February 1, 2022

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.

V
  • vega1979
  • Author
  • February 1, 2022

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.

V
  • vega1979
  • Author
  • February 1, 2022

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.

Community Stats

32,184
Posts
122,181
Replies
39,856
Members

Latest FME

Terms & ConditionsCookie settingsAccessibility statement
A product of
Safe Software respectfully acknowledges that we live, learn and work on the traditional and unceded territories of the Kwantlen, Katzie, and Semiahmoo First Nations.