Skip to content

Fix #13163 Timeline init error when one end of the time domain is empty - #13164

Open
offtherailz wants to merge 2 commits into
geosolutions-it:masterfrom
offtherailz:fix_13163_timeline_init
Open

offtherailz wants to merge 2 commits into
geosolutions-it:masterfrom
offtherailz:fix_13163_timeline_init

Conversation

@offtherailz

@offtherailz offtherailz commented Nov 17, 2026 •

Copy link
Copy Markdown
Member

Description

The Timeline asks for the first and the last value of the time domain with two requests. When one of them fails or returns no value, the initialization of the range throws an error and stops, so the Timeline is not positioned on the data of the layer.

The empty values are now removed before they are processed, so the range is initialized with the available value.

The playback check that detects interval data (setIsIntervalData) failed on the same empty value: it now ignores it too.

Please check if the PR fulfills these requirements

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

  • Bugfix

Issue

What is the current behavior?
Closes #13163

What is the new behavior?
The Timeline is initialized also when only one end of the time domain is available.

Breaking change

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

  • No

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Timeline: error on init when the nearest time values contain an empty value

2 participants