TINGenerator missing Rejected Port

Meanwhile I figured out a way to sort out potential hazardous PointClouds by checking the difference of x and y values. If the x or y difference is below a value 5*Surfacetolerance used in TINGenerator or if the PointCloud has less than 5 points I filter it out.

TINGenerator now runs through my dataset.

I consider this a hack still and think no transformer should break a translation and stop the show, without allowing to control the situation.

A Rejected port would be more than necessary here !!!

I agree! There are cases thinkable where this might occur and given that point cloud transformations can be pretty intensive and time-consuming it would be very bad if something like this causes a multi-hour process to fail.

@natalieatsafe could you pass this on to support please?

Thanks for the feedback @mhab & @redgeographics.

I spoke to our development team regarding this and we are currently looking into more checks for the geometry validator, which will hopefully cover situations like this. If you would like, please submit a case and mention FMEENGINE-16179 in the body so we can link it to the appropriate enhancement request.

I will also create a second enhancement request for a rejected port to be added on the TINGenerator and link your case to that as well.

Thanks!