<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=us-ascii"><meta name=Generator content="Microsoft Word 14 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:"Comic Sans MS";
panose-1:3 15 7 2 3 3 2 2 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman","serif";
mso-believe-normal-left:yes;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p
{mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><![if mso 9]><style>p.MsoNormal
{margin-left:3.0pt;}
</style><![endif]><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=EN-US link=blue vlink=purple style='margin-left:3.0pt;margin-top:3.0pt;margin-right:3.0pt;margin-bottom:.75pt'><div class=WordSection1><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:#1F497D'>Success!<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:#1F497D'>The fastest method I could think of to test all layers was a bulk Find of “STATUS ON” and Replace with “GROUP ‘all’” which indeed allows the layers to display as intended using <layer name="all"/> in the mapbook. <o:p></o:p></span></p><p class=MsoNormal><a name="_MailEndCompose"><span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:#1F497D'>I think this topic needs to be documented front and center in the migration guide as it represents a fundamental change in the way the application works. I am sure there are many instances of legacy GM/MapServer installations that may require significant retooling to work with the new version, especially if they are not configured to serve WMS already.<o:p></o:p></span></a></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:#1F497D'>Thanks for the tips and for a really great product.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:#1F497D'>I am curious about Jim’s “in the default case” statement. Does this mean there is a case where the MapServer layers are *<b>not</b>* translated to WMS calls?<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:#1F497D'>Incidentally, I may have discovered a few other items that may not be as intended. If they are not user error, where is appropriate to report them?<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:#1F497D'>Thanks again,<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:#1F497D'>Johan.<o:p></o:p></span></p><div><div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal style='margin:0in;margin-bottom:.0001pt'><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> Bob Basques [mailto:Bob.Basques@ci.stpaul.mn.us] <br><b>Sent:</b> Monday, April 16, 2012 3:07 PM<br><b>To:</b> Jim Klassen; Johan Forsman<br><b>Cc:</b> geomoose-users@lists.osgeo.org<br><b>Subject:</b> Re: [Geomoose-users] Changes to mapserver-type layer handling in GM 2.6?<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></p><p style='margin:0in;margin-bottom:.0001pt'><span style='font-family:"Comic Sans MS"'>All (of you), <o:p></o:p></span></p><p class=MsoNormal style='margin:0in;margin-bottom:.0001pt'><span style='font-family:"Comic Sans MS"'><o:p> </o:p></span></p><p style='margin:0in;margin-bottom:.0001pt'><span style='font-family:"Comic Sans MS"'>Just adding the desired layers to a GROUP called "all", should fix things (I think) <o:p></o:p></span></p><p class=MsoNormal style='margin:0in;margin-bottom:.0001pt'><span style='font-family:"Comic Sans MS"'><o:p> </o:p></span></p><p style='margin:0in;margin-bottom:.0001pt'><span style='font-family:"Comic Sans MS"'>bobb <o:p></o:p></span></p><p class=MsoNormal style='margin:0in;margin-bottom:.0001pt'><span style='font-family:"Comic Sans MS"'><o:p> </o:p></span></p><p style='margin:0in;margin-bottom:.0001pt'><span style='font-family:"Comic Sans MS"'><br><br>>>> Jim Klassen <<a href="mailto:klassen.js@gmail.com">klassen.js@gmail.com</a>> wrote:<o:p></o:p></span></p><table class=MsoNormalTable border=0 cellpadding=0 style='margin-left:11.25pt;background:#F3F3F3'><tr><td style='padding:.75pt .75pt .75pt .75pt'><div style='border:none;border-left:solid #050505 1.0pt;padding:0in 0in 0in 5.0pt'><p style='margin:0in;margin-bottom:.0001pt'>It was intentional to migrate to using WMS over the MapServer specific calls in the default case as it eases interoperability with other servers and simplifies the code in many cases.<br><br>I don't think it was intentional to loose the layers=all trick (which was implemented inside MapServer not GeoMoose). Do any of the suggestions in the MapServer ticket referenced by Bob work as a workaround for you?<br><br>While 2.6 is near to release, one of the bigger tasks left is finishing up documentation. Thank you for testing and bring this to our attention.<br><br>On Apr 16, 2012, at 2:24 PM, Johan Forsman wrote:<br><br>> All:<br>><br>> I am slowly migrating a GM 2.2 site with some minor customizations to 2.6 and am wondering if what I am observing with my mapserver layers is by design or an error on my part.<br>><br>> On 2.6 it appears that all mapserver layers are requested as WMS which appears to result in<br>><br>> 1) any mapserver-type layer returns an error if the map file does not at least contain something like 'ows_enable_request' '*', and<br>><br>> 2) using the "all" parameter in the layer definition in the mapbook returns an error.<br>><br>> For example, in the 2.2 environment I have a "roads" source defined in the mapbook very simply as such:<br>><br>> <map-source name="roads_simple" type="mapserver" ><br>> <file>./sdwp/roads/webmaps_osm_lahwys.map</file><br>> <layer name="all"/><br>><br>> <layer title="Roads" src="roads_simple/all" status="off" legend="true" show-legend="true" fade="false" unfade="false"/><br>><br>> The forwarded URL request is:<br>><br>> <a href="http://oph-isb-gis01/cgi-bin/mapserv.exe?map=/mapserver/apps/geomoose2/maps//sdwp/roads/webmaps_osm_lahwys.map&layers=all&mode=map&mapext=-10879743+3088767+-9475743+4200267&imgext=-10879743+3088767+-9475743+4200267&map_size=1404+1111&imgx=702&imgy=555.5&imgxy=1404+1111">http://oph-isb-gis01/cgi-bin/mapserv.exe?map=/mapserver/apps/geomoose2/maps//sdwp/roads/webmaps_osm_lahwys.map&layers=all&mode=map&mapext=-10879743+3088767+-9475743+4200267&imgext=-10879743+3088767+-9475743+4200267&map_size=1404+1111&imgx=702&imgy=555.5&imgxy=1404+1111</a><br>><br>> The map file contains many scale-dependent line- and annotation layers and renders beautifully.<br>><br>> In the 2.6 environment the same mapbook definition and mapfile results in this call:<br>><br>> <a href="http://oph-isb-gis01/cgi-bin/mapserv.exe?">http://oph-isb-gis01/cgi-bin/mapserv.exe?</a><br>> MAP=/mapserver/apps/geomoose26/maps//sdwp/roads/webmaps_osm_lahwys.map&FORMAT=image/png&TRANSPARENT=TRUE&SERVICE=WMS&VERSION=1.1.1&REQUEST=GetMap&STYLES=&LAYERS=all&SRS=EPSG%3A3857&BBOX=-10706687.23566,3214635.152984,-9648798.7643401,4074398.847016&WIDTH=865&HEIGHT=703<br>><br>> which returns:<br>><br>> <ServiceException code="LayerNotDefined"><br>> msWMSLoadGetMapParams(): WMS server error. Invalid layer(s) given in the LAYERS parameter.<br>> </ServiceException><br>><br>> I have unsuccessfully searched for documentation on this topic. Please advise.<br>><br>> Thanks!<br>> Johan Forsman<br>> Geologist<br>> Engineering Services<br>> LDHH-OPH-CEHS<br>> 225.342.7309<br>><br>><br>> _______________________________________________<br>> Geomoose-users mailing list<br>> <a href="mailto:Geomoose-users@lists.osgeo.org">Geomoose-users@lists.osgeo.org</a><br>> <a href="http://lists.osgeo.org/mailman/listinfo/geomoose-users">http://lists.osgeo.org/mailman/listinfo/geomoose-users</a><br><br>_______________________________________________<br>Geomoose-users mailing list<br><a href="mailto:Geomoose-users@lists.osgeo.org">Geomoose-users@lists.osgeo.org</a><br><a href="http://lists.osgeo.org/mailman/listinfo/geomoose-users">http://lists.osgeo.org/mailman/listinfo/geomoose-users</a><o:p></o:p></p></div></td></tr></table><p class=MsoNormal style='margin:0in;margin-bottom:.0001pt'><o:p> </o:p></p></div></body></html>