# Answer for a named place in its local time

> Answer for a named place in its local time: 2 companies fully do it, 10 with a limit, 33 carry the tag. Every listing in Weather & climate data with the reason and a source.

- Canonical: https://www.anchorterminal.com/niches/weather.resolve-place/
- Markdown: https://www.anchorterminal.com/niches/weather.resolve-place/index.md (~1,450 tokens)
- Slim: https://www.anchorterminal.com/niches/weather.resolve-place/index.min.md (~380 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/niches/weather.resolve-place/index.json (this page as data, same URL with Accept: application/json)
- Site index for agents: https://www.anchorterminal.com/llms.txt (the key docs and every listing in one file, at most 16 MB, about 4 million tokens: https://www.anchorterminal.com/llms-full.txt)
- API: https://www.anchorterminal.com/api/v1/index.json
- MCP: https://www.anchorterminal.com/mcp (the whole catalogue as tools, no key)
- DNS: dig +short TXT <slug>.grade.anchorterminal.com (the grade as a DNS TXT record, for a sandbox with no HTTP where names still resolve; also top., best.<category>. and <a>.vs.<b>. under the zone, and the same under grade.letme.dev)
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)
- Updated: 2026-11-15

Two or three companies' docs show a full fit.

| Companies, full fit | With a limit | Carry the tag | Share of the category's work | First-hand accounts |
| --- | --- | --- | --- | --- |
| 2 | 10 | 33 | 10 | 5 |

## What counts as done

The place resolves to the intended coordinates, with the resolved name in the requested language, and every timestamp in the response carries the location's UTC offset or time zone name.

How agents ask for it: weather in Springfield; forecast for my postcode; what time is sunset there

## Does the job

The docs show it meets the test above, and nothing we read says otherwise.

- **meteoblue Weather API (meteoblue AG)**: The location search API ranks results by importance and population, localises names by locale path (Bâle for Basel), and returns timezone; forecasts take tz or detect it and return utc_timeoffset.
- **Xweather Weather API (Vaisala Oyj)**: p accepts coordinates, place names, postcodes, airports and more, /places/search ranks matches, lang sets the output language, and responses carry tzname and dateTimeISO with the local offset.

## Does the job, with a limit

It does the job, but something in the docs or a user's account will get in an agent's way. The limit is named in each row.

- **AccuWeather Core Weather API + MCP (AccuWeather Intl., LLC (API terms), AccuWeather, Inc. (privacy))**: Location search takes city names, postal codes, coordinates and points of interest and returns location keys with time zone information, but ranking of ambiguous matches was not shown in the pages read.
- **Google Weather API (Maps Platform) (Google LLC or a regional Google entity, by billing country)**: Location is latitude and longitude only, so a named place needs Google's separate Geocoding API; responses carry the time zone and local display times, and languageCode localises text.
- **Meteosource Weather MCP (Meteosource)**: search_places turns a name, postcode or coordinates into a place_id, but whether it returns ranked candidates or names in a chosen language isn't stated.
- **OpenWeather One Call API (OpenWeather Ltd)**: One Call takes coordinates only; names need the separate Geocoding API, which acc-14 found often resolves the wrong place. timezone_offset is given but timestamps stay UTC.
- **Pirate Weather (PirateWeatherAPI (Ontario, Canada))**: Accepts city,country as well as coordinates and returns nearestCity, nearestSubNational, timezone and offset, but no ranked candidates for an ambiguous name.
- **Tomorrow.io Weather API (The Tomorrow Companies Inc.)**: location accepts a place name and the response returns the resolved name and type; a timezone parameter can localise times. No ranked candidates, and acc-38 got UTC offsets of zero from Tomorrow.io.
- **Visual Crossing Weather API (Visual Crossing Corporation)**: Takes an address, partial address, postcode or coordinates and returns resolvedAddress with timezone and tzoffset, but no ranked candidates; lang translates conditions only and acc-34 got names in local script.
- **The Weather Company Data APIs (The Weather Company, LLC)**: Location Services resolve geocodes, postal keys, IP and IATA codes, and responses translate named fields by language with local times; contract-only access.
- **WeatherAPI.com (Zoomash Ltd)**: q takes a city, coordinates, postcode, IP and more, a search/autocomplete endpoint returns candidates, and the location object carries tz_id and localtime. lang translates condition text only, and acc-38 saw UTC offsets of zero via an integration.
- **Weatherbit API (Weatherbit LLC)**: Takes lat/lon, city with country, postal code or station, with a /geocode endpoint, and returns city_name and timezone; acc-38 found UTC offsets of zero via an integration.

- not this job: Met Office Weather DataHub (Site Specific) (Met Office, an executive agency of the UK government): The official script takes latitude and longitude only; includeLocationName returns a name for the point but there is no place search.
- not this job: Meteomatics Weather API (Meteomatics AG): Locations are coordinates, lines, polygons or country shortcuts; no place-name search was found, and times come back in UTC.
- not this job: NOAA National Weather Service API (api.weather.gov) (National Weather Service, NOAA, U.S. Department of Commerce): No place-name or postcode search; the API takes coordinates, grid cells, stations or zones only.
- not this job: Stormglass API (Storm Glass AB): Coordinates only, and the docs say every timestamp sent and received is UTC; local time is left to the caller.

## What stops agents finishing

- ambiguous names resolved without asking
- times returned in UTC with no offset

## Around it

Before: chat.user-names-place. After: weather.forecast, weather.current.

## Where this comes from

Weight 10 of 100 in Weather & climate data: 5 of 43 accounts: wrong places from name search, names in local script, crag points offset, UTC-only times in three APIs

As data: https://www.anchorterminal.com/api/v1/use-cases/weather.resolve-place.json, or the MCP tool get_use_case with id weather.resolve-place. Draft, read 2026-11-15 from public docs and first-hand accounts, not yet reviewed by a person.

---

Query this catalogue directly over MCP: https://www.anchorterminal.com/mcp (Streamable HTTP, no key). How: https://www.anchorterminal.com/agents/#mcp
