Closed soeren68 closed 2 years ago
Hey, I'll try to have a look over the weekend. Cheers
Hey,
that would be very nice - it’s not urgent. I just have some basic knowledge in Blender, and sometimes I do mapping missions with my Mavic Air. Could be fun to combine this and create something... WebODM is open source also – I couldn’t afford to buy commercial software like Agisoft Metashape or pay for Pix4D services. Maybe it will be interesting for you to see what kind of files WebODM generates… And maybe it’s just a question of the right settings for the import?
Cheers
Am 21.10.2021 um 10:01 schrieb Sebastian @.***>:
Hey, I'll try to have a look over the weekend. Cheers
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/SBCV/Blender-Addon-Photogrammetry-Importer/issues/42#issuecomment-948358632, or unsubscribe https://github.com/notifications/unsubscribe-auth/AWEVUCRCPMPLNAW7IJUXMJ3UH7CFZANCNFSM5GMNKBWA. Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
Hi,
after examining your example I've seen that the data structure of WebODM is quite different compared to OpenSfM.
The data structure of a typical OpenSfM.json
file looks like the example image below. (You can find the full OpenSfM example here)
As you can see the *.json file contains an entry cameras
containing projection_type
, width
, height
, focal
, ... as well as an entry shots
containing the rotation
and translation
for each input image.
In contrast the WebODM result is represented by a folder containing cameras.json
, images.json
and much more. The cameras.json
corresponds more or less to the cameras
entry in theOpenSfM.json
file. However, the images.json
does not contain the rotation
and translation
values for the input images (but only the latitude
, longitude
and altitude
of the camera). See the example from your *.zip
below:
It looks like WebODM removed at some point the information of the local SfM reconstruction?!
On the ODM webpage (not WebODM
), there is a short description of the results generated by ODM
(again not WebODM
).
|-- images/
|-- img-1234.jpg
|-- ...
|-- opensfm/
|-- see mapillary/opensfm repository for more info
|-- odm_meshing/
|-- odm_mesh.ply # A 3D mesh
|-- odm_texturing/
|-- odm_textured_model.obj # Textured mesh
|-- odm_textured_model_geo.obj # Georeferenced textured mesh
|-- odm_georeferencing/
|-- odm_georeferenced_model.laz # LAZ format point cloud
|-- odm_orthophoto/
|-- odm_orthophoto.tif # Orthophoto GeoTiff
As you can see, this list an OpenSfM
folder. I think the information we are looking for resides in this folder. Can you create this folder with WebODM
as well?
Hi Sebastian,
I’m really grateful for your efforts, thank you. Well, I’m not a developer, just somebody who plays sometimes with Blender and does some mapping missions with his drone… And when it comes to WebODM, I’m really a newbie. Would it be o.k. for you if I forward your analysis to the WebODM developers? I think it would be great if the open-source Blender could work with an open-source photogrammetry solution.
Cheers, Sören
Am 25.10.2021 um 17:20 schrieb Sebastian @.***>:
On the ODM webpage https://github.com/OpenDroneMap/ODM (not WebODM), there is a short description of the results generated by ODM (again not WebODM).
|-- images/ |-- img-1234.jpg |-- ... |-- opensfm/ |-- see mapillary/opensfm repository for more info |-- odm_meshing/ |-- odm_mesh.ply # A 3D mesh |-- odm_texturing/ |-- odm_textured_model.obj # Textured mesh |-- odm_textured_model_geo.obj # Georeferenced textured mesh |-- odm_georeferencing/ |-- odm_georeferenced_model.laz # LAZ format point cloud |-- odm_orthophoto/ |-- odm_orthophoto.tif # Orthophoto GeoTiff
As you can see, this list an OpenSfM folder. I think the information we are looking for resides in this folder. Can you create this folder with WebODM as well?
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/SBCV/Blender-Addon-Photogrammetry-Importer/issues/42#issuecomment-951036682, or unsubscribe https://github.com/notifications/unsubscribe-auth/AWEVUCXG3JSFXODWCQ5X2WLUIVYTBANCNFSM5GMNKBWA. Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
Would it be o.k. for you if I forward your analysis to the WebODM developers?
Sure, no problem.
Besides, do not hesitate to come back to me. I think it would be nice, if this addon would also support ODM
/ WebODM
.
Hi Sören, have you received some useful answer of the WebDOM developers?
Hi,
I tried to import some files that were made in WebODM... With the LAZ it worked, but it took very long time. But I couldn't import any of the json-files, for example the "cameras.json" I know that WebODM is based on OpenSFM, so I used that option. Here is a link to a ZIP of all the files: https://testhub.dronedb.app/r/soeren68/42cjmkvjidqsbxaf ("all.zip" on top of the list) Maybe you can analyze the files somehow and discover what's the problem with the WebODM output...
Greeting from Germany, Sören