Coverage mapping that doesn't flatten the country's hill lines into a 30m grid.
Most coverage tools default to the same 30m global elevation model everywhere, which is a rough approximation over the kind of terrain a lot of New Zealand fixed wireless links actually cross. GridVisio pulls LINZ (Toitū Te Whenua)'s own 1m elevation data automatically wherever it's been flown — Canterbury Plains, the volcanic plateau, hill-country stations — and falls back gracefully where it hasn't.
A real link check running on LINZ-sourced terrain, not a generic global DEM
Why New Zealand WISPs end up here
Fixed wireless in New Zealand almost never means flat, open ground. The elevation pipeline, plan limits, and export options here were built around that, not adapted from a US tool afterward.
Real LINZ elevation, not SRTM
LINZ's 1m surface data — much of Canterbury has been resurveyed nine separate times since 2014 alone — is pulled in automatically wherever it's been flown. No setting to enable. Where it hasn't reached yet, links fall back to SRTM 30m instead of failing outright.
Real backhaul distances, not last-mile only
10km link length on Starter, 20km on Pro — enough for a genuine ridge-to-valley or across-the-sounds hop, not just a last-mile drop. Fresnel clearance, bearing, and FSPL computed the same way at any length.
Honest verdicts, not a confident guess
Clear, Borderline, or Obstructed — Borderline is flagged as inconclusive instead of rounded up either way. If a link result ends up in front of a funder, a partner, or your own install crew, it says the same thing every time it's opened.
Predicted signal, not just geometry
ITU-R P.1812 propagation prediction alongside the Fresnel check, extending to ITM or FSPL+P.526 outside its frequency range — a dBm number and, with a CPE model selected, an estimated Mbps. The same engine drives the RF Heatmap so numbers never contradict each other.
Find where to build next
Import your own subscriber list and GridVisio clusters unserved locations by density (DBSCAN), then estimates reach from a hypothetical tower before you commit to a site visit — one more way to compete on the ground where satellite alternatives are weakest: dense clusters, business-grade latency, an install crew that actually turns up.
Coverage widget for your own site
Embed an address-check widget on your website. A visitor's address gets a real LoS check against your nearest towers, not a polygon overlap — so the lead you receive already tells you which tower would serve them.
A ridge doesn't care that a competitor's tool assumed flat ground
A backhaul link along the Canterbury foothills, a hop across a bend in the Marlborough Sounds, a tower reaching into hill country above a river valley — these are exactly the cases where a coarse 30m elevation model quietly gets the answer wrong. LINZ's 1m resolution catches the spur, the tree line, or the roofline a generic DEM smooths straight through.
Where LINZ hasn't surveyed a given stretch yet, GridVisio doesn't just error out — it falls back to SRTM 30m automatically and tells you which source it actually used for that result, every time. You always know how much weight to put on the number in front of you.
Fresnel clearance computed against real 1m surface data, not a smoothed approximation
One coverage map, every layer you actually maintain
Towers and sectors, subscribers, saved LoS links, unserved clusters — all on one map, toggleable by layer. Run an RF Heatmap per sector or per tower and see predicted signal strength across your whole footprint, using the same propagation model as the link checker.
Export a clean PDF or PNG of any link check for a customer file, an internal record, or a funding or partner application — no extra formatting step, no per-file fee.
RF Heatmap for a sector, driven by the same propagation engine as the LoS checker
Frequently asked questions
Does GridVisio actually cover my part of New Zealand?
It depends on where LINZ has flown 1m elevation data, which covers a large and growing share of the country but isn't complete nationwide. Wherever it exists for a link or heatmap area, GridVisio uses it automatically. Outside that coverage, it falls back to SRTM 30m rather than refusing to run — and the result always states which source it used, so you're never guessing.
What's the difference between LINZ's data and the SRTM data most tools use everywhere?
SRTM is a 30m-resolution global radar dataset — fine for a rough first pass, but it can average away a ridge, a shelterbelt, or a roofline that sits inside a single 30m cell. LINZ's data is a 1m surface model, so features that actually intrude on a Fresnel zone show up instead of getting smoothed out.
Can this help with Rural Broadband Initiative or connectivity funding documentation?
GridVisio isn't a filing tool for RBI, NIFF, or any specific funding process and doesn't generate their application forms. What it gives you is exportable, defensible link and coverage data — terrain profile, Fresnel clearance, predicted signal strength — as a PDF or PNG you can attach to whatever documentation a given application requires.
Is pricing in New Zealand dollars?
Billing is in USD — $19/month Starter, $39/month Pro, both with a 14-day free trial and no credit card required to start. There's also a permanent $0 Free plan with core Starter features included.
Do I need to import my own subscriber and tower data?
Yes — towers, sectors, and subscribers are imported via CSV/XLSX or entered directly on the map. Once they're in, white area detection, reach estimates, and the RF Heatmap all run against your real network, not a sample dataset.
See your own network on real New Zealand terrain
14-day free trial — LoS checker, RF heatmap, white area detection, and more. No credit card required.
