Skip to main content
Question

FeatureMerger error after upgrade to FME 2018 : 'REJECT_INVALID_GEOM YES CLEANING_TOLERANCE NONE'

  • May 9, 2018
  • 5 replies
  • 17 views
B
Forum|alt.badge.img

Hello,

After upgrading to FME2018, I have this strange error on featureMerger:

2018-05-09 07:00:21| 2.3| 0.1|ERROR |FeatureMerger(ReferenceFactory): The clause 'REJECT_INVALID_GEOM YES CLEANING_TOLERANCE NONE' within 'FACTORY_DEF {*} ReferenceFactory FACTORY_NAME FeatureMerger INPUT REFERENCER FEATURE_TYPE StringReplacer_OUTPUT INPUT REFERENCEE FEATURE_TYPE StringReplacer_2_OUTPUT REFERENCE_INFO ATTRIBUTES REFERENCE_TABLE @EvaluateExpression(FDIV,STRING_ENCODED,<at>Value<openparen>TEXT<closeparen>,FeatureMerger) @EvaluateExpression(FDIV,STRING_ENCODED,<at>Value<openparen>TEXT<closeparen>,FeatureMerger) AUTO ATTR_ACCUM_MODE HANDLE_CONFLICT ATTR_CONFLICT_RES REQUESTOR_IF_CONFLICT IGNORE_NULLS No HANDLE_NULL_MISSING_KEYS_LIKE_FME2013 No LIST_ATTRS_TO_INCLUDE <Unused> LIST_ATTRS_TO_INCLUDE_MODE <Unused> MERGE_ATTRIBUTES Yes MANAGE_FME_TYPE Yes MODE COMPLETE PROCESS_DUPLICATE_REFERENCEES No REFERENCEES_FIRST No REJECT_INVALID_GEOM YES CLEANING_TOLERANCE NONE OUTPUT COMPLETE FEATURE_TYPE FeatureMerger_MERGED' is incorrect. The clause must look like: REJECT_INVALID_GEOM [(yes|no)]

 

2018-05-09 07:00:21| 2.3| 0.0|INFORM|Closing the Geodatabase reader

 

2018-05-09 07:00:21| 2.3| 0.0|ERROR |The clause 'REJECT_INVALID_GEOM YES CLEANING_TOLERANCE NONE' within 'FACTORY_DEF {*} ReferenceFactory FACTORY_NAME FeatureMerger INPUT REFERENCER FEATURE_TYPE StringReplacer_OUTPUT INPUT REFERENCEE FEATURE_TYPE StringReplacer_2_OUTPUT REFERENCE_INFO ATTRIBUTES REFERENCE_TABLE @EvaluateExpression(FDIV,STRING_ENCODED,<at>Value<openparen>TEXT<closeparen>,FeatureMerger) @EvaluateExpression(FDIV,STRING_ENCODED,<at>Value<openparen>TEXT<closeparen>,FeatureMerger) AUTO ATTR_ACCUM_MODE HANDLE_CONFLICT ATTR_CONFLICT_RES REQUESTOR_IF_CONFLICT IGNORE_NULLS No HANDLE_NULL_MISSING_KEYS_LIKE_FME2013 No LIST_ATTRS_TO_INCLUDE <Unused> LIST_ATTRS_TO_INCLUDE_MODE <Unused> MERGE_ATTRIBUTES Yes MANAGE_FME_TYPE Yes MODE COMPLETE PROCESS_DUPLICATE_REFERENCEES No REFERENCEES_FIRST No REJECT_INVALID_GEOM YES CLEANING_TOLERANCE NONE OUTPUT COMPLETE FEATURE_TYPE FeatureMerger_MERGED' is incorrect. The clause must look like: REJECT_INVALID_GEOM [(yes|no)]

 

2

Any idea ?

Thanks !

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.

5 replies

fmelizard
Safer
Forum|alt.badge.img+20
  • fmelizardSafer
  • Safer
  • 3719 replies
  • May 9, 2018
Hi @biboba, are you able to upload your workspace or a picture of it? It would be helpful to see what's going on and what is entering the FeatureMerger when you see this error.
warren156
Forum|alt.badge.img
  • warren156
  • 16 replies
  • August 9, 2018

Hi @TiaAtSafe

 

Any chance you found a solution to this? I had my workflow throw this error recently and I can't seem to figure out why.

Warren

 

warren156
Forum|alt.badge.img
  • warren156
  • 16 replies
  • August 9, 2018

Hi @TiaAtSafe

 

Any chance you found a solution to this? I had my workflow throw this error recently and I can't seem to figure out why.

Warren

 

I'll add that this workbench runs just fine when initiated from within FME but if I call it from a bat file then it produces this error.

 

 

B
Forum|alt.badge.img
  • biboba
  • Author
  • 17 replies
  • August 9, 2018

Hi @TiaAtSafe

 

Any chance you found a solution to this? I had my workflow throw this error recently and I can't seem to figure out why.

Warren

 

Hi,

 

On my side, I had this error after saving a FME 2016 workbench with FME2018 without having made any modification.

 

Then running it with FME2016 raised the error.

 

Maybe the default FME that is launched by the bat file is not the 2018 ?

 

Hope this can help,

 

 

Nicolas

 

 

 

warren156
Forum|alt.badge.img
  • warren156
  • 16 replies
  • August 9, 2018
Hi,

 

On my side, I had this error after saving a FME 2016 workbench with FME2018 without having made any modification.

 

Then running it with FME2016 raised the error.

 

Maybe the default FME that is launched by the bat file is not the 2018 ?

 

Hope this can help,

 

 

Nicolas

 

 

 

Aha! Thanks Nicolas @biboba,

 

I was opening the workbench with FME 2018, but my .bat file was calling a 2017 installed version. After correcting this my workbench ran without error. I appreciate the post! Warren

 

 

Community Stats

32,084
Posts
121,841
Replies
39,724
Members

Latest FME

Terms & ConditionsCookie settingsAccessibility statement
A product of
Safe Software respectfully acknowledges that we live, learn and work on the traditional and unceded territories of the Kwantlen, Katzie, and Semiahmoo First Nations.