hey, I am a new user and I am trying to figure out if there is a way to trim the model to present it to clients in a way that doesn’t show others property. this is my model
4 Likes
You can clean the models up in either blender.org or meshlab.net. There are a bunch of youtube videos for each detailing how. Meshlab is probably the fastest way to start.
3 Likes
I’m working on documentation for it, but you can also process the full dataset, load the orthophoto into QGIS, make a GeoJSON polyon boundary that represents the full extent of what you want out of the reconstruction, and then re-process with --boundary path/to/GeoJSON.geojson to have all the products limited to this boundary.
If you’re reasonably certain your model aligns with existing boundaries or imagery, you don’t need to process it twice. Just draw up your boundary polygon and away you go.
As Stephen said, you can certainly edit it with the tools he mentioned, but this may also be another path with less direct intervention on your part.
4 Likes
Aha! This is great! One of those features I hadn’t thought hard about.
2 Likes
I didn’t get hands-on with manual boundaries until the power pylon dataset, but it is so NICE to have exactly what you want across all products with (nearly) no fuss.
If Caleb has existing parcel boundaries they can convert to GeoJSON and load, then that’s even better.
I did exactly the workflow I described above here, Caleb:
3 Likes
k, what Saijin described is a little beyond my understanding but after I have trimmed the model in meshlab is there a way to bring it back in to WebODM for viewing or I that not possible
1 Like
nevermind I think I will try what you said when you say convert to “GeoJSON and load” what do you mean by that? sorry, I am very new and have limited understanding, but I am learning!
1 Like
Caleb,
Loosely, GeoJSON is a type of data format for geospatial data, sort of like a shapefile, GeoPackage, KML, etc.
In our case, I was recommending that you draw a bounding box around the boundary of the building or parcel you want to keep in QGIS, and then save it as a GeoJSON so you can load it into WebODM under the Boundary option in the Processing Parameters.
When you run the model with a GeoJSON boundary loaded, it will automatically clip all of the output products to that boundary.
So, in QGIS, you would ideally load your existing Orthophoto, make a New Temporary Layer as a Polygon, edit the new layer with the Digitizing Toolbar to draw your polygon, save the Temporary Layer, and then right-click Export As … GeoJSON to load into WebODM.
You can bring back in edited projects, you just need to replace them on disk by finding the directory that your processed data is in and replacing the existing model and textures with your modified one.
It may be something like:
C:\WebODM\resources\app\data\media\project\1\task\XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXX\assets\odm_texturing\
1 Like
I had this question in the spring… It would be great to be able to define a bounding box visually like what is done in Reality Capture… it makes this process trivial… Short of that, using Meshlab was the easiest for me…
1 Like
k so is this correct?
create the shape:
then export it
do I have my settings correct?
it shows up like this:
and then copy/paste into WebODM:
is this correct?
3 Likes
Absolutely perfect!
1 Like
k then I have to reload the model right?
1 Like
Yes, at this point, you’ll have to reprocess the model, but you won’t need to crop/modify any of your output products manually.
1 Like
restart from post process right?
1 Like
I did restart from load data myself, but I’m not certain what checkpoint would be “safe” later in the pipeline.
Maybe a full rebuild until I work that out?
2 Likes
just wanted to pop back on here and say that this method works impressively well and is fairly easy. thanks Saijin for the help
5 Likes
Hah! Looks great!
Glad it was easy enough.
2 Likes
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.