+5Input:
Output:
How do I know what went wrong?
+19Hi @cecshi25 It's hard to tell what your input data looks like. Is the problem that you split an aggregate and now both features have the same values for MILE_START and MILE_END which were used in the Snipper?
+5Hi @cecshi25 It's hard to tell what your input data looks like. Is the problem that you split an aggregate and now both features have the same values for MILE_START and MILE_END which were used in the Snipper?
FeatureMerger Requestor is an excel file with mile start and end values, Supplier is a calibrated routes spatial layer, with Track name being the join key.
The problem is when the aggregated track is split, the Snipper also outputs the reaggregated piece that is outside of the start and end value range. Any way to only output the track segment within the start and end value?
FeatureMerger Requestor is an excel file with mile start and end values, Supplier is a calibrated routes spatial layer, with Track name being the join key.
The problem is when the aggregated track is split, the Snipper also outputs the reaggregated piece that is outside of the start and end value range. Any way to only output the track segment within the start and end value?
@cecshi25 I've reproduced your example - see the attached workspace (FME 2021).
This is actually by design. If the snip range is outside of the range of the feature, then FME will output a point. But in the case of multi-part lines, this doesn't really make sense. It looks like we should add an option to turn off this behaviour. In the meantime your workaround is to include the GeometryFilter
