Time filters
A time filter restricts the visible network to the nodes and links whose dates fall at or before a chosen instant, or inside a chosen window; the histogram above the filter controls it.
- The histogram shows how dates are distributed over time. Drag its upper handle to reveal values as of that instant. Drag the lower handle inward to select a date window; return it to the beginning to remove the start bound.
- Click the date readout below the histogram to edit exact UTC dates, then press Enter to apply each date. Both boundaries are inclusive.
- Use previous/next to step through distinct timestamps, or Play to advance the end date. For large timelines, 1× covers the selected date range in about 20 seconds, 5× in about 4 seconds, and 20× in about one second. Playback batches dates when needed; previous/next still visits every date. A selected start date stays fixed. Gaps without events do not slow playback.
- The same button becomes Pause during playback. Reset returns to the earliest date, and Loop restarts from the start date at the end. Play at the end also replays from the start. Playback pauses when the tab is hidden, the filter is disabled or removed, the data changes, or a saved view is restored.
Dates must be YYYY-MM-DD (UTC midnight) or an RFC3339 timestamp with an explicit
timezone, such as 2026-01-05T12:30:00Z or 2026-01-05T13:30:00+01:00. Seconds
and milliseconds are preserved in the displayed cursor when needed. Numeric
epochs, locale dates, and timestamps without a timezone are not inferred.
Date-only end values mean midnight; to include events later in a day, use the next date or an explicit time.
Time filters hide excluded nodes and edges by default; the filter mode control can switch to fading them as context.
Every nonempty value in a field must be a valid date for automatic detection. Empty values are reported and excluded by default. Show undated nodes/edges includes them as context. Undated nodes need a connection to dated nodes in the window; disconnected timeless components stay excluded. If an existing temporal field gains an invalid value, its filter becomes unavailable until the value is corrected; the graph is left unfiltered by that row. The match count describes this field’s date range, before other filters are combined.
Node date filters also affect incident edges. Edge date filters exclude nodes
without a connection in the window, so future nodes do not appear as orphans.
Shared URLs, .gph files, and captured Story steps preserve both date bounds
and the undated-value choice. Playback speed and looping are local controls and
do not autoplay when opening a saved view. Hide date filters also narrow the
topology used for community detection and statistics; Fade date filters
leave it intact.