[Geomoose-users] Changes to mapserver-type layer handling in GM 2.6?

[Eli Adam]

Johan,

On Mon, Apr 16, 2012 at 6:08 PM, Johan Forsman <Johan.Forsman at la.gov> wrote:

> ****
>
> Success!****
>
> 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. ****
>
> 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
>

I have updated documentation here,
http://geomoose.org/trunk/releases/2.6.html#release and here,
http://geomoose.org/trunk/docs/faq.html#why-doesn-t-layers-all-work-anymore(should
show updates in a while)  Please review it to confirm that it is
sufficient.


> retooling to work with the new version, especially if they are not
> configured to serve WMS already.****
>
> Thanks for the tips and for a really great product.****
>
> I am curious about Jim’s “in the default case”  statement. Does this mean
> there is a case where the MapServer layers are **not** translated to WMS
> calls?****
>
> 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?
>

The email list is always a great place to confirm things. Once you are
certain, a Trac Ticket is usually the best route,
http://trac.osgeo.org/geomoose/newticket

Bests, Eli

****
>
> Thanks again,****
>
> Johan.****
>
> *From:* Bob Basques [mailto:Bob.Basques at ci.stpaul.mn.us]
> *Sent:* Monday, April 16, 2012 3:07 PM
> *To:* Jim Klassen; Johan Forsman
> *Cc:* geomoose-users at lists.osgeo.org
> *Subject:* Re: [Geomoose-users] Changes to mapserver-type layer handling
> in GM 2.6?****
>
> ** **
>
> All (of you), ****
>
> ** **
>
> Just adding the desired layers to a GROUP called "all", should fix things
> (I think) ****
>
> ** **
>
> bobb ****
>
> ** **
>
>
>
> >>> Jim Klassen <klassen.js at gmail.com> wrote:****
>
> 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.
>
> 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?
>
> 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.
>
> On Apr 16, 2012, at 2:24 PM, Johan Forsman wrote:
>
> > All:
> >
> > 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.
> >
> > On 2.6 it appears that all mapserver layers are requested as WMS which
> appears to result in
> >
> > 1) any mapserver-type layer returns an error if the map file does not at
> least contain something like 'ows_enable_request' '*', and
> >
> > 2) using the "all" parameter in the layer definition in the mapbook
> returns an error.
> >
> > For example, in the 2.2 environment I have a "roads" source defined in
> the mapbook very simply as such:
> >
> > <map-source name="roads_simple" type="mapserver" >
> > <file>./sdwp/roads/webmaps_osm_lahwys.map</file>
> > <layer name="all"/>
> >
> > <layer title="Roads" src="roads_simple/all" status="off" legend="true"
> show-legend="true" fade="false" unfade="false"/>
> >
> > The forwarded URL request is:
> >
> >
> 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
> >
> > The map file contains many scale-dependent line- and annotation layers
> and renders beautifully.
> >
> > In the 2.6 environment the same mapbook definition and mapfile results
> in this call:
> >
> > http://oph-isb-gis01/cgi-bin/mapserv.exe?
> >
> 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
> >
> > which returns:
> >
> > <ServiceException code="LayerNotDefined">
> > msWMSLoadGetMapParams(): WMS server error. Invalid layer(s) given in the
> LAYERS parameter.
> > </ServiceException>
> >
> > I have unsuccessfully searched for documentation on this topic. Please
> advise.
> >
> > Thanks!
> > Johan Forsman
> > Geologist
> > Engineering Services
> > LDHH-OPH-CEHS
> > 225.342.7309
> >
> >
> > _______________________________________________
> > Geomoose-users mailing list
> > Geomoose-users at lists.osgeo.org
> > http://lists.osgeo.org/mailman/listinfo/geomoose-users
>
> _______________________________________________
> Geomoose-users mailing list
> Geomoose-users at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/geomoose-users****
>
> ** **
>
> _______________________________________________
> Geomoose-users mailing list
> Geomoose-users at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/geomoose-users
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.osgeo.org/pipermail/geomoose-users/attachments/20120417/fa1e022f/attachment.html