<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: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=us-ascii"><meta name=Generator content="Microsoft Word 14 (filtered medium)"><style><!--
/* Font Definitions */
@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;}
@font-face
{font-family:"Comic Sans MS";
panose-1:3 15 7 2 3 3 2 2 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman","serif";
mso-believe-normal-left:yes;}
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;}
p
{mso-style-priority:99;
margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
{mso-style-priority:99;
mso-style-link:"Balloon Text Char";
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:8.0pt;
font-family:"Tahoma","sans-serif";}
span.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Tahoma","sans-serif";}
span.EmailStyle20
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.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><![if mso 9]><style>p.MsoNormal
{margin-left:3.0pt;}
</style><![endif]><!--[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 style='margin-left:3.0pt;margin-top:3.0pt;margin-right:3.0pt;margin-bottom:.75pt'><div class=WordSection1><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Hi Bob<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Thanks for the comments, see responses in-line.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Len<o:p></o:p></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:Bob.Basques@ci.stpaul.mn.us] <br><b>Sent:</b> Tuesday, September 28, 2010 2:48 PM<br><b>To:</b> Len Kne; 'geomoose-users@lists.sourceforge.net'(geomoose-users@lists.sourceforge.net)<br><b>Cc:</b> DEAN ANDERSON (ANDERSON.DEAN@co.polk.or.us)<br><b>Subject:</b> Re: [Geomoose-users] FW: GeoMOOSE RFC - Selection Set Proposal<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></p><p><span style='font-family:"Comic Sans MS"'>Len,</span> <o:p></o:p></p><p class=MsoNormal style='margin:0in;margin-bottom:.0001pt'><o:p> </o:p></p><p><span style='font-family:"Comic Sans MS"'>I just around to looking at things you posted. For the most part it looks really good. A couple of nit picky things though.</span> <o:p></o:p></p><p class=MsoNormal style='margin:0in;margin-bottom:.0001pt'><o:p> </o:p></p><p><span style='font-family:"Comic Sans MS"'>** The buffer highlight results, MapServer I believe can handle this type of thing via Geos in order to give a real buffer outline back to the client to display.</span> <o:p></o:p></p><p class=MsoNormal style='margin:0in;margin-bottom:.0001pt'><span style='color:#1F497D'>I’ll look into to see if it applies.<o:p></o:p></span></p><p class=MsoNormal style='margin:0in;margin-bottom:.0001pt'><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p><span style='font-family:"Comic Sans MS"'>** I was trying to find a method in the interface to highlight one of the tabular records by picking on a parcel in the map, and I didn't see a way to do this, don't know if it would require an additional tool in the map control or what, but it just seemed like being able to pick from the map or the tabular display should work (for some reason :c)</span> <o:p></o:p></p><p><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Yes, this is going to take an additional map control on a mouse click. The handler will make a call to a server side service (similar to the Select service) which returns the feature of the active layer where the mouse click happened. On the client side, we will look at the returned feature to see if it is present in the vector layer – if it isn’t present = addFeature(), if it is part of the selection set, it will be removed. Once OL is updated, refresh the table and/or results tab.<o:p></o:p></span></p><p class=MsoNormal style='margin:0in;margin-bottom:.0001pt'><o:p> </o:p></p><p><span style='font-family:"Comic Sans MS"'>** The Tool Icons needs some more work to make them more self explanatory (I think), I used the Tooltips quite q bit.</span> <o:p></o:p></p><p><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Yes, agreed.<o:p></o:p></span></p><p class=MsoNormal style='margin:0in;margin-bottom:.0001pt'><o:p> </o:p></p><p><span style='font-family:"Comic Sans MS"'>While these few items are not necessarily needed, I think they would contribute to a more complete user experience. Either way I think they could be added as to-do items.</span> <o:p></o:p></p><p class=MsoNormal style='margin:0in;margin-bottom:.0001pt'><o:p> </o:p></p><p><span style='font-family:"Comic Sans MS"'>Some of the Specification things mentioned:</span> <o:p></o:p></p><p class=MsoNormal style='margin:0in;margin-bottom:.0001pt'><o:p> </o:p></p><p><span style='font-family:"Comic Sans MS"'>** Related to the Capping limit on features returned. This may sound like a weird idea to begin with, but should the cap be placed on things at the layer level (in the MapBook). My reasoning is that there will likely be layers with varying degrees of feature density, and or feature complexity that might benefit from setting the limit at the layer level vs a single global number. And while the interface doesn't support this currently, selecting from more than one layer might be helped via setting limits on the features at the layer level.</span> <o:p></o:p></p><p><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Also a good point. It would not take much to implement and provide much more flexibility. We would set a system-wide default limit (which could be changed in the Mapbook configuration) to ensure that it is set and let people override at the layer level.<o:p></o:p></span></p><p class=MsoNormal style='margin:0in;margin-bottom:.0001pt'><o:p> </o:p></p><p><span style='font-family:"Comic Sans MS"'>bobb</span> <o:p></o:p></p><p class=MsoNormal style='margin:0in;margin-bottom:.0001pt'><o:p> </o:p></p><p><br><br>>>> Len Kne <<a href="mailto:lkne@houstoneng.com">lkne@houstoneng.com</a>> wrote:<o:p></o:p></p><div style='border:none;border-left:solid #050505 1.0pt;padding:0in 0in 0in 5.0pt;margin-left:11.25pt'><p style='margin-bottom:12.0pt;background:#F3F3F3'>Thanks Dean<br><br>-----Original Message-----<br>From: DEAN ANDERSON [mailto:ANDERSON.DEAN@co.polk.or.us]<br>Sent: Friday, September 24, 2010 1:42 PM<br>To: Len Kne<br>Subject: Re: [Geomoose-users] GeoMOOSE RFC - Selection Set Proposal<br><br>Len<br><br>Attached is a proposed interface and a suggestion for proposed capabilities. Did not respond to all as I am on a remote web-tool for my e-mail.<br><br>Feel free to pass it on to the group.<br><br>Dean<br><br><br>>>> Len Kne <<a href="mailto:lkne@houstoneng.com">lkne@houstoneng.com</a>> 09/24/10 10:38 AM >>><br>Hi All<br><br>Please see the attached request for comment on some new services we have been working on for GeoMOOSE. Having worked on many GeoMOOSE maps for many different uses, a common request that most projects have is the ability to control the selection of features to be included in a set to perform further geo-processing. Some work we have done over the last six months have created a great base for enhancing selection ability and this proposal offers a first attempt at making a really polished service for GeoMOOSE.<br><br>I'm looking for feedback (and participants) for this proposal. What makes sense? What additional features do you think would be important?<br><br>Thanks<br><br>Len<br><br><br>Len Kne, GIS Developer<br>Houston Engineering, Inc.<br>Phone: 763-493-4522<br>Direct: 763-493-6677<br><br><o:p></o:p></p></div></div></body></html>