[OpenDroneMap-users] question about resolution and camera orientation

[Stephen Mather]

Hi Anna,

Yes "--resize-to" will typically help get you a denser point cloud. I have
found --resize-to 3000 to be a useful default, though the project currently
defaults to 2400 to avoid swamping people's machines.

There's a lot to be done on the documentation side. Also, while the meshing
and texturing portions of the codebase are novel, some other portions
(Bundler, CMVS, PMVS) are projects onto themselves, so it will take a bit
of exploration to figure out optimal parameters. As we (as a community)
discover those optimal parameters, we can improve the sane defaults, and
document good alternatives.

(That said, there is plenty of documentation to be written that I or others
already know, so that is a priority)

As to XYZ, yaw, pitch, and roll, OpenDroneMap does not yet take that into
account. I would be excited to see this, perhaps even using SFCGAL or other
3D library for doing proper image footprints a la:

https://smathermather.wordpress.com/2013/12/15/uas-drone-footprint-geometries-calculated-in-postgis-with-sfcgal-for-real-this-time/

This would substantially reduce the processing time on the "match" step,
which is a decent proportion of the current processing time.

Also, I haven't written any documentation on it yet, but in the bundle.out
file in reconstruction-with-image-size-2400 can be loaded in Meshlab to
check camera positions and determine sanity of camera positions. There's a
youtube video on that somewhere that I'll dig up.

Cheers!
Best,
Steve





On Tue, Feb 24, 2015 at 1:52 PM, Anna Petrášová <kratochanna at gmail.com>
wrote:

>
>
> On Tue, Feb 24, 2015 at 1:32 PM, Andy Wilde <awilde76 at gmail.com> wrote:
>
>> Hi Anna,
>>
>> For the resolution issues please read the wiki information which shows
>> some of the parameter information.  This documentation is still under
>> development and will improve.
>>
>
> Yes, I looked at the wiki, but I couldn't find what I was looking for. I
> am still experimenting with different parameters so I will see. I will
> definitely keep checking the wiki.
>
>>
>> For the X, Y, Z values the system will interpreted GPS information if it
>> is in the image data,  I would expect that it will interpret x,y,y values
>> in much the same way.  For the roll and yaw I do not think it will
>> recognise this as yet.
>>
>
> Thanks,
>
> Anna
>
>>
>>
>>
>> —
>> Sent from Mailbox <https://www.dropbox.com/mailbox>
>>
>>
>> On Mon, Feb 23, 2015 at 9:28 PM, Anna Petrášová <kratochanna at gmail.com>
>> wrote:
>>
>>> Hi,
>>>
>>> I am trying to run opendronemap on my 200 images and a better
>>> documentation of the different options would help me a lot. (I know,
>>> writing documentation is always painful.) So I have a couple of questions.
>>>
>>> 1. How do I increase the resolution? I need the point cloud from which I
>>> would construct high-resolution raster DSM. Would higher --resize-to do the
>>> job? Or a different parameter?
>>>
>>> 2. I have the external orientation of camera (x, y, z, yaw, pitch,
>>> roll), is there any way the algorithms could take advantage of this
>>> information? I can imagine using these as initial values for the algorithm.
>>>
>>> Thank you for this great software!
>>>
>>> Anna
>>>
>>
>>
>
> _______________________________________________
> OpenDroneMap-users mailing list
> OpenDroneMap-users at lists.osgeo.org
> http://lists.osgeo.org/cgi-bin/mailman/listinfo/opendronemap-users
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/opendronemap-users/attachments/20150224/8c679f71/attachment.html>