Lately I’ve been thinking a lot about what’s inefficient about the current state-of-the-art for publishing/sharing aerial images. I think Google Drive / Dropbox / USB drives and zip files have served us well, but I think there’s room for improvement.
I think that’s a fantastic idea. It’s actually something I had tried to setup In a manner for myself using an existing package but just couldn’t get it to run properly.
I’m assuming that you’re thinking along the lines of a web-ui again? Sort of Lightroom for drone and photogrammetry users.
The report generation would be brilliant. I actually find it quite awkward to go back and find out the parameters I used to capture the images.
In my case it would the sort of thing I’d be happy to run on my new NAS server.
Longer term would you consider including flight logs? I appreciate that parsing many different manufacturer formats could be a pain. It does however link in with the capture pattern, and could be expanded to be a self hosted version of of the likes of DroneLogBook or AirData.
Yes there will be a web component to access the database (along with a desktop application for managing the database also).
When you say “find out the parameters you used to capture”, which specifically do you mean (overlap? flight speed?)
Definitely looking to add support for flight logs (GCPs, orthophotos, elevation models and point clouds are in the plans as well). By chance would you have a copy of a few logs that you could share (I don’t have much experience with flight log formats)? Would be helpful to have a few examples.
For flight parameters I’d say at a minimum flight speed, front lap, side lap, and any common image capture parameters (iso, shutter speed, white balance), perhaps with user fillable options to add in basic weather params (cloud cover, wind speed). And perhaps total flight time and batteries used if flight logs are added in.
I’ll dig out some flight logs. I have access to a DJI Phantom 3 Pro and a Yuneec H520 & E90 camera. One issue with logs you will come across is each mapping app for DJI products produces a slightly different log format. And theres quite a few different mapping apps!
On what scale or how much of the colourspectrum from a raw does the WebODM use (if it could read raw images)?
Hence JPG/TIF vs Raw colour spectrum.
I know raw from working in lightroom you get much large room to play with wider range of colours, so i just assume a raw file would give more data to play with. But also huge files…
Sorry, i noticed this was not the topic. More kind of metadata
I’m a fan of ODM. I bought the installers and have it running on my pc.
The list of points you shared are very interesting. I am using ODM for agriculture. I’m mapping crops with multispectral, RGB and thermal. I have couple of features I’d love to find on ODM:
Tree measurement (height / canopy width / volume)
Option for selection different types of multispectral cameras (RGNIR / RNIRB)
Besides the NDVI map, a simplified version of it, an AREAS map.
I am a user, not a developer, and I’ve not idea of how feasible, easy or difficult it can be to have those features. What do you think?
Not sure if this could help but a buddy and I have a project going that allows to parse DJI txt flight logs (such as from DJI Go) and convert those to kml files. Perhaps the parsing could be useful to you for your project?
I’ve been wondering about adding the ability to review flight logs on an offline map and view locations along the flight path where photos were taken to get coordinates, etc.