[mapserver-users] moving from version 3.3 to 3.5
Larry Nolan
lrn@zeppo.geosurv.gov.nf.ca
Mon, 11 Feb 2002 15:06:22 -0330
This is a multi-part message in MIME format.
------=_NextPart_000_00C2_01C1B30D.AABB4170
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
First, I am impressed with the WMS Client and Server capabilities, great =
Job.
I have been attempting to move from mapserver version 3.3 to 3.5 and I =
am having some trouble with my map files.
Some layers do not appear in v3.5 which work fine in 3.3
I have changed all the things I can find in the documentation but I must =
be missing something.
FONTS:
I have fixed=20
Filled =3D=3D> Filled True
Antialias =3D=3D> Antialias True
SYMBOLS:
- downloaded the 3.4 combined symbolset and removed the =
Shadeset/Markerset/Lineset definitions
The 3.4 symbolset referenced in Mapserver FAQ at=20
http://www2.dmsolutions.ca/mapserver/dl/symbols-for-ms34.sym caused =
more problems
because the Filled parameter does not have the True qualifier. Fixed =
that.
- In the symbol file the SYMBOL name need to be in quotes
i.e. SYMBOL circle =3D=3D> SYMBOL 'circle'
QUERIES:
I moved my TEMPLATE 'URL query objects to the CLASS objects
- All my queries seem to work fine.
There is a new parameter in the LAYER object for gouping layers, which I =
had done in the past by reusing the layer name.=20
I gave all unique names and used the GROUP parameter. This does not =
seem to make any difference because I have map files=20
which use the multiple layers with the same name and map files which =
use unique layer names and the GROUP parameter and both work.
How important is it that I follow the new GROUP parameter and use =
unique LAYER names?
Projections:
I am not setting any projection information yet so this should not =
affect my files.
Are there other changes which I have missed?
Is there a comprehensive list of the changes from version 3.3 to 3.4 to =
3.5?
ARCSDE Question:
Does anyone have a win32 build of mapserver 3.5 for windows 2000 with:
input support for shapefiles, TIFF/GeoTIFF, and JPEG and GIF output.=20
input support for GDAL (and OGR) as well as WMS client (and server) =
compliance.=20
and ARCSDE 8.1
this would be equivalent to the full meal deal.
thanks
Larry Nolan
Project Geologist - GIS
Geological Survey of Newfoundland
lrn@zeppo.geosurv.gov.nf.ca
709-729-2168
------=_NextPart_000_00C2_01C1B30D.AABB4170
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 http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.2600.0" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>
<DIV><FONT face=3DArial size=3D2>First, I am impressed with the WMS =
Client and=20
Server capabilities, great Job.</FONT></DIV>
<DIV> </DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>I have been attempting to move from =
mapserver=20
version 3.3 to 3.5 and I am having some trouble with my map =
files.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Some layers do not appear in v3.5 which =
work fine=20
in 3.3</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>I have changed all the things I can =
find in the=20
documentation but I must be missing something.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>FONTS:</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>I have fixed </FONT></DIV>
<DIV><FONT face=3DArial size=3D2> Filled =
=3D=3D> =20
Filled True</FONT></DIV>
<DIV><FONT face=3DArial size=3D2> Antialias =3D=3D> Antialias =
True</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>SYMBOLS:</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>- downloaded the 3.4 =
combined symbolset=20
and removed the Shadeset/Markerset/Lineset definitions</FONT></DIV>
<DIV><FONT face=3DArial size=3D2> The 3.4 symbolset =
referenced in=20
Mapserver FAQ at </FONT></DIV>
<DIV><FONT face=3DArial size=3D2> <A=20
href=3D"http://www2.dmsolutions.ca/mapserver/dl/symbols-for-ms34.sym"=20
target=3D_top><FONT face=3D"Times New Roman"=20
size=3D3>http://www2.dmsolutions.ca/mapserver/dl/symbols-for-ms34.sym</FO=
NT></A> =20
caused more problems</FONT></DIV>
<DIV><FONT face=3DArial size=3D2> because the Filled=20
parameter</FONT><FONT face=3DArial size=3D2> does not have the True =
qualifier. Fixed=20
that.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>- In the symbol file the SYMBOL name =
need to be in=20
quotes</FONT></DIV>
<DIV><FONT face=3DArial size=3D2> i.e. SYMBOL circle =
=3D=3D> SYMBOL=20
'circle'</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>QUERIES:</FONT></DIV>
<DIV><FONT face=3DArial size=3D2> I moved my TEMPLATE =
'URL =20
query objects to the CLASS objects</FONT></DIV>
<DIV><FONT face=3DArial size=3D2> - All my queries seem to work=20
fine.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>There is a new parameter in the LAYER =
object for=20
gouping layers, which I had done in the past by reusing the layer name.=20
</FONT></DIV>
<DIV><FONT face=3DArial size=3D2> I gave all unique names and used =
the GROUP=20
parameter. This does not seem to make any difference because I have map =
files=20
</FONT></DIV>
<DIV><FONT face=3DArial size=3D2> which use the multiple =
layers with the=20
same name and map files which use unique layer names and the GROUP =
parameter and=20
both work.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2> How important is it that I follow =
the new=20
GROUP parameter and use unique LAYER names?</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>Projections:</FONT></DIV>
<DIV><FONT face=3DArial size=3D2> I am not setting any projection =
information=20
yet so this should not affect my files.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2> Are there other changes which I =
have=20
missed?</FONT></DIV>
<DIV><FONT face=3DArial size=3D2> Is there a comprehensive list of =
the changes=20
from version 3.3 to 3.4 to 3.5?</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV> </DIV>
<DIV>ARCSDE Question:</DIV>
<DIV>
<DIV><FONT face=3DArial size=3D2>Does anyone have a win32 build of =
mapserver 3.5 for=20
windows 2000 with:</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>input support for shapefiles, =
TIFF/GeoTIFF, and=20
JPEG and GIF output. </FONT></DIV>
<DIV><FONT face=3DArial size=3D2>input support for GDAL (and OGR) as =
well as WMS=20
client (and server) compliance. </FONT></DIV>
<DIV><FONT face=3DArial size=3D2>and ARCSDE 8.1</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>this would be equivalent to the full =
meal=20
deal.</FONT></DIV></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>thanks</FONT></DIV>
<DIV> </DIV>
<DIV><FONT face=3DArial size=3D2>Larry Nolan<BR>Project Geologist -=20
GIS<BR>Geological Survey of Newfoundland<BR><A=20
href=3D"mailto:lrn@zeppo.geosurv.gov.nf.ca">lrn@zeppo.geosurv.gov.nf.ca</=
A><BR>709-729-2168</FONT></DIV></FONT></DIV></BODY></HTML>
------=_NextPart_000_00C2_01C1B30D.AABB4170--