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.
Hey Pete, > Yeah the reason is inexperience. Having none with grib data other than that in > the "Ingesting a new grid" page you nicely put together, we thought this was > "THE" way to submit a grib file manually. And it was super-easy too. That brings up a good point... I'll review the page and add a little more information for how to more "properly" set up a permanent feed like what you're doing. > So it seems you are implying we SHOULD use pqinsert vs this python script. Not at all. I think both are completely valid and efficient ways to insert your data. > If so, due to our inexperience, how do we use it specific for grib2 data? We > typically > do a pqinsert -v -l <somelogfile> -p <someproductID> - f <somefieldtoken> > $DATFILE > So we need some guidance on what do supply pqinsert to get it submitted > properly. I am not an ldm expert so I am not certain on this, but I don't think you need the -l <somelogfile> if you don't have one. Also the productID can be a portion of the grib name I think (it can be anything really, but this is to help you and I think it needs to be or should be unique). If you want to do it with pqact, I can ask Tiffany for some more clarification. If you don't really mind how it gets into EDEX, I say use the python script method and don't worry about it? I guess the benefit to having it use pqinsert is all you're data is going in through the LDM, and you potentially could make use of some LDM tools to see what amounts of data you're getting and all that? --Shay Carter She/Her/Hers AWIPS 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: KEZ-434248 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.