 |
||||
|
||||
[Chameleon] Raster Processing OptionJeff Hamm jeff@planyukon.caTue, 27 Jan 2004 23:16:11 -0800
|
||||
This is a multi-part message in MIME format.
------=_NextPart_000_0005_01C3E52B.8D88E7E0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
I've still not had any resolution of my problem of enabling the =
PROCESSING "BANDS=3D5,4,3" for raster images within Chameleon 1.1alpha6. =
My map file (with Landsat image) works fine under Mapserver 4, but won't =
produce any image using MapDHTML widget(just the waitimage), unless I =
comment out the PROCESSING directive, in which Chameleon produces a map, =
without any processing. Same thing occurs with other PROCESSING options, =
such as SCALE.
Some pertinent extracts from the Map file:
IMAGETYPE png24:
OUTPUTFORMAT
NAME png24
MIMETYPE "image/png"
DRIVER "GD/PNG"
IMAGEMODE RGBA
END
LAYER
DATA "o55_18ref.tif"
NAME "o55_18"
GROUP "Base"
SIZEUNITS PIXELS
STATUS ON
TOLERANCE 0
TOLERANCEUNITS PIXELS
TRANSPARENCY 50
TYPE RASTER
UNITS METERS
PROCESSING "BANDS=3D5,4,3"=20
OFFSITE 255 255 255
PROJECTION
"proj=3Daea"
"ellps=3DGRS80"
"lat_0=3D59"
"lon_0=3D-132.5"
"lat_1=3D61.667"
"lat_2=3D68"
"x_0=3D500000.0"
"y_0=3D500000.0"
"units=3Dm"
"no_defs"
END
METADATA
"wms_title" "o55_18"
"wms_group_title" "Base"
END
END
Is there a workaround? Because the Map file seems to get corrupted when =
the PROCESSING directive is included (an extra END gets inserted in the =
LAYER object according to the tmp map files), is there a parsing issue =
somewhere?
If anyone has Landsat processing working within Chameleon, what's the =
proper configuration in a Linux/Apache installation of Mapserver 4.0:
MapServer version 4.0 OUTPUT=3DPNG OUTPUT=3DWBMP SUPPORTS=3DPROJ =
SUPPORTS=3DFREETYPE SUPPORTS=3DWMS_SERVER SUPPORTS=3DWMS_CLIENT =
INPUT=3DTIFF INPUT=3DEPPL7 INPUT=3DPOSTGIS INPUT=3DOGR INPUT=3DGDAL =
INPUT=3DSHAPEFILE
I'd really prefer to put the Chameleon version into production, which =
works well enough aside from this problem (I'm being generous), but this =
is a show stopper. Any helpful comments appreciated.
Jeff Hamm
GIS and Planning Advisor
Yukon Land Use Planning Council
Whitehorse, Yukon
867 667 7397
------=_NextPart_000_0005_01C3E52B.8D88E7E0
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content=3D"text/html; charset=3Diso-8859-1" =
http-equiv=3DContent-Type>
<META content=3D"MSHTML 5.00.3103.1000" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV> </DIV>
<DIV><FONT face=3DArial size=3D2>I've still not had any resolution of my =
problem of=20
enabling the PROCESSING "BANDS=3D5,4,3" for raster images within =
Chameleon=20
1.1alpha6. My map file (with Landsat image) works fine under =
Mapserver=20
4, but won't produce any image using MapDHTML widget(just the =
waitimage), unless=20
I comment out the PROCESSING directive, in which Chameleon produces a =
map,=20
without any processing. Same thing occurs with other PROCESSING =
options,=20
such as SCALE.</FONT></DIV>
<DIV> </DIV>
<DIV><FONT face=3DArial size=3D2>Some pertinent extracts from the Map=20
file:</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>IMAGETYPE png24:</FONT></DIV>
<DIV> </DIV>
<DIV><FONT face=3DArial size=3D2> =
OUTPUTFORMAT<BR> NAME=20
png24<BR> MIMETYPE "image/png"<BR> =
DRIVER=20
"GD/PNG"<BR> IMAGEMODE RGBA<BR> END</FONT></DIV>
<DIV><FONT face=3DArial size=3D2> LAYER<BR> DATA=20
"o55_18ref.tif"<BR> NAME =
"o55_18"<BR> GROUP=20
"Base"<BR> SIZEUNITS PIXELS<BR> =
STATUS=20
ON<BR> TOLERANCE 0<BR> =
TOLERANCEUNITS=20
PIXELS<BR> TRANSPARENCY 50<BR> TYPE=20
RASTER<BR> UNITS METERS<BR> =
PROCESSING=20
"BANDS=3D5,4,3" <BR> OFFSITE 255 255 =
255<BR> =20
PROJECTION<BR> "proj=3Daea"<BR> =20
"ellps=3DGRS80"<BR> "lat_0=3D59"<BR> =
"lon_0=3D-132.5"<BR> =
"lat_1=3D61.667"<BR> =20
"lat_2=3D68"<BR> =
"x_0=3D500000.0"<BR> =20
"y_0=3D500000.0"<BR> "units=3Dm"<BR> =
"no_defs"<BR> END<BR> =20
METADATA<BR> "wms_title" =
"o55_18"<BR> =20
"wms_group_title" "Base"</FONT></DIV>
<DIV><FONT face=3DArial size=3D2> =
END<BR>END</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>Is there a workaround? Because the Map =
file seems=20
to get corrupted when the PROCESSING directive is included (an =
extra END=20
gets inserted in the LAYER object according to the tmp map files), is =
there a=20
parsing issue somewhere?</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>If anyone has Landsat processing =
working within=20
Chameleon, what's the proper configuration in a Linux/Apache =
installation of=20
Mapserver 4.0:</FONT></DIV>
<DIV> </DIV>
<DIV><FONT face=3DArial size=3D2><FONT color=3D#000000=20
face=3D"Arial, Helvetica, sans-serif" size=3D2>MapServer version 4.0 =
OUTPUT=3DPNG=20
OUTPUT=3DWBMP SUPPORTS=3DPROJ SUPPORTS=3DFREETYPE SUPPORTS=3DWMS_SERVER=20
SUPPORTS=3DWMS_CLIENT INPUT=3DTIFF INPUT=3DEPPL7 INPUT=3DPOSTGIS =
INPUT=3DOGR INPUT=3DGDAL=20
INPUT=3DSHAPEFILE</FONT></FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>I'd really prefer to put the Chameleon =
version into=20
production, which works well enough aside from this problem (I'm being=20
generous), but this is a show stopper. Any helpful comments=20
appreciated.</FONT></DIV>
<DIV> </DIV>
<DIV><FONT face=3DArial size=3D2>Jeff Hamm</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>GIS and Planning Advisor</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Yukon Land Use Planning =
Council</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Whitehorse, Yukon</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>867 667 7397</FONT></DIV>
<DIV> </DIV></BODY></HTML>
------=_NextPart_000_0005_01C3E52B.8D88E7E0--
This archive was generated by Pipermail. |
MapTools.org -- Hosted by DM Solutions Group |