Planner for New Orleans returns invalid min_avg and max_avg temperatures

  • 1
  • Problem
  • Updated 7 months ago
  • (Edited)
This is what it fetches:

MariaDB> select month, temp_low_avg, temp_high_avg from weather_monthly_data where city_id = 3454;
+-------+--------------+---------------+
| month | temp_low_avg | temp_high_avg |
+-------+--------------+---------------+
|     1 |           11 |            15 |
|     2 |           16 |            16 |
|     3 |           19 |            19 |
|     4 |           22 |            22 |
|     5 |           22 |            22 |
|     6 |           28 |            28 |
|     7 |           27 |            28 |
|     8 |           27 |            27 |
|     9 |           28 |            28 |
|    10 |           19 |            19 |
|    11 |           17 |            17 |
|    12 |           14 |            14 |
+-------+--------------+---------------+

It is impossible that low_avg temperature in march and high average temperatures are same (19 degrees C).

API query to illustrate this problem:
http://api.wunderground.com/api/your_api_key/planner_03010331/q/29.9499323,-90.0701156json

In the response I see 

"temp_high": {
		"min": {
"F": "47",
"C": "8"
},
"avg": {
"F": "66",
"C": "19"
},
"max": {
"F": "82",
"C": "28"
}
},
"temp_low": {
"min": {
"F": "47",
"C": "8"
},
"avg": {
"F": "66",
"C": "19"
},
"max": {
"F": "82",
"C": "28"
}
},
Photo of Mladen Adamović

Mladen Adamović

  • 1 Post
  • 0 Reply Likes

Posted 7 months ago

  • 1

Be the first to post a reply!