Raw Slocum files
Read a glider’s own files, here.
Drop the flight and science files off a Slocum — sbd,tbd, dbd, ebd, mbd,nbd and their compressed twins — together with the.cac sensor lists they were written against. They are decoded in this tab and never leave your machine.
Drop files here, or
Nothing is uploaded. There is no server to upload to.
Track
T–S diagram
Waiting for files…
Limits and drawing
Sections
Section
Limits and drawing
What this does, and what it does not
The decoder is the one behindoceansensing.org/data/slocum — a from-scratch reader for Slocum’s dinkum binary format, validated against dbdreader. A Slocum file is factored: the sensor names live in a separate .cac file, so without the matching one a file is a list of numbers with nothing saying what they are. Drop the caches in alongside and they are remembered for next time.
Seawater properties come from the same TEOS-10 implementation the deployment pages use, through the decoder’s own derivation — which matters here in a way it does not for the DAC: a Slocum writes conductivity in S/m and pressure in bar, and TEOS-10 wants mS/cm and dbar. Both are a factor of ten, and both are silent when wrong.
Position needs the same care. A Slocum writes latitude and longitude as NMEA DDDMM.MMMM, which is a perfectly ordinary number — 3936.313 is 39.605° N, and read at face value it is a latitude that does not exist.
No exports here. The decoder on oceansensing.org already writes CSV, netCDF-3 and OceanGliders OG1.0 from these same files, and is tested against a reference; a second implementation would be a second thing to keep correct. This page plots.