<div dir="ltr"><div class="gmail_default" style="font-family:arial,sans-serif">Zachary, </div><div class="gmail_default" style="font-family:arial,sans-serif"><br></div><div class="gmail_default" style="font-family:arial,sans-serif">The interesting geometry functions are essentially all from GEOS, so I'd suggest investigating there for information. </div><div class="gmail_default" style="font-family:arial,sans-serif"><br></div><div class="gmail_default" style="font-family:arial,sans-serif"><a href="https://trac.osgeo.org/geos/">https://trac.osgeo.org/geos/</a><br></div><div class="gmail_default" style="font-family:arial,sans-serif"><br></div><div class="gmail_default" style="font-family:arial,sans-serif">Most GDAL raster operations are essentially linear in the number of pixels though there are a few things (like hole filling, and polygonization, and contour generation) that have more interesting properties. I am not aware an effort to characterize the complexity of these in the GDAL project though at least some thought went into complexity analysis when implementing some of these.</div><div class="gmail_default" style="font-family:arial,sans-serif"><br></div><div class="gmail_default" style="font-family:arial,sans-serif">Best regards,</div><div class="gmail_default" style="font-family:arial,sans-serif">Frank</div><div class="gmail_default" style="font-family:arial,sans-serif"><br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Wed, Sep 2, 2020 at 12:50 PM Zachary Déziel <<a href="mailto:Zachary.Deziel@usherbrooke.ca">Zachary.Deziel@usherbrooke.ca</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div lang="EN-CA">
<div class="gmail-m_2145503460024538277WordSection1">
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">Hi all, <u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">Sorry for disturbing and I hope I am passing through the right channel for my question. If not, please feel free to redirect me!<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">I have been searching in the documentation and elsewhere for information regarding the time complexity of the algorithms of GDAL/OGR. More precisely around the classic operations on point, line and polygon data structures (buffer, intersect,
etc). I have not found any mention of complexity in the documentation. Is there some hidden documentation gem somewhere that covers the time and/or memory complexity of the algorithms? If no such documentation exists, are there reasons for it not existing?
Is it simply a matter of not being a priority in the development cycle?<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">Sorry for the compact and numerous questions, if you have any interest in the subject please reach out.
<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">Sincerely,<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">Zac<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
</div>
_______________________________________________<br>
gdal-dev mailing list<br>
<a href="mailto:gdal-dev@lists.osgeo.org" target="_blank">gdal-dev@lists.osgeo.org</a><br>
<a href="https://lists.osgeo.org/mailman/listinfo/gdal-dev" rel="noreferrer" target="_blank">https://lists.osgeo.org/mailman/listinfo/gdal-dev</a></blockquote></div><br clear="all"><div><br></div>-- <br><div dir="ltr" class="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div><font face="monospace">---------------------------------------+--------------------------------------<br>I set the clouds in motion - turn up | Frank Warmerdam, <a href="mailto:warmerdam@pobox.com" target="_blank">warmerdam@pobox.com</a><br>light and sound - activate the windows | +1 650-701-7823<br>and watch the world go round - Rush | Geospatial Software Developer</font></div></div></div></div></div>