[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [udig-devel] Re: Current and future requirements
|
Is there a particular reason for waiting for gdal for the ECW support?
We used to have it in JGrass through the ermapper library. As far as I
know gdal will have the same problem, i.e. that you can't distribute the
library. However you can produce the code and let the user download the
jar on its own. It is tricky, but I assume gdal has the same problem (I
can't remember right now). Something changed in the licenses, but I
didn't gave it a look.
ERMapper supported in the past some code to to read (ONLY READ) in JAVA
ECW files through JNI bindings. This bindings were provided ONLY FOR WINDOWS
since they were using a subset of the original ECW SDK built as dll (no code
provided).
I have tried them and decided to not spend time on them since besids what
I have written above, they are also quite ugly (no tiling for example).
Going directly to the ERMapper SDK would be great but it would take too much
time
hence the best trade-off is to use GDAL, unless someone is willing to pay
for building complete
SWIG bindings for the ERMapper SDK :-). Note that this apporach would work
on windows, linux and also mac.
Ciao,
Simone.
