NCEPLIBS-bufr
11.7.0
|
Specify the use of standardization when writing BUFR messages. More...
Go to the source code of this file.
Functions/Subroutines | |
subroutine | stdmsg (CF) |
This subroutine is used to specify whether BUFR messages output by future calls to message-writing subroutines and subset-writing subroutines should be internally reformatted to remove all BUFRLIB software extensions to the WMO standard, prior to actually writing each message. More... | |
Specify the use of standardization when writing BUFR messages.
Definition in file stdmsg.f.
subroutine stdmsg | ( | character*1 | CF | ) |
This subroutine is used to specify whether BUFR messages output by future calls to message-writing subroutines and subset-writing subroutines should be internally reformatted to remove all BUFRLIB software extensions to the WMO standard, prior to actually writing each message.
It is strongly recommended to use this subroutine (or, alternatively, subroutine stndrd() for messages which already exist in memory arrays) whenever BUFR messages are being written that will potentially be read using software other than the BUFRLIB software. Otherwise, by default the output messages will contain a number of extensions to allow for faster reading and more efficient storage, but which will be encoded using non-standard descriptors in Section 3, and therefore likely be unrecognizable to other software packages.
This subroutine can be called at any time after the first call to subroutine openbf(), and the specified value for CF will remain in effect for all future calls to message-writing subroutines and subset-writing subroutines for all Fortran logical units that are open for output within the application program, unless a subsequent call is made to this subroutine to reset the value of CF again. If this subroutine is never called, a default value of 'N' is used for CF, as set within subroutine bfrini().
[in] | CF | – character*1: Flag indicating whether future BUFR output messages are to be standardized
|
Program history log:
Date | Programmer | Comments |
---|---|---|
2004-08-18 | J. Ator | Original author |