Skip to main content
Solved

Translation returns "FATAL: Expression false" ???


lifalin2016
Contributor
Forum|alt.badge.img+29

Hi list.

In the curiosity department, I have a workspace, that seems to finish , but misses some data, adding a small FATAL error message "Expression: false":

 

2021-06-09 09_21_42-_202099029 Import RSF DanDas XML to LER 2.0 data model (H__user_GIS-teamet_FME WWhat triggers this ???

Best answer by lifalin2016

I'm closing this question, there seems to be no obvious explanations.

View original
Did this help you find an answer to your question?

5 replies

redgeographics
Celebrity
Forum|alt.badge.img+48

Do you have a SQL statement specified for after writing by any chance? Is the data actually being written?


lifalin2016
Contributor
Forum|alt.badge.img+29
  • Author
  • Contributor
  • June 9, 2021

Yes, but wouldn't that run after all output has been written? In my case I should have 80K "ledning", but only gets 17K.

My SQL run after translation is fairly straight forward:

UPDATE [$(TARGET_SCHEMA)].[Afløbskomponent] SET [geometri] = [geometri].MakeValid() WHERE [geometri].STIsValid() = 0
UPDATE [$(TARGET_SCHEMA)].[Afløbsledning] SET [geometri] = [geometri].MakeValid() WHERE [geometri].STIsValid() = 0

 


lifalin2016
Contributor
Forum|alt.badge.img+29
  • Author
  • Contributor
  • June 9, 2021
lifalin2016 wrote:

Yes, but wouldn't that run after all output has been written? In my case I should have 80K "ledning", but only gets 17K.

My SQL run after translation is fairly straight forward:

UPDATE [$(TARGET_SCHEMA)].[Afløbskomponent] SET [geometri] = [geometri].MakeValid() WHERE [geometri].STIsValid() = 0
UPDATE [$(TARGET_SCHEMA)].[Afløbsledning] SET [geometri] = [geometri].MakeValid() WHERE [geometri].STIsValid() = 0

 

I did manage to get the correct output without encountering any errors, but I had to single-step the entire workspace !!

During my trials I encountered another peculiar error that I haven't seen before:

 

2021-06-09 12_25_25-Window


hkingsbury
Celebrity
Forum|alt.badge.img+51
  • Celebrity
  • June 10, 2021
lifalin2016 wrote:

I did manage to get the correct output without encountering any errors, but I had to single-step the entire workspace !!

During my trials I encountered another peculiar error that I haven't seen before:

 

2021-06-09 12_25_25-Window

I believe that second error relates to the feature caching not finding a cached feature. I wouldn't worry about that one too much...

 


lifalin2016
Contributor
Forum|alt.badge.img+29
  • Author
  • Contributor
  • Best Answer
  • June 15, 2021

I'm closing this question, there seems to be no obvious explanations.


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings