Hi Even,
Thank you for your comments.
At this point the code serves the purposes of the gimed metadata editor.
Of course the utility is going to be re-written if it is to be included
in gdal (with different license).
All your suggestions are very welcome and will be taken under consideration.
Angelos,
Speaking for myself : Your utility is certainly usefull for your purposes, but
I'm not sure if there is enough "added value" and/or general purposeness to
include it as a new utility. Is the output of the utility aimed at some other
utilities of a larger processing chain ?
Some things
Hi everyone,
I have written a small utility based on gdal recently that extracts the
bounding box of any supported spatial data file.
http://gimed.svn.sourceforge.net/viewvc/gimed/trunk/utils/geo_extents.c?revision=14&view=markup
This utility is very useful for creating metadata geographic ext
Even Rouault wrote:
Frank,
swig/include/perl/gdal_perl.i and swig/python/setup.py still contains
reference to 1.7.2 version. The former preventing the Perl bindings from
building due to the mismatch (and in gdal-1.7.2.tar.gz, the perl bindings were
regenerated)
Even,
I have produced an RC2
Frank,
swig/include/perl/gdal_perl.i and swig/python/setup.py still contains
reference to 1.7.2 version. The former preventing the Perl bindings from
building due to the mismatch (and in gdal-1.7.2.tar.gz, the perl bindings were
regenerated)
About r21079, I'm curious of the circumstances that
