Next tide window pending.
Visual field intelligence
Latest field data, converted into a story board
This page is designed to read `data/latest-field-data.json`, which can be updated later by a separate agent stream or cron job. The website concentrates on display, sense-making and committee-friendly storytelling.
Safety boundary
Planning context, not navigation advice
The visual layer can make conditions easier to understand, but official warnings, local judgement and on-water safety procedures stay above any website score or generated summary.
Latest payload
Field operations board
Waiting for the latest field data payload.
Monitor summary pending.
Check-in summary pending.
Upload summary pending.
Narrative readout
The board is ready for incoming data
A cron job or agent can update the JSON payload, and this page will convert it into readable visual blocks for members and committee.
Planning signal
Time windows
Solunar, tide and event windows as a visual ribbon
The page does not need to know where the data came from. It only needs a clean list of labelled windows from the upstream agent.
Solunar tide calendar
A week of moon, tide and bite-window signals
The upstream data stream supplies the values. This page turns them into visual planning cards so the committee can compare the week without reading a spreadsheet.
Tide shape
Sample tide curve
Monitor tiles
Weather and condition points become readable cards
The upstream stream can provide wind, swell, tide, storm, UV, sea-state or any other monitor. This page renders the latest values with a calm tone system.
Weather visualisations
Wind, swell, UV and storm signals as gauges
These are visual placeholders for the latest supplied readings. They are deliberately easy to read at a meeting or on a phone before a competition.
Google map picker
Public PLFC map points that open local field stories
This map is built from the supplied PLFC KMZ / Google My Maps placemarks. Public access points and meeting places can be mapped clearly; private fishing spots and team GPS still stay out of the public layer.
KMZ placemarks extracted locally for this prototype.
Retro team logs
Team movement shown as permissioned summaries
Instead of public live tracking, the site can show after-the-event logs: who consented, what broad zones were visited, what media was captured, and what stays private.
Team coordination
Location sharing is shown as consent status, not public tracking
A future live map should only show event-bound, opt-in team locations to authorised organisers. The public prototype can tell the story without exposing anyone's precise location.
Checked in
People marked as present for the event or working bee.
Sharing location
Opt-in, event-bound sharing only. No background tracking by default.
Location expiry
Live sharing should expire automatically after the event window.
Visibility
Authorised roles only, never a public location board.
Upload storytelling
Photos, video and notes become evidence trails
The display layer can show counts, permission status and story highlights while the actual media storage is handled somewhere else.
Featured story
Competition wrap-up pending
The next uploaded content bundle can become a public wrap-up, committee evidence note or grant-ready activity summary.
Digital twin pathway
Clean field data becomes future local mapping
The digital twin can start as a visual story: broad zones, time windows, conditions, participation and media. Precision and privacy can be added only where they are appropriate.
Data contract
The page expects a simple JSON payload
`data/latest-field-data.json` is the handoff point. A cron job, separate agent or future backend can refresh that file without redesigning the page.
Latest snapshot
Generated time, event name, location label and short narrative summary.
Windows
Labelled tide, solunar, weather, event and media windows for the visual ribbon.
Monitors
Any current data point with label, value, detail and tone.
Stories
Upload counts, permission state, team status and future map layers.