You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Do you have any hints? It looks like it is not taking into account the leading "-" for each coded lat/lon in the Southern Hemisphere. It takes the first 3 characters as the latitude and the last 4 as the longitude. So in the northern hemisphere, the code 6251365 is 62.5 latitude and -136.5 Longitude. In the southern hemisphere, the "-" sign is added. The code -3880854 should be -38.8 latitude and -85.4 longitude. From the map below, the code appears to be reading in the first 3 characters of the code (-38) to get a -3.8 latitude. The longitudes appear to be fine so it looks like the code is taking the last 4 characters correctly.
Never contemplated the need for negative latitudes since WPC didn't document them. 😉 That should be an easy enough update to the parser, we'll see if we can squeeze that into our impending bugfix release.
What went wrong?
Hi,
Since MetPy 1.6, plotting fronts is very easy:
https://unidata.github.io/MetPy/latest/examples/plots/Plotting_Surface_Analysis.html
https://www.unidata.ucar.edu/blogs/developer/entry/metpy-mondays-287-parsing-weather
And parsing the WPC surface bulletins is also easy, with the parse_wpc_surface_bulletin call.
When this new version was released, I was curious to know if WPC produced these bulletins for Latin America and they were not.
So I contacted them and asked if they could produce these bulletins for LatAm and thankfully, they are working on it!
They have already shared some samples, but unfortunatelly, the results are not as expected (image below).
I have also attached a couple of samples provided by WPC: WPC_bulletins_samples_LatAm.zip
Do you have any hints? It looks like it is not taking into account the leading "-" for each coded lat/lon in the Southern Hemisphere. It takes the first 3 characters as the latitude and the last 4 as the longitude. So in the northern hemisphere, the code 6251365 is 62.5 latitude and -136.5 Longitude. In the southern hemisphere, the "-" sign is added. The code -3880854 should be -38.8 latitude and -85.4 longitude. From the map below, the code appears to be reading in the first 3 characters of the code (-38) to get a -3.8 latitude. The longitudes appear to be fine so it looks like the code is taking the last 4 characters correctly.
Thanks!
Operating System
Linux
Version
1.6
Python Version
3.10
Code to Reproduce
Errors, Traceback, and Logs
No response
The text was updated successfully, but these errors were encountered: