[Geomoose-users] RFC 5: Modularize Core GeoMOOSE Services

Andrew Sheppard asheppard at houstoneng.com
Fri Dec 21 08:47:42 PST 2012


My plan is to re-use the existing temporary WMS-enabled highlight layer created by select.php.  As I understand it, this currently works by placing all of the selected features into a temporary SQLite/SpatiaLite database on the server, which is used both for rendering the highlight WMS layer and for extending the selection set with a buffer.  The main server-side change I am suggesting (other than the PHP refactoring) is to enable WFS support in the file select/highlight.map; users would not need to enable WFS in their source layers.   The mapbook would need to be updated to either to replace or supplement the current WMS highlight layer definition with a WFS one.

S. Andrew Sheppard
GIS/Web Developer
Houston Engineering, Inc.

-----Original Message-----
From: Eli Adam [mailto:eadam at co.lincoln.or.us] 
Sent: Thursday, December 20, 2012 1:10 PM
To: Andrew Sheppard
Cc: GeoMOOSE Users List
Subject: Re: [Geomoose-users] RFC 5: Modularize Core GeoMOOSE Services

On Tue, Dec 18, 2012 at 8:05 AM, Andrew Sheppard <asheppard at houstoneng.com> wrote:
> All,
> I have compiled the discussion to date on unifying select.php, query.php and identify.php into a draft RFC:
>
> http://www.geomoose.org/trunk/rfc/rfc-5.html
>
> Please provide any suggestions for improvement.

I have some questions.  Is the WMS backed by SQLite a temporary file and configuration?

How will the extending of existing wms layers to wfs be done?  Is it that users have to enable wfs for all layers that will interact with select or query?  Would this be wfs and not a temporary  wfs(-t) backed by SQLite?  I'm thinking about instances where users change the selection by removing some features and then switching between table and side view.  If the selection set is managed on the client side it may not matter, but if it is from the server each time it would somehow need to know about the change.

This is a general question that perhaps should have a separate thread, have we thought of changing the SQLite dependency to SpatiaLite?  How would that impact the various things that we want to do in GeoMoose?

Best Regards, Eli


>
> Thanks,
>
> S. Andrew Sheppard
> GIS/Web Developer
> Houston Engineering, Inc.
> _______________________________________________
> Geomoose-users mailing list
> Geomoose-users at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/geomoose-users


More information about the Geomoose-users mailing list