Changes between Version 8 and Version 9 of PointObservationConventions
 Timestamp:
 10/26/09 11:25:49 (9 years ago)
Legend:
 Unmodified
 Added
 Removed
 Modified

PointObservationConventions
v8 v9 594 594 }}} 595 595 596 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 gtime(profile,z).596 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). 597 597 598 598 When there are a variable number of observations for different profiles, use alt(profile, z) with missing values. … … 697 697 }}} 698 698 699 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 gtime(p,z).699 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). 700 700 701 701 === 9.5.4 Ragged array (indexed) representation === … … 749 749 }}} 750 750 751 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 gtime(p,z).751 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). 752 752 753 753 … … 766 766 === 9.6.1 Multidimensional representation === 767 767 768 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 t e same number of vertical levels for every profile, one can use the multidimensional representation:768 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: 769 769 770 770 {{{ … … 817 817 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). 818 818 819 The time coordinate may depend on z also, e gtime(station,profile,z). If all of the profiles use the same z coordinate, alt(station, profile, z) may be factored out into z(z).819 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). 820 820 821 821 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. … … 823 823 === 9.6.2 Profile time series at a single station === 824 824 825 If there is only one station in a file, one can use a variation of the Multidimensional representationwhich removes the station dimension:825 If there is only one station in a file, one can use a variation of 9.6.1 which removes the station dimension: 826 826 827 827 {{{ … … 871 871 }}} 872 872 873 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 gtime(profile,z). If all of the profiles use the same z coordinate, alt(profile, z) may be factored out into z(z).873 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). 874 874 875 875 === 9.6.3 Ragged array of station profile time series === … … 935 935 }}} 936 936 937 The profile is associated with a station using the stationIndex(profile). For each profile, the observations must be written contiguously .938 939 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, egtime(obs) instead of time(profile).937 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). 938 939 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). 940 940 941 941 === 9.6.4 Flattened representation of multidimensional profiles === 942 942 943 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:943 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: 944 944 945 945 {{{ … … 988 988 }}} 989 989 990 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. 991 992 == 9.7 Section ProfileData ==993 994 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 thetrajectory.990 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'''". 991 992 == 9.7 Section Data == 993 994 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. 995 995 996 996 === 9.7.1 Multidimensional representation === … … 1050 1050 === 9.7.2 Single section in the file === 1051 1051 1052 If there is only one section in the file, one can use a variation of the9.7.1 which removes the section dimension:1052 If there is only one section in the file, one can use a variation of 9.7.1 which removes the section dimension: 1053 1053 1054 1054 {{{