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.
Michael, The BUFR products being sent in NOAAPORT are prepared by JPL. I added the code to read these products and follow the plotting that NCEP is doing with the data they have in house. NCEP has access to a gridded product which JPL is producing which is what the QSCT datatype is referencing (the reading and display of that data follows from the ggqsrd.f routine (called by ggqsct.f). Since you are at one of the locations that the NCEP developers support, you probably have direct access to the gridded product. Steve Chiswell Unidata User Support >From: Michael Brennan <address@hidden> >Organization: UCAR/Unidata >Keywords: 200511301600.jAUG0F7s005343 >Hi Steve, > >I have a question about the data format with which the real-time >QuikSCAT data is sent through the LDM for display in GEMPAK. I know the >data is in BUFR format, which allows for display with gpmap or in NMAP2. > However, I'm interested in computing derived quantities from the wind >vector and ambiguity fields, which I can't do unless I have the full >vector wind values in a grid. I'm wondering if there is a way I can >read the BUFR data, perhaps with a Fortran program, and generate a >GEMPAK grid file with the wind data that I could compute vorticity, >divergence, etc., with. > >Thanks for any advice. > >-Mike >-- >Dr. Michael J. Brennan >UCAR Visiting Scientist >NOAA/NWS/Tropical Prediction Center >Email: address@hidden >Phone: (305) 229-4439 > -- 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.