Opened 16 years ago
Closed 16 years ago
#1923 closed defect (worksforme)
Error loading MrSID in mapserver
Reported by: | benft | Owned by: | warmerdam |
---|---|---|---|
Priority: | normal | Milestone: | |
Component: | GDAL_Raster | Version: | 1.3.2 |
Severity: | normal | Keywords: | mrsid mapserver |
Cc: |
Description
Hello, Our mapserver project has a raster layer composed of tile-indexed MrSID images. When zoomed in to scales greater than ~20000 they load OK. At smaller scales, we get this error in the apache error.log:
Premature end of script headers: php-cgi.exe
Sometimes, instead, we get these PHP errors:
PHP Warning: Error: msDrawMap(): Failed to draw layer named 'VGIN Aerials'. in ...chameleon\htdocs\common\wrapper\drawmap.php on line 534 PHP Warning: Error: MrSIDRasterBand::IRasterIO(): Failed to load image. mg2 somethi: GDALRasterIO() failed: drawGDAL() in ...chameleon\htdocs\common\wrapper\drawmap.php on line 534
I see a 2-year old unresolved ticket here for what looks like the same problem:
ticket 914 "MrSID fails in MapServer" see: http://trac.osgeo.org/gdal/ticket/914
We're using gdal 1.3.2 with the Lizardtech MrSid code compiled in.
Has it been fixed?
Thanks, Ben Thompson
Change History (2)
comment:1 by , 16 years ago
Priority: | high → normal |
---|---|
Severity: | blocker → normal |
comment:2 by , 16 years ago
Resolution: | → worksforme |
---|---|
Status: | new → closed |
Ben,
Lacking feedback, I'm closing this. Feel free to reopen it if you have more information, or if you can provide a concrete test case that demonstrates the issue with a modern GDAL.
Ben,
I'm not aware of any fixes having been incorporated as a result of #914. However, there have been quite a few changes to the mrsid driver since 1.3.2 as listed at:
http://trac.osgeo.org/gdal/log/trunk/gdal/frmts/mrsid?action=stop_on_copy&rev=12396&stop_rev=&mode=follow_copy
I think r10655 (related to bug #1446) looks like the most likely significant fix in this period and has also been incorporated in the 1.4 branch as r10654.
I would suggest you upgrade to at least GDAL 1.4.2 and see if the problem persists. If so, you will need to isolate the bug in some fashion I can reproduce for me to followup.