[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[AWIPS #XFF-584221]: DAF Inquiry RE: KDAB
- Subject: [AWIPS #XFF-584221]: DAF Inquiry RE: KDAB
- Date: Wed, 21 Sep 2022 15:05:48 -0500
These emails are not published.
I found the GFM on Vlab
(https://vlab.noaa.gov/redmine/projects/nwsscp/wiki/GfeForecastMonitor#AWIPS-GFE-Forecast-Monitor-GFM-using-the-python-Data-Access-Framework-DAF)
and looked at the source code. This tool uses the NWS DAF, not Unidata's
python-awips/DAF. You can tell because Unidata's python-awips/DAF imports the
DataAccessLayer from the awips package, not ufpy. I'm not sure why the NWS DAF
is having issues with the KDAB ob, but I suspect it's an issue with EDEX
ingesting vs DAF. Have you looked at the database to see if the data are
correct in there or tried plotting it in CAVE?
Using Unidata python-awips/DAF, we have an example that requests METAR obs from
EDEX and we have to issues retrieving and plotting the KDAB.
http://unidata.github.io/python-awips/examples/generated/METAR_Station_Plot_with_MetPy.html
Thanks,
Tiffany Meyer
AWIPS Lead Software Engineer
UCAR-Unidata
If you're interested, please feel free to fill out a survey about the support
you receive:
https://docs.google.com/forms/d/e/1FAIpQLSeDIkdk8qUMgq8ZdM4jhP-ubJPUOr-mJMQgxInwoAWoV5QcOw/viewform
Ticket Details
===================
Ticket ID: XFF-584221
Department: Support AWIPS
Priority: Normal
Status: Open
===================
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.