<html 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=utf-8">
<meta name="Generator" content="Microsoft Word 15 (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;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
span.EmailStyle19
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}
.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>
</head>
<body lang="EN-US" link="#0563C1" vlink="#954F72">
<div class="WordSection1">
<p class="MsoNormal"><br>
I would like to reinforce the idea of getting the multiple mapbooks capability, this should help with uptake on the end users behalf of all the new work coming out. Easier to organize too.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">So, related to this, does multiple mapbooks really mean swapping mapbooks, or will we be able to source multiple mapbooks at the same time, in one interface? :c). I can see business cases for isolating the editing functions as well
as mixing them into a larger lookup interface. So swapping of Mapbooks would certainly be used, but having separate mapbooks for lookup and editing??<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">I like the old way of mapbook= for swapping since it’s bookmarkable.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Bobb<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal" style="margin-left:.5in"><b><span style="font-size:12.0pt;color:black">From:
</span></b><span style="font-size:12.0pt;color:black">geomoose-psc <geomoose-psc-bounces@lists.osgeo.org> on behalf of Dan Little <theduckylittle@gmail.com><br>
<b>Date: </b>Saturday, May 22, 2021 at 10:36 AM<br>
<b>To: </b>"geomoose-psc@lists.osgeo.org" <geomoose-psc@lists.osgeo.org><br>
<b>Subject: </b>[geomoose-psc] Examples / Demos / Mulitple Mapbooks<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><o:p> </o:p></p>
</div>
<table class="MsoNormalTable" border="1" cellpadding="0" style="margin-left:.5in;background:#E2F700;border:solid black 1.0pt">
<tbody>
<tr>
<td style="border:none;padding:.75pt .75pt .75pt .75pt">
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><strong><span style="font-family:"Calibri",sans-serif;color:#FF3333">Think Before You Click:
</span></strong><span style="color:black">This email originated <strong><span style="font-family:"Calibri",sans-serif">outside
</span></strong>our organization.</span><o:p></o:p></p>
</td>
</tr>
</tbody>
</table>
<p class="MsoNormal" style="margin-left:.5in"><o:p> </o:p></p>
<div>
<div>
<div>
<p class="MsoNormal" style="margin-left:.5in">I think we have hit a critical mass of needing *four* Desktop demos:<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">1. Editing - The two mapbooks below should be identical but for their target server. I am in favor of having these be a more limited workflow that shows how editing works in a practical way.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"> A. Based on GeoServer.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"> B. Based on PostGIS.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">2. "The Desktop Demo" a la the status quo. The demo that people will "Copy Pasta" and turn into their deployed Website. Drop all the scary warning messages, ensure our comments are up to date, and that we remove
the "Test code". We attempt to show a reasonable set of data types that people would find around in a "typical" County/City/Division website.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">3. "The testing mapbook":<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"> - This can have the same layers configured in different ways (WFS, WMS)<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"> - "Test grids" - So we can test scaling and printing issues.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"> - Can include stuff that is intentionally broken to test error handling.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"> - I feel we can add stuff with a <exp:> prefix to denote some experimental stuff we could point users to but not feel the need to adopt and support long term.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">Does this seem like a lot? Sure. Maybe? Why I don't think it is:<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">1. The editing workflow is pretty dedicated and I feel Brent has put some real time into making sure it is well tested. I feel like that will continue and we have historically had good stakeholders for that functionality.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">2. The "Desktop demo" will be a subset of the functionality that starts in the testing mapbook.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">3. I find it harder to comment, uncomment, and generally futz around with the "Desktop demo" all the time to make sure it looks okay AND that we have all of the needed functionality ready to test. While, yes, additional
unit-testing will help it is very hard to beat a real-world end-to-end test. <o:p>
</o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">I may take an initial swipe at this when I do the multiple mapbooks support but drafting an official RFC may be prudent here.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">Thanks for reading!<o:p></o:p></p>
</div>
</div>
</div>
</div>
</body>
</html>