Selon Trent Piepho tpie...@gmail.com:
Thanks. Would you mind attaching it in a ticket in GDAL trac :
http://trac.osgeo.org/gdal/newticket ?
I see you've created the ticket for the corresponding libgeotiff part. Before
applying the GDAL part, I think we should wait for Frank having reviewed and
I'm trying to compile GDAL 1.9.2 from source by myself using the DEBUG=1
build.
There is a flag on nmake.opt for VLD support:
MSVC_VLD_DIR=C:\Program Files\Visual Leak Detector
although, if I try to use it, it give me strange error while building gdal.
Anyways, I'm building gdal like this:
Nevermind, I got it
I was missing
nmake /f makefile.vc devinstall
On Fri, Nov 8, 2013 at 10:21 AM, Hugo Benicio hbobeni...@gmail.com wrote:
I'm trying to compile GDAL 1.9.2 from source by myself using the DEBUG=1
build.
There is a flag on nmake.opt for VLD support:
Hi all,
Sorry to bother you all again.
We're still struggling with upgrading to GDAL and GEOS.
When I use GDALv1.9 with GEOSv3.3.5 with our C++ application (MapWinGIS), I
have no problems.
The GEOS methods are still working. I've made a test to buffer a geometry.
When I upgrade to GDAL trunk
I guess this should have gone to the list too:
Am 07.11.2013 17:52, schrieb th...@usgs.gov:
All, At least this issue with codes has just not negatively impacted
the planetary community. While the planetary community had its own
attempted codes, maybe it is time to try to start shedding the use
On Thu, Nov 07, 2013 at 04:34:07PM -0500, Jack Howarth wrote:
The failures on x86_64-apple-darwin13 for the png.py test suite from auto
test for gdal 0.10.1 are the same failures described here...
https://github.com/licq-im/licq/pull/32
https://github.com/licq-im/licq/pull/32
The failures
On Fri, Nov 08, 2013 at 10:31:08AM -0500, Jack Howarth wrote:
On Thu, Nov 07, 2013 at 04:34:07PM -0500, Jack Howarth wrote:
The failures on x86_64-apple-darwin13 for the png.py test suite from auto
test for gdal 0.10.1 are the same failures described here...
Jack,
Is there an explanation someplace with more detail as to what is wrong those
png's, why older versions of libpng are okay with it and why libpng has changed
its behavior?
Thanks,
-kurt
On Nov 8, 2013, at 8:02 AM, Jack Howarth howa...@bromo.med.uc.edu wrote:
On Fri, Nov 08, 2013 at
On Fri, Nov 08, 2013 at 09:12:05AM -0800, Kurt Schwehr wrote:
Jack,
Is there an explanation someplace with more detail as to what is wrong those
png's, why older versions of libpng are okay with it and why libpng has
changed its behavior?
Thanks,
-kurt
Kurt,
The following link...
Hi,
Is there a list about the minimum GDAL version for each of the GDAL tools in
http://www.gdal.org/gdal_utilities.html?
-Jukka Rahkonen-
___
gdal-dev mailing list
gdal-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/gdal-dev
Le vendredi 08 novembre 2013 19:19:35, Jukka Rahkonen a écrit :
Hi,
Is there a list about the minimum GDAL version for each of the GDAL tools
in http://www.gdal.org/gdal_utilities.html?
Not directly. A solution would be to download the *doc packages on
http://download.osgeo.org/gdal/ and
Even Rouault even.rouault at mines-paris.org writes:
Le vendredi 08 novembre 2013 19:19:35, Jukka Rahkonen a écrit :
Hi,
Is there a list about the minimum GDAL version for each of the GDAL tools
in http://www.gdal.org/gdal_utilities.html?
Not directly. A solution would be to
Le vendredi 08 novembre 2013 19:30:34, Jukka Rahkonen a écrit :
Even Rouault even.rouault at mines-paris.org writes:
Le vendredi 08 novembre 2013 19:19:35, Jukka Rahkonen a écrit :
Hi,
Is there a list about the minimum GDAL version for each of the GDAL
tools in
On Fri, Nov 8, 2013 at 10:34 AM, Even Rouault
even.roua...@mines-paris.org wrote:
Le vendredi 08 novembre 2013 19:30:34, Jukka Rahkonen a écrit :
Even Rouault even.rouault at mines-paris.org writes:
Le vendredi 08 novembre 2013 19:19:35, Jukka Rahkonen a écrit :
Hi,
Is there a list
Le vendredi 08 novembre 2013 18:50:45, Jack Howarth a écrit :
On Fri, Nov 08, 2013 at 09:12:05AM -0800, Kurt Schwehr wrote:
Jack,
Is there an explanation someplace with more detail as to what is wrong
those png's, why older versions of libpng are okay with it and why
libpng has changed
To whom it may concern,
We have updates to the PCIDSK library that we would like to upstream to GDAL.
We have fixed numerous bugs, we have done many optimizations, and we also
implemented a new binary tile directory.
How should we proceed with the upstream?
Thanks,
Phelippe
On Fri, Nov 08, 2013 at 08:24:51PM +0100, Even Rouault wrote:
Le vendredi 08 novembre 2013 18:50:45, Jack Howarth a écrit :
On Fri, Nov 08, 2013 at 09:12:05AM -0800, Kurt Schwehr wrote:
Jack,
Is there an explanation someplace with more detail as to what is wrong
those png's, why
On Fri, Nov 08, 2013 at 03:31:05PM -0500, Jack Howarth wrote:
On Fri, Nov 08, 2013 at 08:24:51PM +0100, Even Rouault wrote:
Le vendredi 08 novembre 2013 18:50:45, Jack Howarth a écrit :
On Fri, Nov 08, 2013 at 09:12:05AM -0800, Kurt Schwehr wrote:
Jack,
Is there an explanation
On Fri, Nov 08, 2013 at 03:46:12PM -0500, Jack Howarth wrote:
On Fri, Nov 08, 2013 at 03:31:05PM -0500, Jack Howarth wrote:
On Fri, Nov 08, 2013 at 08:24:51PM +0100, Even Rouault wrote:
Le vendredi 08 novembre 2013 18:50:45, Jack Howarth a écrit :
On Fri, Nov 08, 2013 at 09:12:05AM
Phelippe,
There are a few ways we could move forward on this.
I believe the apparent master version of the PCIDSK SDK from GDAL's point
of view is:
http://svn.osgeo.org/gdal/sandbox/warmerdam/pcidsk
And I think the process I used before was to periodally migrate this into
the GDAL tree at:
Hi all, I have a csv file named test.csv with the asociated test.vrt
*test.vrt*
OGRVRTDataSource
OGRVRTLayer name=test
SrcDataSourceC:\\Users\\FedericoJurio\\Desktop\\test.csv/SrcDataSource
GeometryTypewkbPoint/GeometryType
LayerSRSWGS84/LayerSRS
GeometryField
Le vendredi 08 novembre 2013 22:41:07, Federico Jurio a écrit :
Hi all, I have a csv file named test.csv with the asociated test.vrt
*test.vrt*
OGRVRTDataSource
OGRVRTLayer name=test
SrcDataSourceC:\\Users\\FedericoJurio\\Desktop\\test.csv/SrcDataSource
Hello Frank,
We would probably go with the approach #2. We will also have to merge any
changes made in GDAL if any changes were done since our last update which was 2
years ago I think.
I'm going on vacation for the next week, so I will get back to you on the 18th
of November to arrange the
I noticed you're using ArcMap for visualizing the results. Did you check what
histogram/gamma stretch gets applied by default when you load the layer? I run
into this issue often as results from GDAL operations appear much worse when
loaded into ArcMap compared to originals. When I turn off
24 matches
Mail list logo