Skip to main content
Question

FeatureReader vs Reader : Esri ArcGIS Server Feature Services


dms2
Contributor
Forum|alt.badge.img+11
  • Contributor

I can't connect to a specific ArcGIS Server feature service using a FeatureReader.

I get the service layers listed as output ports but when I execute the translation it throws this error:

ArcGIS Feature Service Reader: Encountered an unexpected error. The error code from the server was '400' and the message was: 'Failed to execute query.'. Details: ''

 

Using a Reader instead all service layers are read without problem.

 

I don't understand why the Reader connection works different than the transformer. Any idea?

Generally I would stick to the Reader connection and forget about this weird thing but I prefer using a FeatureReader here because I need to catch any error and work further with it in the translation.

 

 

2 replies

davtorgh
Contributor
Forum|alt.badge.img+10
  • Contributor
  • November 3, 2020

Hi dms2,

 

based on your description seems the FeatureReader tries to execute a "bad" query against the ArcGIS Server feature service. You may check possible where clause or spatial filter setup in the FeatureReader and, eventually, have a look at this article.

 

Hope that helps!


dms2
Contributor
Forum|alt.badge.img+11
  • Author
  • Contributor
  • November 9, 2020
davtorgh wrote:

Hi dms2,

 

based on your description seems the FeatureReader tries to execute a "bad" query against the ArcGIS Server feature service. You may check possible where clause or spatial filter setup in the FeatureReader and, eventually, have a look at this article.

 

Hope that helps!

I'm not using a where clause or a spatial filter so I don't think that's the problem. Maybe it is the "behind the scenes" query the FeaureREader does to read the data.

I read that article before asking here. It shows a workaround when it is the Reader connection that fails and that's working for me. A pity.


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