[Mapserver-users] Large Map Files
Ryan, Adam
ARyan at co.linn.or.us
Tue Feb 11 11:13:15 PST 2003
This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.
------_=_NextPart_001_01C2D201.A0B74200
Content-Type: text/plain;
charset="iso-8859-1"
EXCELLENT IDEA!
Adam Ryan
-----Original Message-----
From: Paul Ramsey [mailto:pramsey at refractions.net]
Sent: Tuesday, February 11, 2003 11:03 AM
To: Jan Hartmann
Cc: mapserver-users at lists.gis.umn.edu
Subject: Re: [Mapserver-users] Large Map Files
I have been thinking that an extremely powerful extension to the .map
file would be an "INCLUDE" directive, which reads a map file fragment
into another map file. A quick-and-dirty map service could then be
assembled with:
MAP
INCLUDE standard-headers.map
INCLUDE standard-basemap-layers.map
LAYER
NAME myspeciallayer
DATA blah
TYPE polygon
END
END
The FME does this in its mapping files, for example. The first stage of
processing is to replace all INCLUDE lines with their referenced
content. It recursively does this up to a max number of loops.
For people maintaining alot of different map services, it could be a
real boon. (Your parcel postgis database is now on a new server? Change
the *one* parcel layer definition, and all the maps which reference it
are now up-to-date.)
P.
Jan Hartmann wrote:
> Just my personal view, but isn't this problem of too many classes (or
> layers) perhaps caused by using a MapFile in two different ways: as a
> generator of a single layered map, and as a repository of all available
> map layers? I can hardly imagine a single map with more than fifty
> classes or one hundred layers. What people seem to do is putting every
> GIS file they have in a single MapFile and turning layers on and off as
> needed. As every layer needs its own classes, the maximum number of 50
> is very soon reached, even if only a small part of these will be ever
> used in any actual map.
--
__
/
| Paul Ramsey
| Refractions Research
| Email: pramsey at refractions.net
| Phone: (250) 885-0632
\_
_______________________________________________
Mapserver-users mailing list
Mapserver-users at lists.gis.umn.edu
http://lists.gis.umn.edu/mailman/listinfo/mapserver-users
------_=_NextPart_001_01C2D201.A0B74200
Content-Type: text/html;
charset="iso-8859-1"
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<META NAME="Generator" CONTENT="MS Exchange Server version 5.5.2653.12">
<TITLE>RE: [Mapserver-users] Large Map Files</TITLE>
</HEAD>
<BODY>
<P><FONT SIZE=2>EXCELLENT IDEA!</FONT>
</P>
<P><FONT SIZE=2>Adam Ryan</FONT>
</P>
<P><FONT SIZE=2>-----Original Message-----</FONT>
<BR><FONT SIZE=2>From: Paul Ramsey [<A HREF="mailto:pramsey at refractions.net">mailto:pramsey at refractions.net</A>]</FONT>
<BR><FONT SIZE=2>Sent: Tuesday, February 11, 2003 11:03 AM</FONT>
<BR><FONT SIZE=2>To: Jan Hartmann</FONT>
<BR><FONT SIZE=2>Cc: mapserver-users at lists.gis.umn.edu</FONT>
<BR><FONT SIZE=2>Subject: Re: [Mapserver-users] Large Map Files</FONT>
</P>
<BR>
<P><FONT SIZE=2>I have been thinking that an extremely powerful extension to the .map </FONT>
<BR><FONT SIZE=2>file would be an "INCLUDE" directive, which reads a map file fragment </FONT>
<BR><FONT SIZE=2>into another map file. A quick-and-dirty map service could then be </FONT>
<BR><FONT SIZE=2>assembled with:</FONT>
</P>
<P><FONT SIZE=2>MAP</FONT>
<BR><FONT SIZE=2> INCLUDE standard-headers.map</FONT>
<BR><FONT SIZE=2> INCLUDE standard-basemap-layers.map</FONT>
<BR><FONT SIZE=2> LAYER</FONT>
<BR><FONT SIZE=2> NAME myspeciallayer</FONT>
<BR><FONT SIZE=2> DATA blah</FONT>
<BR><FONT SIZE=2> TYPE polygon</FONT>
<BR><FONT SIZE=2> END</FONT>
<BR><FONT SIZE=2>END</FONT>
</P>
<P><FONT SIZE=2>The FME does this in its mapping files, for example. The first stage of </FONT>
<BR><FONT SIZE=2>processing is to replace all INCLUDE lines with their referenced </FONT>
<BR><FONT SIZE=2>content. It recursively does this up to a max number of loops.</FONT>
</P>
<P><FONT SIZE=2>For people maintaining alot of different map services, it could be a </FONT>
<BR><FONT SIZE=2>real boon. (Your parcel postgis database is now on a new server? Change </FONT>
<BR><FONT SIZE=2>the *one* parcel layer definition, and all the maps which reference it </FONT>
<BR><FONT SIZE=2>are now up-to-date.)</FONT>
</P>
<P><FONT SIZE=2>P.</FONT>
</P>
<P><FONT SIZE=2>Jan Hartmann wrote:</FONT>
<BR><FONT SIZE=2>> Just my personal view, but isn't this problem of too many classes (or </FONT>
<BR><FONT SIZE=2>> layers) perhaps caused by using a MapFile in two different ways: as a </FONT>
<BR><FONT SIZE=2>> generator of a single layered map, and as a repository of all available </FONT>
<BR><FONT SIZE=2>> map layers? I can hardly imagine a single map with more than fifty </FONT>
<BR><FONT SIZE=2>> classes or one hundred layers. What people seem to do is putting every </FONT>
<BR><FONT SIZE=2>> GIS file they have in a single MapFile and turning layers on and off as </FONT>
<BR><FONT SIZE=2>> needed. As every layer needs its own classes, the maximum number of 50 </FONT>
<BR><FONT SIZE=2>> is very soon reached, even if only a small part of these will be ever </FONT>
<BR><FONT SIZE=2>> used in any actual map.</FONT>
</P>
<P><FONT SIZE=2>-- </FONT>
<BR><FONT SIZE=2> __</FONT>
<BR><FONT SIZE=2> /</FONT>
<BR><FONT SIZE=2> | Paul Ramsey</FONT>
<BR><FONT SIZE=2> | Refractions Research</FONT>
<BR><FONT SIZE=2> | Email: pramsey at refractions.net</FONT>
<BR><FONT SIZE=2> | Phone: (250) 885-0632</FONT>
<BR><FONT SIZE=2> \_</FONT>
</P>
<P><FONT SIZE=2>_______________________________________________</FONT>
<BR><FONT SIZE=2>Mapserver-users mailing list</FONT>
<BR><FONT SIZE=2>Mapserver-users at lists.gis.umn.edu</FONT>
<BR><FONT SIZE=2><A HREF="http://lists.gis.umn.edu/mailman/listinfo/mapserver-users" TARGET="_blank">http://lists.gis.umn.edu/mailman/listinfo/mapserver-users</A></FONT>
</P>
</BODY>
</HTML>
------_=_NextPart_001_01C2D201.A0B74200--
More information about the MapServer-users
mailing list