Ciao Even,
I have asked daniele to make those changes (which have not been reviewed yet)
in order to move away from the explicit usage of Vector and HashTable in method
signatures in favour of using the respective interfaces (List and Map).
Daniele can add more as needed...
As you mentioned this
Thanks Frank for these remarks.
I work on pds driver (in fact the subdriver ISIS2). I agree with you
that
some folks would want to distinguish the various kinds of nodata
values.
And it's the reason i would like the default behaviour is we have
various no data value
but we can add a flag option
Hi,
We would like to use gdal_translate for reading fromn our WMS service which is
secured by our own certificate and thus not automatically trusted. Our
developer had a quick look on a gdal source code and tried to find how options
CURLOPT_SSL_VERIFYPEER (1) and CURLOPT_CAPATH (2) are used
Ciao Simone, Salut Even,
You guy did a great job improving the performance of reading and writing pixels
buffer.
http://www.mail-archive.com/search?l=gdal-dev%40lists.osgeo.orgq=ReadRaster_Direct
But, With great power comes great responsibility.
Now we find users asking for changes that are
Ciao Ivan,
well, what you are suggesting (deprecation/removal) cycle is a
standard policy within the porjects we have been involved, therefore
I am in favour of it. It is a natural way for having an API evolving.
On the other hand GDAL is well known for the rock solid stability of
its API, but
Le vendredi 10 décembre 2010 10:27:49, Simone Giannecchini a écrit :
Ciao Even,
I have asked daniele to make those changes (which have not been reviewed
yet) in order to move away from the explicit usage of Vector and HashTable
in method signatures in favour of using the respective interfaces
