New answers tagged geowebcache
An easy way of finding GeoWebCache's tile directory is having a look at the bottom of the GeoWebCache homepage:
The same max render time is applied to any WMS request. When doing meta-tiling the internal GeoWebCache makes a single WMS request, which is subject to the max render time. So, if you want to render larger meta-tiles, you will have to increase the max render time accordingly.
The easiest way to combine the layers and still cache them using GeoWebCache is to use a LayerGroup which acts exactly like a layer in OpenLayers but is built up from the 3 layers in GeoServer. This is only more efficient if your client always wants to see all three layers.
Do you want it dynamic, as in, you can change which of the three to view client-side? IF so, you can form up a request that combines 1,2 or 3 layers into a single get request, and OpenLayers can handle this, I reckon. But, do you need to? Try it the simple way first, and then if you are experiencing performance issues, look into combining it. To answer ...
Yes. Check out MapProxy, which is capable of combining multiple tile sources, among lots of other things. Really cool app. I can't speak authoritatively on efficiency with this approach, but your app is only making one call instead of three. That seems more efficient, right? You might even find that it's preferable to handle caching with MapProxy instead. ...
Ciao, a few things: It looks to me you are mostly rendering vector data, hence JAI does not helpat all If you are mostly serving vector data with complex styling rules, I am hoping you are using a DBMS rather than shapefiles especially for OSM. If not at global scale GeoServer will have to load all the shapefile into memory and then filters as we only ...
Top 50 recent answers are included