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

[LDM #QZC-966326]: LMD bzip2 nexrad



Paul,

Glad you got it sorted out. If you have questions about the MetPy code, feel 
free to reach out here or on our python-users mailing list:

http://www.unidata.ucar.edu/support/#mailinglists

Welcome to the world of Python!

Ryan

> Ryan
> 
> Thank you, problem solved.
> 
> I went through the python code and saw that the frames was âdeclaredâ 
> byte array() and I had it as a list or something like that.
> 
> I am relatively new to python and I suspected something like that but 
> wasnât sureâ it all works now and looking at using your code.
> 
> P
> 
> 
> 
> > On Jun 16, 2017, at 12:44 AM, Unidata Python Support <address@hidden> wrote:
> >
> > Paul,
> >
> > You need to skip 12 bytes before every message header to account for the 
> > legacy "CTM Header"; this information is hidden in section 7.6 of this 
> > document:
> >
> > https://www.roc.noaa.gov/wsr88d/PublicDocs/ICDs/2620010E.pdf
> >
> > In general though, I'd recommend looking at the NEXRAD Level 2 
> > implementation in the MetPy package:
> >
> > https://github.com/Unidata/MetPy/blob/master/metpy/io/nexrad.py
> >
> > MetPy's NEXRAD level 2 (and level 3) support exhaustively covers the entire 
> > gamut of various message types. I'd be happy to help you install and use 
> > MetPy if that's of interest.
> >
> > Ryan
> >
> >> Hello,
> >>
> >> I am trying to write a decode for the nexrad2 level 2 with the new LDM 
> >> BZIP2 format.
> >> Attached is the python code to decompress the file and it seems to be 
> >> working - according
> >> to the byte counting.  However, the contents seem incorrect...that is the 
> >> first 16 bytes
> >> after the 24 byte header is strange as if the decompressed output is not 
> >> of the type byte
> >> or I have to do something to it to make it correct.  I have seen the 
> >> output of my decode
> >> for good (old) and bad (new) decodes.  I expected to see a 16 byte header 
> >> with msg size and
> >> msg type information and I get something in non-interpretable format (at 
> >> least to me).
> >>
> >> Your advice is appreciated.
> >
> > Ticket Details
> > ===================
> > Ticket ID: QZC-966326
> > Department: Support Python
> > Priority: Normal
> > Status: Closed
> > ===================
> > 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.
> >
> >
> 
> 
> --
> ------------------------------------------------------------------------------
> The information contained in this electronic message and any attachments
> are intended for specific individuals or entities, and may be confidential,
> proprietary or privileged. If you are not the intended recipient, please
> notify the sender immediately, delete this message and do not disclose,
> distribute or copy it to any third party or otherwise use this message. The
> content of this message does not necessarily reflect the official position
> of the World Meteorological Organization (WMO) unless specifically stated.
> Electronic messages are not secure or error free and may contain viruses or
> may be delayed, and the sender is not liable for any of these occurrences.
> ------------------------------------------------------------------------------
> Please do not print this e-mail unless absolutely necessary - SAVE PAPER
> 
> 

Ticket Details
===================
Ticket ID: QZC-966326
Department: Support Python
Priority: Normal
Status: Closed
===================
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.