Skip to main content
Question

Is there a way of preventing the SurfaceDraper from creating a surface model unless it receives at least one DrapeFeature

  • June 9, 2021
  • 1 reply
  • 36 views

btl
Contributor
Forum|alt.badge.img+3
  • Contributor

This is my workspace, it adds elevation to lake polygons and river lines from a DEM. Lakes are calculated by clipping the raster and getting median elevation, meanwhile river lines are draped onto a surface.

 

Most of the time my data does not contain any lines, but the SurfaceDraper still creates a surface, which can take a while - is there a way to improve performance by preventing the SurfaceDraper from doing anything unless it receives at least one DrapeFeature?screenshot

1 reply

Forum|alt.badge.img+2

@btl​  You need to link the two pipelines in some way and the add a Tester to block the DEM.

  • VariableSetter & VariableRetreiver can be used to link pipelines. Proved you can control the order of the inputs (make sure your line reader is the first reader in the navigator)
  • There is a NoFeatureTester on the FME HUB. If there are no features, then a single feature is output on the No Input port . Use the NoFeatureTester on the lines. Join the NoInput to your DEM (FeatureJoiner) and then if the join fails, don't pass those features.

Something like that...


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