Skip to main content
Solved

Writing to multiple CityGML files results in an error (FME2020)

  • August 10, 2020
  • 2 replies
  • 18 views

harmen_kampinga
Forum|alt.badge.img+2

Screenshot_1When I have created a CityGML writer and add another one with the same specs except for the file name, running the process ends in an error. 

Both writers are separate. So it's not one CityGML writer writing two Feature Types (that won't work). 

 

Those are the warnings and the only error I get:

2020-08-10 10:38:15|  13.3|  0.0|WARN  |Duplicate XML Schema attribute declaration found -  QName: 'xml:lang', schema URL: 'file:///C:/Program Files/FME2020/xml/schemas/CityGML/CityGML/2.0/3.1.1/smil/xml-mod.xsd'
2020-08-10 10:38:15|  13.3|  0.0|WARN  |Duplicate XML Schema attribute declaration found -  QName: 'xml:space', schema URL: 'file:///C:/Program Files/FME2020/xml/schemas/CityGML/CityGML/2.0/3.1.1/smil/xml-mod.xsd'
2020-08-10 10:38:15|  13.3|  0.0|WARN  |Duplicate XML Schema attribute group definition found -  QName: 'xml:specialAttrs', schema URL: 'file:///C:/Program Files/FME2020/xml/schemas/CityGML/CityGML/2.0/3.1.1/smil/xml-mod.xsd'
2020-08-10 10:38:15|  14.1|  0.0|WARN  |Duplicate XML Schema attribute declaration found -  QName: 'xml:lang', schema URL: 'file:///C:/Program Files/FME2020/xml/schemas/CityGML/CityGML/2.0/3.1.1/smil/xml-mod.xsd'
2020-08-10 10:38:15|  14.1|  0.0|WARN  |Duplicate XML Schema attribute declaration found -  QName: 'xml:space', schema URL: 'file:///C:/Program Files/FME2020/xml/schemas/CityGML/CityGML/2.0/3.1.1/smil/xml-mod.xsd'
2020-08-10 10:38:15|  14.1|  0.0|WARN  |Duplicate XML Schema attribute group definition found -  QName: 'xml:specialAttrs', schema URL: 'file:///C:/Program Files/FME2020/xml/schemas/CityGML/CityGML/2.0/3.1.1/smil/xml-mod.xsd'
Error running translation.

 

Best answer by virtualcitymatt

Ha! you are so right - I get something similar. No warnings but the same ERROR/Crash

 

Heres a simple test. If you disable either of the Writers in the Navagator pane then the worksapce works fine. Having two just failes.

 

I've been trying to figure out what was causing these random crashes for ages! Thanks for sharing you issue.

 

No issues in FME 2018.

 

@daveatsafe​  - Are you able to have someone take a look at this?

@Harmen Kampinga​  You should be about to workaround the issue by removing the second writer and using the fanout. You will need to create a filename attribute which is a bit annoying.

 

The other thing to try is to use the FeatureWriter. That may not have the same bug.

 

 

 

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.

2 replies

virtualcitymatt
Celebrity
Forum|alt.badge.img+47
  • Celebrity
  • Best Answer
  • August 10, 2020

Ha! you are so right - I get something similar. No warnings but the same ERROR/Crash

 

Heres a simple test. If you disable either of the Writers in the Navagator pane then the worksapce works fine. Having two just failes.

 

I've been trying to figure out what was causing these random crashes for ages! Thanks for sharing you issue.

 

No issues in FME 2018.

 

@daveatsafe​  - Are you able to have someone take a look at this?

@Harmen Kampinga​  You should be about to workaround the issue by removing the second writer and using the fanout. You will need to create a filename attribute which is a bit annoying.

 

The other thing to try is to use the FeatureWriter. That may not have the same bug.

 

 

 


harmen_kampinga
Forum|alt.badge.img+2

Thanks @virtualcitymatt​ ! Ah, good to find out that you have found it as an error also. Yeah, those are indeed probably the best solutions to work with. For now, I just deactivated the one and activated the other one to have it running. Good enough for me, but certainly not when you like to have that in production!