Fix #9208 Timeline map sync does not update for time ranges visualization

[allyoucanmap]

Description

This PR improved the get time items selector to use the updated range data if provided

Please check if the PR fulfills these requirements

• The commit message follows our guidelines: https://github.com/geosolutions-it/MapStore2/blob/master/CONTRIBUTING.md
• Tests for the changes have been added (for bug fixes / features)
• Docs have been added / updated (for bug fixes / features)

What kind of change does this PR introduce? (check one with "x", remove the others)

• Bugfix

Issue

What is the current behavior?

#9208

What is the new behavior?

Breaking change

Does this PR introduce a breaking change? (check one with "x", remove the other)

• No

Other useful information

@tdipisa
It seems there is a problem with the spatial filter of domains, here an example:

The following example shows a DescribeDomains request where we expect to get information of a single feature but instead we get two:

request: https://development.demo.geonode.org/geoserver/gwc/service/wmts?service=WMTS&REQUEST=DescribeDomains&version=1.0.0&layer=geonode:test_time&tileMatrixSet=EPSG:4326&bbox=829991.4716345865,5755211.389189923,1039581.8031925397,5899065.876422625,EPSG:3857&expandLimit=20&time=2022-06-01T00:00:00.000Z/2024-01-09T11:07:53.218Z

response:

<Domains xmlns="http://demo.geo-solutions.it/share/wmts-multidim/wmts_multi_dimensional.xsd" xmlns:ows="http://www.opengis.net/ows/1.1" version="1.2">
<SpaceDomain>
<BoundingBox CRS="EPSG:4326" minx="2.021484375000004" miny="40.871987756697415" maxx="30.849609375000014" maxy="50.645977340713586"/>
</SpaceDomain>
<DimensionDomain>
<ows:Identifier>time</ows:Identifier>
<Domain>2023-01-01T00:00:00.000Z/2023-06-01T00:00:00.000Z,2023-01-01T00:00:00.000Z/2023-12-31T00:00:00.000Z</Domain>
<Size>2</Size>
</DimensionDomain>
</Domains>

Visual representation of bbox param (red) and returned space domain (orange)

Note: We are also applying the bbox param to GetDomainValues and GetHistogram so they could have the same problem

[offtherailz]

I should

• move expandLimitSelector default internally if possible
• Check and debug the single point use case to indentify why it works

[allyoucanmap]

@offtherailz below test done with master without applying fix from this PR:

The layer in this map does not have data.values and the domain contains -- for this reason it always pass to the else if

in this case the rangeData is populated from this app initialization because of the updateRangeDataOnRangeChange epic that update the value for all domain that returns true for isTimeDomainInterval

check-getTimeItems.mp4

---

The check || data && data.domain && !isTimeDomainInterval(data.domain) is still used by domain that are not interval because they have a rangeData equal to undefined at initialization

[tdipisa]

@offtherailz you forgot to merge this :)

@ElenaGallo please test in DEV and let us know if we can backport.

Let's spend some more time on what you have reported for the GS issue you have experienced, maybe checking it with someone from the GS team.

[aaime]

The issue with the bbox capturing two features is due to the WMTS multidimensional using a "BBOX" filter against the database, which in turn is configured for loose bbox filtering:

With loose bbox, queries are very fast, but not precise, as a "bbox vs bbox" filter is applied: the second line does not intersects the red search area, but the bbox of the line does, that's why it's returned.

How to fix it:

• Disable loose bbox at the store level. That will slow down all GetMap/GetFeature requests (I don't recall how much) to make all the filters more precise.
• Change the WMTS multidimensional code to use a "intersect polygon" filter instead, which is always precise, regardless of that setting.

[tdipisa]

Thank you so much for reporting the above @aaime

[ElenaGallo]

Test passed, @allyoucanmap please backport to the stable branch. Thanks