<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:x="urn:schemas-microsoft-com:office:excel" xmlns:p="urn:schemas-microsoft-com:office:powerpoint" xmlns:a="urn:schemas-microsoft-com:office:access" xmlns:dt="uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" xmlns:s="uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882" xmlns:rs="urn:schemas-microsoft-com:rowset" xmlns:z="#RowsetSchema" xmlns:b="urn:schemas-microsoft-com:office:publisher" xmlns:ss="urn:schemas-microsoft-com:office:spreadsheet" xmlns:c="urn:schemas-microsoft-com:office:component:spreadsheet" xmlns:odc="urn:schemas-microsoft-com:office:odc" xmlns:oa="urn:schemas-microsoft-com:office:activation" xmlns:html="http://www.w3.org/TR/REC-html40" xmlns:q="http://schemas.xmlsoap.org/soap/envelope/" xmlns:rtc="http://microsoft.com/officenet/conferencing" xmlns:D="DAV:" xmlns:Repl="http://schemas.microsoft.com/repl/" xmlns:mt="http://schemas.microsoft.com/sharepoint/soap/meetings/" xmlns:x2="http://schemas.microsoft.com/office/excel/2003/xml" xmlns:ppda="http://www.passport.com/NameSpace.xsd" xmlns:ois="http://schemas.microsoft.com/sharepoint/soap/ois/" xmlns:dir="http://schemas.microsoft.com/sharepoint/soap/directory/" xmlns:ds="http://www.w3.org/2000/09/xmldsig#" xmlns:dsp="http://schemas.microsoft.com/sharepoint/dsp" xmlns:udc="http://schemas.microsoft.com/data/udc" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:sub="http://schemas.microsoft.com/sharepoint/soap/2002/1/alerts/" xmlns:ec="http://www.w3.org/2001/04/xmlenc#" xmlns:sp="http://schemas.microsoft.com/sharepoint/" xmlns:sps="http://schemas.microsoft.com/sharepoint/soap/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:udcs="http://schemas.microsoft.com/data/udc/soap" xmlns:udcxf="http://schemas.microsoft.com/data/udc/xmlfile" xmlns:udcp2p="http://schemas.microsoft.com/data/udc/parttopart" xmlns:wf="http://schemas.microsoft.com/sharepoint/soap/workflow/" xmlns:dsss="http://schemas.microsoft.com/office/2006/digsig-setup" xmlns:dssi="http://schemas.microsoft.com/office/2006/digsig" xmlns:mdssi="http://schemas.openxmlformats.org/package/2006/digital-signature" xmlns:mver="http://schemas.openxmlformats.org/markup-compatibility/2006" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns:mrels="http://schemas.openxmlformats.org/package/2006/relationships" xmlns:spwp="http://microsoft.com/sharepoint/webpartpages" xmlns:ex12t="http://schemas.microsoft.com/exchange/services/2006/types" xmlns:ex12m="http://schemas.microsoft.com/exchange/services/2006/messages" xmlns:pptsl="http://schemas.microsoft.com/sharepoint/soap/SlideLibrary/" xmlns:spsl="http://microsoft.com/webservices/SharePointPortalServer/PublishedLinksService" xmlns:Z="urn:schemas-microsoft-com:" xmlns:st="&#1;" 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 12 (filtered medium)">
<style>
<!--
 /* Font Definitions */
 @font-face
        {font-family:"Cambria Math";
        panose-1:2 4 5 3 5 4 6 3 2 4;}
@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;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
        {margin:0in;
        margin-bottom:.0001pt;
        font-size:12.0pt;
        font-family:"Times New Roman","serif";}
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;}
span.EmailStyle17
        {mso-style-type:personal-reply;
        font-family:"Calibri","sans-serif";
        color:#1F497D;}
.MsoChpDefault
        {mso-style-type:export-only;}
@page WordSection1
        {size:8.5in 11.0in;
        margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
        {page:WordSection1;}
-->
</style>
<!--[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>

<div class=WordSection1>

<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>So where are we at? I do like the idea. The technical solution,
IMHO, will probably point to how this might work operationally. For example, if
the plan were to simply embed a HTML/OL template in code then a mode=openlayers
would make sense. However, if the template were stored externally and a basic
one shipped with MapServer then I&#8217;d opt for
mode=browse&amp;template=openlayers. The advantage of the external templates is
extensibility and users could edit the one(s) provided or add their own. They
could also disable the functionality altogether by removing all templates. The
downside is setting up access and then security. If external templates used the
templating code and magic strings that would mitigate many issues&#8230;<o:p></o:p></span></p>

<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p>&nbsp;</o:p></span></p>

<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Steve<o:p></o:p></span></p>

<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p>&nbsp;</o:p></span></p>

<div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'>

<p class=MsoNormal><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"'>
mapserver-dev-bounces@lists.osgeo.org [mailto:mapserver-dev-bounces@lists.osgeo.org]
<b>On Behalf Of </b>Tamas Szekeres<br>
<b>Sent:</b> Friday, September 24, 2010 4:46 PM<br>
<b>To:</b> Daniel Morissette<br>
<b>Cc:</b> MapServer Dev List<br>
<b>Subject:</b> Re: [mapserver-dev] Proposal to add built-in OpenLayers map
viewer<o:p></o:p></span></p>

</div>

<p class=MsoNormal><o:p>&nbsp;</o:p></p>

<p class=MsoNormal style='margin-bottom:12.0pt'>Daniel,<br>
<br>
Adding a viewer with zoom and pan capabilities is a good idea which is better
then having a single image in some cases. I foresee a reasonable Web
administration interface to mapserver could also be established by such
additions which would be a requirement too.<br>
However embedding code from a separate project seems to be a hassle, though the
technical solution hasn't yet been mentioned in the ticket.<br>
<br>
I would be in favour of doing either:<br>
<br>
1. Create a simple&nbsp; (mapserver specific) .js to provide the required functionality
(which could be extended later with further options)<br>
2. Provide a (pluggable) interface for use by the potential viewers in
mapserver, and&nbsp; create a separate support package for at least one (like
openlayers for instance) and include the external code to this package.<br>
<br>
<br>
(Just to put my 2 cents in)<br>
<br>
Best regards,<br>
<br>
Tamas<br>
<br>
<br>
<br>
<br>
<o:p></o:p></p>

<div>

<p class=MsoNormal>2010/9/24 Daniel Morissette &lt;<a
href="mailto:dmorissette@mapgears.com">dmorissette@mapgears.com</a>&gt;<o:p></o:p></p>

<p class=MsoNormal>This was discussed at the code sprint in Barcelona, and I
just created a<br>
ticket for it. We'd like to add this to 6.0... but I am realizing just<br>
now that maybe I should start with a RFC...<br>
<br>
Anyway, here is what I wrote in the ticket, please feel free to comment,<br>
keeping in mind this has to remain __simple__:<br>
<br>
<a href="http://trac.osgeo.org/mapserver/ticket/3549" target="_blank">http://trac.osgeo.org/mapserver/ticket/3549</a><br>
<br>
Every once in a while we get requests for a simple way to test a<br>
mapfile. One way to handle this could be to do as GeoServer does and<br>
provide a built-in OpenLayers based map viewer. In the GeoServer case,<br>
this viewer is returned when one issues a WMS GetMap request with<br>
format=application/openlayers in it.<br>
<br>
I propose that we provide a similar functionality in MapServer, which<br>
would be triggered in one of two ways:<br>
<br>
1- Using mapserv?map=/path/to/my.map&amp;'''mode=openlayers''' ... in this<br>
case the viewer would be initialized based on the mapfile defaults, and<br>
some of the traditional mapserv CGI params may also work (such as map<br>
size, layer selection, etc.)<br>
<br>
2- Using '''format=application/openlayers''' in a WMS GetMap request as<br>
GeoServer does. Note that in this case the rest of the GetMap parameters<br>
would be used to configure the map to view (BBOX, WIDTH, HEIGHT, LAYERS,<br>
etc.)<br>
<br>
Both cases would call the same function internally to produce a simple<br>
OpenLayeres viewer with one singletile layer for the whole map with the<br>
selected layers.<br>
<span style='color:#888888'><br>
<br>
--<br>
Daniel Morissette<br>
<a href="http://www.mapgears.com/" target="_blank">http://www.mapgears.com/</a><br>
_______________________________________________<br>
mapserver-dev mailing list<br>
<a href="mailto:mapserver-dev@lists.osgeo.org">mapserver-dev@lists.osgeo.org</a><br>
<a href="http://lists.osgeo.org/mailman/listinfo/mapserver-dev" target="_blank">http://lists.osgeo.org/mailman/listinfo/mapserver-dev</a></span><o:p></o:p></p>

</div>

<p class=MsoNormal><o:p>&nbsp;</o:p></p>

</div>

</body>

</html>