[python #WOU-884629]: Metpy METAR Parsing
- Subject: [python #WOU-884629]: Metpy METAR Parsing
- Date: Tue, 23 Feb 2021 14:54:41 -0700
I see the issue, thanks for posting.
Completely understand. Thanks for the kind words, and if you run into any
problems or more things you think are missing, either from MetPy/Siphon or our
training materials, don't hesitate to reach out.
Have a good one!
> Here is what I submitted to GitHub under your recommendation:
> *Hello there! I have been using this module to parse METAR data and would
> like to suggest the addition of parsing precipitation data and and other
> miscellaneous objects in the remarks section of a METAR into the "metar"
> part of the module. Parsing METARs into CSV's helps make working with the
> data that are contained in them much less intimidating, and fleshing out
> the parsing capabilities of this module would make this the no-brainer
> module to use for this purpose. Here is an example:5-MIN KOMA 190550Z
> 16005KT 10SM -FZDZ SCT019 OVC026 M01/M03 A3015 770 88 -900 150/05 RMK AO2
> SLP219 FZDZB44 P0000 60000 I1000 I6000 T10111028 10006 21039 400281056
> 51018Very useful information located within the "RMK" (or remarks) section
> include the following items:FZDZB44 -> Freezing drizzle began at 0544ZP0000
> -> The amount of precipitation the has occurred since the last METAR is
> considered a trace.I1000 -> 1-hr Ice accretion of a traceI6000 -> 6-hr Ice
> accretion of a traceThanks for doing what you guys do! Like I said the
> amount of documentation with this python module is great, and fleshing this
> feature would make the the "go-to" METAR parser for python. *
> I am still working on my "sea legs" in terms of coding in Python, so I
> don't feel like totally comfortable doing a pull request at my skill
> level. In the meantime, I am going to explore using the metar 1.8.0 module (
> https://pypi.org/project/metar/), and work through it with the limited
> documentation compared to your guys'. Thanks for getting back to me, you
> guys do great work for a ton of people; from public builds of software like
> GEMPAK and AWIPS to python resources like MetPy. I am pretty fresh out of
> school at ~1 year, and being able to learn python by doing stuff with
> weather data is CONSIDERABLY more enjoyable than learning it otherwise.
> address@hidden> wrote:
> > Greetings!
> > Thanks for the kind words. We would definitely like to do more to parse
> > some important fields from the remarks section (I assume that's where
> > you're talking about?), but we haven't gotten around to it yet.
> > It'd be great if you could open a feature request to add it so we can
> > capture the community interest:
> > https://github.com/Unidata/MetPy/issues/new?assignees=&labels=Type%3A+Feature&template=feature_request.md
> > You might also mention providing access to the remarks section, since I
> > see that we don't even do that right now (oops). A Pull Request
> > implementing it would be even more awesome, but I know that's a big ask.
> > Cheers,
> > Ryan
> > > Hello!
> > >
> > > I was wondering if you had any plans to add the precipitation
> > accumulation
> > > groups into the capabilities of the Metpy module? I have been using it to
> > > parse 5-minute observations from NCEI, but one of the important things I
> > > was needing was precipitation. Thanks for doing what you guys do!
> > >
> > Ticket Details
> > ===================
> > Ticket ID: WOU-884629
> > Department: Support Python
> > Priority: Low
> > 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.
Ticket ID: WOU-884629
Department: Support Python
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.