On Tue, Jun 18, 2013 at 12:46 AM, Even Rouault
wrote:
>
> From gdal_translate man page:
>
>-b band:
>Select an input band band for output. Bands are numbered from 1.
> Multiple -b switches may be used to select a set of input bands to write to
> the output file, or
>
Le lundi 17 juin 2013 10:52:18, Paolo Corti a écrit :
> Hi list
> When working with NETCDF data I have always been finding extremely
> useful the NETCDF:filename:variable_name syntax.
> Now I have to process a large amount of GRIB data: do I understand
> correctly that the GRIB driver does not supp
Le lundi 17 juin 2013 17:55:19, Etienne Trimaille a écrit :
> Hi,
>
> I'm trying to use Python API with an OSM file.
>
> According to the documentation of OSM driver, we can use a custom
> OSM_CONFIG_FILE.
> http://www.gdal.org/ogr/drv_osm.html
>
> However, I can't find how to use my own config
I have created a ticket and a patch for this problem
http://trac.osgeo.org/gdal/ticket/5119
On Fri, May 31, 2013 at 3:28 PM, Etienne Tourigny
wrote:
>
>
> On Fri, May 31, 2013 at 1:04 PM, Jonathan Greenberg wrote:
>
>> Thanks -- I did notice it was an earlier version (switching to the latest
>>
Hi Ivan,
Fine, that makes sense. So, experience and technical reasons qualify one driver
to be up or down in the list. Thanks for the response.
--
Jorge Arevalo
Freelance developer
http://www.krop.com/jorgearevalo
http://about.me/jorgeas80
Enviado con Sparrow (http://www.sparrowmailapp.c
This is an old(ish) thread but I wanted to follow-up since I've been
dealing with SMB2 and GIS stuff recently and came across this in my
searches. Some of this is specific to reading files from a Samba
server (linux, typically), but modern Windows file servers have a
similar problem. A couple of
Hi,
I'm trying to use Python API with an OSM file.
According to the documentation of OSM driver, we can use a custom
OSM_CONFIG_FILE.
http://www.gdal.org/ogr/drv_osm.html
However, I can't find how to use my own config file with the API.
from osgeo import ogr
osmfile = 'test.osm'
driver = ogr.G
Jan Hartmann uva.nl> writes:
>
>
> Hi Peter,
> You can get a compress-ratio to about 10% of the original size
> with the GDAL option -co COMPRESS=JKEG -co PHOTOMETRIC=YCBCR.
> Perhaps even more for you sort of data. Of course that compression
> is lossy, so for archi
Hi Peter,
You can get a compress-ratio to about 10% of the original size with the
GDAL option -co COMPRESS=JKEG -co PHOTOMETRIC=YCBCR. Perhaps even more
for you sort of data. Of course that compression is lossy, so for
archival purposes it is useless. For viewers, you won't note the
differenc
Hi list
When working with NETCDF data I have always been finding extremely
useful the NETCDF:filename:variable_name syntax.
Now I have to process a large amount of GRIB data: do I understand
correctly that the GRIB driver does not support such a syntax?
In such a case, is there a way to access to a
Selon Peter Freimuth :
> Hi,
>
> I have a 5 band, 16-bit orthorectified GeoTIFF from a satellite image that
> contains a significant amount of blackfill and has a file size of over 21GB.
> I would like to decrease the file size by eliminating or negating the
> blackfill. I have attempted to use th
11 matches
Mail list logo