When using the ChangeDetector, the order of the output is different then the input. For example:
Input Original 12,5,13,8,4
Input Revised 10,4,11,6,1,8,14,2
Output Unchanged 4,8
Output Added 1,10,2,14,6,11
Output Deleted 13,12,5
I can't find the logic of it. Does anyone know? The solution I have is using the sorter afterwards, but I want to prevend to using it because of the long processing time with large datasets.
@cwisse I don't think you can predict the output order of features exiting the ChangeDetector. In my experiments the Updated and Unchanged appear to follow the order of the Original input. Inserted and Deleted are shuffled. But any FME blocking transformer will potentially re-order features.
@cwisse I don't think you can predict the output order of features exiting the ChangeDetector. In my experiments the Updated and Unchanged appear to follow the order of the Original input. Inserted and Deleted are shuffled. But any FME blocking transformer will potentially re-order features.
@markatsafe The result you're having is what I need. I'm still working with the 2017 version, where every output of the ChangeDetector seems to be shuffled. I'll have to wait till we have the 2020 version. The problem is that the next update will be the 2019 version (yes yes, I know, slow organization).
@markatsafe The result you're having is what I need. I'm still working with the 2017 version, where every output of the ChangeDetector seems to be shuffled. I'll have to wait till we have the 2020 version. The problem is that the next update will be the 2019 version (yes yes, I know, slow organization).
@cwisse makes a good point. The ChangeDetector I was testing is the newer version which was added in FME 2019 and replaces the pre-2019 versions of ChangeDetector (you have to update the transformer to take advantage if the new version) and also it replaces the UpdateDetector available on the FME HUB. See the blog for more details
@cwisse. Is your 3D generalizer tool available for FME community?
Thanks
Frank