Annotation Improvements

In Release 2, when multiple annotations overlap on the same time range, they are applied in simple creation-time order. While this works for many use cases, it lacks predictability when annotations grow in number and complexity.

Release 3 will introduce several improvements to make annotation behavior more deterministic, easier to manage, and idempotent — meaning the same set of annotations will always produce exactly the same result for any given timeframe, regardless of the order in which they were created or attached.

Planned enhancements include:

Enhancement	Description
Automatic prioritization by specificity	Narrower (more specific) time intervals take precedence over broader ones.
Priority tiers	Automatic grouping into tiers (e.g. Auto-generated, User corrections, Admin/QA overrides) with sensible defaults.
Optional explicit ordering	Within the same tier, users can assign a custom order value when fine control is needed.
Real-time preview	Users can toggle annotations or entire tiers on and off and immediately see the impact in charts and queries.

Location at Query Time

Note

Release 3 applies the same query-time configuration model beyond data cleaning. When a station moves, its geo-spatial context updates through metadata, not by writing coordinates into raw datapoints.

A Site is the persistent location: latitude, longitude, elevation, and related attributes. A Station is the deployed equipment; it can be moved or redeployed to a different site over time. Each Deployment records which site a station occupied during an interval.

When data is queried, location is applied through configuration—the Site coordinates for each time period reflect where the station was deployed during that interval.

---
config:
  flowchart:
    nodeSpacing: 40
    rankSpacing: 60
    padding: 16
---
flowchart TB
    ST["Station<br/>datalogger & sensors"]

    D1["Deployment 1<br/>2020 – 2023"]
    D2["Deployment 2<br/>2023 – present"]

    SA["Site A<br/>lat · lon · elev"]
    SB["Site B<br/>lat · lon · elev"]

    ST --> D1
    ST --> D2
    D1 --> SA
    D2 --> SB
    D1 -.->|"moved"| D2