Worldweatheronline suspending free API keys, need new backends

[schachmat]

According to this post there will soon be no possibility for new users to get a free API key. Therefore wego needs at least one new backend. I don't have much time in the near future, so any help is greatly appreciated.

Here is a list of weather services which should be usable. I will update the list.

• forecast.io (done, see forecast.io backend progress #83)
  • https
  • location can only be specified as latitude,longitude pair
• openweathermap
  • easy interface
  • no https
• weatherunlocked
  • https
• yourweather
  • only XML
  • focused on weather in the UK
  • no https?
• your proposed weather service here

A service which does not require registration / an API key would be nice.

[pramodk-git]

A couple of alternatives:

https://developer.weatherunlocked.com/localweather/pricing

• HTTP and HTTPS supported
• JSON or XML

http://api.yourweather.co.uk/index.php?p=a

• Looks like it is XML only
• http only, AFAICT.
• Could not find any documented usage limits

[schachmat]

thanks @pramodk-git, I added them to the list. weatherunlocked looks very promising, but for the new default I want a backend with no need for registration, so probably openweathermap.

[cVeqT2vkiSX5kJVJxcVmz7rKHKbu9M9FNixoPNC]

As far as I can tell, openweathermap also requires registration to receive an API key.

I tried getting forecast.io running, but still have some issues with the frontend. The Forecast Slots are not working correctly atm.
=> camelinc@7318a3cf0304e6de99a1e606e8c00421e309fc4a

• forecast.io
  • registration needed
  • https
  • json

[schachmat]

As a quick hint: You can use the json frontend for debugging. It will show the iface.Data struct. I could not try it yet, but I assume it's related to the iface.Cond.Time element.

[cVeqT2vkiSX5kJVJxcVmz7rKHKbu9M9FNixoPNC]

that did quite help. The first working commit is camelinc@36123edb98291314ceb6378edbe04d8f56084494

probably needs some polishing and testing

[schachmat]

cool. Is it okay for you, if I pull your commits, squash them to a single one (for a cleaner history) and push them to my repo? You will still be the author of the commit, but I will probably have to do some fixup (you changed the import path).

[cVeqT2vkiSX5kJVJxcVmz7rKHKbu9M9FNixoPNC]

Sure! Are you going to do the pull or should I open a unified pull request?

[schachmat]

I already started the pull and fixes, so there is no need to open a pull request.

[schachmat]

First forecast.io backend draft is up, refer to #83 for further status information and discussion.

[polyzen]

It would seem 2.0 no longer works with WWO's API (using a trial premium key). Appears to be the same issue as #81 (comment).

I'm trying to build a package for Arch Linux against the release (there is a Git package which works great). Perhaps it's time for a new release? :)

[schachmat]

Heyho @polyzen,

If you are able to, you are very welcome to help get a 2.1 release ready. Only the second step mentioned in #98 is missing, but I am writing my thesis currently so I don't have much time to think about a good solution for that.

[schachmat]

Thanks to @R11baka we now have a openweathermap.org backend! 🎉