diff --git a/docs/Users_Guide/appendixA.rst b/docs/Users_Guide/appendixA.rst
index 9b47a535bd..6fe28f380f 100644
--- a/docs/Users_Guide/appendixA.rst
+++ b/docs/Users_Guide/appendixA.rst
@@ -147,9 +147,10 @@ Q. How do I choose a time slice in a NetCDF file?
A.
When processing NetCDF files, the level information needs to be
-specified to tell MET which 2D slice of data to use. There is
-currently no way to explicitly define which time slice to use
-other than selecting the time index.
+specified to tell MET which 2D slice of data to use. The index is selected from
+a value when it starts with "@" for vertical level (pressure or height)
+and time. The actual time, @YYYYMMDD_HHMM, is allowed instead of selecting
+the time index.
Let's use plot_data_plane as an example:
@@ -160,6 +161,11 @@ Let's use plot_data_plane as an example:
obs.ps \
'name="APCP"; level="(5,*,*)";'
+ plot_data_plane \
+ gtg_obs_forecast.20130730.i00.f00.nc \
+ altitude_20000.ps \
+ 'name = "edr"; level = "(@20130730_0000,@20000,*,*)";'
+
Assuming that the first array is the time, this will select the 6-th
time slice of the APCP data and plot it since these indices are 0-based.
diff --git a/docs/Users_Guide/config_options.rst b/docs/Users_Guide/config_options.rst
index e0f573ed9f..5e4ae8fdbe 100644
--- a/docs/Users_Guide/config_options.rst
+++ b/docs/Users_Guide/config_options.rst
@@ -991,7 +991,8 @@ File-format specific settings for the "field" entry:
* (i,...,j,*,*) for a single field, where i,...,j specifies fixed
dimension values and *,* specifies the two dimensions for the
- gridded field. For example:
+ gridded field. @ specifies the vertical level value or time value
+ instead of offset, (i,...,@NNN,*,*). For example:
.. code-block:: none
@@ -1006,6 +1007,17 @@ File-format specific settings for the "field" entry:
}
];
+ field = [
+ {
+ name = "QVAPOR";
+ level = "(@20220601_1200,@850,*,*)";
+ },
+ {
+ name = "TMP_P850_ENS_MEAN";
+ level = [ "(*,*)" ];
+ }
+ ];
+
* Python (using PYTHON_NUMPY or PYTHON_XARRAY):
* The Python interface for MET is described in Appendix F of the MET
diff --git a/internal/test_unit/xml/unit_plot_data_plane.xml b/internal/test_unit/xml/unit_plot_data_plane.xml
index 02f85765bc..f581160b33 100644
--- a/internal/test_unit/xml/unit_plot_data_plane.xml
+++ b/internal/test_unit/xml/unit_plot_data_plane.xml
@@ -273,6 +273,20 @@
+
+ &MET_BIN;/plot_data_plane
+ \
+ &DATA_DIR_MODEL;/nccf/gtg/latlon/gtg_obs_forecast.20130730.i00.f00.nc \
+ &OUTPUT_DIR;/plot_data_plane/gtg_obs_forecast.20130730.i00.f00.NCCF_latlon_20000.ps \
+ 'name = "edr"; level = "(0,@20000,*,*)";' \
+ -title "NCCF Latitude/Longitude Level 0" \
+ -v 1
+
+
+
+
&MET_BIN;/plot_data_plane
\
@@ -403,7 +417,7 @@
\
&DATA_DIR_MODEL;/easm/pr_day_MPI-ESM-MR_rcp85_r1i1p1_20060101-20091231.nc \
&OUTPUT_DIR;/plot_data_plane/EaSM_CMIP5_pr_day_MPI-ESM-MR_rcp85_r1i1p1_20060101_12_time.ps \
- 'name="pr"; level="(20060102_000000,*,*)";' \
+ 'name="pr"; level="(@20060102_000000,*,*)";' \
-v 4