Le mardi 22 octobre 2013 22:21:41, Jukka Rahkonen a écrit :
Chris Hanson xenon at alphapixel.com writes:
What is the proper process for requesting a DataWindow region
and getting a proper reoreferenced raster subset back?
I am not sure about how changing the DataWindow size in the XML
Hello,
Le mardi 22 octobre 2013 20:00:16 Even Rouault a écrit :
Le mardi 22 octobre 2013 17:53:27, Yves Jacolin (Free) a écrit :
[..]
Which is incorrect (check the decimal caracter) and is create on l.469 in
the cpp file.
Salut Yves,
Yes this is a known issue that has been fixed
thanks, I tried this yesterday but I get another issue:
/home/yjacolin/Documents/Dev/gdal/gdal/frmts/wms/wmsutils.cpp:136: multiple
definition of `URLSearchAndReplace(CPLString*, char const*, char const*,
...)'
/home/yjacolin/Documents/Dev/gdal/gdal/frmts/o/.libs/stuff.o:/home/yjacoli
Thanks Hermann for your explaination.
I probably made a typo because now the pixels have different colors/values
as I would expect.
Thanks,
Paul
*Paul Meems *
Release manager, configuration manager
and forum moderator of MapWindow GIS.
www.mapwindow.org
Owner of MapWindow.nl - Support for
Le dimanche 20 octobre 2013 18:21:23, Frank Warmerdam a écrit :
Even,
I'm happy with this RFC. It's a bit sad that the list of domains is
duplicated and has to be freed again by the caller, but it certainly
avoids any doubts about the lifetime of the returned list.
Hi Frank,
Indeed, for
Hello List,
Apologies if this is a repeat post. Not sure that I was subscribed properly.
I have a number of individual Landsat bands that I'm converting to GeoTiff and
would then like to merge to a multiband file using either gdal_merge.py or
another gdal utility (gdalbuildvrt,
Even,
I have been trying to think through how an OGR driver for ISO19115 / 19139
would work. I'm going to work on a band aid to the new BAG tweak to their ISO
metadata, but we definitely could use a bare driver for read / write. The
quest boils down to what is the minimal set of things that
Kurt,
I have been trying to think through how an OGR driver for ISO19115 / 19139
would work.
Do you mean a driver that would read (and/or write) ISO 19139 XML files ? Do
such documents fit (enough) well with the OGR data model ? Is there a concept
of record/feature ? I'm unfortunately not
Does that include the upcoming ISO19115-1 ?
Doug
On Wed, Oct 23, 2013 at 10:29 AM, Even Rouault even.roua...@mines-paris.org
wrote:
Kurt,
I have been trying to think through how an OGR driver for ISO19115 /
19139
would work.
Do you mean a driver that would read (and/or write) ISO
Michele,
I have a number of individual Landsat bands that I'm converting to GeoTiff
and would then like to merge to a multiband file using either
gdal_merge.py or another gdal utility (gdalbuildvrt, gdal_translate). In
the individually derived geotif files, I am able to internally label
The reader in the BAG directory is a bare minimum implementation. Out side
of BAGs there is definitely a need. Pardon my ignorance, but what is CSW?
OGC CSW (Catalog Service Webservice) :
http://www.opengeospatial.org/standards/cat
And there are a few OSGeo related projects around this :
-
Thank you Even,
Very useful information.
Kind regards,
Michele
-Original Message-
From: Even Rouault [mailto:even.roua...@mines-paris.org]
Sent: Wednesday, October 23, 2013 10:41 AM
To: gdal-dev@lists.osgeo.org
Cc: Thornton, Michele M.
Subject: Re: [gdal-dev] keep metadata tags when
ReprojectImage does not maintain areas of nodata as I would expect it should.
Small areas of nodata are getting erased and larger areas are reduced in size.
I'm reprojecting from geographic to Albers, using approximately the same cell
size (converted from dd to meters). I'm using GDAL 1.9.2
Le mercredi 23 octobre 2013 19:05:18, Ochs, Elke ERDC-RDE-CRREL-NH a écrit :
ReprojectImage does not maintain areas of nodata as I would expect it
should. Small areas of nodata are getting erased and larger areas are
reduced in size. I'm reprojecting from geographic to Albers, using
Thank-you Even,
The source nodata values that are erased in the target data source aren't 0,
but interpolated values based on surrounding non-nodata values.
I am using bilinear resampling in both my ReprojectImage and gdalwarp tests. I
don't know if that makes any difference (sorry I didn't
Hi,
I propose a motion to formally adopt RFC 42 : OGR Layer laundered field lookup
http://trac.osgeo.org/gdal/wiki/rfc42_find_laundered_fields
There was only a short discussion following the call for discussion:
http://lists.osgeo.org/pipermail/gdal-dev/2013-October/037188.html
So I
Le mercredi 23 octobre 2013 21:19:48, David Shean a écrit :
Even,
I encountered the issue you mention back in May:
http://osgeo-org.1560.x6.nabble.com/gdal-dev-ReprojectImage-and-nodata-td50
57270.html
The current ReprojectImage nodata handling is a bit confusing. Do you see
a
My first vote as PSC member:
+1
No doubt the feature will be useful and I trust that RFC is technically sound.
I wonder why the list of affected drivers does not include any of the
JPEG2000 drivers. Don't they need changes or is metadata handling in
JPEG2000 special in some way? I guess that
18 matches
Mail list logo
