I'm wondering - is there a reason that the JP2Open is distributed with
QGIS/GDAL given it seems to do a terrible job? At least it does with all
the ones I've tested against. Could the JP2ECW be distributed as the
default instead?
(again, I'm using the weekly build here).
Cheers,
Jonathan
On 18
Hi Jonathan,
On Thu, 19. Dec 2013 at 15:16:05 +, Jonathan Moules wrote:
I'm wondering - is there a reason that the JP2Open is distributed with
QGIS/GDAL given it seems to do a terrible job? At least it does with all the
ones I've tested against. Could the JP2ECW be distributed as the
Selon Jonathan Moules jonathanmou...@warwickshire.gov.uk:
I'm wondering - is there a reason that the JP2Open is distributed with
QGIS/GDAL given it seems to do a terrible job? At least it does with all
the ones I've tested against. Could the JP2ECW be distributed as the
default instead?
It
Hi,
On Thu, 19. Dec 2013 at 16:33:01 +0100, Jürgen E. Fischer wrote:
Um, maybe not overly clear. _didn't_ was meant to imply that they do now.
The last nightly builds already depended on gdal-ecw/mrsid and in turn the
next weekly will, too.
Correction: Only the 64bit build already did, but
*Even,*
Thanks for the information. I agree with the ideal of a FOSS JP2 library
but we're not in a position to contribute towards it; at best it's
ancilliary to our needs. At worst I could use any one of a number of other
formats, it just so happens that for now the data is in JP2.
Jürgen,
Ok,
Hi Jukka,
I'm only seeing the JP2OpenJPEG in there (this is for the weeklies, I've
uninstalled my 2.0 so can't check that).
So I guess given the behaviour/speed difference that 2.0 comes with the
JP2ECW driver? Would it be much effort to add to the weeklies? Or is there
a way to for me to
Hi,
Speed difference comes probably from the GDAL driver. I have no idea about what
it means to add JP2ECW driver to GDAL and QGIS. I can see that there is a dll
file gdal_ECW_JP2ECW.dll in a directory C:\Program Files\QGIS
Dufour\bin\gdalplugins but I do not know if the plugin and GDAL must
Hi Jonathan,
On Wed, 18. Dec 2013 at 12:20:31 +, Jonathan Moules wrote:
I'm only seeing the JP2OpenJPEG in there (this is for the weeklies, I've
uninstalled my 2.0 so can't check that).
The qgis-dev package didn't depend on gdal-ecw and gdal-mrsid - in turn the
weeklies didn't pull those
Am 17.12.2013 20:47, schrieb Jukka Rahkonen:
If there are several drivers for JPEG2000 GDAL is using the first on the
list. You can skip a driver by setting GDAL_SKIP environment. Thus, if I
would like to have a try with JP2OpenJPEG I should run SET GDAL_SKIP=JP2ECW
first. No idea really how
Anyone?
On 11 December 2013 17:04, Jonathan Moules
jonathanmou...@warwickshire.gov.uk wrote:
Hi List,
A question about the weekly builds (www.qgis.org/downloads/weekly). They
seem to struggle with loading JP2 files using the usual raster dialog.
First they're incredibly slow, but on top of
Jonathan Moules jonathanmoules@... writes:
Anyone?
On 11 December 2013 17:04, Jonathan Moules
jonathanmou...@warwickshire.gov.uk wrote:
Hi List,
A question about the weekly builds (www.qgis.org/downloads/weekly). They
seem to struggle with loading JP2 files using the usual raster
Hi List,
A question about the weekly builds (www.qgis.org/downloads/weekly). They
seem to struggle with loading JP2 files using the usual raster dialog.
First they're incredibly slow, but on top of that when they do load they
tend to be some sort of horrible mess of lots of black of random colours
12 matches
Mail list logo
