Import

Importing your history

There are four ways to get jumps into Skytime:

1. CSV / XML / PDF file

Drop a file onto the dropzone at /jumps/import. We recognise the column headers from Skytime, Boogie, Skysavage, Skyduck, and Tobu CSV exports, plus generic XML. PDF parsing (scanned logbooks) is on the roadmap.

Starter CSV: download the sample with all expected columns and a handful of example rows — fill it in with your own jumps and drop it back.

Whatever file you upload also lands in your Documents library so you can re-download the original later.

2. Online logbook portals

Skytime opens a session against the portal with your credentials, reads your jumps, and imports them. Credentials are used once in-memory — we never persist them.

• Skyrats.com (Skydive Empuriabrava) — full history in one go.
• Skydive Bulgaria (app.skydivebulgaria.com) — one month per click, pick year + month.
• Skydive Sofia (app.skydivesofia.com) — same flow; dropzone blank for 2025+ jumps (the portal stopped populating it).

3. Scan a written logbook

Photograph a page of your paper logbook and we'll read the handwriting into Skytime. This is coming soon — we're evaluating handwriting models that cope with logbook grids. Hit "I'm interested" on /jumps/import/scan to register demand.

4. Manual entry

Always available — Log jump. Duplicate + bulk-create flows let you batch-enter a weekend's jumps in seconds.

Dedupe

Every imported jump carries an import-key:<source>/<date>/<aircraft>/<flight> marker in notes plus an import-id:<run>. Re-runs skip jumps that match the exact key, the (date + aircraft + altitude) fingerprint, or the natural (date + aircraft + load #) fingerprint. No matter how you run it, the same jump never lands twice.

Something not working?

Every import attempt shows up in the history panel on /jumps/import. Failed runs have an "Ask admin to help" button that routes to /admin/requests — we'll take a look.