[mapserver-dev] Proposal to add built-in OpenLayers map viewer

[Paul Ramsey]

The beauty part of mode=openlayers is that mapserver doesn't even need
to ship code with it, it can just emit an HTML page that references
openlayers.org. Any framework that requires server-side components and
isn't cloud-hosted already is kind of out-of-luck. There could also be
a mode=googlemaps in combination with the tile mode or a mode=bingmaps
...

P.

On Fri, Sep 24, 2010 at 11:48 AM, Bob Basques
<Bob.Basques at ci.stpaul.mn.us> wrote:
> All,
>
> Ok, no problem, but I want a mode=geomoose too, and mode= . . .   (well you
> get the idea  :c)
>
> Is there possibly a way to implement this as an include of some sort vs a
> complete embedding in MapServer?  I've often wondered how setting up
> additional output modes in this manner might be added to mapserv without
> undue hardship on the core development.
>
> I would like to see some thought put into this topic around setting up some
> sort of reusable output modes of operation, vs embedding any single one.
>
> I can also tell you right now, that it would be very valuable (to us) to be
> able to run these alternate modes of output for a number of reasons, both
> for testing as well as integration of multiple and task specific output
> modes.
>
> We've been playing around with this idea from time to time and have even
> implemented some of them in our own environment, the reason it's never gone
> back into trunk is that there wasn't much interest in being able to do these
> types of things in the past (as there are now apparently )
>
> bobb
>
>
>>>> Daniel Morissette <dmorissette at mapgears.com> wrote:
>
> This was discussed at the code sprint in Barcelona, and I just created a
> ticket for it. We'd like to add this to 6.0... but I am realizing just
> now that maybe I should start with a RFC...
>
> Anyway, here is what I wrote in the ticket, please feel free to comment,
> keeping in mind this has to remain __simple__:
>
> http://trac.osgeo.org/mapserver/ticket/3549
>
> Every once in a while we get requests for a simple way to test a
> mapfile. One way to handle this could be to do as GeoServer does and
> provide a built-in OpenLayers based map viewer. In the GeoServer case,
> this viewer is returned when one issues a WMS GetMap request with
> format=application/openlayers in it.
>
> I propose that we provide a similar functionality in MapServer, which
> would be triggered in one of two ways:
>
> 1- Using mapserv?map=/path/to/my.map&'''mode=openlayers''' ... in this
> case the viewer would be initialized based on the mapfile defaults, and
> some of the traditional mapserv CGI params may also work (such as map
> size, layer selection, etc.)
>
> 2- Using '''format=application/openlayers''' in a WMS GetMap request as
> GeoServer does. Note that in this case the rest of the GetMap parameters
> would be used to configure the map to view (BBOX, WIDTH, HEIGHT, LAYERS,
> etc.)
>
> Both cases would call the same function internally to produce a simple
> OpenLayeres viewer with one singletile layer for the whole map with the
> selected layers.
>
>
> --
> Daniel Morissette
> http://www.mapgears.com/
> _______________________________________________
> mapserver-dev mailing list
> mapserver-dev at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/mapserver-dev
>
> _______________________________________________
> mapserver-dev mailing list
> mapserver-dev at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/mapserver-dev
>
>