Force Fahrenheit conversion to Celsius

[agilebean]

Hi,
I'm in Latinamerica now so I get the weather reports all in Fahrenheit but really want to keep Celsius.
Is there a flag I can force this conversion?

[eirik-rune]

?m forces metric and does apply to the whole report, not just format=. Measured just now (2026-08-06 07:42 UTC), same coordinate, counting unit occurrences in the full ANSI output:

/4.7110,-74.0721        degC 13  km/h 13   degF 0   mph 0
/4.7110,-74.0721?m      degC 13  km/h 13   degF 0   mph 0
/4.7110,-74.0721?u      degC 0   km/h 0    degF 13  mph 13

So curl 'wttr.in/Bogota?m', or with a format string curl 'wttr.in/Bogota?m&format=3'.

Two things worth knowing that aren't in :help:

u beats m when both are present, in either order. If something in your setup is already appending u (a shell alias, a $WTTRIN style wrapper, a bookmarked URL), adding m will not rescue it:

?u      +50°F
?u&m    +50°F
?m&u    +50°F
?um     +50°F
?mu     +50°F

The default appears to key on the client, not on the place you ask about. From this host every location returns metric by default:

New_York  +33°C   (?u -> +92°F)
Bogota    +10°C   (?u -> +49°F)
London    +14°C   (?u -> +58°F)
Yangon    +32°C   (?u -> +89°F)
Monrovia  +25°C   (?u -> +76°F)

i.e. I can't reproduce a Fahrenheit default for a Latin American query from here, which points at where the request comes from rather than what it asks about. That's one client, so it's a hint, not a proof — but it does mean the fix is a flag on your side, and ?m is that flag.

Not related to the units question, but in case anyone measures near this: Accept-Language is part of the cache key, so two otherwise identical requests can return different temperatures simply because the entries were filled at different times (observation_time 06:58 AM vs 07:41 AM for the same coordinate). I briefly thought language was changing the number; it isn't.