It would be good if for AnchoredSnapper, a Snapping Tolerance could be an attribute? Currently it only accepts parameters.
I understand why not for a Snapper - because everything might move around, but for an AnchoredSnapper, that's not a problem, the base doesn't move.
The attribute could come from the "Candidate" (and only the candidate). Then each candidate can snap to a different tolerance to the base.
+23We have the issue where snapping needs to be dynamic i.e. we want the snapping to be half the distance of the shortest line. Currently snapping transformers i.e. Snapper / AnchorSnapper or transformers with snapping functions i.e. AreaBuilder can only take in a value or a parameter. It would be great to be able to use transformers like StatisticCalculator and feed the minimum value into the mentioned transformers.
I think Snapper should be able to support this to. You could just use the value of the attribute for the first feature receieved for the current group. Then it could be the callers responsibility to either ensure all features in the same group have the same value for the attribute or at least ensure that the feature with the appropriate value is the first sent to the Snapper for that group.
+10Please Safe, we need this implemented,
In my scenario: the NeightbourFinder determines the (_distanc)e value that I should use for each case for the Point to snap to the closest Line, but then the AnchoredSnapper stuck to receive the Snapping Distance parameter as an attribute (_distance).😢
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
