{ "componentChunkName": "component---src-templates-issues-tsx", "path": "/issues/613", "result": {"data":{"issuesJson":{"id":"722c9631-de8b-5c2f-95c6-bac34f6bceb6","title":"chubin/wttr.in: 执行 curl wttr.in 在终端中显示天气预报","number":613,"bodyHTML":"
\n



\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
Reposchubin/wttr.in
Views\"views\"
Stars\"stars\"
Forks\"forks\"
License\"license\"
UpdatedAt\"last-commit\"
CreatedAt\"create-at\"
\n\n

\"\"

\n\n
\n

wttr.in — the right way to check curl the weather!

\n

wttr.in is a console-oriented weather forecast service that supports various information
\nrepresentation methods like terminal-oriented ANSI-sequences for console HTTP clients
\n(curl, httpie, or wget), HTML for web browsers, or PNG for graphical viewers.

\n

Originally started as a small project, a wrapper for wego,
\nintended to demonstrate the power of the console-oriented services,
\nwttr.in became a popular weather reporting service, handling tens of millions of queries daily.

\n

You can see it running here: wttr.in.

\n

Documentation | Usage | One-line output | Data-rich output format | Map view | Output formats | Moon phases | Internationalization | Installation

\n

Usage

\n

You can access the service from a shell or from a Web browser like this:

\n
$ curl wttr.in\nWeather for City: Paris, France\n\n     \\   /     Clear\n      .-.      10 – 11 °C\n   ― (   ) ―   ↑ 11 km/h\n      `-’      10 km\n     /   \\     0.0 mm\n
\n

Here is an example weather report:

\n

\"Weather

\n

Or in PowerShell:

\n
Invoke-RestMethod https://wttr.in
\n

Want to get the weather information for a specific location? You can add the desired location to the URL in your
\nrequest like this:

\n
$ curl wttr.in/London\n$ curl wttr.in/Moscow\n$ curl wttr.in/Salt+Lake+City\n
\n

If you omit the location name, you will get the report for your current location based on your IP address.

\n

Use 3-letter airport codes in order to get the weather information at a certain airport:

\n
$ curl wttr.in/muc      # Weather for IATA: muc, Munich International Airport, Germany\n$ curl wttr.in/ham      # Weather for IATA: ham, Hamburg Airport, Germany\n
\n

Let's say you'd like to get the weather for a geographical location other than a town or city - maybe an attraction
\nin a city, a mountain name, or some special location. Add the character ~ before the name to look up that special
\nlocation name before the weather is then retrieved:

\n
$ curl wttr.in/~Vostok+Station\n$ curl wttr.in/~Eiffel+Tower\n$ curl wttr.in/~Kilimanjaro\n
\n

For these examples, you'll see a line below the weather forecast output that shows the geolocation
\nresults of looking up the location:

\n
Location: Vostok Station, станция Восток, AAT, Antarctica [-78.4642714,106.8364678]\nLocation: Tour Eiffel, 5, Avenue Anatole France, Gros-Caillou, 7e, Paris, Île-de-France, 75007, France [48.8582602,2.29449905432]\nLocation: Kilimanjaro, Northern, Tanzania [-3.4762789,37.3872648]\n
\n

You can also use IP-addresses (direct) or domain names (prefixed with @) to specify a location:

\n
$ curl wttr.in/@github.com\n$ curl wttr.in/@msu.ru\n
\n

To get detailed information online, you can access the /:help page:

\n
$ curl wttr.in/:help\n
\n

Weather Units

\n

By default the USCS units are used for the queries from the USA and the metric system for the rest of the world.
\nYou can override this behavior by adding ?u, ?m or ?M to a URL like this:

\n
$ curl wttr.in/Amsterdam?u  # USCS (used by default in US)\n$ curl wttr.in/Amsterdam?m  # metric (SI) (used by default everywhere except US)\n$ curl wttr.in/Amsterdam?M  # metric (SI), but show wind speed in m/s\n
\n

If you have several options to pass, write them without delimiters in between for the one-letter options,
\nand use & as a delimiter for the long options with values:

\n
$ curl 'wttr.in/Amsterdam?m2&lang=nl'\n
\n

It would be a rough equivalent of -m2 --lang nl for the GNU CLI syntax.

\n

Supported output formats and views

\n

wttr.in currently supports five output formats:

\n\n

The ANSI and HTML formats are selected based on the User-Agent string.

\n

To force plain text, which disables colors:

\n
$ curl wttr.in/?T\n
\n

To restrict output to glyphs available in standard console fonts (e.g. Consolas and Lucida Console):

\n
$ curl wttr.in/?d\n
\n

The PNG format can be forced by adding .png to the end of the query:

\n
$ wget wttr.in/Paris.png\n
\n

You can use all of the options with the PNG-format like in an URL, but you have
\nto separate them with _ instead of ? and &:

\n
$ wget wttr.in/Paris_0tqp_lang=fr.png\n
\n

Useful options for the PNG format:

\n\n

Transparency is a useful feature when weather PNGs are used to add weather data to pictures:

\n
$ convert source.jpg <( curl wttr.in/Oymyakon_tqp0.png ) -geometry +50+50 -composite target.jpg\n
\n

In this example:

\n\n

\"Picture

\n

You can embed a special wttr.in widget, that displays the weather condition for the current or a selected location, into a HTML page using the wttr-switcher. That is how it looks like: wttr-switcher-example or on a real world web site: https://feuerwehr-eisolzried.de/.

\n

\"Embedded

\n

One-line output

\n

One-line output format is convenient to be used to show weather info
\nin status bar of different programs, such as tmux, weechat, etc.

\n

For one-line output format, specify additional URL parameter format:

\n
$ curl wttr.in/Nuremberg?format=3\nNuremberg: 🌦 +11⁰C\n
\n

Available preconfigured formats: 1, 2, 3, 4 and the custom format using the percent notation (see below).

\n\n

You can specify multiple locations separated with : (for repeating queries):

\n
$ curl wttr.in/Nuremberg:Hamburg:Berlin?format=3\nNuremberg: 🌦 +11⁰C\n
\n

Or to process all this queries at once:

\n
$ curl -s 'wttr.in/{Nuremberg,Hamburg,Berlin}?format=3'\nNuremberg: 🌦 +11⁰C\nHamburg: 🌦 +8⁰C\nBerlin: 🌦 +8⁰C\n
\n

To specify your own custom output format, use the special %-notation:

\n
    c    Weather condition,\n    C    Weather condition textual name,\n    x    Weather condition, plain-text symbol,\n    h    Humidity,\n    t    Temperature (Actual),\n    f    Temperature (Feels Like),\n    w    Wind,\n    l    Location,\n    m    Moon phase 🌑🌒🌓🌔🌕🌖🌗🌘,\n    M    Moon day,\n    p    Precipitation (mm/3 hours),\n    P    Pressure (hPa),\n    u    UV index (1-12),\n\n    D    Dawn*,\n    S    Sunrise*,\n    z    Zenith*,\n    s    Sunset*,\n    d    Dusk*,\n    T    Current time*,\n    Z    Local timezone.\n\n(*times are shown in the local timezone)\n
\n

So, these two calls are the same:

\n
    $ curl wttr.in/London?format=3\n    London: ⛅️ +7⁰C\n    $ curl wttr.in/London?format=\"%l:+%c+%t\\n\"\n    London: ⛅️ +7⁰C\n
\n

tmux

\n

When using in tmux.conf, you have to escape % with %, i.e. write there %% instead of %.

\n

The output does not contain new line by default, when the %-notation is used, but it does contain it when preconfigured format (1,2,3 etc.)
\nare used. To have the new line in the output when the %-notation is used, use '\\n' and single quotes when doing a query from the shell.

\n

In programs, that are querying the service automatically (such as tmux), it is better to use some reasonable update interval. In tmux, you can configure it with status-interval.

\n

If several, : separated locations, are specified in the query, specify update period
\nas an additional query parameter period=:

\n
set -g status-interval 60\nWEATHER='#(curl -s wttr.in/London:Stockholm:Moscow\\?format\\=\"%%l:+%%c%%20%%t%%60%%w&period=60\")'\nset -g status-right \"$WEATHER ...\"\n
\n

\"wttr.in

\n

WeeChat

\n

To embed in to an IRC (WeeChat) client's existing status bar:

\n
/alias add wttr /exec -pipe \"/mute /set plugins.var.wttr\" url:wttr.in/Montreal?format=%l:+%c+%f+%h+%p+%P+%m+%w+%S+%s;/wait 3 /item refresh wttr\n/trigger add wttr timer 60000;0;0 \"\" \"\" \"/wttr\"\n/item add wttr \"\" \"${plugins.var.wttr}\"\n/eval /set weechat.bar.status.items ${weechat.bar.status.items},spacer,wttr\n/eval /set weechat.startup.command_after_plugins ${weechat.startup.command_after_plugins};/wttr\n/wttr\n
\n

\"wttr.in

\n

conky

\n

Conky usage example:

\n
${texeci 1800 curl wttr.in/kyiv_0pq_lang=uk.png\n  | convert - -transparent black $HOME/.config/conky/out.png}\n${image $HOME/.config/conky/out.png -p 0,0}\n
\n

\"wttr.in

\n

IRC

\n

IRC integration example:

\n\n

Emojis support

\n

To see emojis in terminal, you need:

\n
    \n
  1. Terminal support for emojis (was added to Cairo 1.15.8);
    2. \n
  2. Font with emojis support.
    3. \n
\n

For the emoji font, we recommend Noto Color Emoji, and a good alternative option would be the Emoji One font;
\nboth of them support all necessary emoji glyphs.

\n

Font configuration:

\n
$ cat ~/.config/fontconfig/fonts.conf\n<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n<!DOCTYPE fontconfig SYSTEM \"fonts.dtd\">\n<fontconfig>\n  <alias>\n    <family>serif</family>\n    <prefer>\n      <family>Noto Color Emoji</family>\n    </prefer>\n  </alias>\n  <alias>\n    <family>sans-serif</family>\n    <prefer>\n      <family>Noto Color Emoji</family>\n    </prefer>\n  </alias>\n  <alias>\n    <family>monospace</family>\n    <prefer>\n      <family>Noto Color Emoji</family>\n    </prefer>\n  </alias>\n</fontconfig>
\n

(to apply the configuration, run fc-cache -f -v).

\n

In some cases, tmux and the terminal understanding of some emoji characters may differ, which may
\ncause strange effects similar to that described in #579.

\n

Squeak

\n

To embed into the world main docking bar:

\n
wttr := (UpdatingStringMorph on: [(WebClient httpGet: 'https://wttr.in/?format=%20%20%l:%20%C+%t') content] selector: #value)\n\tstepTime: 60000;\n\tuseStringFormat;\n\tyourself.\ndockingBar := World mainDockingBars first.\ndockingBar addMorph: wttr after: (dockingBar findA: ClockMorph).
\n

\"wttr.in

\n

Data-rich output format (v2)

\n

In the experimental data-rich output format, that is available under the view code v2,
\na lot of additional weather and astronomical information is available:

\n\n
  $ curl v2.wttr.in/München\n
\n

or

\n
  $ curl wttr.in/München?format=v2\n
\n

or, if you prefer Nerd Fonts instead of Emoji, v2d (day) or v2n (night):

\n
  $ curl v2d.wttr.in/München\n
\n

\"data-rich

\n

(The mode is experimental, and it has several limitations currently:

\n\n

Currently, you need some tweaks for some terminals, to get the best possible visualization.

\n

URXVT

\n

Depending on your configuration you might be taking all steps, or only a few. URXVT currently doesn't support emoji related fonts, but we can get almost the same effect using Font-Symbola. So add to your .Xresources file the following line:

\n
    xft:symbola:size=10:minspace=False\n
\n

You can add it after your preferred font and it will only show up when required.
\nThen, if you see or feel like you're having spacing issues, add this: URxvt.letterSpace: 0
\nFor some reason URXVT sometimes stops deciding right the word spacing and we need to force it this way.

\n

The result, should look like:

\n

\"URXVT

\n

Map view (v3)

\n

In the experimental map view, that is available under the view code v3,
\nweather information about a geographical region is available:

\n
    $ curl v3.wttr.in/Bayern.sxl\n
\n

\"v3.wttr.in/Bayern\"

\n

or directly in browser:

\n\n

The map view currently supports three formats:

\n\n

Terminal with inline images protocols support:

\n

⟶ Detailed article: Images in terminal

\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
TerminalEnvironmentImages supportProtocol
uxtermX11yesSixel
mltermX11yesSixel
kittyX11yesKitty
weztermX11yesIIP
DarktileX11yesSixel
JexerX11yesSixel
GNOME TerminalX11in-progressSixel
alacrittyX11in-progressSixel
footWaylandyesSixel
DomTermWebyesSixel
YaftFByesSixel
iTerm2Mac OS XyesIIP
minttyWindowsyesSixel
Windows TerminalWindowsin-progressSixel
RLoginWindowsyesSixel
\n

Different output formats

\n

JSON output

\n

The JSON format is a feature providing access to wttr.in data through an easy-to-parse format, without requiring the user to create a complex script to reinterpret wttr.in's graphical output.

\n

To fetch information in JSON format, use the following syntax:

\n
$ curl wttr.in/Detroit?format=j1\n
\n

This will fetch information on the Detroit region in JSON format. The j1 format code is used to allow for the use of other layouts for the JSON output.

\n

The result will look something like the following:

\n
{\n\t\"current_condition\": [\n\t\t{\n\t\t    \"FeelsLikeC\": \"25\",\n\t\t    \"FeelsLikeF\": \"76\",\n\t\t    \"cloudcover\": \"100\",\n\t\t    \"humidity\": \"76\",\n\t\t    \"observation_time\": \"04:08 PM\",\n\t\t    \"precipMM\": \"0.2\",\n\t\t    \"pressure\": \"1019\",\n\t\t    \"temp_C\": \"22\",\n\t\t    \"temp_F\": \"72\",\n\t\t    \"uvIndex\": 5,\n\t\t    \"visibility\": \"16\",\n\t\t    \"weatherCode\": \"122\",\n\t\t    \"weatherDesc\": [\n\t\t\t{\n\t\t\t    \"value\": \"Overcast\"\n\t\t\t}\n\t\t    ],\n\t\t    \"weatherIconUrl\": [\n\t\t\t{\n\t\t\t    \"value\": \"\"\n\t\t\t}\n\t\t    ],\n\t\t    \"winddir16Point\": \"NNE\",\n\t\t    \"winddirDegree\": \"20\",\n\t\t    \"windspeedKmph\": \"7\",\n\t\t    \"windspeedMiles\": \"4\"\n\t\t}\n\t],\n...
\n

Most of these values are self-explanatory, aside from weatherCode. The weatherCode is an enumeration which you can find at either the WorldWeatherOnline website or in the wttr.in source code.

\n

Prometheus Metrics Output

\n

The Prometheus Metrics format is a feature providing access to wttr.in data through an easy-to-parse format for monitoring systems, without requiring the user to create a complex script to reinterpret wttr.in's graphical output.

\n

To fetch information in Prometheus format, use the following syntax:

\n
$ curl wttr.in/Detroit?format=p1\n
\n

This will fetch information on the Detroit region in Prometheus Metrics format. The p1 format code is used to allow for the use of other layouts for the Prometheus Metrics output.

\n

A possible configuration for Prometheus could look like this:

\n
    - job_name: 'wttr_in_detroit'\n        static_configs:\n            - targets: ['wttr.in']\n        metrics_path: '/Detroit'\n        params:\n            format: ['p1']
\n

The result will look something like the following:

\n
# HELP temperature_feels_like_celsius Feels Like Temperature in Celsius\ntemperature_feels_like_celsius{forecast=\"current\"} 7\n# HELP temperature_feels_like_fahrenheit Feels Like Temperature in Fahrenheit\ntemperature_feels_like_fahrenheit{forecast=\"current\"} 45\n[truncated]\n
\n

...

\n

Moon phases

\n

wttr.in can also be used to check the phase of the Moon. This example shows how to see the current Moon phase
\nin the full-output mode:

\n
$ curl wttr.in/Moon\n
\n

Get the moon phase for a particular date by adding @YYYY-MM-DD:

\n
$ curl wttr.in/Moon@2016-12-25\n
\n

The moon phase information uses pyphoon as its backend.

\n

To get the moon phase information in the online mode, use %m:

\n
$ curl wttr.in/London?format=%m\n🌖\n
\n

Keep in mind that the Unicode representation of moon phases suffers 2 caveats:

\n\n

See #247, #364 for the corresponding tracking issues,
\nand pyphoon#1 for pyphoon. Any help is welcome.

\n

Internationalization and localization

\n

wttr.in supports multilingual locations names that can be specified in any language in the world
\n(it may be surprising, but many locations in the world don't have an English name).

\n

The query string should be specified in Unicode (hex-encoded or not). Spaces in the query string
\nmust be replaced with +:

\n
$ curl wttr.in/станция+Восток\nWeather report: станция Восток\n\n               Overcast\n      .--.     -65 – -47 °C\n   .-(    ).   ↑ 23 km/h\n  (___.__)__)  15 km\n               0.0 mm\n
\n

The language used for the output (except the location name) does not depend on the input language
\nand it is either English (by default) or the preferred language of the browser (if the query
\nwas issued from a browser) that is specified in the query headers (Accept-Language).

\n

The language can be set explicitly when using console clients by using command-line options like this:

\n
curl -H \"Accept-Language: fr\" wttr.in\nhttp GET wttr.in Accept-Language:ru\n
\n

The preferred language can be forced using the lang option:

\n
$ curl wttr.in/Berlin?lang=de\n
\n

The third option is to choose the language using the DNS name used in the query:

\n
$ curl de.wttr.in/Berlin\n
\n

wttr.in is currently translated into 54 languages, and the number of supported languages is constantly growing.

\n

See /:translation to learn more about the translation process,
\nto see the list of supported languages and contributors, or to know how you can help to translate wttr.in
\nin your language.

\n

\"Queries

\n

Installation

\n

To install the application:

\n
    \n
  1. Install external dependencies
    2. \n
  2. Install Python dependencies used by the service
    3. \n
  3. Configure IP2Location (optional)
    4. \n
  4. Get a WorldWeatherOnline API and configure wego
    5. \n
  5. Configure wttr.in
    6. \n
  6. Configure the HTTP-frontend service
    7. \n
\n

Install external dependencies

\n

wttr.in has the following external dependencies:

\n\n

After you install golang, install wego:

\n
go install github.com/schachmat/wego@latest
\n

Install Python dependencies

\n

Python requirements:

\n\n

If you want to get weather reports as PNG files, you'll also need to install:

\n\n

You can install most of them using pip.

\n

Some python package use LLVM, so install it first:

\n
apt-get install llvm-7 llvm-7-dev
\n

If virtualenv is used:

\n
virtualenv -p python3 ve\nve/bin/pip3 install -r requirements.txt\nve/bin/python3 bin/srv.py
\n

Also, you need to install the geoip2 database.
\nYou can use a free database GeoLite2 that can be downloaded from (http://dev.maxmind.com/geoip/geoip2/geolite2/).

\n

Configure IP2Location (optional)

\n

If you want to use the IP2location service for IP-addresses that are not covered by GeoLite2,
\nyou have to obtain a API key of that service, and after that save into the ~/.ip2location.key file:

\n
$ echo 'YOUR_IP2LOCATION_KEY' > ~/.ip2location.key\n
\n

If you don't have this file, the service will be silently skipped (it is not a big problem,
\nbecause the MaxMind database is pretty good).

\n

Installation with Docker

\n\n
/root/.wegorc\n/root/.ip2location.key (optional)\n/app/airports.dat\n/app/GeoLite2-City.mmdb\n
\n

Get a WorldWeatherOnline key and configure wego

\n

To get a WorldWeatherOnline API key, you must register here:

\n
https://developer.worldweatheronline.com/auth/register\n
\n

After you have a WorldWeatherOnline key, you can save it into the
\nWWO key file: ~/.wwo.key

\n

Also, you have to specify the key in the wego configuration:

\n
$ cat ~/.wegorc\n{\n\t\"APIKey\": \"00XXXXXXXXXXXXXXXXXXXXXXXXXXX\",\n\t\"City\": \"London\",\n\t\"Numdays\": 3,\n\t\"Imperial\": false,\n\t\"Lang\": \"en\"\n}
\n

The City parameter in ~/.wegorc is ignored.

\n

Configure wttr.in

\n

Configure the following environment variables that define the path to the local wttr.in
\ninstallation, to the GeoLite database, and to the wego installation. For example:

\n
export WTTR_MYDIR=\"/home/igor/wttr.in\"\nexport WTTR_GEOLITE=\"/home/igor/wttr.in/GeoLite2-City.mmdb\"\nexport WTTR_WEGO=\"/home/igor/go/bin/wego\"\nexport WTTR_LISTEN_HOST=\"0.0.0.0\"\nexport WTTR_LISTEN_PORT=\"8002\"
\n

Configure the HTTP-frontend service

\n

It's recommended that you also configure the web server that will be used to access the service:

\n
server {\n\tlisten [::]:80;\n\tserver_name  wttr.in *.wttr.in;\n\taccess_log  /var/log/nginx/wttr.in-access.log  main;\n\terror_log  /var/log/nginx/wttr.in-error.log;\n\n\tlocation / {\n\t    proxy_pass         http://127.0.0.1:8002;\n\n\t    proxy_set_header   Host             $host;\n\t    proxy_set_header   X-Real-IP        $remote_addr;\n\t    proxy_set_header   X-Forwarded-For  $remote_addr;\n\n\t    client_max_body_size       10m;\n\t    client_body_buffer_size    128k;\n\n\t    proxy_connect_timeout      90;\n\t    proxy_send_timeout         90;\n\t    proxy_read_timeout         90;\n\n\t    proxy_buffer_size          4k;\n\t    proxy_buffers              4 32k;\n\t    proxy_busy_buffers_size    64k;\n\t    proxy_temp_file_write_size 64k;\n\n\t    expires                    off;\n\t}\n}
","updatedAt":"2025-05-22T01:53:30Z","upvoteCount":null,"author":{"login":"eryajf","avatarUrl":"https://avatars.githubusercontent.com/u/33259379?u=e4a4090a38ac2473aaed4ef9945233636776c6c3&v=4","url":"https://github.com/eryajf"},"category":null,"labels":{"edges":[{"node":{"name":"更多","color":"25B472"}},{"node":{"name":"命令行工具","color":"e05879"}},{"node":{"name":"chubin","color":"73564b"}}]},"comments":{"edges":[]}}},"pageContext":{"number":613,"previous":{"title":"axetroy/wsm: 通过 Web 来管理远端服务器，简易的堡垒机","number":612},"next":{"title":"enix/x509-certificate-exporter: Prometheus 导出器用于监控 Kubernetes 集群或独立系统中的 x509 证书过期情况","number":614}}}, "staticQueryHashes": ["151096407","2861350382"]}