Skip to main content

Occasionally the upstream service from external provider might not retuning any features, in those cases, there will be 0 features going to the “Revised” stream. How do I stop ChangeDectector instead of keep running and delete existing features.

  

 

You could probably do something with the NoFeaturesTester transformer from the Hub, published by Safe Software. I quickly put together a demo using a NoFeaturesTester together with a FeatureMerger set to merge 1 = 1. If there are no features entering the NoFeaturesTester, then there will be a single feature going up to the FeatureMerger, which will stop the features from reaching the ChangeDetector.

 

Good luck!

/Jacques

 


@_jacques_  Thanks, works perfectly.