Apparent erratic behaviour of timeline

[giohappy]

The cursors apparently moves randomly through the timeline with this layer (ImageMosaic).

The time dimension in Geoserver is configured as the following:

[offtherailz]

Confirmed on dev with this (private) map

[offtherailz]

Checking the requests, looks that WMTS multidim replies in a strange way.

In fact the tool asks dynamically the nearest value to the current point, performing 2 requests (1 asc and 1 desc) from the same starting point), to determine previous and next times.

This is the first request , asking the domain values ascending from 2013-09-10T18:59:16.451Z

curl 'https://development.demo.geonode.org/geoserver/gwc/service/wmts?service=WMTS&version=1.0.0&request=GetDomainValues&tileMatrixSet=EPSG:4326&layer=geonode:temperature_surface&domain=time&fromValue=2013-09-10T18:59:16.449Z&sort=asc&limit=1&fromEnd=false' \
  -H 'Accept: application/json, text/plain, */*' \
  -H 'Accept-Language: en-US,en;q=0.9,it-IT;q=0.8,it;q=0.7' \
  -H 'Cache-Control: no-cache' \
  -H 'Connection: keep-alive' \
  -H 'Origin: http://localhost:8081' \
  -H 'Pragma: no-cache' \
  -H 'Referer: http://localhost:8081/' \
  -H 'Sec-Fetch-Dest: empty' \
  -H 'Sec-Fetch-Mode: cors' \
  -H 'Sec-Fetch-Site: cross-site' \
  -H 'User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/122.0.0.0 Safari/537.36' \
  -H 'sec-ch-ua: "Chromium";v="122", "Not(A:Brand";v="24", "Google Chrome";v="122"' \
  -H 'sec-ch-ua-mobile: ?0' \
  -H 'sec-ch-ua-platform: "Linux"'

The server replies with 2013-09-14 at 02

<?xml version="1.0" encoding="UTF-8"?><DomainValues xmlns="http://demo.geo-solutions.it/share/wmts-multidim/wmts_multi_dimensional.xsd" xmlns:ows="http://www.opengis.net/ows/1.1">
  <ows:Identifier>time</ows:Identifier>
  <Limit>1</Limit>
  <Sort>asc</Sort>
  <FromValue>2013-09-10T18:59:16.449Z</FromValue>
  <Domain>2013-09-14T02:00:00.000Z</Domain>
  <Size>1</Size>
</DomainValues>

But there are more values before sept 14th

I suggest to investigate on WMTS multidim bahavior first

[gannebamm]

We can confirm this issue with a GeoNode 4.2.5 based instance. The dataset is a vector timeseries and is publicly accessible here: https://atlas.thuenen.de/catalogue/uuid/1cad7ad5-3c8f-4067-8865-2f0085cf841c

These are the GeoServer settings:

It worked properly in an older release of GeoNode with the above settings.

[giohappy]

Upgrading to Geoserver 2.24.5 fixes the problem, The map reported in the description is working fine now: https://development.demo.geonode.org/catalogue/#/dataset/84

The issue was caused by a problem in Geoserver 2.24.4 itself that was fixed with the new patch version.