Dear CF,
I have oceanographic data from IES instruments (inverted echo sounder) that I
would like to publish via OceanSITES in a CF-compliant form. The data in
question are acoustic travel times from the echo sounding device. This means
the time it took for the acoustic signal to run from the i
Dear All,
Of Matthias's suggestions I have a strong preference for a slight extension of
roundtrip_acoustic_travel_time_in_sea_water, namely
acoustic_signal_roundtrip_travel_time_in_sea_water. 'two-way' is a possible
alternative to 'roundtrip' but I think the former carries unfortunate seismic
+1 for Roy's choice.
Can you explain the following for the acoustically naive? "I assume the data
would need some additional description to denote the vertical extent of the
measurement, such as cell_bounds and cell_methods='Z:sum'."
John
On May 30, 2013, at 06:45, "Lowry, Roy K." wrote:
> D
Hi John,
Not exactly. The travel time in both water column echosounding and seismics is
a proxy for distance and therefore provides information on the vertical
distribution of returned signal intensity.
Cheers, Roy.
From: John Graybeal [grayb...@marine
Let me rephrase my question as a statement. I didn't understand Matthias'
original statement about denoting the vertical extent of the measurement (to
me, a naive viewer, travel time is simply travel time, and I don't need to
understand the vertical extent of the measurement to interpret the nu
Hi,
thanks already for these comments. Roy's suggested name sounds pretty to my
ears.
Trying to explain my "cell_methods" thing:
The instrument is sitting at a fixed spot on the seafloor, so unlike the echo
sounder on a ship, the distance does not change (well, there are tides, but we
filter
> Bottom line: I need to tell the user what depth range I am covering (0-4500
> or 0-3000), and in my limited understanding of the situation this is done
> via the cell_methods and cell_bounds attributes.
Right, got it (I think). In your particular use case it's important to describe
the depth
