Because the default CRC-32 algorithm occasionally returns duplicates I use MD5.
I noticed that MD5 does not uses geometry.
Archived
CRCCalulator: MD5 algorithm also with geometry
This post is closed to further activity.
It may be an old question, an answered question, an implemented idea, or a notification-only post.
Please check post dates before relying on any information in a question or answer.
For follow-up or related questions, please post a new question or idea.
If there is a genuine update to be made, please contact us and request that the post is reopened.
It may be an old question, an answered question, an implemented idea, or a notification-only post.
Please check post dates before relying on any information in a question or answer.
For follow-up or related questions, please post a new question or idea.
If there is a genuine update to be made, please contact us and request that the post is reopened.
+9- Contributor
Tested in 2018.1.0.1: same problem.
@david_r: in CRCCalculator use _creation_instance as attribute and you get the duplicate. Change MD5 to CRC32 and it works fine.
+9- Contributor
Tested in 2018.1.0.1: same problem.
@david_r : in CRCCalculator use _creation_instance as attribute and you get the duplicate. Change MD5 to CRC32 and it works fine.
crccalculator-md5-no-geometry-v2018101.fmw
+9- Contributor
'>
In 2020.1.0.0 still not corrected. When using Selected Attributes Geometry is not used, resulting in duplicate crc value. Only when using MD5
+9- Contributor
David, you did not include the _creation_instance attribute in the CRCCalculator.
In 2022.0 issue still present
Same problem in 2021.0. Works if no selected attributes. But when adding one or more attributes geometries is no longer used when the MD5 is calculated.
Login to the community
No account yet? Create an account
An FME Account is required to contribute
LoginEnter your E-mail address. We'll send you an e-mail with instructions to reset your password.