Hi,
- try adding the following line:
outlayer-SetFeature(outfeature);
after:
outfeature-SetField(production, FALL-Production);
ends up being:
[...]
outfeature-SetField(production, FALL-Production);
outlayer-SetFeature(outfeature);
[...]
make sure OGRDataSource::DestroyDataSource(outsource) is
, 2014 at 11:06 AM, Daniel Testa danielte...@suremptec.com.ar
wrote:
You could have the dataset report subdataset names, like
LANDSAT8:LC82300942013289LGN00_MTL.txt:panchromatic,
LANDSAT8:LC82300942013289LGN00_MTL.txt:multispectral, etc... And when
those
names are passed to the Open
You could have the dataset report subdataset names, like
LANDSAT8:LC82300942013289LGN00_MTL.txt:panchromatic,
LANDSAT8:LC82300942013289LGN00_MTL.txt:multispectral, etc... And when
those
names are passed to the Open() methods would return a dataset that would
point
to the relevant tif.
I see
Hi, I'm writing to you because I need support for the new Landsat-8
metadata format (_MTL.txt file)
I took a look at the latest version, 1.11.0, and I couldn't find anything
on the matter. So, I was thinking I could add support for the new format by
myself.
There are 3 groups of bands:
Hi Even,
There's no real need of a new API for that (although it might be cleaner
to
have a dedicated one at some point). I'd note that your proposed API would
only work for a single subdataset, not a vector of them.
Sorry, my bad. Should have been:
GDALDataset** pporSubDatasets;
virtual
It is also possible that the GDAL GeoTIFF driver actually needs the
libgeotiff support csv files which would normally live somewhere like
/usr/share/epsg_csv and key files would have names like
coordinate_reference_system.csv.
Best regards,
Frank
On Wed, Oct 2, 2013 at 2:29 PM, Daniel Testa
Hello everyone, I´m experiencing a weird behavior when reading a raster
image (GTiff/GeoTIFF)
I'm using GDAL 1.9.1 for Linux (Ubuntu 12.04 LTS) and Windows (Win 7
Ultimate SP1) to open a raster image with EPSG:22194
Sample output from gdalinfo for that image on Windows (WKT):
[...]
PROJCS[Campo
