I woul dlike to see some inmprovements on the SurfaceModeller, so you can choose what needs to be modelled. A bit like the checkboxes in the GeometryFilter. This will improve workflows and make it a whole lot faster I think.
Released
SurfaceModeller improvement
+10+10@daleatsafe @daveatsafe
Dale and Dave, not sure you're the right persons to mention, but I'd like to draw your attention to this suggestion, not only because I think it would be a great improvement, but most of all, because I run into issues using the SurfaceModeller in combination with large(r) datasets and Feature Caching turned on. Often the VoronoiDiagram (output port) seems to be blocking the output to be written (at least I think this is happening, since the log says FME starts building the Voronois and then it seems to stall).
And something similar was mentioned by @stevenjh in the comments on this post.
+17- Safer
Hi
As of FME 2024.2, we’ve made some significant improvements to the SurfaceModeller and the related transformers (ContourGenerator, DEMGenerator, RasterDEMGenerator, SurfaceDraper, TINGenerator, and VoronoiGenerator)
We’ve improved the performance and stability of the main transformer and the related ones as well through how the underlying TIN is generated. You may not notice as much of a slow down or blocking nature now with these latest improvements.
Currently, when feature caching is turned on all output ports are needed to be generated, hence why the VoronoiDiagram output port is “blocking” the transformers processing. I’d invite you to vote and comment on this issue as it better covers the issue of feature caching and ports:
Login to the community
No account yet? Create an account
An FME Account is required to contribute
LoginEnter your E-mail address. We'll send you an e-mail with instructions to reset your password.