I'm going to remove the GML aspect from my answer as i've never used it or really know much about it - @virtualcitymatt can probably help out more with GML specifics.
From what I can see (without knowing the intricacies of your process) I think you might be encountering a bit of an order of operations confusion. eg you're wanting things to run in the order 'Ar' 'Bw' 'Cr' 'Dw' (lower case r meanign read, w meaning write), but instead you're probably getting 'Ar' 'Cr' 'Bw' 'Dw'.
To solve this i'd look at using feature readers and writers. This will allow you to perform 'Ar' and then 'Bw'. The output of the 'Bw' feature writer can then be used to trigger 'Cr' and subsequently 'Dw'
https://docs.safe.com/fme/html/FME_Desktop_Documentation/FME_Transformers/Transformers/featurereader.htm
https://docs.safe.com/fme/html/FME_Desktop_Documentation/FME_Transformers/Transformers/featurewriter.htm
Are you writing out multiple CityGML files? I've seen FME crash/ERROR when writing out multiple files of CityGML. I haven't been able to pinpoint exactly where the issue comes from as not all processes seem to be affected. Perhaps it is related to the order of operations.
The next thing to test is to turn of the validation step to see if it has any effect.
Are you writing out multiple CityGML files? I've seen FME crash/ERROR when writing out multiple files of CityGML. I haven't been able to pinpoint exactly where the issue comes from as not all processes seem to be affected. Perhaps it is related to the order of operations.
The next thing to test is to turn of the validation step to see if it has any effect.
Hi @virtualcitymatt ,
I am writing only one CityGML file, with multiple feature types (CityModel, Building, BuildingPart, .....).
I installed FME Desktop on another computer to test if the computer was the issue. The result is however the same.
Then I followed your piece of advice and removed the XML validation step. In turns out that the workspace runs without fatal error, and the log file points that all features were written successfully.
But when I inspect the CityGML file, I see all sorts of results.
This last time, for instance, FMEDesktop only wrote the SolitaryVegetationObject features and two X3D Materials. All other feature types weren't written.
On another test, it wrote all cityobjectmember features, but did not write the x3D materials
On another test, it wrote everything but the trees.
Notice that I haven't changed anything in terms of input parameters, I am just trying to run the same workspace again and again.
It seems that I need to ask FME to only start writing feature types once all processes were completed. Only then, with the available memory, FMEDesktop could start writing the output file.
I'm going to remove the GML aspect from my answer as i've never used it or really know much about it - @virtualcitymatt can probably help out more with GML specifics.
From what I can see (without knowing the intricacies of your process) I think you might be encountering a bit of an order of operations confusion. eg you're wanting things to run in the order 'Ar' 'Bw' 'Cr' 'Dw' (lower case r meanign read, w meaning write), but instead you're probably getting 'Ar' 'Cr' 'Bw' 'Dw'.
To solve this i'd look at using feature readers and writers. This will allow you to perform 'Ar' and then 'Bw'. The output of the 'Bw' feature writer can then be used to trigger 'Cr' and subsequently 'Dw'
https://docs.safe.com/fme/html/FME_Desktop_Documentation/FME_Transformers/Transformers/featurereader.htm
https://docs.safe.com/fme/html/FME_Desktop_Documentation/FME_Transformers/Transformers/featurewriter.htm
Hi @hkingsbury,
I will have a look at these two transformers. Thanks!
Hi @virtualcitymatt ,
I am writing only one CityGML file, with multiple feature types (CityModel, Building, BuildingPart, .....).
I installed FME Desktop on another computer to test if the computer was the issue. The result is however the same.
Then I followed your piece of advice and removed the XML validation step. In turns out that the workspace runs without fatal error, and the log file points that all features were written successfully.
But when I inspect the CityGML file, I see all sorts of results.
This last time, for instance, FMEDesktop only wrote the SolitaryVegetationObject features and two X3D Materials. All other feature types weren't written.
On another test, it wrote all cityobjectmember features, but did not write the x3D materials
On another test, it wrote everything but the trees.
Notice that I haven't changed anything in terms of input parameters, I am just trying to run the same workspace again and again.
It seems that I need to ask FME to only start writing feature types once all processes were completed. Only then, with the available memory, FMEDesktop could start writing the output file.
ok that's super weird I've never seen that before - can you try removing/disabling the CityModel feature type in the output. FME will just create this by default anyway and it could somehow be related to this.
Another thing I would look at is the Appearence and X3DMMaterial feature types - If the features themselves have the appearences then FME will also automatically create these as well - unless of course there is a specific reason you are defining these outputs.
Hi @virtualcitymatt ,
I am writing only one CityGML file, with multiple feature types (CityModel, Building, BuildingPart, .....).
I installed FME Desktop on another computer to test if the computer was the issue. The result is however the same.
Then I followed your piece of advice and removed the XML validation step. In turns out that the workspace runs without fatal error, and the log file points that all features were written successfully.
But when I inspect the CityGML file, I see all sorts of results.
This last time, for instance, FMEDesktop only wrote the SolitaryVegetationObject features and two X3D Materials. All other feature types weren't written.
On another test, it wrote all cityobjectmember features, but did not write the x3D materials
On another test, it wrote everything but the trees.
Notice that I haven't changed anything in terms of input parameters, I am just trying to run the same workspace again and again.
It seems that I need to ask FME to only start writing feature types once all processes were completed. Only then, with the available memory, FMEDesktop could start writing the output file.
Hi @virtualcitymatt,
In the end, it turns out that the "fanout dataset" option was on.
Since the name of my output CityGML file is based on a timestamp, and each output feature type is reached at different moments in time, the city model features were being written in multiple files with different names (because of different timestamps at every minute that passes during the translation).
A silly mistake, unfortunately. The workaround was to create a script user parameter that defines a unique timestamp at the beginning of the translation, and from there to assign the output file name based on this unique timestamp. In this sense, all features are now written in the same output file.
- Side note 1: Removing/disabling the CityModel feature type would remove all attributes at CityModel level, and that's something I don't want to.
- Side note 2: The cityobject features (walls, grounds, roofs, solitaryvegetationobjects, relief, etc.) do not have appearances by themselves... I am using the Appearance and X3DMaterial feature types to encode lists of Xlink references to their geometrical gml_id's.
Thanks for the hints anyway. Much appreciated!
Denis
