# Changes between Version 8 and Version 9 of PointObservationConventions

Ignore:
Timestamp:
10/26/09 11:25:49 (11 years ago)
Comment:

--

Unmodified
Added
Removed
Modified
• ## PointObservationConventions

 v8 }}} The pressure(p,i), temperature(p,i), and humidity(p,i) data is associated with the coordinate values time(p), alt(p,i), lat(p), and lon(p). If the vertical coordinates are the same for all profiles, one can use z(z) instead of alt(profile,z). The time coordinate may depend on z also, eg time(profile,z). The pressure(p,i), temperature(p,i), and humidity(p,i) data is associated with the coordinate values time(p), alt(p,i), lat(p), and lon(p). If the vertical coordinates are the same for all profiles, one can use z(z) instead of alt(profile,z). The time coordinate may depend on z also, e.g. time(profile,z). When there are a variable number of observations for different profiles, use alt(profile, z) with missing values. }}} The pressure(i), temperature(i), and humidity(i) data is associated with the coordinate values time(p), z(i), lat(p), and lon(p), where p is found by reading the rowSize variable values. The time coordinate may depend on z also, eg time(p,z). The pressure(i), temperature(i), and humidity(i) data is associated with the coordinate values time(p), z(i), lat(p), and lon(p), where p is found by reading the rowSize variable values. The time coordinate may depend on z also, e.g. time(p,z). === 9.5.4 Ragged array (indexed) representation === }}} The pressure(i), temperature(i), and humidity(i) data is associated with the coordinate values time(p), z(i), lat(p), and lon(p), where p=parentIndex(i). The time coordinate may depend on z also, eg time(p,z). The pressure(i), temperature(i), and humidity(i) data is associated with the coordinate values time(p), z(i), lat(p), and lon(p), where p=parentIndex(i). The time coordinate may depend on z also, e.g. time(p,z). === 9.6.1 Multidimensional representation === When storing time series of profiles at multiple stations in the same file, if there are the same number of time points for all stations, and te same number of vertical levels for every profile, one can use the multidimensional representation: When storing time series of profiles at multiple stations in the same file, if there are the same number of time points for all stations, and the same number of vertical levels for every profile, one can use the multidimensional representation: {{{ The pressure(s,p,i), temperature(s,p,i), and humidity(s,p,i) data is associated with the coordinate values time(s,p), z(s,p,i), lat(s), and lon(s). The time coordinate may depend on z also, eg time(station,profile,z). If all of the profiles use the same z coordinate, alt(station, profile, z) may be factored out into z(z). The time coordinate may depend on z also, e.g. time(station,profile,z). If all of the profiles use the same z coordinate, alt(station, profile, z) may be factored out into z(z). When there are varying number of profiles for different stations, use time(station, profile) with missing values. When there are varying number of levels for different profiles, use alt(station, profile, z) with missing values. === 9.6.2 Profile time series at a single station === If there is only one station in a file, one can use a variation of the Multidimensional representation which removes the station dimension: If there is only one station in a file, one can use a variation of 9.6.1 which removes the station dimension: {{{ }}} The pressure(i,j), temperature(i,j), and humidity(i,j) data are associated with the coordinate values time(p), alt(p,i), lat, and lon. The time coordinate may depend on z also, eg time(profile,z). If all of the profiles use the same z coordinate, alt(profile, z) may be factored out into z(z). The pressure(i,j), temperature(i,j), and humidity(i,j) data are associated with the coordinate values time(p), alt(p,i), lat, and lon. The time coordinate may depend on z also, e.g. time(profile,z). If all of the profiles use the same z coordinate, alt(profile, z) may be factored out into z(z). === 9.6.3 Ragged array of station profile time series === }}} The profile is associated with a station using the stationIndex(profile). For each profile, the observations must be written contiguously. The pressure(i), temperature(i), and humidity(i) data is associated with the coordinate values time(p), z(i), lat(s), and lon(s). The time coordinate may depend on z also, eg time(obs) instead of time(profile). The profile is associated with a station using the stationIndex(profile). For each profile, the observations must be written contiguously, and the number of obs for each profile written in numRows(profile). The pressure(i), temperature(i), and humidity(i) data is associated with the coordinate values time(p), z(i), lat(s), and lon(s), where s = stationIndex(p). The time coordinate may depend on z also, e.g. time(obs) instead of time(profile). === 9.6.4 Flattened representation of multidimensional profiles === A variation of multidimensional profiles (9.5.1) allows these to be associated into a station time series. The station information (lat, lon, id) is repeated in each profile: A variation of multidimensional profiles (9.5.1) allows these to be associated into a station time series of profiles. The station information (lat, lon, station_id) is repeated in each profile: {{{ }}} This is the same as 9.5.1, except that a station_id variable is added for each profile, which associates the profile to a station. The station information is repeated for each profile and should be the same for all profiles with the same station_id. == 9.7 Section Profile Data == When profiles are taken along a trajectory, one gets a time series of profiles called a section. This looks like a collection of profiles (see 9.5), except that the profile locations are assumed to be a connected set of points along the trajectory. This is the same as 9.5.1, except that a station_id variable is added for each profile, which associates the profile to a station. The station information is repeated for each profile and should be the same for all profiles with the same station_id. Note that therre is no station dimension, but station description, altitude and wmo_id can be specified using the standard_name attributes "'''station_desc'''", "'''station_altitude'''", and "'''station_wmoid'''". == 9.7 Section Data == When profiles are taken along a trajectory, one gets a time series of profiles called a section. This looks like a collection of profiles (see 9.5), except that the profile locations are assumed to be a connected set of points along a trajectory. === 9.7.1 Multidimensional representation === === 9.7.2 Single section in the file === If there is only one section in the file, one can use a variation of the 9.7.1 which removes the section dimension: If there is only one section in the file, one can use a variation of 9.7.1 which removes the section dimension: {{{