+18Hi,
Does anybody know of a way to use the CRCCalculator only on geometry?
When specifying coordinates and attributes the included attributes NEEDS an attribute,something that is NOT necessary when the requirement is to base the CRC on geometry ONLY.
Bug? or am I missing something?
Solved it by using the @CRC function,but should be possible in the transformer.
Best answer by mark2catsafe
Yes. It used to be able to do that. Thankfully we've added that capability back in FME2016.1.1 - any build 16585 or higher will have it. 2016.1.1 is still beta I think, but pretty stable.
fyi it's PR#69680 in case you need to follow up about anything.
Regards
Mark
+23A work-around can be to create a dummy attribute with a fixed value (1) and use that combined with the geometry. Or use the GeometryExtractor and calculate the CRC on the _geometry only. But I agree that geometry only would make sense as an option.
+18A work-around can be to create a dummy attribute with a fixed value (1) and use that combined with the geometry. Or use the GeometryExtractor and calculate the CRC on the _geometry only. But I agree that geometry only would make sense as an option.
Hi Erik,thx but I am trying to avoind extra transformers or balast....
+23Hi Erik,thx but I am trying to avoind extra transformers or balast....
And that is why I agree.
+18Strangly using the function works properly and that is the way it worked in te past.
+5Yes. It used to be able to do that. Thankfully we've added that capability back in FME2016.1.1 - any build 16585 or higher will have it. 2016.1.1 is still beta I think, but pretty stable.
fyi it's PR#69680 in case you need to follow up about anything.
Regards
Mark
+18Yes. It used to be able to do that. Thankfully we've added that capability back in FME2016.1.1 - any build 16585 or higher will have it. 2016.1.1 is still beta I think, but pretty stable.
fyi it's PR#69680 in case you need to follow up about anything.
Regards
Mark
Awesome, Thx for the info.
