[Geoserver-users] Unexpected GeoWebCache behaviour

Hi,

I’m a bit confused and have a couple of questions to ask about GWC. My setup is geoserver 2.7.0 and I’m using the GWC bundled with that but using gwc endpoint rather than having the wms service auto-integrated. I’m doing this as I do not want any request been made direct to the WMS, everything must go through the cache so only my gwc endpoint is exposed on the proxy server.

The layers (actually layer groups should that make a difference) are setup in GWC using 3 gridsets:

900913 256x256 png (the built in one)

3875 512x512 png

27700 256x256 png

The first oddity I have found in the past is that after running for a while gwc seems to forget the fact that 900913 == 3875 for non-built in gridsets, hence the 512x512 cache we use for hi-res displays uses an ESPG of 3875, I used to use 900913 but after a few days of running it would start moaning about the client using 3875/512x512 as the srs saying it is not suitable. Worked fine ever since I switched it over to 3875. I can live with this so not really an issue for me to worry about.

My next oddity is the one that has me worried and seems concerned with default values for filters.

To support hi-res and normal res images on the first two gridsets above I have filter using FORMAT_OPTIONS as defined below

FORMAT_OPTIONS

dpi:90

dpi:90

dpi:180

Our main clients explicitly set the format options as required, however another client does not, I had expected that by providing a default that would be taken care off. We do get images from GWC which I guess is the important thing, however GWC appears to maintaining a separate image cache for requests that do not contain a FORMAT_OPTIONS parameter. Is this what people would expect, I assumed that a default value would contribute to which set of cached images were used.

My seeding process is done using dpi:90 and dpi:180, this suggests I should also be doing one without any options. This would seem a shame as my disk cache now uses half as much space with one third a duplicate.

Am I missing something obvious in the config or is this expected behaviour?

Kind Regards, Vic

image001.png

image002.png

image003.png

image004.png

image005.png

image006.png

image007.png

···

Cubic Transportation Systems

Victor Kirk

Senior Software Engineer

Cubic Transportation Systems (ITMS) Ltd

+44 1642 636894

cubic.com/transportation

NextCity

RSS

Facebook

Twitter

LinkedIn

YouTube



Joint Winner, Operational and Technical Excellence, Contactless Bankcard Payment



UITP (International Association of Public Transport) Awards 2015



Joint Winner, Best New Innovative Practice-Partnership Deployment, Ventra



ITS-America Awards 2015



http://www.cubic.com/Transportation/About-CTS/Awards

Hi, I've just noticed that even requests that have the default value of dpi=90 are causing new tiles to be generated, the tiles I've seeded with dpi=90 simply are not being touched.

After my seed I have a particular zoom level has (number disk size) tiles

  386848 EPSG_900913_18_8e0cae5c6a00f859dc26a06986db3e01e3efbcef

But as soon as I run a quick test that has the options

  HEIGHT=256&WIDTH=256&&FORMAT_OPTIONS=dpi%3A90& SRS=EPSG%3A3857

I get a new directory created

  7052 EPSG_900913_18
  386848 EPSG_900913_18_8e0cae5c6a00f859dc26a06986db3e01e3efbcef

Am I missing something obvious? This seems a discrepancy between what GWC does when seeding and when it does a cache lookup and creates an image on demand.

Thanks, Vic

From: Kirk, Victor [mailto:VICTOR.KIRK@…7093…]
Sent: 18 January 2016 14:16
To: GeoServer Mailing List List
Subject: [Geoserver-users] Unexpected GeoWebCache behaviour

Hi,

I’m a bit confused and have a couple of questions to ask about GWC. My setup is geoserver 2.7.0 and I’m using the GWC bundled with that but using gwc endpoint rather than having the wms service auto-integrated. I’m doing this as I do not want any request been made direct to the WMS, everything must go through the cache so only my gwc endpoint is exposed on the proxy server.

The layers (actually layer groups should that make a difference) are setup in GWC using 3 gridsets:

900913 256x256 png (the built in one)
3875 512x512 png
27700 256x256 png

The first oddity I have found in the past is that after running for a while gwc seems to forget the fact that 900913 == 3875 for non-built in gridsets, hence the 512x512 cache we use for hi-res displays uses an ESPG of 3875, I used to use 900913 but after a few days of running it would start moaning about the client using 3875/512x512 as the srs saying it is not suitable. Worked fine ever since I switched it over to 3875. I can live with this so not really an issue for me to worry about.

My next oddity is the one that has me worried and seems concerned with default values for filters.

To support hi-res and normal res images on the first two gridsets above I have filter using FORMAT_OPTIONS as defined below

<parameterFilters>
<stringParameterFilter>
<key>FORMAT_OPTIONS</key>
<defaultValue>dpi:90</defaultValue>
<values>
<string>dpi:90</string>
<string>dpi:180</string>
</values>
</stringParameterFilter>
</parameterFilters>

Our main clients explicitly set the format options as required, however another client does not, I had expected that by providing a default that would be taken care off. We do get images from GWC which I guess is the important thing, however GWC appears to maintaining a separate image cache for requests that do not contain a FORMAT_OPTIONS parameter. Is this what people would expect, I assumed that a default value would contribute to which set of cached images were used.

My seeding process is done using dpi:90 and dpi:180, this suggests I should also be doing one without any options. This would seem a shame as my disk cache now uses half as much space with one third a duplicate.

Am I missing something obvious in the config or is this expected behaviour?

Kind Regards, Vic

Victor Kirk
Senior Software Engineer
Cubic Transportation Systems (ITMS) Ltd
+44 1642 636894
cubic.com/transportation

Joint Winner, Operational and Technical Excellence, Contactless Bankcard Payment
UITP (International Association of Public Transport) Awards 2015
Joint Winner, Best New Innovative Practice-Partnership Deployment, Ventra
ITS-America Awards 2015
http://www.cubic.com/Transportation/About-CTS/Awards

________________________________________
This document is intended for, and should only be read by, those persons to whom it is addressed. Its contents are confidential and if you have received this message in error, please delete it. Any form of reproduction, dissemination, copying, disclosure, modification, distribution and / or publication of this message without our prior written consent is strictly prohibited.
Any views expressed in this message are those of the individual sender, and do not necessarily represent the position of Cubic Transportation Systems (ITMS) Limited (‘CTS’). Furthermore CTS does not authorise or use e-mail for official contractual correspondence. Nothing received in e-mail has any contractual validity.
CTSL and each legal entity in Cubic Corporation reserve the right to monitor all e-mail communications through its networks.
Registered Office:
Cubic Transportation Systems Ltd
AFC House
Honeycrock Lane
Salfords
Surrey
RH1 5LA
United Kingdom
Registered in England under number 8498086
________________________________________