Skip to main content
Solved

Modify / add additional file extensions on an existing reader

  • November 21, 2024
  • 6 replies
  • 70 views

charisph
Contributor
Forum|alt.badge.img+3

Hi 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

View original
Did this help you find an answer to your question?

6 replies

jobvdnoort
Supporter
Forum|alt.badge.img+10
  • Supporter
  • November 21, 2024

Is 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.

 


charisph
Contributor
Forum|alt.badge.img+3
  • Author
  • Contributor
  • November 21, 2024

It 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.


jobvdnoort
Supporter
Forum|alt.badge.img+10
  • Supporter
  • November 21, 2024

You can use the format: Esri Arcgis Layer 

in the FeatureReader for this: 

 


jobvdnoort
Supporter
Forum|alt.badge.img+10
  • Supporter
  • November 21, 2024

I 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.

 


bwn
Evangelist
Forum|alt.badge.img+26
  • Evangelist
  • Best Answer
  • November 21, 2024

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


charisph
Contributor
Forum|alt.badge.img+3
  • Author
  • Contributor
  • November 21, 2024

Dear BWN you are a LIFE Saver!!!! I struggle since longtime with this problem!

THANKS a LOT


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings