Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Model Coordinate System #32

Open
VCGP-TIAANJ opened this issue Dec 9, 2024 · 3 comments
Open

Model Coordinate System #32

VCGP-TIAANJ opened this issue Dec 9, 2024 · 3 comments
Assignees

Comments

@VCGP-TIAANJ
Copy link

Hi,

I am having issues with my iTwin mode (based in HS2 Snake Grid) being placed geographically not aligned with the Cesium tiling.
My 4D model is working, but it is being placed somewhere in the sky and miles away from the location it should be.

We have resolved this issue earlier, but am looking for a permanent fix to address this issue.

Regards,
T

@AlexandreWalensa
Copy link
Collaborator

Hi John,
Thanks for having shared your iTwin.
I have noticed that the "project extents" of your iModel is huge (more than 200 km along the Y axis) compared to the size of the actual model.
This can lead to several issues:

  • When loading the iModel, the actual model appears very far away from the camera (more than 100 km in your case), because the GeoReference is set at the center of the project extent box.
  • Even after manually fixing the GeoReference position, the model may still appear at an incorrect position because of precision issues due to the large extents.
    So, could you try to adjust the project extents so that it encompasses your model more closely ?

@VCGP-TIAANJ
Copy link
Author

VCGP-TIAANJ commented Dec 10, 2024 via email

@AlexandreWalensa
Copy link
Collaborator

AlexandreWalensa commented Dec 11, 2024

Hi Tiaan,
The first issue I mentioned (model appearing far away from camera) can be easily fixed in Unreal by shifting the placement of the GeoReferences.
However, for the second the second issue (wrong placement dur to potential precision issue), as far as I know there is no workaround.
It would be very helpful if you could try adjusting the model position and extents in synchro, so that:

  • the model is located around the origin in local space (currently the model is around local position |x = 280 km, y = 280 km])
  • the extents closely encompasses the model.

This would allow me to quickly see if it is really a precision issue.
In the meantime, I will continue to try to spot a precision issue in the code.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants