Rather than hardcoding assumptions or conclusions about what the machine is now, why not future-proof it?

Yes - that is certainly the plan.

It seems to me that if I need this functionality, someone else will as well. Or, at the very least, would benefit from a head-start in developing code for the next part of dealing with a GeoPackage. So some of the code will probably form a module for CPAN.

since you have not apparently tried sanity-checking your interpretation with another tool

I haven't yet as I have been away on training much of this week and haven't had the opportunity! I also feel that an external tool won't be very helpful for checking te envelope data. It will be the next step once I've decoded some fo the actual geometry data.

In reply to Re^10: Geo Package files by Bod
in thread Geo Package files by Bod

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.