Expand alerts CSV export with sequence and camera context

[MateoLostanlen]

Follow-up to #577.

The current /alerts/export endpoint only exposes 5 columns (id, lat, lon, started_at, last_seen_at), which is too thin for studying past alerts.

We want the export to include every field relevant to alert analysis.

Proposed columns

Core

• alert_id
• started_at_date (UTC)
• started_at_time (UTC)
• last_seen_at (ISO)
• duration_seconds
• lat, lon (empty when null)
• organization_id

Sequences (multi-value cells, |-separated, ordered by sequence.started_at ASC so positions align across columns)

• sequence_ids
• sequence_count
• sequence_labels (is_wildfire: wildfire / other / unknown)
• sequence_azimuths
• pose_ids

Cameras (same ordering as sequences)

• camera_ids
• camera_names
• camera_count

[MateoLostanlen]

Hi @Acruve15 , thanks for the first PR here is follow up if you are interested 😄

[Acruve15]

hi @MateoLostanlen, is the current endpoint integrated to the platform? If yes, do you have the link to the PR? merci 😊

[fe51]

About to be integrated, the PR is in progress :)

pyronear/new-pyro-platform#220

[Acruve15]

noice :) question, what does it mean when an alert has no long/lat?

[MateoLostanlen]

lat, lon is computed by triangulation so if there is an alert with only one seq you do not have lat,lon