Have a look on the Pregeneralized Features extensions http://docs.geoserver.org/stable/en/user/data/featurepregen.html http://docs.geotools.org/latest/userguide/library/data/pregeneralized.html
A tutorial is here http://osgeo-org.1803224.n2.nabble.com/attachment/6137141/0/pregen_tutorial.html Cheers Zitat von Andrea Aime <andrea.a...@geo-solutions.it>: > 2011/6/14 Andrés Maneiro <amane...@icarto.es> > >> Hello people, >> >> these days I'm organizing several layers of data I have stored in >> postgis. I have some doubts related to how to better organize the data >> for improving my geoportal performance (geoserver responses + minimizing >> the data sent by the network): >> >> -- Option 1 >> >> * having in the same postgis table alphanumeric information + geometry >> to scale A + geometry at scale B. >> >> * select by means of SLD which geometry to show at different scale. See: >> >> http://www.mail-archive.com/geoserver-devel@lists.sourceforge.net/msg06005.html >> >> * the petitions of my geoportal will go for this layer. >> >> >> --- Option #2 >> >> * having 1 table for alphanumeric plus geometry at A scale + 1 table >> for alphanumeric plus geometry at B scale. >> >> * using SLD, manage when to show a layer assigning two different SLD >> styles. See: >> >> http://ian01.geog.psu.edu/geoserver_docs/data/naturalearth/naturalearth_physical.html >> >> * make a layergroup containing both layers and make my geoportal to ask >> for the layergroup. >> >> >> Any help about how could one approach or the other to affect to >> performance will be greatly appreciated. >> >> > I never tried by would go for Option #1 for pure data management questions > (mind, you need to spatial index both columns). > However I doubt you will get a very significant speedup in either cases, > instead of having less coordinates I would suggest you to try > out having less fetaures: > - find an attribute that can be used to tell apart important features > from the less important ones, use it to show only the important > ones at low zoom levels > - find alternate layers that provide similar information, for example, > instead of display the roads of a city display the polygon of the > city area and switch to roads when you're zoomed in enough. > > Generally speaking, try to have less than 1000-2000 geometries in your > map, going above you're just adding noise in the map and slowing down > rendering > > Cheers > Andrea > > > > -- > ------------------------------------------------------- > Ing. Andrea Aime > GeoSolutions S.A.S. > Tech lead > > Via Poggio alle Viti 1187 > 55054 Massarosa (LU) > Italy > > phone: +39 0584 962313 > fax: +39 0584 962313 > > http://www.geo-solutions.it > http://geo-solutions.blogspot.com/ > http://www.youtube.com/user/GeoSolutionsIT > http://www.linkedin.com/in/andreaaime > http://twitter.com/geowolf > > ------------------------------------------------------- > ---------------------------------------------------------------- This message was sent using IMP, the Internet Messaging Program. ------------------------------------------------------------------------------ EditLive Enterprise is the world's most technically advanced content authoring tool. Experience the power of Track Changes, Inline Image Editing and ensure content is compliant with Accessibility Checking. http://p.sf.net/sfu/ephox-dev2dev _______________________________________________ Geoserver-users mailing list Geoserver-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-users
