-
Notifications
You must be signed in to change notification settings - Fork 15
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Oceans674 #689
Oceans674 #689
Conversation
Codecov Report
@@ Coverage Diff @@
## main-dev #689 +/- ##
============================================
+ Coverage 76.81% 76.86% +0.05%
============================================
Files 97 97
Lines 17536 17548 +12
============================================
+ Hits 13471 13489 +18
+ Misses 4065 4059 -6
Flags with carried forward coverage won't be shown. Click here to find out more.
Continue to review full report at Codecov.
|
Q: Also, why is there no "W Europe": https://aeroval.met.no/overall.php?project=cams2-82&exp_name=IFS&station=WORLD&tab=timeseries# A: Not in _HTAP_NAMES |
@AugustinMortier Are the regions on the website defined from |
Here's how I see the situation. The problem is that the "Ocean" region is applied to many of the stations. However, the statistics (e.g., time series) for each region appear to be computed correctly. Indeed, they are. This is because the filtering for a colocated data object takes place in "N America": {
"minLat": 18.95,
"maxLat": 71.15,
"minLon": 172,
"maxLon": -52
}, If the regions are are stored as an array (#580), then Therefore, we either need to completely re-overhaul how regions are defined on the web interface, or on the web, we only need to plot points for which "Oceans" are their only region. However, having the regions defined in terms of the NetCDF filters and also be flexible enough to be an array is fundamentally incompatible. |
@AugustinMortier do you want W Europe on the web as well? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🏁 🏇🏼
maybe test_get_regions_coord_with_supplied_regions_dict
could do with some clean up, but it is a very minor nitpick.
Please, merge when you see fit.
You've heard of Ocean's 11, Ocean's 12, and Ocean's 13. Well get ready for....
Addressing issues described in #674 and this comment: #582 (comment)
We know that almost all regions are contained in "Oceans". This is because the the HTAP definition in
regions_def.py
. A first observation is that on the website, when you select "North America", "Pacific, Australia, and New Zealand", or "Russia, Ukraine, Belarus", stations on the globe do not "light up" as they do for the rest of the region (e.g., Europe, Eastern Europe, etc.). I suspected this might have to do with the face that each of these regions have longitude boundaries in which the easterly-most coordinate is "greater than" the westerly-most coordinate (i.e., the bounding box goes through the antipodes of the prime meridian), Sure enough, the functioncontains_coordinate
was not set up for this case. So I changed it, and added some tests.This needs testing on a run, which I will try tomorrow. Not sure if it will correct everything in the issue, but this is a start.