[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[python #OXJ-988166]: DAA file ingested from NOAAPort error in MetPy

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.

  • Subject: [python #OXJ-988166]: DAA file ingested from NOAAPort error in MetPy
  • Date: Wed, 28 Mar 2018 20:18:45 -0600
Randy and Danny,

So it turns out that your error is happening because, at least in the case
of the problematic product you sent, the file actually contains two copies
of the product back-to-back. This triggers an explicit check for the
expected amount of bytes remaining in the file.

The next MetPy release will contain improved diagnostics for this case; we
will also change the error to just a warning message, since in your case we
could have continued parsing the file without error. If you want to follow
that development, please look here:
https://github.com/Unidata/MetPy/pull/793

Ryan

address@hidden> wrote:

> New Client Reply: DAA file ingested from NOAAPort error in MetPy
>
> Ryan,
>
> We have only been looking at the DAA products but Danny informed me today
> when we put it on another machine running Centos 7.3 it worked fine w/o
> having to strip the header. go figure.
>
> Randy
> ________________________________________
> From: Unidata Python Support <address@hidden>
> Sent: Wednesday, March 28, 2018 6:35 PM
> To: Alliss, Randy [US] (MS)
> Cc: Alliss, Randy [US] (MS); address@hidden; Felton,
> Danny [US] (MS)
> Subject: EXT :[python #OXJ-988166]: DAA file ingested from NOAAPort error
> in MetPy
>
> Danny,
>
> Ok with the DAA product you attached, I can reproduce the problem. These
> are coming from your LDM feed? Does this happen regularly with all
> products, or just certain ones?
>
> I don't see this error with our locally filed LDM Level 3 products.
>



Ticket Details
===================
Ticket ID: OXJ-988166
Department: Support Python
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.