-
Notifications
You must be signed in to change notification settings - Fork 14
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ECW support on OpenJUMP #65
Comments
is it possible that GvSIG is indeed just using the aformentioned 32bit ECW native drivers? wrt. GDAL there is little we can do. you could try if cmd line GDAL works better, to pinpoint an issue in the ImageIO-Ext implementation. you can try the latest OSGEO-Live 15 where i took strife to have gdal-jni included. maybe it just does not work well on windows? but in the end, i don't see us fixing up those or compile 64bit binaries from the outdated Ermapper SDK 3.3 files, in case we are able to find the sources ;) |
It is not possible to compile 64bit binaries from 3.3. SDK https://supportsi.hexagon.com/help/s/question/0D52o0000CMbSJDCQ3/ecw-jp2-sdk-3x-still-available?language=en_US |
is Hexagon the current ECW patent holder? they just write |
I used GvSIG with java 64 bit, possibly the embedded GDAL is also 64 bit. I choose GvSIG as it was in Java like OpenJUMP. But it seems that GvSIG doesn't use imageio-ext libraries. |
|
Hi Ede,
Large ECW: Small ECW: |
I use Windows 10 with JRE 64-bit 1.8.0 |
will have a look when time permits. any idea where i can find the sources for the latest gvSIG desktop release ? |
Not found. |
2.0.xxx too would you mind contacting them and ask for the sources?
|
I wrote them, |
Hi Ede, this is the answer from GvSIG teamç Good morning Giuseppe, Regarding your question about where the gvSIG Desktop sources are, you can find all the information in this post: The only thing is that it has been around for some time, and the only sentence that has become obsolete is the one that talks about “Create your own gvSIG (New plugin!!)”, which is a plugin that no longer exists. For the rest, that post is still the answer to the question of where are the sources. Anyway, after knowing where they are, the next thing you usually need to know is the following links: How to download and compile gvSIG 2.1.0 on Linux and Windows How to download and compile a gvSIG 2.1.0 plugin Compiling and debugging an example plugin for gvSIG 2.1.0 from an IDE (NetBeans). although it indicates 2.1.0 it applies to the 2.x branch. Regarding where to find the sources of each plugin... you would have to look at For example if you search for GDAL there, you will find And our advice is that you enter the project and look in the "repository" tab (having the browser configured in English, it will be something similar in Spanish) and look at the date to try to find out which projects have been developed more. Then you go to the "Overview" tab to see where the SVN is. We hope this information has been useful to you. All the best |
Not sure it is related but in my installation process, nowadays, I have the following message : |
jecw JNI are the above mentioned "Ermapper SDK 3.3" native libs avail for 32bit only mentioned above. |
Recently I needed to use some ECW files of large size (6-8 Gb) on OpenJUMP in Windows with JRE 64bit.
OpenJUMP has embedded native ECW drivers (coming from ECW, I think) that work fine with this files, unfortunately these drivers work only with Java 32bit.
I tried to use OpenJUMP and GDAL , following the note at: https://ojwiki.soldin.de/index.php?title=Working_with_Raster#GDAL_support_.28Windows.2C_Linux_only.29
I used the most recent GDAL 3.5.0 (https://sourceforge.net/projects/jump-pilot/files/OpenJUMP_plugins/Drivers/GDAL-win-x86x64-3.5.0stable-20220620.zip/download).
I realized that (with both java 64bit and 32 bit) small/medium size ECW are opened with no problem but not with this large ECW files.
Could it be a problem of GDAL version? Other java software, like GvSIG, seems not to have this limitation on loading ECW via GDAL.
I gave a look to the bug reports and find also this note which could be useful for the discussion
https://sourceforge.net/p/jump-pilot/bugs/444/
Best regards
Peppe
The text was updated successfully, but these errors were encountered: