Actually looks like OWM doesn't provide weather alerts in the same fashion as DarkSky. Instead you have to create a trigger, then poll that trigger for changes. It's not end-user friendly as it is at DarkSky.
So I may have to deprecate weather alerts and only offer current conditions and forecasts. On Friday, April 3, 2020 at 10:17:06 AM UTC-4, Pat wrote: > > yr.no isn't commercially owned, so the theory is they won't get bought > out or go away. They're owned by the Norwegian Broadcasting Corporation > and the Norwegian Meteorological Institute. That said, it's only in > metric, does not have weather alerts and is in XML format only. > > The pro is that they don't seem at risk of being purchased and going away. > The con is it may not be a good fit for how the skin is being used. > > > On Friday, April 3, 2020 at 10:01:39 AM UTC-4, G Hammer wrote: >> >> I'd say OWM, simply because I see no way to get anything except metric/C >> from yr.no >> >> On Thursday, April 2, 2020 at 9:11:43 PM UTC-4, Pat wrote: >>> >>> I'm sure the Belchertown skin could benefit from the forecasts plugin, >>> but Belchertown does more than that. It shows weather alerts for your >>> location as well as current conditions. The forecasting plugin doesn't >>> provide those 2 bits. For that you need a service, and if you're getting >>> info from the service (in my opinion), one stop shop for it (get the >>> forecast too). >>> >>> As for maintaining a plugin base for each region/location, that's not >>> something I can develop or support right now. The JSON would have to be >>> formatted exactly for each service in order to support the current way of >>> updates. Again, this is a simple task for 1 provider who has all this data >>> for worldwide regions >>> >>> I understand that OWM could become the next DarkSky but I think it's the >>> best option for what we have right now. The free tier should be able to >>> provide enough data to replace DarkSky. >>> >>> It's just a matter of time on my end. >>> >>> >>> On Thursday, April 2, 2020 at 6:38:28 PM UTC-4, William Burton wrote: >>>> >>>> Hello, >>>> >>>> On Thursday, April 2, 2020 at 4:34:46 PM UTC-4, Wes Witt wrote: >>>>> >>>>> how about implementing a design that allows for weather forecast >>>>> extensions/plugins. then regional plugins can be built and allow the user >>>>> to choose the weather forecast service that is best for them. this way >>>>> you >>>>> don't need a single service that works for everyone. it can be very >>>>> difficult to find a service that works everywhere and if you can find one >>>>> it may result in a low bar terms of quality and features from the service. >>>>> >>>> >>>> I was thinking the exact same thing as it doesn't make sense for every >>>> skin author to have to implement forecasting from scratch. There are many >>>> API's and there won't be one that works for everyone everywhere. >>>> >>>> The weewx-forecast extension ( >>>> https://github.com/matthewwall/weewx-forecast), already handles the >>>> following weather forecasting services: >>>> >>>> US National Weather Service (NWS) >>>> the weather underground (WU) >>>> open weathermap (OWM) >>>> UK Met Office (UKMO) >>>> Aeris Weather >>>> World Weather Online (WWO) >>>> Dark Sky (DS) >>>> Zambretti >>>> >>>> The extension also handles tide predictions using xtide. >>>> >>>> >>>> My thought was to enhance the weewx-forecast extension to: >>>> >>>> >>>> - Output a generic JSON file that can be loaded via Ajax into a theme. >>>> As much as possible, the JSON would be generated in a manner that's >>>> consistent across different API implementations to make it easier to >>>> incorporate into a skin. >>>> - Output one or more include files that can be included into other >>>> skins. >>>> >>>> Skins like Belchertown can incorporate this output using either method as >>>> appropriate. The end result is it would be far easier for skin maintainers >>>> to expand forecasting options. >>>> >>>> The benefit to this approach is the ability to support many more options >>>> for forecasting more widely. However, a small drawback is users of WeeWX >>>> will have to install another extension and configure it in addition to the >>>> selected skin. >>>> >>>> -Bill >>>> >>>> -- You received this message because you are subscribed to the Google Groups "weewx-user" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/b5bd029e-bfdf-46e5-9da2-a8f141a5d4de%40googlegroups.com.
