#657 OpenWeatherMap - bugs in Locality, Forecast
Since the unexpected EoL on Yahoo weather API took us by surprise, I decided to go with OpenWeatherMap to keep the app functioning -- I got an API key assigned, entered the key and necessary coordinates for each of my desired locations... but after failing to get the app working again, I started checking with Console and doing some API call tests in my browser -- found a couple issues.
1) The suggested Locality format of "lat,long" in the preferences appears to be injecting the "," character into the latitude string, instead of ignoring it as the delimiter between lat & long -- this is causing the API call to fail, since OpenWeatherMap is reading the added comma as a math symbol. If the suggestion is changed to "Typical location is lat long" and a user's coordinates are formatted with just a single blank space between the coordinate strings (123.45 678.90), the current weather call starts working and displaying properly.
2) The forecast content is not appearing while using OpenWeatherMap, no matter how the settings/preferences are adjusted. I checked the OpenWeatherMap API, and they only offer a 5-day forecast in the free version now... so I tried adjusting my settings, but to no avail. I then returned to Console to check things again -- the app doesn't appear to be making the forecast call in the format required by OpenWeatherMap.
Call being made (throwing a 401 error):
http://api.openweathermap.org/data/2.5/forecast/daily?lat=123&lon=456&appid=abc123&mode=json&units=imperial
Call needed to retrieve 5-day forecast data:
http://api.openweathermap.org/data/2.5/forecast?lat=123&lon=456&appid=abc123&mode=json&units=imperial
I'm guessing that there is also going to be a JSON formatting difference between how "forecast/daily?" was being served, and how "forecast?" is now being served... so unfortunately, this probably isn't going to be as simple as just removing "/daily" from the API call string, but might also require additional code changes to snag all the data properly.
Hope this info helps -- thanks so much for all your hard work, and for a fantastic app -- it's greatly appreciated.
