Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

OpenDroneMap

opendronemap.org

Post reply on HN
Print view View original

61–66 of 66 posts

Re: OpenDroneMap

#61

Post by kfarr »

pierotofy wrote: post #53
kfarr wrote: post #52

Earlier quoted context omitted.

Very cool! I noticed AGPL 3 License, do you offer licensing options if folks want to host this integrated with other closed source code? Or would it be permissible to create a "microservice" with ODM only that closed source software can use API calls to contact?

We do not offer other licensing options. We encourage people and organizations to create services that leverage ODM, closed or open, while respecting the terms of the AGPL.

Thanks I also see there is webodm.net which fits the bill to pay for a third party service.

Re: OpenDroneMap

#62

Post by pierotofy »

the__alchemist wrote: post #58
pierotofy wrote: post #55

Earlier quoted context omitted.

Pretty much any camera (even multiple cameras), from any orientation (no gimbal required). Also works with your cellphone camera or DSLR camera. Just try not to change the focus between shots too much. DJI models are well supported.

Are DJI models the only ones supported?

Nop, you can use pretty much any drone camera.

Re: OpenDroneMap

#63

Post by pierotofy »

palata wrote: post #57
laen wrote: post #6

I've been trying to get my organization to use ODM, but finding it difficult. The problem is analogous to the issues that Gimp has to Photoshop or Linux to Windows -- ease of use. Additionally, even if you properly configure the software the quality still is not comparable to the big proprietary players in the photogrammetry field: Bentley Systems; Pix4D; Drone Deploy. A major reason for the quality issues is that th…

> A major reason for the quality issues is that the major drone manufacturers work directly with the proprietary photogrammetry software providers in the field to optimize the algorithms to their drones. Would you care to elaborate? My belief is that all the photogrammetry engine wants is that the drone manufacturer does as few processing as possible on the images, in order to not alter the geometry. I don't see what…

Direct knowledge of the lens distortion model and complete control of the image generation, with perfect knowledge and use of the associated metadata tags, can certainly give an engine a leg up in some cases. One example I can think of is the Parrot Sequoia which is a camera that works OK-ish in ODM, but works flawlessly with Pix4D (which is owned by Parrot).

Re: OpenDroneMap

#64

Post by palata »

pierotofy wrote: post #63
palata wrote: post #57

Earlier quoted context omitted.

> A major reason for the quality issues is that the major drone manufacturers work directly with the proprietary photogrammetry software providers in the field to optimize the algorithms to their drones. Would you care to elaborate? My belief is that all the photogrammetry engine wants is that the drone manufacturer does as few processing as possible on the images, in order to not alter the geometry. I don't see what…

Direct knowledge of the lens distortion model and complete control of the image generation, with perfect knowledge and use of the associated metadata tags, can certainly give an engine a leg up in some cases. One example I can think of is the Parrot Sequoia which is a camera that works OK-ish in ODM, but works flawlessly with Pix4D (which is owned by Parrot).

But none of that is private data, right? It feels like "tuning". Surely one could characterise Sequoia to improve the camera model, and I doubt they encrypt the exif data, do they? Also Sequoia is a bit of a special example here, that most likely has been carefully tuned by Pix4D. But DJI most probably does nothing for Pix4D that ODM couldn't access.

Not criticising ODM (I love OpenSfM and ODM), on the contrary: I feel like those are not fundamental limitations of ODM, and one could put the work of improving support for specific cameras without the need for proprietary information available only to Parrot employees.

Or am I missing something?

Re: OpenDroneMap

#65

Post by palata »

the__alchemist wrote: post #50

What sort of setups does this support? What drone models and firmware? What sort of cameras are supported? Quads? Fixed? DJI? Betaflight? Ardupilot? Does it need a camera with a gimbal?

The nice thing is that the drone is completely independent :-). You can use any frame (quad, heli, fixedwing, vtol, rover, boat, submarine, ...) with any autopilot (betaflight, ardupilot, px4, ...) and try it with any camera you want.

At the end of the day, all you need is pictures taken "the right way" for the engine. Typically, you want:

* Sufficient overlap between the pictures: you need multiple pictures looking at each point in the scene from different angles. * Don't change the focal length, because that changes the camera model and makes it at least harder for the engine. * Ideally have some fairly accurate GPS location in the exif metadata of the pictures. * Avoid motion blur (i.e. don't fly too fast for your camera), and blur in general (i.e. you don't want too much vibration, but you don't need a gimbal).

Some Android/iOS apps out there do "flight planning" for you, so it may help (you select the area you want to map and the app instructs the drone to take the right pictures for you). Different apps support different drones, so that's something you want to check.

But anyway you should try ODM, because it does not depend on the drone, it just needs pictures =).

Hope this helps.

Re: OpenDroneMap

#66

Post by pierotofy »

palata wrote: post #64
pierotofy wrote: post #63

Earlier quoted context omitted.

Direct knowledge of the lens distortion model and complete control of the image generation, with perfect knowledge and use of the associated metadata tags, can certainly give an engine a leg up in some cases. One example I can think of is the Parrot Sequoia which is a camera that works OK-ish in ODM, but works flawlessly with Pix4D (which is owned by Parrot).

But none of that is private data, right? It feels like "tuning". Surely one could characterise Sequoia to improve the camera model, and I doubt they encrypt the exif data, do they? Also Sequoia is a bit of a special example here, that most likely has been carefully tuned by Pix4D. But DJI most probably does nothing for Pix4D that ODM couldn't access. Not criticising ODM (I love OpenSfM and ODM), on the contrary: I fe…

EXIF data is not encrypted, but often times is not documented (or documented well). DJI has many differences between models (even between firmware versions). They also sell DJI Terra, which is their own photogrammetry solution.

The point being that you are correct, these are not limitations of ODM, but in some cases it does give vendors a head start (a leg up) in implementing good support for certain cameras, especially multispectral cameras like the Sequoia.

Post reply on HN