File formats
This content is not available in your language yet.
Piranha interoperates with the standard swim-meet file formats so you can move rosters, entries, and results in and out.
Formats
Section titled “Formats”- SD3 / CL2 (SDIF) — the long-standing SDIF exchange format. SD3 is used
for roster and entry import (dual-meet entry files also carry relay
lineups) and results export (field-for-field parity with Meet Manager’s
own results file, including per-leg relay splits).
.cl2is exported as a first-class results file too; CL2 import syncs Meet Manager heat/lane seeding onto already-imported entries. - Hy-Tek
.hy3— Hy-Tek/SwimTopia’s native format. Read for relay results, and written as a full results export (results.hy3— individual results complete; relay results are a known gap). Theresults.zipexport bundles the.cl2+.hy3pair exactly the way Meet Manager’s own results export does, under Meet Manager’s filename convention (Meet Results-<meet>-<date>-001.zip). - Lenex — the modern XML interchange format (
.lef/.lxf), import and export. .hyv+.ev3(the meet-events.zip) — the event order / program definition, exported before the meet for team distribution and read back for event classification.- TimeDrops
.gen— per-heat results files from the timing system, ingested live on deck (round-aware, and idempotent on re-import). - Colorado
.scb— scoreboard start-list export. - Hy-Tek
.rec— record-board files (read, and byte-exact write). - Meet Manager native
.mdb— read-only, on the server: sessions, prelim/final rounds, IM time standards, records, and DQ sync are imported by operator command-line tools (there is no in-app.mdbupload). - TeamUnify roster XLSX and the Acorn season CSV feed — read-only imports run as server-side tools.
Fidelity
Section titled “Fidelity”Piranha stores the richest representation it can parse as the canonical value and flattens at each exporter, so importing then re-exporting preserves as much detail as the target format allows. Round-trip coverage is tracked per format.
For developers
Section titled “For developers”The in-repo docs/file-formats.md carries the authoritative field-parity and
round-trip coverage matrix and is the source of truth for parser/exporter
details.