Configurable data source needed (was: wrong weather data for Sevastopol)

[ricky-ticky]

right now it shows me -9 – -3 °C

but it's +6 in reality

[chubin]

@ricky-ticky It's a strange, but an interesting Issue. There are at least two Sevastopol in the datasource: Sevastopol, Russia and Sevastopol, Ukraine (and of course Sebastopol in the USA, but it does not matter, because of the b in the name). So, if you try Sevastopol,+Ukraine, you will probably get the correct results. At the moment I configured the wttr.in so, that it takes Sevastopol,+Ukraine by default. I think, its data is more precise than from Sevastopol,+Russia. Please try: http://wttr.in/Sevatopol and give me feedback if it delivers better data now

[chubin]

We have several similar issues, and that's not out issue actually, it's an issue of our data source. So I mark this issue as a duplicate. The best solution that I see here is to have a configurable data source (or to be more concrete: to have many data sources to chose from).

[masolimano]

Hello there!

I want to add that the service is currently giving wrong readings for my location, Santiago de Chile. We are having a very warm summer here while wttr.in reports freezing temperatures. A month ago, the predictions were fine, but in the last two weeks has been underestimating temperatures. See for yourselves:

wttr.in

meteochile.cl (The most accurate source I know)

World Weather Online

Accuweather

These were taken on Jan 24, 2019 roughly at 11:30 local time. I hope you get the idea. I'm sorry I don't have screenshots for other days in the past two weeks but I assure you the differences were even greater.

So I totally agree with @chubin, a configurable data source would be a killer feature! Is there already a way to get the source is currently using? It would be nice to notify them!

[mhalano]

I'm very interested about the solution of this issue. The forecast I get from wttr.in is quite different from the forecast I get on my Android device (which uses AccuWeather). So would be nice to be able to select the forecast service. BTW: what is the main issue about the implementation of multiple backends, since all related issues seems marked as duplicate?

[chubin]

@mhalano The main issue is probably lack of funding, because it is much easier to paid for one data source that for several ones. wttr.in generates a lot of traffic, and so support of multiple backends may become expensive. But it would be still reasonable, at least add their support from the code side. We started gathering all possible data sources that would be great to support, and so I hope that we will add support for at least some of them in future.