-
Notifications
You must be signed in to change notification settings - Fork 2
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
Coordinate System to support OBJ models #117
Comments
isn't this just basis change for objects (pretransform?) |
Hi @haraldsteinlechner. A pre-transform would work if PRo3D could recognize or be told that it is importing an OBJ in this particular reference frame. Let me know if there is any information I can provide. Thanks! |
basically the arguments to FromCoordinateFrame - question is how well this needs to be prepared for users - could this be just a choice of presets? |
maybe we can agree on one or two presets, A full blown import dialog or UI would be quite costly to implement and difficult to use. |
Hi @ThomasOrtner, note that the Sol51 model and many of the early models are in a different transformation. Only the last few models are in the X-Y-Z=East-North-Up orientation that I think makes the most sense going forward. Sorry for the confusion, but the scalebar is there to specify North, and the text on the scalebar is normal to the Up vector. If a strategy works for the Sol 204 model, then that is sufficient. |
In light of the above, I don't think we should call this special transformation "sketchfab" or "cdt". How about "ENU" to describe East-North-Up for X-Y-Z? |
Hi @ThomasOrtner and @haraldsteinlechner, There is something odd happening with the left-handed XYZ bars that PRo3D displays. The X-axis crossed with the Y-axis should give Z-axis (per the right-hand rule), but these bars give X x Y = -Z. This really confuses me! I could believe it if the "flip Z" button turns Z into -Z and just forgets to actually turn around the blue vector. Ok, so, the blue vector might or might not be accurate. What is important is the following:
If the above is satisfied, then the Z-axis can be up or down and it shouldn't matter. Once we get this settled, then I can start measuring Strike&Dip and confirming that we get the values expected. I appreciate your work on this, PRo3D will be an incredible tool once it works for these models. Thanks a lot! |
Hi Thomas,
Thank you. I checked the strike and dip tool and its angles look right. I
imported a cube that was rotated by 30-degrees along each of the three
Euler axes. I expected to get slopes between 30 and 60 degrees and bearings
approximately120 degrees apart. That is what I got!
I was confused by the difference between Bearing and Slope in the
Measurements table versus Dipping Angle and Orientation in the
Dip&Strike table. Do you know what bearing and slope are in this context?
CT
[image: image.png]
|
Nevermind, I read the manual about the bearing and slope. |
I hope you values make sense now, these values and namings are often discussed and not 100% clear. I am open to suggestions, Steve and Rob also have some comments on that I suppose. |
- improved true thickness computation via point over plane height - merged xzy coordinate system and renamed it to ENU (East North Up) [#117](#117) - added missing calculation numbers of measurements to csv export (slope, bearing, vertical distance, horizontal distance) [#100](#100) - added `showText`flag to annotations to show or hide text [#114](#114)
what is the status of this one @ThomasOrtner |
…el.fs => MeshLoaderType), first implementation of #274, the sketchfab transformation is unclear to me - fixed it temporarily to make show the results of #274 (further discussion here #117), started integrating glTF loader, renamed SurfaceType.SurfaceOBJ to SurfaceType.Mesh which better fits its semantics
There is a conversation thread with Christian Tate link. Objs downloadable from sketchfab on Christians account do have the wrong orientation.
Further, xyz axis do align with north east and up and should be used for dip and strike and other measurements.
yellow expected behavior
best what we can do currently in PRo3D ... yx horizontal plane is vertical
add new coordinate system to support roverframe northed data with y as Up and z as North
The text was updated successfully, but these errors were encountered: