[Geomoose-users] utilize wfs for select service?

[Dan Little]

Why change the highlight layer definition, which breaks the built-in services you would still be trying to use (presumably) instead of defining a new Vector layer (as WFS if you'd like) and then have your service return Javascript to manipulate it?




>________________________________
> From: Andrew Sheppard <asheppard at houstoneng.com>
>To: GeoMOOSE Users List <geomoose-users at lists.osgeo.org> 
>Sent: Wednesday, June 27, 2012 5:44 PM
>Subject: [Geomoose-users] utilize wfs for select service?
> 
>
> 
>Hi all,
>I’m currently working on porting the custom select tool to GeoMOOSE 2.6.  The customizations enable direct interaction by using vector features for the selection result (instead of rendering a raster image).  This makes it possible to e.g. highlight an individual feature by clicking an icon in the result list.  In the old custom code the service sent back commands to create the vectors in the <script> result of the service.  I could replicate this but would like to propose utilizing a WFS layer instead.  This could be done in at least two ways:
> 
>1.)    We could change the highlight layer in the mapbook to be a read-only WFS layer.  This would also mean altering the highlight.map template in htdocs/php/select/ to enable WFS requests.  select.php would work more or less as it does now (but some of the rendering commands it sent back would be different).
> 
>2.)    We could try to utilize the OpenLayers GetFeature control which can be used to directly transform interaction with a WMS layer into WFS requests (see
http://openlayers.org/dev/examples/getfeature-wfs.html).  This would require the user to enable WFS in the mapfile for each layer they wanted the select service for.  Since WFS supports spatial filters, select.php would not be used (but we would need to a different way to render the HTML).
> 
>Either of these options would to need be configurable so that the current raster-based approach would still be available (especially when there is a potential for large selection result sets).
> 
>  S. Andrew Sheppard
>GIS/Web Developer 
>O763.493.4522 | D 763.493.6676  | M 763.227.8106 
>     6901 E Fish Lake Rd. , Suite 140 • Maple Grove, MN • 55369     
>www.houstoneng.com             
>This entire message (including all forwards and replies) and any attachments are for the sole use of the intended recipient(s) and may contain proprietary, confidential, trade secret, work-product, attorney-client or privileged information. Any unauthorized review, use, disclosure or distribution is prohibited and may be a violation of law. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message.
> 
> 
>_______________________________________________
>Geomoose-users mailing list
>Geomoose-users at lists.osgeo.org
>http://lists.osgeo.org/mailman/listinfo/geomoose-users
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/geomoose-users/attachments/20120628/97dfbd05/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.jpg
Type: image/jpeg
Size: 1059 bytes
Desc: image001.jpg
URL: <http://lists.osgeo.org/pipermail/geomoose-users/attachments/20120628/97dfbd05/attachment-0001.jpg>