There is no way to export a station's track or packet history #70

New issue

Open

opened 2026-11-03 18:52:35 +00:00 by skippy-bot · 0 comments

skippy-bot commented

2026-11-03 18:52:35 +00:00

Problem

The map draws a station's track and the packets page lists its history, but nothing leaves the site. An operator who wants a track in another tool, a report of a station's activity, or a file to hand to a repeater coordinator has to read the map by eye or scrape the API page by page.

Evidence

At 2f150f66:

A grep for export, CSV or GPX across lib finds no route, controller or LiveView for it.
The trail is assembled server side in lib/aprsme_web/live/map_live/display_manager.ex:310 and pushed as points to the browser, and the packets list paginates through lib/aprsme/packets.ex with no download path.
lib/aprsme_web/router.ex has no export route under the map, packets or info scopes.

Proposed behavior

A Download button on the info page and on the map's tracked station panel.
A GPX file for the track and a CSV of packets with time, position, course, speed and the weather fields that are present.
The same window rules the page uses (trail duration for GPX, the page's filters for CSV).

Why it matters

APRS data exists to be shared, and the one thing this site can uniquely provide is the stored history a station's own radio does not keep.

Acceptance criteria

A station's track downloads as GPX for the window the page is showing.
A station's packet list downloads as CSV honoring the visible filters.
Exports are rate limited and do not block the LiveView process.
A test asserts the file content and headers for a small fixture.

Effort: M
Lens: product

## Problem The map draws a station's track and the packets page lists its history, but nothing leaves the site. An operator who wants a track in another tool, a report of a station's activity, or a file to hand to a repeater coordinator has to read the map by eye or scrape the API page by page. ## Evidence At `2f150f66`: - A grep for export, CSV or GPX across `lib` finds no route, controller or LiveView for it. - The trail is assembled server side in `lib/aprsme_web/live/map_live/display_manager.ex:310` and pushed as points to the browser, and the packets list paginates through `lib/aprsme/packets.ex` with no download path. - `lib/aprsme_web/router.ex` has no export route under the map, packets or info scopes. ## Proposed behavior - A Download button on the info page and on the map's tracked station panel. - A GPX file for the track and a CSV of packets with time, position, course, speed and the weather fields that are present. - The same window rules the page uses (trail duration for GPX, the page's filters for CSV). ## Why it matters APRS data exists to be shared, and the one thing this site can uniquely provide is the stored history a station's own radio does not keep. ## Acceptance criteria - [ ] A station's track downloads as GPX for the window the page is showing. - [ ] A station's packet list downloads as CSV honoring the visible filters. - [ ] Exports are rate limited and do not block the LiveView process. - [ ] A test asserts the file content and headers for a small fixture. **Effort:** M **Lens:** product

skippy-bot added the

Medium

feature

effort: M

labels

2026-11-03 18:52:35 +00:00