Rejected features when using Clipper because of NULL Geomotry

A Clipper transformer does a spatial overlap query.

Without a geometry that is impossible.

The solution would be filtering the Null geometries using the GeometryFilter transformer before feeding features to the Clipper. You can decide to route the Null geometries to the next transformer (act Null as Inside) or ignore the Null geometries.

Another option is to route the Rejected port to the next transformer, so Null geometries are included.

Hope this helps.

@shekmister

Hi.

The clipper does not fall over.

NUll geometries cannot be spatially related or clipped etc. So they are rejected.

You need to set the "Workpace: Rejected feature Handling"

Either you set it to continue.

Or you attach a inspector to the rejected port (you can disable the inspector if not needed).

Right mouse click on the rejected port gives you acces to this setting.

Or, test for Null geometries before yuo send them to the clipper.

Thanks erik_jan and Gio,

It's good to understand that the basis of clipper is a spatial overlap. Without geometry it is impossible to do this query.

Understanding that, it is easy to deal with the NULL geometries with either a GeometryFilter or to continue the translation with these objects.

Thank you!