This archive contains answers to questions sent to Unidata support through mid-2025. Note that the archive is no longer being updated. We provide the archive for reference; many of the answers presented here remain technically correct, even if somewhat outdated. For the most up-to-date information on the use of NSF Unidata software and data services, please consult the Software Documentation first.
Clint, NMAP2 uses the models listed in mod_res.tbl to come up with the list of choices to search for in th config/datatype.tbl file. In cases where the template in datatype.tbl has an "*" character, the pattern matched by the "*" is presented in the data selection menu following the ":". For the radar floater example, nexf, the station that the floater was centered on is used in the file name, eg YYYYMMDD_float_nyc.gem and the template used is YYYYMMDDHH_float_* so NMAP2 can present multiple menu items for floater data sets with one mod_res.tbl item. This is particularly useful if you had multiple floater locations chosen in a day (Or concurrent sectors, etc) where the center location etc is not known ahead of time. Its also useful for tropical storm files where the storm name/number are identified in the file name. The QPF grids come from each office, so the issuing office is in the grid file name, and therefore used in the data selection. You could have a template such as YYYYMMDDHH_nam* and then have one "nam" entry in mod_res.tbl for nam, then your data sets would be NAM:211, NAM:212, NAM:212 etc. However, this would create problems for certain nts files such as using P03I for the 211 data set, where the data is only available at 6 hourly forecast intervals. Steve Chiswell Unidata User Support >From: Clint Rowe <address@hidden> >Organization: University of Nebraska Geosciences >Keywords: 200506091829.j59ITKZu013455 >Chiz, > >I'm a bit confounded trying to trace how nmap2 gets the list of >grids to display in the drop-down menu. I can see how each of >the other choices (except VGF) get the second level of the data >source menu from $GEMTBL/config/datatype.tbl, based on the >catgory (i.e., IMAGE uses CAT_IMG, SURF_OBS uses CAT_SFC, etc). >I also see that VGF makes use of $GEMTBL/nmap/vgf.nmap to generate >its list. But where the heck does the list of grids come from under >GRID? I assume it's a sorted list based on the models listed in >$GEMTBL/nmap/mod_res.tbl, but why does it come up with strange >entries like nexf:nyc.gem and a bunch of qpf:(kalr|kkrf|..)218.gem? >There are entries in $GEMTBL/config/datatype.tbl for these qpf >files, but nmap2 doesn't seem to be using that to generate the list. >So where do the grids with colons in there names come from? > >Clint >-- >==================================================================== >Clinton M. Rowe >Associate Professor >Meteorology/Climatology Program phone:(402)472-1946 >Department of Geosciences fax:(402)472-4917 >University of Nebraska-Lincoln address@hidden > -- NOTE: All email exchanges with Unidata User Support are recorded in the Unidata inquiry tracking system and then made publicly available through the web. If you do not want to have your interactions made available in this way, you must let us know in each email you send to us.