Johan,<br> <br><div class="gmail_quote">On Mon, Apr 16, 2012 at 6:08 PM, Johan Forsman <span dir="ltr"><<a href="mailto:Johan.Forsman@la.gov" target="_blank">Johan.Forsman@la.gov</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<u></u><u></u><div link="blue" vlink="purple" style="margin-left:3.0pt;margin-top:3.0pt;margin-right:3.0pt;margin-bottom:.75pt" lang="EN-US"><div><p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial","sans-serif";color:#1f497d">Success!<u></u><u></u></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. <u></u><u></u></span></p>
<p class="MsoNormal"><a name="136bf52db388b4bd_136bdd7e9cb5e500__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 </span></a></p>
</div></div></blockquote><div><br>I have updated documentation here,
<a href="http://geomoose.org/trunk/releases/2.6.html#release" target="_blank">http://geomoose.org/trunk/releases/2.6.html#release</a> and here, <a href="http://geomoose.org/trunk/docs/faq.html#why-doesn-t-layers-all-work-anymore">http://geomoose.org/trunk/docs/faq.html#why-doesn-t-layers-all-work-anymore</a> (should show updates in a while) Please review it to confirm that it is sufficient. <br>
</div><blockquote class="gmail_quote" style="margin:0pt 0pt 0pt 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div link="blue" vlink="purple" style="margin:3pt 3pt 0.75pt" lang="EN-US">
<div><p class="MsoNormal"><a name="136bf52db388b4bd_136bdd7e9cb5e500__MailEndCompose"><span style="font-size:10pt;font-family:"Arial","sans-serif";color:rgb(31,73,125)">retooling to work with the new version, especially if they are not configured to serve WMS already.<u></u><u></u></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.<u></u><u></u></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?<u></u><u></u></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?</span></p>
</div></div></blockquote><div><br>The email list is always a great place to confirm things. Once you are certain, a Trac Ticket is usually the best route, <a href="http://trac.osgeo.org/geomoose/newticket" target="_blank">http://trac.osgeo.org/geomoose/newticket</a><br>
<br>Bests, Eli<br><br></div><blockquote class="gmail_quote" style="margin:0pt 0pt 0pt 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div link="blue" vlink="purple" style="margin:3pt 3pt 0.75pt" lang="EN-US">
<div><p class="MsoNormal"><span style="font-size:10pt;font-family:"Arial","sans-serif";color:rgb(31,73,125)"><u></u><u></u></span></p><p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial","sans-serif";color:#1f497d">Thanks again,<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial","sans-serif";color:#1f497d">Johan.<u></u><u></u></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:<a href="mailto:Bob.Basques@ci.stpaul.mn.us" target="_blank">Bob.Basques@ci.stpaul.mn.us</a>] <br>
<b>Sent:</b> Monday, April 16, 2012 3:07 PM<br><b>To:</b> Jim Klassen; Johan Forsman<br><b>Cc:</b> <a href="mailto:geomoose-users@lists.osgeo.org" target="_blank">geomoose-users@lists.osgeo.org</a><br><b>Subject:</b> Re: [Geomoose-users] Changes to mapserver-type layer handling in GM 2.6?<u></u><u></u></span></p>
</div></div><div><div><p class="MsoNormal"><u></u> <u></u></p><p style="margin:0in;margin-bottom:.0001pt"><span style="font-family:"Comic Sans MS"">All (of you), <u></u><u></u></span></p><p class="MsoNormal" style="margin:0in;margin-bottom:.0001pt">
<span style="font-family:"Comic Sans MS""><u></u> <u></u></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) <u></u><u></u></span></p>
<p class="MsoNormal" style="margin:0in;margin-bottom:.0001pt"><span style="font-family:"Comic Sans MS""><u></u> <u></u></span></p><p style="margin:0in;margin-bottom:.0001pt"><span style="font-family:"Comic Sans MS"">bobb <u></u><u></u></span></p>
<p class="MsoNormal" style="margin:0in;margin-bottom:.0001pt"><span style="font-family:"Comic Sans MS""><u></u> <u></u></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" target="_blank">klassen.js@gmail.com</a>> wrote:<u></u><u></u></span></p><table style="margin-left:11.25pt;background:#f3f3f3" border="0" cellpadding="0">
<tbody><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" target="_blank">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?" target="_blank">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" target="_blank">Geomoose-users@lists.osgeo.org</a><br>> <a href="http://lists.osgeo.org/mailman/listinfo/geomoose-users" target="_blank">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" target="_blank">Geomoose-users@lists.osgeo.org</a><br><a href="http://lists.osgeo.org/mailman/listinfo/geomoose-users" target="_blank">http://lists.osgeo.org/mailman/listinfo/geomoose-users</a><u></u><u></u></p>
</div></td></tr></tbody></table><p class="MsoNormal" style="margin:0in;margin-bottom:.0001pt"><u></u> <u></u></p></div></div></div></div><br>_______________________________________________<br>
Geomoose-users mailing list<br>
<a href="mailto:Geomoose-users@lists.osgeo.org" target="_blank">Geomoose-users@lists.osgeo.org</a><br>
<a href="http://lists.osgeo.org/mailman/listinfo/geomoose-users" target="_blank">http://lists.osgeo.org/mailman/listinfo/geomoose-users</a><br>
<br></blockquote></div><br>