<html>
<head>
<style type="text/css">
<!--
body { margin-right: 4px; font-variant: normal; margin-left: 4px; margin-bottom: 1px; line-height: normal; margin-top: 4px }
p { margin-bottom: 0; margin-top: 0 }
-->
</style>
</head>
<body style="margin-right: 4px; margin-left: 4px; margin-bottom: 1px; margin-top: 4px">
<p style="margin-bottom: 0; margin-top: 0">
<font size="3" face="Comic Sans MS">Len,</font> </p>
<br>
<p style="margin-bottom: 0; margin-top: 0">
<font size="3" face="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.</font> </p>
<br>
<p style="margin-bottom: 0; margin-top: 0">
<font size="3" face="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.</font> </p>
<br>
<p style="margin-bottom: 0; margin-top: 0">
<font size="3" face="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)</font> </p>
<br>
<p style="margin-bottom: 0; margin-top: 0">
<font size="3" face="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.</font> </p>
<br>
<p style="margin-bottom: 0; margin-top: 0">
<font size="3" face="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.</font> </p>
<br>
<p style="margin-bottom: 0; margin-top: 0">
<font size="3" face="Comic Sans MS">Some of the Specification things mentioned:</font> </p>
<br>
<p style="margin-bottom: 0; margin-top: 0">
<font size="3" face="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.</font> </p>
<br>
<p style="margin-bottom: 0; margin-top: 0">
<font size="3" face="Comic Sans MS">bobb</font> </p>
<br>
<p style="margin-bottom: 0; margin-top: 0">
<br>
<br>
>>> Len Kne <lkne@houstoneng.com> wrote:<br> </p>
<div style="margin-right: 0; border-left: solid 1px #050505; background-color: #f3f3f3; margin-left: 15px; margin-bottom: 0; padding-left: 7px; margin-top: 0">
<p style="margin-bottom: 0; margin-top: 0">
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 <lkne@houstoneng.com> 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><br>
</p>
</div>
</body>
</html>