Hi,
I am working on swig bindings for librarified GDAL utilities as part of my
Google Summer of Code project. I have already librarified gdalinfo utility.
https://github.com/fazam/gdal/blob/gdalinfo/gdal/apps/gdal_utils.h
https://github.com/fazam/gdal/blob/gdalinfo/gdal/apps/gdalinfo_lib.cpp
The
+1
Daniel
On 2015-06-03 8:01 AM, Howard Butler wrote:
On Jun 3, 2015, at 4:13 AM, Even Rouault wrote:
Hi,
As no points have been raised on the RFC itself (peripheral discussions on how
to address out-of-range nodata values) :
Motion : I move to adopt RFC 58: Removing Dataset Nodata Value
Le mercredi 03 juin 2015 15:21:07, Rutger a écrit :
> Dear list,
>
> When i try to write a floating point Geotiff from Python (both 32 or 64
> bit), the resulting file size is significantly larger compared to the
> output of gdal_translate. I wrote a small test script which tests this it
> for var
Dear list,
When i try to write a floating point Geotiff from Python (both 32 or 64
bit), the resulting file size is significantly larger compared to the output
of gdal_translate. I wrote a small test script which tests this it for
various creation options like compression and block-sizes. It seems
Even Rouault spatialys.com> writes:
>
> Hi,
>
> As no points have been raised on the RFC itself (peripheral discussions on
how
> to address out-of-range nodata values) :
>
> Motion : I move to adopt RFC 58: Removing Dataset Nodata Value
>
> https://trac.osgeo.org/gdal/wiki/rfc58_removing_dat
> On Jun 3, 2015, at 4:13 AM, Even Rouault wrote:
>
> Hi,
>
> As no points have been raised on the RFC itself (peripheral discussions on
> how
> to address out-of-range nodata values) :
>
> Motion : I move to adopt RFC 58: Removing Dataset Nodata Value
>
> https://trac.osgeo.org/gdal/wiki/
On Fri, May 15, 2015 at 11:48 AM, Even Rouault
wrote:
> Dennis,
>
> https://www.digitalglobe.com/sites/default/files/ISD_External.pdf indeed
> confirms your findings (page 37 & 38, doc of originX and ulX)
>
on http://www.gdal.org/formats_list.html there isn't an entry to til
format or I'm mistake
Dear Even
There is an issue with the viewer! Why didn't I check this first?!
But I also liked a review of my commands, and they should be okay now when I
include the '-co TILED=YES'.
Thanks
--
View this message in context:
http://osgeo-org.1560.x6.nabble.com/gdal-translate-and-gdal-gdaladdo-t
Le mercredi 03 juin 2015 11:15:16, Koen2704 a écrit :
> Dear community
>
>
> I am trying to create tiled pyrimidal tifs through GDAL library tools:
> First I do: gdal_translate test.tif tiled_test.tif -b 1 -b 2 -b 3 -co
> COMPRESS=JPEG -co PHOTOMETRIC=RGB,
Note: the resulting dataset will not b
Dear community
I am trying to create tiled pyrimidal tifs through GDAL library tools:
First I do: gdal_translate test.tif tiled_test.tif -b 1 -b 2 -b 3 -co
COMPRESS=JPEG -co PHOTOMETRIC=RGB, then I do: gdal_gdaladdo --config
COMPRESS_OVERVIEW JPEG --config PHOTOMETRIC_OVERVIEW RGB --config
INTE
Hi,
As no points have been raised on the RFC itself (peripheral discussions on how
to address out-of-range nodata values) :
Motion : I move to adopt RFC 58: Removing Dataset Nodata Value
https://trac.osgeo.org/gdal/wiki/rfc58_removing_dataset_nodata_value
Starting with my +1
Best regards,
Ev
Hi,
I've just created the 2.0 branch so that development in trunk is not blocked
during the 2.0.0 release process.
So any fixes that should go to 2.0.0 (and later 2.0.X releases once 2.0.0 is
out) should go to branches/2.0 and trunk.
trunk is now 2.1.0dev
I'm still intending to snapshot the 2.0
12 matches
Mail list logo
