Invalid export settings - FBX export

[noynpe]

Hi,

I have a problem that started in IW2020 and persists in 2021.

When exporting an FBX I get a warning message telling me that the given extent is not inside the defined boundaries of the target coordinate system.

The UCS is set up as ETRS89.UTM-32N, the same as the target coordinate system for the fbx. The model was first created with model builder. The extents for the export is loaded from an .sdf file in the correct coordinate system. I get the same message if I try exporting the entire model - which means I cannot export anything at all to fbx!

Any help would be greatly appreciated!

[noynpe]

Hi,

I have a problem that started in IW2020 and persists in 2021.

When exporting an FBX I get a warning message telling me that the given extent is not inside the defined boundaries of the target coordinate system.

The UCS is set up as ETRS89.UTM-32N, the same as the target coordinate system for the fbx. The model was first created with model builder. The extents for the export is loaded from an .sdf file in the correct coordinate system. I get the same message if I try exporting the entire model - which means I cannot export anything at all to fbx!

Any help would be greatly appreciated!

[Karsten.Saenger]

Hi @noynpe ,

I am trying to recreate this issue on my system.
I created a Model Builder model that has a database CS (DBCS) of LL84. The area of interest is somewhere close to Munich, Germany.

I tested the FBX export and used ETRS89-UTM.32 as target CS.
Everything worked fine.

Is it possible to send me your area of interest SDF file?
The coordinate system definition for ETRS89.UTM-32 has tight boundaries defined for Norway. In the attached image, you can see that the Western part of Norway is missing. If your AOI is located there, you will receive the error message in InfraWorks.

A possible workaround is to copy the CS in Map/Civil 3D and edit the boundaries that way that your AOI is included.

Regards,

Karsten.

[Karsten.Saenger]

Hi @noynpe ,

I am trying to recreate this issue on my system.
I created a Model Builder model that has a database CS (DBCS) of LL84. The area of interest is somewhere close to Munich, Germany.

I tested the FBX export and used ETRS89-UTM.32 as target CS.
Everything worked fine.

Is it possible to send me your area of interest SDF file?
The coordinate system definition for ETRS89.UTM-32 has tight boundaries defined for Norway. In the attached image, you can see that the Western part of Norway is missing. If your AOI is located there, you will receive the error message in InfraWorks.

A possible workaround is to copy the CS in Map/Civil 3D and edit the boundaries that way that your AOI is included.

Regards,

Karsten.

[noynpe]

Hi Karsten,

thanks for the reply. This project is in Bergen on the west coast in Norway, so right at the edge of the displayed image. The attached file contains the required extents.

In shear desperation I created a new model without the model builder, set the UCS to UTM32 and tried the same procedure - everything worked with no problem! I am wondering if it's something with the conversion from LL84 from model builder to UTM32 that screws anything up? even if IW says that the UCS wont alter anything?

Fun fact: the image below is actually not the same as shown from Bing maps in civil 3d for UTM32. There it cuts alot further east, and its annoying!

*Edit: wow, .sdf files aren't allowed to be uploaded - https://we.tl/t-4dnUrW2Paw

[noynpe]

Hi Karsten,

thanks for the reply. This project is in Bergen on the west coast in Norway, so right at the edge of the displayed image. The attached file contains the required extents.

In shear desperation I created a new model without the model builder, set the UCS to UTM32 and tried the same procedure - everything worked with no problem! I am wondering if it's something with the conversion from LL84 from model builder to UTM32 that screws anything up? even if IW says that the UCS wont alter anything?

Fun fact: the image below is actually not the same as shown from Bing maps in civil 3d for UTM32. There it cuts alot further east, and its annoying!

*Edit: wow, .sdf files aren't allowed to be uploaded - https://we.tl/t-4dnUrW2Paw

[Karsten.Saenger · Accepted solution]

Hi @noynpe ,

your SDF file is not within the ETRS89 UTM 32 boundaries if you load it into Civil 3D.

This is the explanation why you get the error message in InfraWorks, when you export into a different CS.

The User Coordinate System is not relevant in InfraWorks when it comes to transformation, because it's only used for displaying the coordinates in the lower left corner.

The boundary check in InfraWorks is only done if a transformation between coordinate system happens.
A Model Builder model has a database CS = LL84. If you export to ETRS89 UTM 32 a transformation needs to be done and the CS check finds your data is out of boundary.
A possible solution is to create your own ETRS 89 UTM 32 system with different boundaries with the help of Map/Civil 3D.

If you create a new local InfraWorks model with database CS = ETRS89 UTM 32 and you export from there to ETRS89 UTM 32 - no transformation is conducted, so no boundary checks are not done and no error message appears.

The future best practices workflow is to create a Model Builder model directly in the desired CS to avoid such workflow hiccups with transformation of data. This will be possible in the Model Builder in the next InfraWorks release.

Regards,
Karsten

[Karsten.Saenger · Accepted solution]

Hi @noynpe ,

your SDF file is not within the ETRS89 UTM 32 boundaries if you load it into Civil 3D.

This is the explanation why you get the error message in InfraWorks, when you export into a different CS.

The User Coordinate System is not relevant in InfraWorks when it comes to transformation, because it's only used for displaying the coordinates in the lower left corner.

The boundary check in InfraWorks is only done if a transformation between coordinate system happens.
A Model Builder model has a database CS = LL84. If you export to ETRS89 UTM 32 a transformation needs to be done and the CS check finds your data is out of boundary.
A possible solution is to create your own ETRS 89 UTM 32 system with different boundaries with the help of Map/Civil 3D.

If you create a new local InfraWorks model with database CS = ETRS89 UTM 32 and you export from there to ETRS89 UTM 32 - no transformation is conducted, so no boundary checks are not done and no error message appears.

The future best practices workflow is to create a Model Builder model directly in the desired CS to avoid such workflow hiccups with transformation of data. This will be possible in the Model Builder in the next InfraWorks release.

Regards,
Karsten

[noynpe]

Thank you very much for the good explanation @Karsten.Saenger !

Excellent to hear that creating models in model builder with different coordinate systems will be avaliable in the next release!

For now the temporary fix is creating a new model without using the model builder as it was not strictly necessary in this case. But the problems remains with older models that has been upgraded.. I will try your recomendation for these as son as I get a chance.

[noynpe]

Thank you very much for the good explanation @Karsten.Saenger !

Excellent to hear that creating models in model builder with different coordinate systems will be avaliable in the next release!

For now the temporary fix is creating a new model without using the model builder as it was not strictly necessary in this case. But the problems remains with older models that has been upgraded.. I will try your recomendation for these as son as I get a chance.