There's scope for improvement of the Change Detector. It's only version 1, so I don't think it's something that has received any real love since its creation. This is particularly surprising given it's a fairly highly used transformer at #62
Suggestions (probably not all feasible):
- Group By
- Parallelism (workspace optimisation)
- Original/Revised first (workspace optimisation)
- Input is ordered by.... (workspace optimisation)
- Pairing - like Group By - one original feature should match one revised feature and then the changes compared between them. Potentially in combination with some of the above, this could also allow comparison of features without needing to store them all first.
- Split the dialog up so that the attribute stuff is all together and the geometry stuff is all together. Currently it's all mushed together. * Following from last item, disable "geometry" portion of dialog if only attribute matching. And disable attribute section if only geometry matching. (as standard in other dialogs).
