GNIP 13 - Collections

6 views
Skip to first unread message

David Winslow

unread,
Jan 10, 2012, 12:16:48 PM1/10/12
to geono...@opengeo.org
See the proposal on the wiki at https://github.com/GeoNode/geonode/wiki/GNIP-13---Collections

As discussed this sounds like a suitable feature for inclusion in GeoNode 1.2.  It might be interesting to have collections correspond to GeoServer's Virtual Services (http://docs.geoserver.org/latest/en/user/services/virtual-services.html) but then we would need to enforce that every layer is part of one and only one collection, which I think would be too strict for many use cases that collections address.

--
David Winslow

Jeffrey Johnson

unread,
Jan 10, 2012, 12:29:20 PM1/10/12
to David Winslow, geono...@opengeo.org

Im -1 on _enforcing_ this kind of correspondence, but it does make
sense to provide an 'option' to do things this way. David can you
elaborate on what kind of benefit could be expected by optionally
tying Collections to Virtual Services?

Jeff

David Winslow

unread,
Jan 10, 2012, 4:03:33 PM1/10/12
to Jeffrey Johnson, geono...@opengeo.org
GeoServer's Virtual Services allow you to have separate WMS, WFS, etc. services for subsets of the catalog.  This feature is currently tied to workspaces, which is why a layer can only be in one Virtual Service (and in fact must be in one virtual service.)  I think the integration between layer collections and virtual services is pretty obvious - make a workspace for each collection and assign the workspace for each layer according to its collection.  But as I said, without changes to GeoServer this comes along with probably unacceptable technical limitations.

--
David Winslow
Reply all
Reply to author
Forward
0 new messages