Open lklic opened 3 years ago
I would prefer to use existing semantic-timeline
in a way as I described here - https://github.com/researchspace/researchspace/issues/140#issuecomment-726368782
The good thing about it is that we can use it for both, visualization and boundary setting.
We can cover quite fancy use-cases, like moving the map bounding box and show on the timeline events on the timeline that happened somewhere in the selected region. And at the same time we can zoom-in/out in the timeline to make query even more specific, etc.
We came out with a solution like the following one: .
The component would be similar to a time slider starting from 1500 to 2020. It will have ticks defining years (a tick every 25 or 100, TBD) and the sliding part will decide the year to display.
Let's imagine we slide to 1600, we are going to show all the buildings that have been already created and not yet destroyed in that time.
So, more than a timeline, our idea is to treat it as a time slider. @lklic @aindlq, toughts?
Personally, I would prefer to use timeline component instead of simple slider, to make it more generically applicable. On the timeline we can show corresponding events/periods and have more context for filtering than just point in time.
This is now part of semantic-map-controls, awaiting PR
To reach the expected level of usability, the Structured Search Component should be integrated with the Semantic Map component and with a “Semantic Timeline Filter”. The component should be used as an input control, and not be used to visualize elements within. It must be customizable in style and values (such as the time range and pitch) The component must be able to filter for a specific point in time (this may be a specific year, date, or other). The component must be compatible with the Semantic Search Component.