Weather Lookup

Current weather and a 7-day forecast for any city. No account, no API key — data straight from Open-Meteo.

About this tool

Weather sites usually show you more than you asked for: radar maps, ten-day models, air-quality charts, three ad slots. If all you want is "what is it like outside in Lisbon right now", most of that is noise.

This page does one thing: it turns a city name into coordinates, asks Open-Meteo for the current conditions and a forecast, and shows you the result. Forecast times are given in the local time of the place you looked up — not in your own time zone, which is the usual way these pages get confusing when you are checking on somewhere far away.

Nothing is stored on a server. Your last lookup and your unit preference stay in your own browser, and the coordinates never pass through us — the request goes from your browser straight to the weather service.

Why a dozen weather codes collapse into one label

Open-Meteo reports weather as WMO 4677 codes — over twenty of them. This tool merges them into fourteen labels, because the difference between light, moderate and heavy rain matters far less than whether it is raining at all. Codes it does not recognise fall back to “Unknown”.

The raw scale is finer than the interface needs. Drizzle arrives as three codes, rain as three more, and snow, showers and thunderstorms as three each; every group is flattened to a single label. What survives the merge is the difference in kind rather than in degree: freezing rain is kept apart from rain, and snow grains apart from snow, because those describe different things happening, where light or heavy is only a question of how much.

The mapping lives in the logic layer, not the language packs. It produces short semantic keys such as clear or freezingRain, and the wording for each comes from the locale file — which is why the same merged code reads as “Gefrierender Regen” in German and 冻雨 in Chinese. A code that is missing from the table resolves to “Unknown”, so a new value from the source degrades to a plainer label instead of an empty cell.

Because the list of keys is fixed and public, the build checks that every locale defines all fourteen. Making one distinction finer means splitting a code in the mapping table and adding the key to all four language files at once — the change cannot land half-finished.

How a wind angle becomes one of eight compass points

A wind direction arrives as a number of degrees. The tool normalises it into 0–360, divides by 45 and rounds to the nearest whole step, which gives one of eight points: N, NE, E, SE, S, SW, W, NW. Each point covers a 45-degree sector centred on it.

The rounding is what fixes the boundaries. North is not a point at 0 degrees; it is the whole span from 337.5 up to 22.5, because 337.5 divided by 45 rounds to 8, and the remainder modulo 8 wraps back to the first entry in the list. A reading of 340 degrees is therefore shown as north rather than northwest — close enough to the boundary that a one-degree shift in the source would flip the label.

The eight names are translated rather than shown as bare letters. English and German use the familiar N, NO, O set, while Japanese writes 北東 and Chinese 东北风, literally “northeast wind”. The four cardinal directions N, E, S, W are near-universal, but the four diagonals are where each language wants a word of its own.

If the direction is absent, or is not a finite number, the function returns null and the page simply drops the compass point, leaving the wind speed on its own. There is no replacement arrow and no default to north — a wind with no known direction is shown without one.

Why switching units re-fetches instead of converting

Changing from Celsius to Fahrenheit does not multiply the numbers already on screen. It adds temperature_unit and wind_speed_unit to the next request and asks Open-Meteo again, because the service converts temperature, wind and precipitation in one pass — rebuilt locally, it would be easy to get half of it wrong.

A local conversion would have to touch every value that carries a unit: the current temperature, the feels-like reading, each daily high and low, and the wind speed. Miss one and the page shows a mixture — Fahrenheit in the headline, Celsius in the rows below. Letting the source convert keeps them consistent, and the wind speed comes back in the matching unit in the same request.

The preference is remembered between visits, and it is stored in your own browser rather than on a server. When you return, the page fetches with your saved unit already applied, so the first thing on screen is in the units you last chose.

Because the unit only ever changes what is requested, everything behind it — coordinates, dates, conditions — is identical in either system. Switching to imperial and back returns the same weather; only the numbers attached to it change.

This tool issues no requests of its own

Every lookup goes through the data layer: a place name is resolved to coordinates, then the coordinates to weather. The tool does not know whether that request goes direct from the browser or through an edge function — that decision stays in the layer.

A source has to be declared before use: the manifest lists which data sources the tool may call, and undeclared calls are refused by the client. That way which external services a given tool can reach is readable statically, instead of being scattered through the code and held in someone memory.

Fetching never throws; success or failure is in the return value. That convention buys something important: three very different failures can be told apart. No such place is an input problem, an upstream outage is worth retrying, and a source that is not wired up is a configuration problem that has nothing to do with the visitor, so telling them to try again would be misleading.

This makes weather the only tool on the site that reaches the network; everything else works with it switched off. Verifying that claim takes one step: disconnect, then open any other tool.

Frequently asked questions

Do I need an API key or an account?

No. The data comes from Open-Meteo, which is free and keyless for non-commercial use, and the request is made directly from your browser. There is nothing to register and nothing to configure.

Which time zone are the forecast times in?

The time zone of the place you searched, resolved from its coordinates. So if you look up Tokyo from Berlin, "as of 21:00" means 21:00 in Tokyo, and the day rows follow Tokyo days too.

How far ahead does the forecast go?

Seven days. Beyond about a week, day-to-day forecasts stop being useful information and start being decoration — a specific-looking number that is not really a prediction.

Why does it ask for my location?

Only if you press the button. Then your browser resolves your position locally and the coordinates go straight to the weather service. If you would rather not, just type a city name — that path is identical apart from where the coordinates come from.

What does the percentage on each day mean?

The highest chance of precipitation at any point during that day, in percent. It is a probability of any rain or snow falling at that location, not the share of the day you should expect to be wet.

Related tools