+3Hi all,
I would like to use an existing FME reader to open a file with an unsupported extension. Is there a workaround to achieve this? Alternatively, how can I clone an existing reader and modify it to support the desired file extension?
Thanks a lot! 🤓
hp
Best answer by bwn
Well….this might be simpler instead. It’s dumb, but it works on my version of FME (2021)
Add [**\*.gdb] to the Reader File Path. This works also for other Formats I’ve tried like Shape. This seems to force FME to treat whatever file path is input as an Archive container, no matter what the file extension is.
Eg.
https://docs.safe.com/fme/html/FME-Form-Documentation/FME-Form/Workbench/archive_files_reading.htm
+13Is the file readable in Notepad++ for example?
You can always read a file as text/csv when you know it is filled with ascii.
If you have some more information about the extension, or an example file you try to read, we can probably help you out a bit better.
+3It is a .lpkx file which I would like to read it with the File Geodatabase Reader but this reader does not support this extension. When i change the extension to .zip the File Gedotabase Reader reads it correctly.
+13I notice a similar issue when I have more layers in my LPKX.
A dirty workaround is to add a attribute creator:
Generate your destenation filename.ZIP.
And in the featurewriter just say file operation “Move” as your first manual workaround.
+26Well….this might be simpler instead. It’s dumb, but it works on my version of FME (2021)
Add [**\*.gdb] to the Reader File Path. This works also for other Formats I’ve tried like Shape. This seems to force FME to treat whatever file path is input as an Archive container, no matter what the file extension is.
Eg.
https://docs.safe.com/fme/html/FME-Form-Documentation/FME-Form/Workbench/archive_files_reading.htm
