mapbench

February 2, 2026 · 7 min read · MapBench editorial

Hardiness Zones & Climate Codes: Will It Grow Here?

A hardiness zone is one brutal statistic wearing a friendly number: the average coldest temperature your winter delivers, banded into the zones printed on every seed rack. It answers exactly one question — will this plant survive your worst night? — which is not the same as will it thrive, and the gap between those verbs is where gardens are won and lost. Get your zone from real data (twenty-plus winters of minima at your coordinates, not a remembered map) and you've bought the foundation, not the house.

The Köppen letter next to it widens the picture: is your rain seasonal or steady, is your summer Mediterranean-dry or humid-subtropical sticky? Two gardens in the same hardiness zone can be opposites on water logic — a Csb coast that never hurries and a Dfa interior that floods and bakes. The climate zone finder shows both the code and the monthly normals that produced it, and reading that small table is the cheapest horticultural education available.

The microclimate clause

  • South walls borrow half a zone; cold-air pockets lend one back at 4 am.
  • Slopes drain frost like water; the bottom of the bowl is the last to thaw.
  • Urban heat is real: city gardens routinely run a zone warmer than their postcode.
  • So the zone is your starting bid, and your garden's corners are the negotiation.

And plants run on two calendars, not one: pair the zone with the daylight chart, because a tomato that survives your winter still sulks without your summer's light budget. Used together — zone for the worst night, Köppen for the water logic, daylight for the growing season — three free numbers replace a shelf of folklore. The seed packet finally means something, and 'will it grow here?' becomes the honest, answerable question it always pretended to be.

The toolkit behind this post, in depth

USDA Hardiness Zone Finder

Plant hardiness zones track one brutally practical statistic: the average annual extreme minimum temperature, banded into the zones printed on every seed rack in the English-speaking gardening world. This tool computes yours from first principles — 24 winters of daily minima from the ERA5 reanalysis at your exact coordinates, averaged the way the concept intends, then mapped onto USDA band widths of roughly 5.6 °C per zone — and shows both the zone and the underlying extreme so you can judge the margin yourself.

The page keeps the microclimate truth front and centre: walls, slopes, urban heat and cold-air pools shift a real garden half a zone or more, so the result is guidance beside the USDA map, not a replacement for it. Still, as a screening number it is superb — compare two houses' gardens, understand why a neighbour's fig survives and yours sulks, or plan a move's planting palette before the boxes are packed. It pairs with the Köppen finder for the wider climate picture and the daylight chart for the other half of a plant's calendar, completing a genuinely useful horticultural corner of the platform.

Climate Zone Finder (Köppen)

The Köppen system remains the world's shared shorthand for climate — Af rainforest, Csa Mediterranean, Dfb snowy continental — because its letters compress exactly the right facts: how cold the winter gets, whether rain has a season, whether summers burn. This tool computes your point's classification the rigorous way: thirty years of monthly temperature and precipitation normals from the ERA5 reanalysis, run through the standard threshold tree, with the resulting code, a plain-language label, and the monthly normal table that produced it.

The page prints its method because the method is the honesty: main groups follow the textbook thresholds, rare subtypes are merged and labelled as such, and the 1991–2020 window is the conventional 'climate normal' rather than this year's weather. Use it to understand a move ('why do my plants sulk here?'), to sanity-check a garden centre's advice, to compare two cities beyond their postcards, or to teach the system with live examples. It sits beside the hardiness finder and the daylight chart — three lenses on the same climate — and like everything here it is free, accountless, and reproducible from the URL.

Daylight Hours Calculator (Year Chart)

Single-day daylight figures hide the story; the story is the curve. Pick any place on Earth and this tool computes day length for the entire year with the same NOAA-grade solar math as the sunrise calculator, then draws it as one continuous chart — flat and calm near the equator, gently seasonal at mid-latitudes, dramatic to the point of snapping at the polar circles. The longest and shortest days come labelled with their dates, so 'how dark will December be in Tromsø?' stops being folklore and becomes a readable shape.

The curve is latitude's signature, which makes the chart a teaching instrument as much as a planning one: compare two cities and you are comparing their light climates, with consequences for mood, gardening, solar yield and photography. Daylight here means geometric sun-above-horizon time — clouds belong to the climate tools, and the page says so. Use it to set expectations before a move or a trip, to time a planting schedule, or to understand why your new city's evenings feel 'wrong' in June. One search, one curve, a year of light made legible.

Elevation Finder

Click the map or paste coordinates and this tool reports the ground elevation at that exact point, in metres and feet, sampled from the Copernicus GLO-90 global digital elevation model via the free Open-Meteo elevation API. No account, no key, real satellite-derived terrain data at roughly 90-metre resolution. Sample several points to compare a site's high and low corners, check a pass before a trip, or settle the 'how high is my town' question with a number instead of a guess.

Two honesty notes stay attached to every result: the value is terrain height above sea level, not building altitude, and DEM vertical accuracy is typically a few metres — better on open flat ground, noisier under steep slopes and forest canopy. For survey-grade work, national geodetic benchmarks remain authoritative. The point is shareable via URL, and the tool chains naturally into the elevation profile for a line, the line-of-sight calculator for visibility, and the horizon calculator for how far that height lets you see.

Reading the third dimension: terrain, visibility and deep time

Everything on a flat map is a rumour about height. Digital elevation models — satellite-derived grids like Copernicus GLO-90 at roughly 90 metres — turn the rumour into numbers: ground height at any coordinate, cross-sections along any line, ascent and descent totals for any route sketch. The models see terrain, not trees or buildings, and vertical accuracy of a few metres is typical; knowing that is the difference between using them wisely and over-trusting them.

Visibility questions add physics. Over open ground the horizon sits at about 3.86 × √(height in metres) kilometres once standard atmospheric refraction is included; between two observers the ranges add. Between specific points, terrain enters through the same DEM: sample the line, add Earth-curvature drop with the conventional refraction coefficient, and the verdict — clear or blocked, and where — follows by comparison. It is telecom planning's classic calculation, now comfortably runnable in a browser.

The deep-time companions — antipodes, climate zones, hardiness bands, seismicity — reframe your point on longer clocks. The antipode is pure geometry with a geographic punchline (usually ocean). Köppen classes and hardiness zones compress thirty years of temperature and precipitation into letters that gardeners and planners trust. Recent earthquakes are the live signature of faults. Each is an estimate with a stated recipe; together they make a portrait of place that no street map can offer.

Using terrain intelligence without overclaiming it

Digital elevation models transformed what amateurs can ask of terrain, and they also created a new overconfidence: a number with decimals feels surveyed. Hold the model's nature in mind — a ~90 m grid of bare-earth heights, vertical error of a few metres, blind to buildings and canopies — and every output slots into its proper weight. Elevation at a point: planning-grade. A profile: the shape of the truth with noisy amplitude. Line-of-sight: terrain's answer, pending trees and towers. Horizon: curvature plus standard refraction over open ground. Each is genuinely useful; none is the last word.

The longer-clock tools carry the same lesson at larger scale. A Köppen letter compresses thirty years of weather into climate's shorthand; a hardiness zone compresses winter extremes into a gardener's number; recent seismicity sketches a fault's mood. Used as orientation — choosing crops, siting panels, understanding a region's tectonic character — they are superb. Used as guarantees, they fail. The discipline is to print the recipe with the result, which is what honest tools do by default.

  • Attach the model and vintage to every terrain number you republish (e.g. 'Copernicus GLO-90 via Open-Meteo').
  • For visibility work, add land cover from local knowledge after the terrain verdict, not before.
  • Average multiple years for climate-adjacent numbers; single-year values are weather wearing climate's coat.
  • When a decision is expensive, upgrade terrain from DEM to survey — the tool's job is to tell you when that matters.

Honest limits & when to escalate

Terrain intelligence carries one dominant limit: the model sees bare earth at ~90 m spacing with metres of vertical error, and is blind to canopies, walls and wires. Every downstream answer inherits it — profiles show terrain truth with noisy amplitude, line-of-sight verdicts are pending trees, horizons assume open ground, and solar radiation averages assume an unshaded panel. The second limit is temporal: climate letters and hardiness zones are thirty-year character, not this year's behaviour, and seismicity is a mood, not a hazard model. Each result here is printed with its recipe precisely so these boundaries travel with the number.

The value proposition is screening-grade truth at zero cost: orientation for sites, gardens, antennas, shoots and curiosity, with the upgrade points clearly marked. When money or safety attaches to the answer — tower siting, flood insurance, structural shading, avalanche terrain — the escalation is professional: licensed survey, certified shade studies, regulatory flood determinations and geological hazard services. A good free tool makes that ladder visible instead of pretending to be the top of it.

  • Construction and tower siting → licensed topographic survey.
  • Flood decisions → regulatory determinations (FEMA/FIRM in the US).
  • Solar finance → certified shade and production studies.
  • Seismic safety → national hazard models and building codes.

Step-by-step masterclass

  1. State the model with the number'Copernicus GLO-90, ~90 m, ±few metres vertical' turns an elevation claim from vibes into a citable fact.
  2. Add heights explicitlyEye height, mast height, deck level — visibility answers are unreproducible without them, and the tools here keep them as named inputs.
  3. Layer land cover after terrainThe DEM sees bare earth; woods and walls are local knowledge you add after the curvature verdict, not before.
  4. Average years, not daysClimate letters and hardiness zones want 30-year character; single-year values are weather wearing climate's coat.
  5. Escalate when it's expensiveDEM for screening, licensed survey for decisions with money attached — knowing the upgrade point is the professionalism.

Terrain data is genuinely global (satellites don't respect borders), but its texture varies: flat plains resolve beautifully, steep forested relief noisier; seismicity tools are worldwide via USGS, while mapped fault and flood layers are US-first — the scope chips on each tool state exactly where each answer stands.

Tips & common mistakes

Remember that elevation models see bare terrain: no buildings, no forest canopy. A line-of-sight 'clear' verdict can still be blocked by a wood, and a horizon distance assumes open ground — treat results as the terrain baseline, then add land cover from local knowledge.

Include your height inputs explicitly (eye height, mast height, deck level) when sharing visibility results: the same hill answers differently for a child, an adult and a 10 m antenna, and unstated heights make numbers unreproducible.

Treat climate and hardiness outputs as 30-year character, not this year's weather: a zone tells you what winters usually allow, and microclimates — walls, slopes, urban heat — shift a real garden half a zone either way.

Quick glossary

  • DEM: Digital elevation model: a grid of terrain heights, e.g. Copernicus GLO-90.
  • Refraction coefficient: The standard 0.13 factor bending sightlines over the curvature.
  • Antipode: The diametrically opposite point; latitude flips, longitude shifts 180°.
  • Köppen class: The letter-code climate system from temperature/precipitation thresholds.

Two more questions, answered

Why does my profile differ from my GPS track?

The profile samples terrain truth; your track carries device noise and bridges. Compare shape, not amplitude.

Is Köppen stable under climate change?

The classes shift over decades — compute with recent normals and date the result, as this tool does.