Open DocOtak opened 9 years ago
Original comment by see (Bitbucket: sescher, GitHub: sescher).
Going Forward: Good Question!
1. This is usually an estimate anyways, eg ctd depth + altimiter off bottom, or knudson depth, or seabeam (most accurate)
2. In the future, DEPTH may be more accurate with some new device, thus a decimal will already be “ready"
3. Probably safer to make it a decimal because a integer can be expressed accurately as a decimal, but not visa-versa
4. will JOA or ODV break if this is a decimal?
Original comment by abarna (Bitbucket: abarna, GitHub: abarna).
JOA does not seem to break when it is a decimal, however it does not report the decimal part (but does display a .0
). JOA does not round either, it seems to simply truncate and append the .0
.
ODV appears to round the depth to the nearest integer value (and does not report a decimal).
I think we can safely set this to a 'decimal' type in the future exchange format spec.
Original report by see (Bitbucket: sescher, GitHub: sescher).
one ct1.csv file in the exchange ct1.zip file contains the line
DEPTH = 5129.000000
the online documentation for DEPTH states that the value is %11s
the command hydro convert ctd zip_exchange_to_zip_netcdf aborts when it reaches this statement.