Re: [gembud] BND question

See $GEMTBL/config/clo.tbl

! CLO.TBL
!
! This table specifies the alias name for GEMPAK station table and boundary
! info files used by the NMAP seek and locator functions. Alias names defined
! in this table are referenced in the table "$GEMTBL/nmap/locator.tbl".
! Note that both types of data sets can be used by the locator function,
! whereas the seek function can only access the station table data sets.
!
! The first column of this table, (ALIAS), specifies the alias name used
! by the table "locator.tbl".
!
! The second column of this table, (FILE TYPE), specifies whether the
! data set is a GEMPAK station table (0) or boundary info file (1).
! Note that boundary info files only contain information about the actual
! boundary files such as boundary names and pointers into the boundary files.
!
! The third column of this table, (TABLE NAME) is the actual file name
! for the station table or boundary file.  Avaliable station tables are
! located in the directory "$GEMTBL/stns". Available boundary info files are
! located in the directory "$GEMTBL/bounds".


Michael James
Unidata



On 02/22/2011 03:33 PM, pmanousos@xxxxxxxxxxxxxxxxxxx wrote:
How does one tell per available file in $GEMTBL/boundary which corresponding "name" to use in gpmap's "BND" parameter??

The required entry for BND seems independent of the corresponding file name or any tag in the .info files.

Examples: BND=state_bnds for $GEMTBL/statebnds.tbl but BND=lakes for $GEMTBL/lakesbnds.tbl (notice you need an "_bnds" in BND when plotting states, but no so for lakes).

Where is this defined?

Pete ----------------------------------------- The information contained in this message is intended only for the personal and confidential use of the recipient(s) named above. If the reader of this message is not the intended recipient or an agent responsible for delivering it to the intended recipient, you are hereby notified that you have received this document in error and that any review, dissemination, distribution, or copying of this message is strictly prohibited. If you have received this communication in error, please notify us immediately, and delete the original message.


_______________________________________________
gembud mailing list
gembud@xxxxxxxxxxxxxxxx
For list information or to unsubscribe,  visit: 
http://www.unidata.ucar.edu/mailing_lists/