GDAL is coded in C (or maybe C++, I'm not sure). What I meant was I just used the output of the command line program gdalinfo to get at the coordinates (using the `` operator).

Doing that means incurring some overhead, but since you can cache the results you really only have to do /whatever you need to do/ once per image, so usually you don't care*.

Besides, if you need to, it's probably relatively easy to write XS extensions using the GDAL library. I just didn't have to. I wrote some pretty extensive interfaces to geos though.

* or at least, not if you've got about two hundred images, all about 10Mb+ in size. The overhead of starting a separate process and filtering its output will be dwarfed by the disk IO.


In reply to Re^3: Geotiffs and GTK2 by Joost
in thread Geotiffs and GTK2 by deadpickle

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":



  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.