Igor Chubin

I think that the problem is with our data source, at least it is how it is reporting it. There are several similar bugs: https://github.com/chubin/wttr.in/issues?q=is%3Aissue+is%3Aopen+label%3Adata-source Probably, the only possible solution...

geolocation data is the same everywhere. You are just parsing `Location:` line? If you want, we could create a special query type for you, that would return geolocation data only,...

Something like this would work for you? ``` $ curl -s wttr.in/?format=location | jq . { "latitude": 48.1371079, "timezone": "Europe/Berlin", "longitude": 11.5753822, "address": "München, OB, Bayern, Deutschland" } ``` (CAUTION:...

So you want to have the IP data too? Not only geolocation data?

Accepted :+1:

@scfrank Stella, yes I am fully agree with you. It seems to be a WWO problem indeed, and I believe we should slowly start looking for a new data provider....

I think we need a list of supported weather APIs, and slowly add support for each of them, because no API seems to be perfect

(Sorry all for the late reply.) @Danfro No, I would absolutely not mind. Please feel free to use our JSON data stream (`j1`). Please also feel free to contact me...

@scfrank @ReazerDev the problem with the location was fixed (#523). Can you please test it?

No @pvonmoradi it is not realted to wego at all, it is a problem of the data source, and wego is rendering. We can't do here anything except add other,...