My imported dives look wrong
Usually it's the units the file was read in, or the time zone. Both are quickest to fix before you save.
Two things go wrong often enough to check first: the units your file was read in, and the time zone its dives were recorded in. Both are far quicker to fix while the batch is still waiting in Divemates → Dives → Incoming, before you save it to your logbook.
Check the units
A dive file doesn't always say what its numbers mean, and a file read in the wrong unit is wrong by the same factor on every dive in it. That's what makes it hard to catch: each row still looks perfectly plausible on its own.
So the review screen states it near the top, something like "Depths were read as feet." Tap that notice, set whichever measurement we got wrong, and tap Apply. Every dive still waiting in the batch is redone at once, and you'll be told how many changed.
Worth knowing:
- It's one choice per measurement, not one for the file. A real export can state depth in feet and temperature in Celsius at the same time.
- You'll only be offered the measurements your file labeled a unit for. A correction works by re-reading what the file said, so a measurement it never labeled has nothing to re-read.
- Cylinder volume is the exception. It isn't read straight off the file, it's worked out from two of its numbers together, so no single switch undoes it. Fix a wrong cylinder on the dive itself.
Wrong dates or times
Plenty of exports write down a local time without saying which zone it belonged to. When the file carries coordinates, we work the zone out from those, and a stated zone that disagrees with them is corrected to match. When it carries none, the dive site fills the gap, which is why choosing the right site is also how you fix a dive's time.
Dives in review are grouped under the day they'll land on, so a batch that came in a day out is obvious at a glance. Open one, set its dive site, and a dive whose file left the zone out is read again in that site's zone. A time you typed yourself is left exactly as you set it.
Note: if the day and month look swapped, the file wrote dates in a form that reads both ways, like 03/04/2026. There's nothing to switch here. Export again with dates written as 2026-04-03 and import that instead.
The whole app is in the wrong units
If depths read as feet everywhere rather than only on the imported dives, that's how Divemates is displaying them, not how the file was read. It's Divemates → Settings → Units, one picker per measurement, and changing it never rewrites a logged dive.
Dives you already saved
A units correction only touches dives still waiting in the batch. Anything already in your logbook keeps the values it was saved with.
For one or two dives, edit them where they are: see "Editing or deleting a dive". For a whole batch that went in wrong, deleting those dives and importing the file again is quicker, and this time the units are set before you save.
Still wrong with everything set correctly? Tell us and send the original file, untouched.