Empty Textured Mesh

New to webodm. Paid for and using the windows installer. Have a small project that I need to create a 3D textured mesh for. After running several tests with anywhere from 50-100 images, the textured meshes are empty. I did a manual flight at varying heights and distances - this was not flown in a “grid” or defined project with an app - most of the time I can’t use the flight planning apps, I have to fly manually to avoid obstacles, trees, etc.
If I load the 3D map in WebODM, there is nothing there. If I try to import the OBJ file into Esri, there is nothing there. WebODM creates a pretty good point cloud though, so I know it’s processing data. Is this an issue or bug with the software? I’ve used Drone2Map and Pix4D in the past so I’m familiar with processing data in general. Again, I’m new to webodm so I plan to mess with settings and tweak things but it seems odd that right out of the box i’m getting an empty textured mesh when the point cloud is actually really good. Any initial thoughts? Am I missing something basic when processing?



Sorry for the trouble.

Can you try importing the OBJ into a proper 3D program like Blender or MeshLab to verify the model?

1 Like

Hadn’t heard of MeshLab before, thanks for that. I was able to load the OBJ file and it looks pretty good. Guess I’ll have to mess with WebODM and figure out why it doesn’t show up in the 3D map. And I know OBJ files are temperamental with Esri so I’ll have to do some testing this weekend. But thanks for the meshlab suggestion - at least I know it’s being processed.


The Waveform OBJ format doesn’t have an official specification for geolocation, so it likely needs to be manually referenced to line up with your GIS data in ArcGIS/ArcMap.

See this for some more information:

1 Like

Yeah I’ve had to do that before with meshes in ArcGIS Pro, but I’m following the same process as I did in the past with the output from WebODM and it’s not working. Pro won’t load the mesh file correctly. I read through that post about offsets and it’s not really clear. Here are my values in each of those files.

mtllib odm_textured_model_geo.mtl
v 2.760751 0.506292 -5.248561

439714 4844981

I’m not sure what this person means when they say “take the xxxxxx values, add with the aaaaaa → get UTM easting. take the yyyyyy values, add with the bbbbbb → get UTM northing”

What is “add with”? Just add the values after/before?

1 Like

I guess that was it. I thought I had clicked everything I could think of. It makes sense since the model doesn’t have the correct coordinate values so the 3d map doesn’t initially know “where” it is? Hitting full extent brought the model into view.
Lots of oddities to learn with new software I guess. Thanks.


Nope, it has the proper coordinates and the map/viewer locate it properly. The issue is a result of a fix we made where the viewport can permanently break when a user removes camera animation path nodes. As a side-effect, the camera starts at an aribitrary location and needs to be centered on the dataset for most models.

1 Like

It looks like you’ll need to manually edit the OBJ file’s mesh vertices. So what they’re talking about in that post is taking the existing vertex locations in the OBJ and adding the offset values to each of them.

I have not tried this procedure yet, however.

1 Like

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.