I’m having an issue with an .OBJ 3D mesh that imports into Leapfrog in a local coordinate system instead of UTM, which prevents it from lining up with my sample locations and other datasets.
The mesh looks fine visually, but when I bring the OBJ into Leapfrog the coordinates clearly aren’t UTM—everything comes in as a small local grid instead of real-world Eastings/Northings. I’m assuming the problem is either:
The OBJ was exported with no spatial reference, or
It has an embedded local/custom coordinate system that Leapfrog is honouring.
I need the mesh to be in my project’s UTM zone so it aligns properly with sample points, topography, and geology.
Before I start re-processing or re-exporting the mesh, does anyone have pointers or workflows to convert/assign the correct CRS for an OBJ so Leapfrog reads it properly?
iniciar sessão para comentar.
All of the outputs we provide are in WGS 84. The geoalignment information is embedded in the file. Any projections beyond that are up to you but I can say we have lots of users that use our outputs in local coordinate systems.
I’m having an issue with an .OBJ 3D mesh that imports into Leapfrog in a local coordinate system instead of UTM. Because of this, it won’t line up with my sample locations or any of my other spatial datasets. Thanks
The OBJ is a 3D file, not a spatial file. If you need a 3D spatial file you should be using the KMZ or the LAS file types.
