On 02/08/2012 02:48 AM, Andrea Aime wrote: > On Tue, Feb 7, 2012 at 10:28 PM, John Armstrong<[email protected]> wrote: >> Hi, everybody. >> >> I'm trying to use GeoServer in an instance where we have thousands of >> layers to register, with tens to hundreds of new layers each day. It >> seemed a perfect situation for dbconfig, but I'm having a lot of >> difficulty getting that module to work. >> >> This can't be all that unusual a use case, though; does anyone here have >> any suggestions for strategies to make GeoServer scale better so that >> keeping the catalog around in memory doesn't become too onerous, and >> loading from disk if the webapp has to be reset doesn't take forever? > The most common cause of "tons of layers", that is, dealing with > time/elevation > based data, has been taken care of on trunk with the true time and elevation > support, which means those thousands of layers magically turned back > to being one.
I wasn't aware that there was any way of registering many time-related layers as a single layer within GeoServer; do you have a quick pointer to some documentation of how to get this working? > Changing this is not trivial, but it's orthogonal to having the configuration > in a database and it's likely to be easier to solve that get a working db > config layer Yeah, I'm looking for alternate solutions to the underlying problem; considering many layers over time as a single layer may actually be just the thing. Thanks for letting me know about this feature. ------------------------------------------------------------------------------ Keep Your Developer Skills Current with LearnDevNow! The most comprehensive online learning library for Microsoft developers is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, Metro Style Apps, more. Free future releases when you subscribe now! http://p.sf.net/sfu/learndevnow-d2d _______________________________________________ Geoserver-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-users
