GeoServer Time Dimension Queries in 2.25.0

Question

My project has a large number of time enabled WMS layers. We are looking at moving from GeoServer 2.24.2 to 2.25.0 and all of our existing time filters are failing.

Our queries look something like: <GEOSERVER_URL>&TIME=2022-01-01/2022-01-02

These queries work in 2.24.2 but result in the following error when running against a 2.25.0 server:

code="InvalidDimensionValue" locator="time" Could not find a match for 'time' value: '2022-01-01/2022-01-02'

I've looked through the release notes and I don't see any mentions about this capability changing in 2.25. Is this a regression?

Answer 1

It looks like you are running a foul of the changes made recently to conform to specification, looking at the manual:

Dimensions settings

The WMS specification mandates the throwing of an InvalidDimensionValue exception when a dimension value is not valid, and the nearest match is not enabled. This is the default behavior of GeoServer starting with version 2.25, while older versions simply ignored the invalid value and returned empty responses.

The behavior can be controlled in the Dimension Settings section, with a choice of three possible values:

• Use GS version default. Will return an exception if version is greater or equal than 2.25, otherwise will ignore the invalid value.

• Return InvalidDimensionValue. Will return an exception on invalid value, unless nearest neighbor match has been enabled for the layer (standard compliant behavior).

• Ignore invalid value. Will ignore invalid values and return an empty map/info (legacy behavior).

So you can change the setting to Ignore or turn nearest neighbour match on depending on which is your preferred behaviour.