Hi Guido, There is now ongoing work on Federating GeoNodes together (and with other OGC servers) such that its possible to search one GeoNode from within another and vice versa. We've discussed this on the developers list a bit. There is a very long mail I wrote on the topic a few weeks back https://groups.google.com/a/opengeo.org/group/geonode-dev/browse_thread/thread/7815b2b724ec4d94/cf33c41672230a36?lnk=gst&q=Federation#cf33c41672230a36 ...
Is it possible for you to review this and write back with your own use cases so that these could be taken into account as we work on this functionality. Thanks! Jeff On Tue, Oct 11, 2011 at 7:48 AM, <[email protected]> wrote: > Dear List, > > I am following GeoNode development via the list and have tried out > various versions > at different stages. I understand the relevance of GeoNode especially in > "spontaneous > aggregation" of geospatial resources in case of a sudden crisis event. > In such a scenario, > each GeoNode host would have a particular piece of information to share, > likely > something that changes over time through incremental changes. > > My question is about the mechanism to discover or publish the existence > of relevant > GeoNodes in that case. How would this work? Is there some active push of > the GeoNode > metadata required? Supposedly, this would be something like > GetCapabilities, with > info on data holdings, updating policy, retirement date, etc.). If so, > is there some GeoNode > repository that would keep lists of current nodes? Speed would be an > issue, so passive > discovery would probably not work. > > Any thoughts about this? > > Guido Lemoine > > >
