<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML DIR=ltr><HEAD></HEAD><BODY>
<DIV id=idOWAReplyText33374 dir=ltr>
<DIV dir=ltr><FONT face=Arial color=#000000 size=2>Hi all,</FONT></DIV>
<DIV dir=ltr><FONT face=Arial size=2></FONT> </DIV>
<DIV dir=ltr><FONT face=Arial size=2>I'm working on a way to
make a large amount of our vector and raster data available via WMS and
WFS, and I've come up against the MAXLAYERS setting (200 in our install I
think).</FONT></DIV>
<DIV dir=ltr><FONT face=Arial size=2></FONT> </DIV>
<DIV dir=ltr><FONT face=Arial size=2>I'm already trying to get around the need
for having so many layers in a single mapfile by reducing the granularity
available as you get to mapfiles which cover a larger time period - let me see
if I can explain what I mean without rambling on too much.</FONT></DIV>
<DIV dir=ltr><FONT face=Arial size=2></FONT> </DIV>
<DIV dir=ltr><FONT face=Arial size=2>At the lowest level of granularity, we're
providing access to raster and vector files which are derived from satellite
passes - and there may be 10-40 passes per day, depending on the product. I've
already set up a process to automatically generate a mapfile containing the last
5 days worth of data, using the GROUP parameter to group them according to the
day. This is jolly nifty for those customers who need to look at the recent info
on a pass by pass basis.</FONT></DIV>
<DIV dir=ltr><FONT face=Arial size=2></FONT> </DIV>
<DIV dir=ltr><FONT face=Arial size=2>However, if I try to give people access to
the entire archive (several years worth, and 10-15 different products, at 10-40
passes per day) on a pass by pass basis, the number of layers involved will be
horrendous, so I'm trying to reduce the granularity at which archival data is
available.</FONT></DIV>
<DIV dir=ltr><FONT face=Arial color=#000000 size=2></FONT> </DIV>
<DIV dir=ltr><FONT face=Arial size=2>My current plan is
to (programmatically) create a series of weekly mapfiles, structured in the
same way as mentioned above, with individual satellite passes grouped by day. I
would have 52 of those for each year, and then to wrap them up so that
people could have an overview of what's available, I'm planning to create some
mapfiles (either yearly or monthly, maybe both), which connect to these weekly
mapfiles via WMS, and pull in each daily group from the 52 weekly mapfiles, and
define them as a single layer.</FONT></DIV>
<DIV dir=ltr><FONT face=Arial size=2></FONT> </DIV>
<DIV dir=ltr><FONT face=Arial size=2>So I think I would end up with a mapfile
for each year, with a group for each week, and under each group, 7 individual
layers - one for each day. Hopefully then there are two options:</FONT></DIV>
<DIV dir=ltr><FONT face=Arial size=2>1) People's clients are able to pull apart
the vector data, and maybe do a query (for instance) to only display the
lightning data from one particular satellite pass - although having used ArcMap
and ArcExplorer for testing I'm not too hopeful about this;</FONT></DIV>
<DIV dir=ltr><FONT face=Arial size=2>2) Specific file naming conventions could
allow users to find the week they're interested in in the yearly mapfile, and
then work out what the mapfile name/URL for that week's lower level mapfile
would be.</FONT></DIV>
<DIV dir=ltr><FONT face=Arial size=2></FONT> </DIV>
<DIV dir=ltr><FONT face=Arial size=2>So, now I'm finally going to get to my
point - even using this structure, a MAXLAYERS setting of 200 is too low for me
- I can do about 5 or 6 days of satellite passes in 200 layers, but to get to a
whole week I would need to increase the MAXLAYERS parameter. To have a
layer for each day in my yearly mapfile, I'd need a MAXLAYERS of around
370.</FONT></DIV>
<DIV dir=ltr><FONT face=Arial size=2></FONT> </DIV>
<DIV dir=ltr><FONT face=Arial size=2>I gather it's relatively easy to change the
parameter and recompile Mapserver, but as I have very little experience in this
area (and I've seen so many emails on this list seeking help with compiling
mapserver!) I was hoping somebody might possibly have already done this, and
might have Windows binaries compiled with a higher MAXLAYERS that they would be
willing to share.</FONT></DIV>
<DIV dir=ltr><FONT face=Arial size=2></FONT> </DIV>
<DIV dir=ltr><FONT face=Arial size=2>Alternatively, if the structure I described
above sounds silly or you can think of something more effective, please let me
know :) We do have another approach in mind for the vector data, which is to
produce an ongoing concatenated shapefile which contains all the features for
that product (for instance, as a new pass's worth of lightning data becomes
available, it is automatically added in to one big Lightning shapefile),
and then to use classes to colour them up a bit according to the time that
each event occurred. It's a nice theory for the vector info, but I'd still
need to do something about the raster info.</FONT></DIV>
<DIV dir=ltr><FONT face=Arial size=2></FONT> </DIV>
<DIV dir=ltr><FONT face=Arial size=2></FONT> </DIV>
<DIV dir=ltr><FONT face=Arial size=2>Any advice (or binaries!) would be very
much appreciated :)</FONT></DIV>
<DIV dir=ltr><FONT face=Arial size=2></FONT> </DIV>
<DIV dir=ltr><FONT face=Arial size=2></FONT> </DIV>
<DIV dir=ltr><FONT face=Arial size=2>Thanks,</FONT></DIV>
<DIV dir=ltr><FONT face=Arial size=2></FONT> </DIV>
<DIV dir=ltr><FONT face=Arial size=2></FONT> </DIV>
<DIV dir=ltr><FONT face=Arial size=2>Bonnie</FONT></DIV>
<DIV dir=ltr><FONT face=Arial size=2></FONT> </DIV></DIV>
<DIV id=idSignature69961 dir=ltr>
<DIV><FONT face=Arial color=#000000 size=2><FONT face=Helv size=2>
<DIV>
<DIV><FONT face=Arial color=#000000 size=2><FONT face=Helv color=#000000 size=2>
<DIV><FONT face=Arial color=gray size=2><SPAN lang=EN-AU
style="FONT-SIZE: 11pt; COLOR: gray; FONT-FAMILY: Arial">__________________________________</SPAN></FONT></DIV>
<DIV>
<DIV class=MsoNormal><FONT face=Arial color=gray size=2><SPAN lang=EN-AU
style="FONT-SIZE: 11pt; COLOR: gray; FONT-FAMILY: Arial"></SPAN></FONT><FONT
face=Arial color=gray size=2><SPAN lang=EN-AU
style="FONT-SIZE: 11pt; COLOR: gray; FONT-FAMILY: Arial">Bonnie
Stewart</SPAN></FONT></DIV>
<DIV class=MsoNormal><FONT face=Arial color=gray size=2><SPAN lang=EN-AU
style="FONT-SIZE: 11pt; COLOR: gray; FONT-FAMILY: Arial">Research
Officer<BR></SPAN></FONT><FONT face=Arial color=gray size=2><SPAN lang=EN-AU
style="FONT-SIZE: 11pt; COLOR: gray; FONT-FAMILY: Arial">Satellite Remote
Sensing Services<BR></SPAN></FONT><FONT face=Arial color=gray size=2><SPAN
lang=EN-AU style="FONT-SIZE: 11pt; COLOR: gray; FONT-FAMILY: Arial">Information
Access Division<BR></SPAN></FONT><FONT face=Arial color=gray size=2><SPAN
lang=EN-AU style="FONT-SIZE: 11pt; COLOR: gray; FONT-FAMILY: Arial">Department
of Land Information<BR></SPAN></FONT><FONT face=Arial color=gray size=2><SPAN
lang=EN-AU style="FONT-SIZE: 11pt; COLOR: gray; FONT-FAMILY: Arial">65 Brockway
Road, FLOREAT WA </SPAN></FONT><FONT face=Arial color=gray size=2><SPAN
lang=EN-AU
style="FONT-SIZE: 11pt; COLOR: gray; FONT-FAMILY: Arial">6014<BR></SPAN></FONT><FONT
face=Arial color=gray size=2><SPAN lang=EN-AU
style="FONT-SIZE: 11pt; COLOR: gray; FONT-FAMILY: Arial">Ph. (08) 9387 0342
| Fx. (08) 9383 7142<BR></SPAN></FONT><FONT face=Arial color=gray
size=2><SPAN lang=EN-AU
style="FONT-SIZE: 11pt; COLOR: gray; FONT-FAMILY: Arial"><A
href="mailto:bonnie.stewart@dli.wa.gov.au">bonnie.stewart@dli.wa.gov.au</A><BR></SPAN></FONT><FONT
face=Arial color=gray size=2><SPAN lang=EN-AU
style="FONT-SIZE: 11pt; COLOR: gray; FONT-FAMILY: Arial"><A
href="http://www.dli.wa.gov.au">www.dli.wa.gov.au</A></SPAN></FONT></DIV></DIV></FONT></FONT></DIV></DIV></FONT></FONT></DIV></DIV><FONT SIZE=3><BR>
<BR>
This e-mail and any files transmitted with it are intended only for the use of the addressee(s). It may contain information that is confidential and privileged. If you are not an intended recipient, any use, interference with, disclosure, distribution or copying of this material is unauthorised and prohibited. If you receive this in error, please notify the author by Return email to the sender. Information in this message not relating to the official business of DLI shall be understood as neither given nor endorsed by it. While every care is taken, it is recommended that you scan any attachments for viruses. DLI liability is limited to re-supplying affected attachments.<BR>
</FONT>
</BODY></HTML>