What are some algorithms involved in building a project like this?
OpenDroneMap
41–50 of 66 posts
Re: OpenDroneMap
#42What are some algorithms involved in building a project like this?
Re: OpenDroneMap
#43edit: the above was user error (or my lack of patience waiting on the high-rez final photo to load!), everything works wonderfully.
Re: OpenDroneMap
#44This is a very cool software! I highly recommend to try it out if you own a drone, even if just for a fun, I learned so much when I was tinkering with it. Around a year ago I needed to obtain an aerial map of some specific area, but due to recent drastic changes (construction work) and poor quality of the public maps I had to somehow create my own. I fly drones for recreational purposes so I was thinking about using…
Re: OpenDroneMap
#45This is really cool, just took my drone out and took 64 pics of my neighborhood and turned them into a TIFF viewable on qGIS via the ODM CLI. Love it. There are a few oddities, for example it produced a few geoTIFFs for viewing, two of them are correctly placed, but the high resolution one doesn't seem to contain geo bounds and just displays in qGIS adjacent to the world map. Seems like there's still some development…
Re: OpenDroneMap
#46This is really cool, just took my drone out and took 64 pics of my neighborhood and turned them into a TIFF viewable on qGIS via the ODM CLI. Love it. There are a few oddities, for example it produced a few geoTIFFs for viewing, two of them are correctly placed, but the high resolution one doesn't seem to contain geo bounds and just displays in qGIS adjacent to the world map. Seems like there's still some development…
Glad you like it! :) Is this the odm_orthophoto_render.tif file? If so, that's normal. That file is not a higher resolution image, it's just an intermediate file that doesn't have georeferencing and compression. The final georeferenced image, odm_orthophoto.tif, by default is cropped to the bounds of the model and you can disable that by passing "--crop 0". The two images will look identical without crop.
Thanks so much for the ad hoc tech help, will definitely be playing with this more!
Re: OpenDroneMap
#47Earlier quoted context omitted.
Glad you like it! :) Is this the odm_orthophoto_render.tif file? If so, that's normal. That file is not a higher resolution image, it's just an intermediate file that doesn't have georeferencing and compression. The final georeferenced image, odm_orthophoto.tif, by default is cropped to the bounds of the model and you can disable that by passing "--crop 0". The two images will look identical without crop.
Very interesting, thank you! i mostly drone as a hobby to get some interesting shots, so this is my first foray into using it to do anything like this. Indeed I am talking about odm_orthophoto_render.tif, I assumed it was the higher resolution one because of the size (about 3x the size of the other two), and qGIS was not treating odm_orthophoto.tif well, but after closer inspection looks like qGIS just didn't like od…
You can also use --build-overviews for speeding up load times in QGIS or --cog for generating Cloud Optimized GeoTIFFs that both open fast in QGIS and can be streamed fast over HTTP.
Re: OpenDroneMap
#48Earlier quoted context omitted.
I found, in practice, that the divide and conquer approach led to weird altitude artifacts, where different divisions would result in different heights, so the point clouds didn't line up. Could have been a one off bug though.
It can happen; point cloud alignment between submodels can be tricky. Sometimes increasing the amount of split overlap can help, but not always.
Re: OpenDroneMap
#49Earlier quoted context omitted.
It can happen; point cloud alignment between submodels can be tricky. Sometimes increasing the amount of split overlap can help, but not always.
Amazing piece of software! I've a question. It's a bit unclear to me, is there a global adjustment applied to the sub-blocks that would help with the overlap issues?