Your version of gdal needs to be built against the ECW SDK from
ermapper. Someone else who supports the binary packages will have to
tell you how to get a version with the correct build, but if you are
building yourself you can just:
1) Download and install the SDK from ermapper
(http://www.ermapper.com/downloads/sdks.aspx#16)
2) Build gdal with the correct config option (--with-ecw)
Hope that helps...
Aaron
+----------------------------------------+
| Aaron Racicot | aaronr@ecotrust.org |
| GIS Programmer | 503.467.0759 |
+----------------------------------------+
| e c o t r u s t |
| Jean Vollum Natural Capital Center |
| 721 NW Ninth Avenue |
| Suite 200 |
| Portland, OR 97209 |
| www.ecotrust.org |
+----------------------------------------+
-----Original Message-----
From: grassuser-bounces@grass.itc.it
[mailto:grassuser-bounces@grass.itc.it] On Behalf Of Kirk R. Wythers
Sent: Monday, July 31, 2006 2:33 PM
To: grassuser@grass.itc.it
Subject: [GRASS-user] r.in.gdal and .ecw files
Does anyone know if r.in.gdal reads .ecw files? According to the docs it
does (http://www.gdal.org/formats_list.html). However, I am getting a
"not recognised as a supported file format" error. If I use the -f (list
supported files option) with r.in.gdal, ecw is not listed.
Thanks,
Kirk
Kirk R. Wythers, Research Fellow
Dept. of Forest Resources
University of Minnesota
1530 Cleveland Ave N
Saint Paul, MN 55108
tel: 612.625.2261
email: kwythers@umn.edu
On Jul 31, 2006, at 4:43 PM, Aaron Racicot wrote:
Your version of gdal needs to be built against the ECW SDK from
ermapper. Someone else who supports the binary packages will have to
tell you how to get a version with the correct build, but if you are
building yourself you can just:
1) Download and install the SDK from ermapper
(http://www.ermapper.com/downloads/sdks.aspx#16)
2) Build gdal with the correct config option (--with-ecw)
Hope that helps...
Thanks Aaron. I just re-ran my gdal config script and see saw that you are correct:
ECW support: no
I also see that the free version will only read files up to 500 megs... what a bother.
Aaron
+----------------------------------------+
| Aaron Racicot | aaronr@ecotrust.org |
| GIS Programmer | 503.467.0759 |
+----------------------------------------+
| e c o t r u s t |
| Jean Vollum Natural Capital Center |
| 721 NW Ninth Avenue |
| Suite 200 |
| Portland, OR 97209 |
| www.ecotrust.org |
+----------------------------------------+
-----Original Message-----
From: grassuser-bounces@grass.itc.it
[mailto:grassuser-bounces@grass.itc.it] On Behalf Of Kirk R. Wythers
Sent: Monday, July 31, 2006 2:33 PM
To: grassuser@grass.itc.it
Subject: [GRASS-user] r.in.gdal and .ecw files
Does anyone know if r.in.gdal reads .ecw files? According to the docs it
does (http://www.gdal.org/formats_list.html). However, I am getting a
"not recognised as a supported file format" error. If I use the -f (list
supported files option) with r.in.gdal, ecw is not listed.
Thanks,
Kirk
Kirk R. Wythers, Research Fellow
Dept. of Forest Resources
University of Minnesota
1530 Cleveland Ave N
Saint Paul, MN 55108
tel: 612.625.2261
email: kwythers@umn.edu
Unfortunately I have yet to get the ECW SDK to work on OS X. You need the current 3.3 version for Tiger/GCC 4 support, I think. Supposedly reading will work, but I can't even get that to work. Writing has threading issues. I patiently wait...
But, the free version should be able to read any size images. Maybe the older versions were limited to 500MB. The licensing was changed recently for a more open source-friendly free version.
On Jul 31, 2006, at 4:47 PM, Kirk R. Wythers wrote:
On Jul 31, 2006, at 4:43 PM, Aaron Racicot wrote:
Your version of gdal needs to be built against the ECW SDK from
ermapper. Someone else who supports the binary packages will have to
tell you how to get a version with the correct build, but if you are
building yourself you can just:
1) Download and install the SDK from ermapper
(http://www.ermapper.com/downloads/sdks.aspx#16)
2) Build gdal with the correct config option (--with-ecw)
Hope that helps...
Thanks Aaron. I just re-ran my gdal config script and see saw that you are correct:
ECW support: no
I also see that the free version will only read files up to 500 megs... what a bother.
-----
William Kyngesburye <kyngchaos@kyngchaos.com>
http://www.kyngchaos.com/
"I ache, therefore I am. Or in my case - I am, therefore I ache."
- Marvin
Hi William,
Do you get your gdal crash with ecw 3.3 rc2, or ecw 3.1 rc2? I ask because I see in the 3.3 release notes:
Version Features
Numerous bug fixes, including:
- functional ECWP on platforms other than Windows
- a fix to lossless JPEG 2000 compression
- change to headers to allow overloading new and delete on Windows
- correct calculation of compression throughput
- large file support issues fixed
- fix to UNICODE support making it orthogonal to the use of UNICODE #define in client code
- fixes to the platform-dependent code for MacOS X
Release Date: Tuesday, February 07, 2006
On Jul 31, 2006, at 5:35 PM, William Kyngesburye wrote:
Unfortunately I have yet to get the ECW SDK to work on OS X. You need the current 3.3 version for Tiger/GCC 4 support, I think. Supposedly reading will work, but I can’t even get that to work. Writing has threading issues. I patiently wait…
But, the free version should be able to read any size images. Maybe the older versions were limited to 500MB. The licensing was changed recently for a more open source-friendly free version.
On Jul 31, 2006, at 4:47 PM, Kirk R. Wythers wrote:
On Jul 31, 2006, at 4:43 PM, Aaron Racicot wrote:
Your version of gdal needs to be built against the ECW SDK from
ermapper. Someone else who supports the binary packages will have to
tell you how to get a version with the correct build, but if you are
building yourself you can just:
- Download and install the SDK from ermapper
(http://www.ermapper.com/downloads/sdks.aspx#16)
- Build gdal with the correct config option (–with-ecw)
Hope that helps…
Thanks Aaron. I just re-ran my gdal config script and see saw that you are correct:
ECW support: no
I also see that the free version will only read files up to 500 megs… what a bother.
William Kyngesburye <kyngchaos@kyngchaos.com>
http://www.kyngchaos.com/
“I ache, therefore I am. Or in my case - I am, therefore I ache.”
3.3rc2. It puzzles me - because of those Mac OS X fixes mentioned, and I've heard others have been successful (as far as being able to read ECW). And it's not just GDAL, the example progs in ECW also crash.
If you want to try it, I'd like to hear how it goes. I've tried it a few times since the 3.3rc2 release, I think thru a couple Tiger updates (currently 10.4.7), and an Xcode update or two, and from PPC and Intel Macs. Maybe something I'm doing different than expected. I should try again, I really want ECW support, but have been distracted by installer stuff and recently the frameworks. I even went as far as trying to get it to work on Fedora 5 on my MacBook, but I had compile errors, and Linux is too much hassle to use on the MacBook with Parallels (no easy file sharing like with Windows).
On Aug 1, 2006, at 9:10 AM, Kirk R. Wythers wrote:
Hi William,
Do you get your gdal crash with ecw 3.3 rc2, or ecw 3.1 rc2? I ask because I see in the 3.3 release notes:
Version Features
Numerous bug fixes, including:
functional ECWP on platforms other than Windows
a fix to lossless JPEG 2000 compression
change to headers to allow overloading new and delete on Windows
correct calculation of compression throughput
large file support issues fixed
fix to UNICODE support making it orthogonal to the use of UNICODE #define in client code
fixes to the platform-dependent code for MacOS X
-----
William Kyngesburye <kyngchaos@kyngchaos.com>
http://www.kyngchaos.com/
"Those people who most want to rule people are, ipso-facto, those least suited to do it."
- A rule of the universe, from the HitchHiker's Guide to the Galaxy
Hi,
I also would like to have ecw support for gdal, but I'm running on cygwin/winXP. But compiling ecw 3.3rc2 crashes :-((
Wolfgang
William Kyngesburye schrieb:
3.3rc2. It puzzles me - because of those Mac OS X fixes mentioned, and I've heard others have been successful (as far as being able to read ECW). And it's not just GDAL, the example progs in ECW also crash.
If you want to try it, I'd like to hear how it goes. I've tried it a few times since the 3.3rc2 release, I think thru a couple Tiger updates (currently 10.4.7), and an Xcode update or two, and from PPC and Intel Macs. Maybe something I'm doing different than expected. I should try again, I really want ECW support, but have been distracted by installer stuff and recently the frameworks. I even went as far as trying to get it to work on Fedora 5 on my MacBook, but I had compile errors, and Linux is too much hassle to use on the MacBook with Parallels (no easy file sharing like with Windows).
On Aug 1, 2006, at 9:10 AM, Kirk R. Wythers wrote:
Hi William,
Do you get your gdal crash with ecw 3.3 rc2, or ecw 3.1 rc2? I ask because I see in the 3.3 release notes:
Version Features
Numerous bug fixes, including:
functional ECWP on platforms other than Windows
a fix to lossless JPEG 2000 compression
change to headers to allow overloading new and delete on Windows
correct calculation of compression throughput
large file support issues fixed
fix to UNICODE support making it orthogonal to the use of UNICODE #define in client code
fixes to the platform-dependent code for MacOS X
-----
William Kyngesburye <kyngchaos@kyngchaos.com>
http://www.kyngchaos.com/
"Those people who most want to rule people are, ipso-facto, those least suited to do it."
- A rule of the universe, from the HitchHiker's Guide to the Galaxy
_______________________________________________
grassuser mailing list
grassuser@grass.itc.it
http://grass.itc.it/mailman/listinfo/grassuser