Weather Forecast and History by Place Name avatar

Weather Forecast and History by Place Name

Pricing

Pay per event

Go to Apify Store
Weather Forecast and History by Place Name

Weather Forecast and History by Place Name

Hourly weather for any place, by name or coordinates, up to 16 days ahead and 92 days back. Every row carries both the local time and a real UTC instant, so readings from different locations are actually comparable. No key and no login.

Pricing

Pay per event

Rating

0.0

(0)

Developer

Gregory Bolshakov

Gregory Bolshakov

Maintained by Community

Actor stats

0

Bookmarked

1

Total users

0

Monthly active users

5 days ago

Last modified

Share

Hourly weather for any place, given a name or a coordinate pair. Up to 16 days ahead and 92 days back, in one flat table.

The timestamp problem, which is the reason this exists

Open-Meteo returns the same timestamp string whether it answered in GMT or in Tokyo. Only a separate utc_offset_seconds field says which moment it is.

Tokyo localTime 2026-08-30T00:00 really 2026-08-29T15:00Z
London localTime 2026-08-30T00:00 really 2026-08-30T00:00Z

Put two locations in one table and the timestamps look comparable and are not. Sort by them and you get nonsense. Join two locations on time and you join the wrong hours together.

Every row here carries both. localTime is the reading in the location's own clock, which is what you want for a chart of one place. utcTime is the real instant, which is what you need the moment there is more than one location in the file.

Place names

Type London, or 51.5,-0.13 if you already know the point.

A bare name that matches several places resolves to the most populated one, and the run summary lists the rest under otherPlacesWithThisName. Springfield is five real towns in the United States alone. Pass coordinates when you need a specific one.

A name that matches nothing is reported as not found. It is never quietly resolved to somewhere nearby.

Null is not zero

A null reading means the model has no value for that hour. It is left null rather than filled with a zero, which matters most for precipitation, where zero is a real and very common answer and the two are easy to confuse.

Units are recorded on every row, because they depend on which variables you asked for.

Output

One row per location per hour. Location, coordinates, elevation, timezone, both timestamps, then one column per variable you selected.

Access

Free, no key, no login. Ten rapid requests with no pacing all returned 200, so it does not throttle at the rate this Actor works at.