How to enable wttr.in in a PowerShell console

Enable-wttr.in-for-PowerShell

# To enable ANSI sequences in a PowerShell console run the following commands.
# After that you can use wttr.in in you PowerShell just lake that:
#   (curl http://wttr.in/ -UserAgent "curl" ).Content
#
# More on it:
#  http://stknohg.hatenablog.jp/entry/2016/02/22/195644 (jp)
#  

Add-Type -MemberDefinition @"
[DllImport("kernel32.dll", SetLastError=true)]
public static extern bool SetConsoleMode(IntPtr hConsoleHandle, int mode);
[DllImport("kernel32.dll", SetLastError=true)]
public static extern IntPtr GetStdHandle(int handle);
[DllImport("kernel32.dll", SetLastError=true)]
public static extern bool GetConsoleMode(IntPtr handle, out int mode);
"@ -Namespace Win32 -Name NativeMethods
# コンソールモードを変更
$Handle = [Win32.NativeMethods]::GetStdHandle(-11) #  stdout
$Mode = 0
$Result = [Win32.NativeMethods]::GetConsoleMode($Handle, [ref]$Mode)
$Mode = $Mode -bor 4 # undocumented flag to enable ansi/vt100
$Result = [Win32.NativeMethods]::SetConsoleMode($Handle, $Mode)

chcp 437

@strangeronline Yes, the gist is already 4 years old. Now it should just work out of the box, as you did it

This does not work. When I run it with the curl command as below:

(curl wttr.in/SanDiego?0 -UserAgent "curl" ).Content

I get the following output

When I try to use this command by itself. it gets even worse:

(curl wttr.in/SanDiego -UserAgent "curl" ).Content

Is there anyway to fix this?

Anyone figured out a fix to this?