Skip to main content
Open

FeatureReader and FILEGDB with Where-clause

Related products:Transformers
  • October 4, 2017
  • 12 replies
  • 112 views
david_r
Celebrity

The FeatureReader currently doesn't support a where-clause for the FILEGDB reader, although the regular FILEGDB reader does.

It would be great if the FeatureReader could also support a where-clause.

See also: https://knowledge.safe.com/questions/54705/select-statement-using-file-geodb-open-api.html

12 replies

nielsgerrits
VIP
Forum|alt.badge.img+66
A no-brainer if it is a GUI thing only, as it is already working in the traditional reader.

Traditional Reader.

'

FeatureReader GDB API

'

FeatureReader GDB

'

featurereadergdbapi_2.png
Buckle your seatbelt Dorothy, cause Kansas is going bye-bye...
bruceharold
Influencer
Forum|alt.badge.img+19
  • bruceharoldInfluencer
  • Influencer
  • December 22, 2017
Also GEODATABASE_FILE reader needs a where clause per feature type.

 

 

aarcra
Contributor
  • aarcraContributor
  • Contributor
  • February 21, 2018

I wonder if this has to do with how the regular readers execute where clauses.

The ESRI fgdb's where clause is executed against the entire gdb (and currently can not have where clauses on different feature types from the same gdb). Where as the OPEN API reader can execute individual where clauses at the feature type level.

fmelizard
Safer
Forum|alt.badge.img+22
  • fmelizardSafer
  • Safer
  • February 23, 2018

Hi @bruceharold and @aarcra, in our latest FME 2018 betas you can specify a feature type where clause on both File Geodatabase Readers (GEODATABASE_FILE and FILE_GEODB).

nielsgerrits
VIP
Forum|alt.badge.img+66
Nice work!
Buckle your seatbelt Dorothy, cause Kansas is going bye-bye...
bruceharold
Influencer
Forum|alt.badge.img+19
  • bruceharoldInfluencer
  • Influencer
  • February 23, 2018
Woohoo! I'm on it...

 

 

nic_ran
Contributor
Forum|alt.badge.img+20
  • nic_ranContributor
  • Contributor
  • June 25, 2018
Hi @TiaAtSafe, I'm on FME 2018.1 beta build 18501 and this option is greyed out. Was it made available and then taken away again?

 

fmelizard
Safer
Forum|alt.badge.img+22
  • fmelizardSafer
  • Safer
  • June 25, 2018
Hi @nic_ran, my apologies, I wasn't explicit in my post. The where clause is on the feature type for both Readers. The FeatureReader currently only supports a where clause for the GEODATABASE_FILE version (not the API version).
nic_ran
Contributor
Forum|alt.badge.img+20
  • nic_ranContributor
  • Contributor
  • June 26, 2018
Are there any pans to add this support to the FeatureReader? It would seem to be not too difficult if it's already implemented in the standard Reader.

 

 

fmelizard
Safer
Forum|alt.badge.img+22
  • fmelizardSafer
  • Safer
  • June 27, 2018
Hi @nic_ran, there is an existing problem report asking for this functionality. I've linked this idea to the report, we will update here when the report is resolved.
M
Forum|alt.badge.img+2
  • mark_f
  • October 14, 2018

Throwing my two cents worth in. Using the File Geodb API as a standard reader with a WHERE clause but wanted the flexibility to apply a process before reading using a FeatureReader but not possible without more complexity.

I have a 40M row table that I need to extract 1.4M rows from. Standard reader without where clause and a tester 78 minutes... using a where clause 9 minutes!

winkel_tripel
Contributor
Forum|alt.badge.img+1
  • winkel_tripelContributor
  • Contributor
  • February 21, 2019

Is there any update on this? This feature would really help to reduce processing time for some of our workspaces.

Community Stats

32,749
Posts
124,193
Replies
41,251
Members
Terms & ConditionsAccessibility 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.