Timeline map sync does not update for time ranges visualization

[allyoucanmap]

Description

The timeline chart does not update based on viewport even if the map sync button is selected.

time-map-sync.mp4

How to reproduce

• open this map (login as admin if needed)
• expand the timeline
• zoom on a feature to exclude the other
• click on map sync

Expected Result

The timeline should update the visualization of time intervals based on the viewport of the map

Current Result

The timeline does not update the visualization of time intervals based on the viewport of the map

• Not browser related

Browser info

(use this site: https://www.whatsmybrowser.org/ for non expert users)

Browser Affected	Version
Internet Explorer
Edge
Chrome
Firefox
Safari

Other useful information

The sync issue it seems related to inconsistent state of the time domain property. The timeline updates the new range data inside the updateRangeDataOnRangeChange epic dispatching rangeDataLoaded action and then read the new histograms and rang line items using the itemsSelector. The itemsSelector is using different parts of the state to create the correct items used by the timeline for the visualization:

• layer reducer static domain properties
• dimension reducer domain properties
• timeline reducer rangeData properties

After some check it seems that even if the rangeData is correctly updated the dimension reducers is still containing information related to domain that are taking precedence over the new rangeData.
We will need to review the update workflow of range data to properly fix this issue.

• Layer for testing

[offtherailz]

I noticed that with this map works.
https://dev-mapstore.geosolutionsgroup.com/mapstore/#/viewer/42064
What's the difference ?

[ale-cristofori]

I noticed that with this map works. https://dev-mapstore.geosolutionsgroup.com/mapstore/#/viewer/42064 What's the difference ?

@offtherailz, I suspect it is because the time dimension on the layers included in the map you link is unique rather than a range (start/end date).