![]() Left handed, right handed, Z-up, Y-UP, Z-Down etc etc. The problem here is that there are loads of possible coordinate systems. It’s better if Three has a simple tool to let anyone convert the basis of imported data to Three’s rendering basis. I’m finding myself wishing I had an little app to generate the transforms between each coordinate system, so I could throw in my current and desired systems and get back a transformation matrix. Position is correct now but orientation still seems to be off. It’s quite a headache actually, converting from whatever coordinate system the GPS data is in (unknown, because I just have lists of lat/lon/alt positions and kappa/yaw/phi orientations), through Revit’s coordinate systems into the Forge Viewer system and then comparing it to the actual photos. In these cases it’s unneccesary mental overhead that should be stuck in a resuable method somewhere, although not necessarily on the three.js repoĪs another example aside from I’m currently dealing with matching GPS data from drone photos to 3D models, and I’m having to do loads of conversion between coordinate systems. However, it doesn’t account for times when users need to do this conversion manually. I’ve dealt with this in the LWOLoader and FBXLoader and agree with you, regarding importers specifically. However, the PR was not merged since we have come to the conclusion that exporters should perform the conversion of coordinate systems (and not the engine when importing 3D models) ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |