Weather shows incorrectly, with or without formatting now...

[althonich]

Using a one liner with the command: curl wttr.in/LOCATION?format="%C+\nFeels+like:+%f+\nActually+is:+%t+\nSunrise:+%S+\nSunset:+%s\n", the "%C" part shows "Partly cloudy".

When using the other command setup (not sure what to call it) with the command "curl wttr.in/LOCATION?0", it shows that it's "Partly cloudy", along with all the wrong statistics and shows the sun even though it set a long time ago.

The only thing that I know consistently shows the right information is this command "wttr.in/LOCATION".

It's pretty weird, even now, anything that has ANY formatting is completely wrong...

I'll try continue looking on my end of things with how I'm entering these commands as that's likely what's going on here.

[eulerfan271]

I think I've run into a similar issue, perhaps identical. Using flags like wttr.in/?m to change units outputs updated/correct weather (i.e. the result of just viewing wttr.in, which is comparable with other weather services). However, any formatting (i.e. format=) results in outdated weather. Following other threads, I've tried wttr.in/[location]+?format=1 and curl 'wttr.in/?nonce=$RANDOM neither of which seems to fix the problem.

Perhaps unrelated, I've noticed that v2 is also old; v2.wttr.in gives the same old results as with formatting, unlike the updated wttr.in. I know v2 is experimental and am not adding this as an additional "bug report"; I mention it simply becomes it seems it might be related. And thanks for all your work!

[althonich]

RIP

Even the normal output is messed up.

Really likes the sun!

Even shows the sun in the current weather section even though the sun has set hours ago.

This is when it's completely unformatted, the URL wttr.in shows this! The error grows! O_o

[althonich]

Using a VPN I set my location to Melbourne, Australia; the time there currently as I type this is 12:35am (past midnight).

This is what wttr.in has to say about the weather...

Very, very, weird...

I know nothing about how this code works or anything like that, so how this is happening is beyond me, let alone why...

Is this project dead or is it still being managed every now and again?

I am now curious.

[chubin]

Sorry for the late reply. Don't know if it still relevant for you or not, but still.

Your command works perfect for me:

$ curl wttr.in/Munich?format="%C+\nFeels+like:+%f+\nActually+is:+%t+\nSunrise:+%S+\nSunset:+%s\n"
Sunny
Feels like: +16°C
Actually is: +16°C
Sunrise: 06:57:44
Sunset: 16:56:08

I don't see any problems here.

Yes, it is possible that it shows some other data than wttr.in/Munich, but they are more recent, not the other way around. The main view has some additional caching.

@eulerfan271 actually, if you use nonce=$RANDOM, you bypass almost all caching layers of wttr.in itself, and get the data as it was delivered by the data source. The data source is not perfect, and we plan to add additional data sources in future, but currently it is only this one.

Sunny night

Regarding Sun in the night, yes, it should be something different instead of the sun, for example Moon, that's an old issue (#52), and that was even the reason why http://wttr.in/Moon emerged, but the last step (displaying of the moon instead of the sung, for the night column) is yet to be done.