graphqurl VS wttr.in

Don't forget about xmlstarlet for xpath, https://github.com/hasura/graphqurl for graphql and httpie for a more syntax friendly http client.

There are some tools for GraphQL queries one of them is hasura's graphcurl which has autocompetion and provides prompt for query construction. Check it out, since it might be what you need.

And the actual tool: https://github.com/hasura/graphqurl

If you want to read more about the project make sure to visit Graphqurl GitHub repo.

wttr.in is unfortunately not accurate in many cities in the world, check their github issues

The difference with weafetch is that it has its own config file which can just be configured and not touched anymore. When using wttr.in with curl, any custom changes you want to get from the output will need to be typed in everytime.

What about https://wttr.in/ ?

The source of the data that are presented: https://github.com/chubin/wttr.in

I don't recommend using wttr.io at all, their current provider shows inaccurate information for many cities, including Berlin. (source)

Oups the last link was incorrect it should have been https://github.com/chubin/wttr.in. I pull the info and store it in a txt file then I reference with cat or sed. That way it's super quick.

See https://github.com/chubin/wttr.in