OGC API (WFS3.0) Feature Reader bbox from attribute

I have tried some more things but I am sometimes getting the impression the featurereader only accepts the first collection query parameter and ignores any more than the first one. 

What version of FME?

I’m able to send multiple inputs into a featurereader and use attributes to create a bbox value in the parameters in 2024.1

Hi ebygomm,

I tried both fme 2024.1.1 and fme 2023.0.0.3

The issue is not with multiple attribute in one parameter value, but multiple different parameters:

So datetime based on @Value(_datetime) and in combination with bbox based on xmin etc.. 

This is giving me issues

I’ve just done a quick test, and it doesn’t seem to work with multiple parameters at all, e.g. bbox and limit, whether hardcoded or dynamic

It's so strange. This would be a huge bug.

I can however combine the limit parameter with the bbox parameter. That does work.

For now my workaround is to only filter on bbox as this has by far the largest impact on the resulting amount of features, and only afterwards filter out based on datetime (which still eliminates 80% of the features). 

Hi ​@takanaka,

Apologies for the delayed response, and thank you for posting on the FME Community!

I can confirm that I’m also seeing the same behaviour when working with OGC API (WFS 3.0) in the FeatureReader. This is a known issue that we’re currently tracking internally as FMEENGINE-87152.

At the moment, the best workaround is to continue filtering the results after reading, as you’ve already been doing.

We understand this is inconvenient, and we appreciate your patience while our development team investigates and addresses the issue.

Hi ​@crystalwang, thank you for confirming this is a bug.

I hope to be updated via this thread.

Thank you!