6

You can set up GeoWebCache to request WMS layers from any WMS server. This may be easiest with a standalone install of GWC but should be possible in the integrated version too. You need to edit the configuration file, see the manual for more detail. Alternatively you can use the GeoServer WMS datastores to cascade requests to the MapServer instance and the ...


3

Associate them with a SLD style that disables rendendering at the desired scale denominators. In GeoServer the PBF contents are driven by the default style, both in terms of scale dependencies and filters (but of course, not symbolizers). This is done so that you can get a similar output from server side rendering (PNG Output) and client side rendering (PBF +...


3

Have you already read https://www.geowebcache.org/docs/current/concepts/gridsets.html? The result of request bbox-A is not saved into cache but the tiles which intersects with bbox-A. In case of OpenLayers there is usuallly one-to-one relation because OL map is usually configured to make tiled 256x256 pixel request which suit with the tile limits of the ...


3

I have fixed this problem. Previously at the time of publishing the layer, I had selected Tile Image Formats: JPEG. Whereas Map legend supports only PNG format. So NOW, I have selected Tile Image Formats to PNG and I am getting map legend in GWC WMS.


2

Okay, we figured this out. It turns out that the tile bounding box (the bbox of the 256 x 256 tile you are rendering) needs to be in EPSG:900913 (Spherical Mercator), even if geoserver's underlying SRS is Lat/Lng. Also, Spherical Mercator uses meters as units, so we needed to convert degrees to meters using the code below, which we found on the web. ...


2

Have a look in the resource endpoint - on my machine http://localhost:8080/geoserver/rest/resource/gwc-gs.xml gives me, usually I GET it, edit and then PUT it back. <?xml version="1.0"?> <GeoServerGWCConfig> <version>1.1.0</version> <directWMSIntegrationEnabled>true</directWMSIntegrationEnabled> <WMSCEnabled>...


2

If data is being requested in EPSG:3857 you could simply set the OpenLayers WMS parameters tiled: true, tilesorigin: ol.extent.getBottomLeft(ol.proj.get('EPSG:3857').getExtent()).toString(), The standard XYZ (OpenLayers default) tilegrid for EPSG:3857 is square and tiles originate at each corner, so although OpenLayers uses top left internally the default ...


2

Here's what I found out that works for me so far: Log into your Geoserver admin panel. Go to Tile Caching > Tile Layers. Click on the layer you wish to customize the cache settings for. Scroll down to the HTTP Settings section. Check "Response Cache Headers". Enter a huge value for the cache time, like 99999999. Click on the "Tile Caching" tab at the top. ...


2

Your resolutions array is based on a different extent to the tilegrid (and also assumes 256px tiles). Assuming your server is using a standard EPSG:3857 tilegrid this should work: var tileGrid = new ol.tilegrid.TileGrid({ minZoom: 6, extent: projExtent, resolutions: resolutions.slice(1), tileSize: [512, 512] }); ...


2

GeoWebCache will receive the request for the tile, if it is in the cache then the cached image is returned. If the tile is not in the cache then GeoWebCache will pass the request onto the WMS it is caching and ask for the tile to be rendered. It will cache the returned tile (assuming no error) and pass the tile back to the requesting client.


1

It was a couple of problem: 1)deleted styles for N layers. 2) using by N layers geogrid, wich doesn't exist. Good way is find a aproach wich allows to detecte layers with broken styles.. What I did? I check it manually.. How to find layers with bad geogrid? You have to find this grid and next using something like that on your server in geoserver/data ...


1

As user30184 said in comments, MapProxy works very nice! Now I have my offline layer cache! I'm using the easy Docker deploy: https://hub.docker.com/r/kartoza/mapproxy


1

After some real world experience with this I can see that on rebooting the server or restarting Tomcat, GeoWebCache loses any current/pending tasks.


1

You should create an image mosaic layer rather than a layer group (which assumes the layers are roughly on top of each other and doesn't have any indexing). Checkout the tutorial for more details. If you intend to display the images when the user is zoomed out a long way then you will also benefit from using an image pyramid which will prevent GeoServer ...


1

If you want to do anything out of the ordinary you should use the WMTS/WMS-C/TMS end points rather than relying on the GWC WMS endpoint which makes a best guess effort to break your requests into tiles and merge them to give you a WMS response.


1

At the moment, this is not possible. You can truncate one particular parameterization, or all of them but you can not hold one filtered parameter fixed while truncating across all values of another. The PR you found was for truncating all paramaterizations within a fixed bounding box. As GWC is FOSS, you could add the feature if you have Java development ...


1

In my particular situation the problem was that I was accessing a Layer Group, instead of a layer. As soon as I switched it to request a single layer, caching started working. This page has some useful information: https://docs.geoserver.org/stable/en/user/geowebcache/troubleshooting.html


1

Ran into this same issue with EPSG:27700 and managed to get the requests to align by defining the SRS bounds as integers for both the gridset and layer. So use the default extents but round them to the nearest integer. Hope this helps someone.


1

As MilanMuňko has already pointed out, you'll have to use the standalone geowebcache to publish ArcGIS compact cache. Your ArcGIS compact cache folder must include conf.xml and conf.cdi, and an _allLayers folder. To add the ArcGIS compact cache layer, edit geowebcache.xml (you can locate this file by visiting http://localhost:8080/geowebcache then look at ...


1

I know this is an old thread, but probably it can help others who reach here. One more reason for GWC dying prematurely (or not showing any status at all upon clicking refresh) is when you have data level security or user roles or service level security. Disabling them worked like a charm for us and we enabled them again after suffiecient caching. We are ...


1

If your geoserver url is http://localhost:8080/geoserver or just replace localhost with your domain and then go to the url: http://localhost:8080/geoserver/gwc. You are now at GeoWebCache home page and scroll down the page. Below the page you will see something like this Storage Locations Config file: /tmp/tomcat7-tomcat7-tmp/geowebcache/geowebcache....


1

Computing labels with collision resolution (moving labels out of the way or removing lower priority ones so they don't overlap) requires knowing about every label that might collide with the label you are drawing, every label that might collide with them, and so on. So, in general, you either need to compute all the labels at once by looking at every ...


Only top voted, non community-wiki answers of a minimum length are eligible