William Kyngesburye wrote:
On Nov 30, 2008, at 1:21 PM, Even Rouault wrote:
ECW tests 14 and 15 check for the wrong driver - they are jp2ecw tests
but check for ecw. (I disabled JP2 in my ECW library build for some
reason I can't remember.)
Hum, you're right. Fixed in trunk in r15864
Hm, do
On Dec 1, 2008, at 6:05 PM, Frank Warmerdam wrote:
I have also re-snapped the autotest suite, and produced a docs
package:
http://download.osgeo.org/gdal/gdal160doc.zip
http://download.osgeo.org/gdal/gdalautotest-1.6.0.zip
Cool, tiff_write_55 now works, osr_esri_10 now works.
-
Willi
On Nov 30, 2008, at 1:21 PM, Even Rouault wrote:
ECW tests 14 and 15 check for the wrong driver - they are jp2ecw
tests
but check for ecw. (I disabled JP2 in my ECW library build for some
reason I can't remember.)
Hum, you're right. Fixed in trunk in r15864
Hm, doesn't look like it made it
On Dec 1, 2008, at 9:00 PM, William Kyngesburye wrote:
On Nov 30, 2008, at 1:21 PM, Even Rouault wrote:
The gdalhttp test is trying to use the DODS driver.
Yes, this is known : see http://trac.osgeo.org/gdal/ticket/2696
There's little we can do to solve that, except maybe change the
syntax
On Dec 1, 2008, at 12:20 PM, Even Rouault wrote:
Yes, ILI/IOM has been fixed, but the GML driver has also been
changed so that
it behaves correctly with Xerces 3.0. I can confirm that GDAL
1.6.0RC2 passes
the GML autotest when compiled and run against xerces-3.0.0 (x86
Linux).
Are you sure
On Nov 30, 2008, at 1:21 PM, Even Rouault wrote:
The gdalhttp test is trying to use the DODS driver.
Yes, this is known : see http://trac.osgeo.org/gdal/ticket/2696
There's little we can do to solve that, except maybe change the
syntax of the
connection string for the GDAL DODS driver, to so
On Dec 1, 2008, at 3:27 PM, Frank Warmerdam wrote:
I am not in favor of apply the change for 2661 in the 1.6 branch.
I'm not
opposed to it going into trunk now that 1.6 is settling.
Rats. So, 1.6.1?
At least I can apply it to my own binary release, to keep 1.5 and
1.6 plugins separate.
Sorry to keep digging up stuff - this one keeps bugging me (I'm
patching it out of habit now):
http://trac.osgeo.org/gdal/ticket/1242
-
William Kyngesburye
http://www.kyngchaos.com/
"Those people who most want to rule people are, ipso-facto, those
least suited to do it."
- A rule of
Folks,
There have been a few noteworthy errors identified and corrected since
RC2 was issued. So I've decided to retract it and prepare an RC3. RC3
is available at:
http://download.osgeo.org/gdal/gdal160RC3.zip - source as a zip
http://download.osgeo.org/gdal/gdal-1.6.0RC3.tar.gz - source as
Folks,
There have been a few noteworthy errors identified and corrected since
RC2 was issued. So I've decided to retract it and prepare an RC3. RC3
is available at:
http://download.osgeo.org/gdal/gdal160RC3.zip - source as a zip
http://download.osgeo.org/gdal/gdal-1.6.0RC3.tar.gz - source as
Hi All,
I'm new in this mail-list.
I have a problem when trying to use gdal.
I use VC++ 6. After creating a project, I add some header files, C/C++ source
files and inc files to my project, not all files included in gdal zip file.
They are :
[..] [.]geo_normalize.c
Hi all,
Quick question, Is MrSid SDK (7.0.0.2167) supported by GDAL?
As indicated by the release notes 4. there are fixes to the JP2 readers
and I'm wondering if that might resolve my JP2 issue since I'm currently
on: MrSid SDK 6.0.7.1407
Thanks,
-Steve
Release Notes for SDK (7.0.0.2167)
William Kyngesburye wrote:
On Nov 30, 2008, at 1:17 PM, Frank Warmerdam wrote:
William Kyngesburye wrote:
Ahh, I was just running thru the autotests with RC1.
Any chance of getting http://trac.osgeo.org/gdal/ticket/2661 into
1.6? Tested on RC1, no problems.
William,
I am not in favor of a
Stephen Woodbridge wrote:
I just checked RC2 this against the jp2 problem we have been struggling
with. I believe the patch you made or this is in RC1 and RC2. See below.
...
MrSID: RasterIO() - using optimized dataset level IO.
MrSID: Dataset:IRasterIO(25432,42149 5066x6973 -> 5066x6973 ->
50
Frank Warmerdam wrote:
Folks,
There have been a few noteworthy errors identified and corrected since
RC1 was issued. So I've decided to retract it and prepare an RC2. RC2
is available at:
http://download.osgeo.org/gdal/gdal160RC2.zip - source as a zip
http://download.osgeo.org/gdal/gdal-1.6
On Dec 1, 2008, at 12:20 PM, Even Rouault wrote:
I think all that addressed was setting some macro so that ILI/IOM
would compile.
Yes, ILI/IOM has been fixed, but the GML driver has also been
changed so that
it behaves correctly with Xerces 3.0. I can confirm that GDAL
1.6.0RC2 passes
the
Frank Warmerdam pisze:
Folks,
There have been a few noteworthy errors identified and corrected
since RC1 was issued. So I've decided to retract it and prepare an
RC2. RC2 is available at:
http://download.osgeo.org/gdal/gdal160RC2.zip - source as a zip
http://download.osgeo.org/gdal/gdal-1.6.
Maciej Sieczka wrote:
Frank Warmerdam pisze:
Folks,
There have been a few noteworthy errors identified and corrected
since RC1 was issued. So I've decided to retract it and prepare an
RC2. RC2 is available at:
http://download.osgeo.org/gdal/gdal160RC2.zip - source as a zip
http://download.o
Le Monday 01 December 2008 18:43:52 William Kyngesburye, vous avez écrit :
> On Dec 1, 2008, at 11:30 AM, Frank Warmerdam wrote:
> > William Kyngesburye wrote:
> >> I'm working on some autotest errors for 1.6, and I need some help
> >> to figure out how to fix them.
> >> - ogr_gml
> >> TEST: ogr_g
On Dec 1, 2008, at 11:30 AM, Frank Warmerdam wrote:
William Kyngesburye wrote:
I'm working on some autotest errors for 1.6, and I need some help
to figure out how to fix them.
- ogr_gml
TEST: ogr_gml_1 ... ERROR 1: element missing value.
fail (blowup)
Traceback (most recent call last):
Fil
William Kyngesburye wrote:
I'm working on some autotest errors for 1.6, and I need some help to
figure out how to fix them.
- ogr_gml
TEST: ogr_gml_1 ... ERROR 1: element missing value.
fail (blowup)
Traceback (most recent call last):
File "pymod/gdaltest.py", line 89, in run_tests
re
William Kyngesburye wrote:
On Nov 30, 2008, at 4:03 PM, William Kyngesburye wrote:
- tiff_write
TEST: tiff_write_55 ... PROJCS["Equirectangular
Mars",GEOGCS["GCS_Mars",DATUM["unknown",SPHEROID["unnamed",3394813.857975945,0]],PRIMEM["Greenwich",0],UNIT["degree",0.0174532925199433]],PROJECTION
Benjamin R Welton wrote:
Thanks for your quick response.
The geotiff files that i am trying to convert are single band. I am not
looking to create a false three color tiff from these images i only need to
have a gray scale representation of the images.
Iv had a little bit of time to look over t
Thanks for your quick response.
The geotiff files that i am trying to convert are single band. I am not looking
to create a false three color tiff from these images i only need to have a gray
scale representation of the images.
Iv had a little bit of time to look over the documentation on the V
Managed to get it working with the following
raster = numpy.zeros( (n_rows, n_cols), dtype = numpy.uint8)
On Mon, Dec 1, 2008 at 12:49 PM, Andre <[EMAIL PROTECTED]> wrote:
> Good day,
>
> I implemented Python the tutorial
> (http://www.gdal.org/gdal_tutorial.html) that explains how to create a
>
25 matches
Mail list logo