Skip to main content
Solved

Duplicate records reading from zipped open file gdb

  • November 20, 2024
  • 1 reply
  • 34 views

helmoetz
Contributor
Forum|alt.badge.img+13

Hi this puzzles me: using FME(R) 2022.2.3.0 (20230131 - Build 22789 - WIN64), when reading an Open File Geodatabase from a zip file, features are duplicated. I created and attached a template which demonstrates the error. 

The workspace uses two readers to demonstrate the phenomena, both of type File Open Geodatabase.

  • The first reader reads from ..\test.zip\test.gdb
  • The second reader reads from ..\test.gdb

Records on the first reader are duplicated. When reading from just test.zip the duplication does not take place. 

Is this behaviour as meant to be?

Best answer by nielsgerrits

I am able to reproduce this using FeatureReaders in 2023.2 using the path:

"C:\TMP\New folder (191)\test.zip\test.gdb"

Also, the parameter cog turns red when I use this path, so I suspect this is not the way it is meant to be used.

 

According to the documentation the syntax should be:

"C:\TMP\New folder (191)\test.zip[test.gdb]"

But this also returns 2 features.

 

The only way I get it to work as expected is when I use the path:

"C:\TMP\New folder (191)\test.zip"
Because of the structure of a file geodatabase, it often works differently than expected. Same if you want to read a .gdb using a user parameter, it is different from other files.

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

1 reply

nielsgerrits
VIP
  • Best Answer
  • November 20, 2024

I am able to reproduce this using FeatureReaders in 2023.2 using the path:

"C:\TMP\New folder (191)\test.zip\test.gdb"

Also, the parameter cog turns red when I use this path, so I suspect this is not the way it is meant to be used.

 

According to the documentation the syntax should be:

"C:\TMP\New folder (191)\test.zip[test.gdb]"

But this also returns 2 features.

 

The only way I get it to work as expected is when I use the path:

"C:\TMP\New folder (191)\test.zip"
Because of the structure of a file geodatabase, it often works differently than expected. Same if you want to read a .gdb using a user parameter, it is different from other files.


Reply


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