ASCII-Vision VS wttr.in

I've always wanted to make an ASCII renderer, but the drawing functions from pillow for writing characters were always too slow to get close to real time. I set out to see if this could be vectorized and this is what I came up with. I also made a video about the algorithm: https://youtu.be/SzqKClkCi_0, and made a repo showcasing the algorithm working on a webcam: https://github.com/AlexEidt/ASCII-Vision.

Webcam Demo: https://github.com/AlexEidt/ASCII-Vision

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