Comments and answers for "Error running translation. IFC to CityGML"

Comment by xiaomengatsafe on xiaomengatsafe's answer

xiaomengatsafe — Fri, 21 Dec 2018 18:56:34 GMT

Thanks@prusswanfor your feedback.I agree, the error does not very clearly indicate what the issue is.If you are still struggling to solve the problem, would you mind sharing your data, workspace here, so we can help investigate?If you are not comfortable sharing the data in this public forum, feel free touse this form, to submit a case with your data and workspace, and a more detailed discription of the problem.Thank you very much!

Answer by prusswan

prusswan — Thu, 20 Dec 2018 18:44:16 GMT

We have a similar error using the Riverside workflow with our own data, could use a more descriptive error here..

Geometry instance was modified, the geometry definition will be instantiated Error running translation.During translation, some features were read that did not match a reader feature type in the workspace.ÂÂ This can happen if the reader dataset is changed, or a reader feature type removed or renamed.

Comment by hadhafang on hadhafang's answer

hadhafang — Tue, 26 Jun 2018 17:39:07 GMT

Thanks for your answer @DaveAtSafe

Yes the same thing happens in FME 2018.

3. log3ifcbeamenabledfme18.txt
The only difference I can see in log 3 from log 2 is that I use FME2018 instead of 17.The error type is still "Error running translation".What could the error mean?

Answer by daveatsafe

daveatsafe — Fri, 22 Jun 2018 22:27:42 GMT

Hi@hadhafang,

The log files do not provide a lot of information about the problem that caused the workspace to fail.I would really need to experiment with your data file to see what is causing the problem.

However, I did notice that you are running FME 2017.Does the same problem happen if you update to FME 2018?