Skip to main content
Question

Spatailfilter different behaviour (script vs. application)


geobiker
Contributor
Forum|alt.badge.img

Hi,

 

my workbench use the Spatialfilter to detect if features from ESRI Geodatabase are inside a polygon.

 

 

Candidate: 10 featureclasses (diffrent geometry) from ESRI Geodatebase

 

Filter: 1 Polygon from File-Geodatebase.

 

 

With FME 2016.1.3 and Windows Server 2008 the workbench works fine. Now I have switched operating yystem to Windows Server 2016 and FME Desktop to 2018.1.

 

And now I have the problem that the SpatialFilter only works if I run the workbench in the FME application. If I use a script to start the workbench via par-file no feature will pass against the filter.

 

 

Kind regards

Stefan

4 replies

redgeographics
Celebrity
Forum|alt.badge.img+49

Are you absolutely sure you're using the same parameters? I know this seems like a very obvious thing but I can assure you it's happened to me multiple times.


fmelizard
Safer
Forum|alt.badge.img+18
  • Safer
  • December 6, 2018

I'd carefully examine the log file of both to see where things diverge.


gmbutler2
Contributor
Forum|alt.badge.img+10
  • Contributor
  • December 6, 2018
redgeographics wrote:

Are you absolutely sure you're using the same parameters? I know this seems like a very obvious thing but I can assure you it's happened to me multiple times.

I would also verify that both objects coming into the spatialfilter are at the same coordinate system. Another obvious thing but something that can be easily overlooked.


geobiker
Contributor
Forum|alt.badge.img
  • Author
  • Contributor
  • December 6, 2018

Hi,

in the meantime I have replaced SpatialFilter instead of Feature Reader. Now I get the excepected results with script and application.

A nice benefit of this change is the workbench looks much simpler and the performance is also better than before.

 

Kind reagards

Stefan


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