in FME 2020 the behaviour of Generic Reader changed in a way, that "Guess format from extension" for GPKG now defaults to GEOPACKAGE_RASTER instead of GEOPACKAGE (vector). This broke a workflow in our application. Why was this changed ?
+10- Contributor
- 106 replies
It may be an old question, an answered question, an implemented idea, or a notification-only post.
Please check post dates before relying on any information in a question or answer.
For follow-up or related questions, please post a new question or idea.
If there is a genuine update to be made, please contact us and request that the post is reopened.
+56- Safer
- 2554 replies
It could be that the last time you manually selected a gpkg file, you selected Raster Geopackage, and now the generic reader thinks this is correct for all files. I would manually add a gpkg file to a new workspace using the Vector Geopackage reader. Then it's possible that the Generic reader action will be reversed.
In short: it's just using the last format you used manually.
+10- Contributor
- 106 replies
It could be that the last time you manually selected a gpkg file, you selected Raster Geopackage, and now the generic reader thinks this is correct for all files. I would manually add a gpkg file to a new workspace using the Vector Geopackage reader. Then it's possible that the Generic reader action will be reversed.
In short: it's just using the last format you used manually.
Thanks Mark for the explanation.
I fixed the problem by passing the desired format as a parameter to the workspace for the Generic Reader instead of relying on defaults which are getting more and more unpredicatable ;-)
+11- Contributor
- 105 replies
It could be that the last time you manually selected a gpkg file, you selected Raster Geopackage, and now the generic reader thinks this is correct for all files. I would manually add a gpkg file to a new workspace using the Vector Geopackage reader. Then it's possible that the Generic reader action will be reversed.
In short: it's just using the last format you used manually.
Hi @mark2atsafe,
I have the same problem and I've never used the Raster Geopackage Reader. Unfortunatley this issue prevents users to load data in geopackage vector format in a dynamic workspace I have published to FME Server. I will have to use the same workaround as mhab.
In case of news about this issue, please let me know.
Thanks!