Skip to main content
Solved

WFS GetFeature Error, but still get results


jeroen_hack
Contributor
Forum|alt.badge.img+7

Hello FME enthousiasts,

 

I've been building a simple workspace for a collegue to get some parcel data from a public WFS. When I run the process it all seems to work (i get the desired parcel written to a File Geodatabase). But it keeps giving a single WFS error in the log, but the error apparently doesn't stop it from running:

<WFS> GetFeature URL: `https://service.pdok.nl:443/kadaster/kadastralekaart/wfs/v5_0?SERVICE=WFS&VERSION=2.0.0&REQUEST=GetFeature&TYPENAMES=kadastralekaart%3APerceel&FILTER=%3CFilter%3E%3CAnd%3E%3CPropertyIsEqualTo%3E%3CPropertyName%3EAKRKadastraleGemeenteCodeWaarde%3C%2FPropertyName%3E%3CLiteral%3ERNN01%3C%2FLiteral%3E%3C%2FPropertyIsEqualTo%3E%3CPropertyIsEqualTo%3E%3CPropertyName%3Esectie%3C%2FPropertyName%3E%3CLiteral%3EK%3C%2FLiteral%3E%3C%2FPropertyIsEqualTo%3E%3CPropertyIsEqualTo%3E%3CPropertyName%3Eperceelnummer%3C%2FPropertyName%3E%3CLiteral%3E36%3C%2FLiteral%3E%3C%2FPropertyIsEqualTo%3E%3C%2FAnd%3E%3C%2FFilter%3E&OUTPUTFORMAT=application%2Fgml%2Bxml%3B%20version%3D3.2&COUNT=100&STARTINDEX=0'

When i paste this link into a browser it also shows the expected result.

So what am i missing? Why is FME Form giving me this error? Anyone got any idea? I would like to figure out what's causing the error (and fix it if possible) before i deploy this to production.

I'm working with FME version 2024.0.1.0

 

Cheers!

Best answer by rahulsharma

@jeroen_hack Thanks for bringing this to our attention. We have now resolved the issue with FME 2024.0 (24211 and newer)
You should be able to get the latest version from our downloads page with week or so, we have tested this internally and everything should work as expected. 

 

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

5 replies

danilo_fme
Evangelist
Forum|alt.badge.img+44
  • Evangelist
  • April 17, 2024

Hi @jeroen_hack 

 

I tested with sucess here 2024.0.1.0 (20240328 - Build 24202 - WIN64).

 

 


liamfez
Influencer
Forum|alt.badge.img+34
  • Influencer
  • April 17, 2024

It may be possible that FME is categorizing it incorrectly as an ERROR, when perhaps it could be a WARN. I have had an issue in the past where connections to a mongo database would always report an error but not actually cause an issues. It ended up being a common potential response from the server based on security settings, which should have been a WARN but was just miscategorized by FME.
Not sure if that is what is happening with you, but figured I would mention it as a possibility


nielsgerrits
VIP
Forum|alt.badge.img+54

I can reproduce this (process reads one feature, but error in log) in 2024, but not in 2023. You probably want to submit a case at Safe.

 

https://support.safe.com/s/support


jeroen_hack
Contributor
Forum|alt.badge.img+7
  • Author
  • Contributor
  • April 17, 2024
nielsgerrits wrote:

I can reproduce this (process reads one feature, but error in log) in 2024, but not in 2023. You probably want to submit a case at Safe.

 

https://support.safe.com/s/support

Thanks, just created a ticket


rahulsharma
Safer
Forum|alt.badge.img+10
  • Safer
  • Best Answer
  • April 29, 2024

@jeroen_hack Thanks for bringing this to our attention. We have now resolved the issue with FME 2024.0 (24211 and newer)
You should be able to get the latest version from our downloads page with week or so, we have tested this internally and everything should work as expected. 

 


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