For property listings & location tools
Help people understand how loud an address could be.
Add modelled outdoor day and night noise estimates to your product with a coordinate API or an embeddable map. Start with eight Canadian city regions.
A precomputed model of period averages. It does not measure a property, predict indoor noise or show live traffic.
Try the data
A real response from the demo
Sample: Toronto, near the Gardiner Expressway and Spadina Avenue. The values below are fetched from the public service when you open this page.
Public demo response
Waiting for the service…
Where it works
Eight city regions
Coverage is bounded by the modelled extracts, not municipal or postal boundaries. A covered region can still contain locations with no valid model estimate.
- Loading coverage…
Traffic input coverage varies by region. A regional count-match summary is not an address-level confidence score.
Integration
One coordinate lookup. Both periods.
- Tell us your use case, required cities and expected monthly volume.
- Receive a pilot key for your server. Geocode addresses separately using your chosen provider.
- Call
/v1/noisefor a point or/v1/noise/batchfor up to 100 locations. Handle missing data explicitly. - Display the model date, limitations and OpenStreetMap attribution alongside the result.
Keep API keys on your backend. The public iframe below needs no key. Pilot pricing, permitted use, refresh expectations and any service commitment are agreed before launch.
Server-side request
Placeholder key only. This request is for your server; customer keys are never embedded in this page.
Widget preview
Embed the public map
This first widget uses the public demo and its request limits. Attribution, methodology and day/night controls remain available. A custom customer-hosted integration needs its allowed origin configured separately.
What the estimate can tell you
These are modelled outdoor averages: LAeq,16h by day and LAeq,8h by night. Individual building shielding, terrain and barriers are approximated rather than traced. Rail frequency, aircraft operations and typical site activity include assumptions. Events such as construction or sirens are not predicted.
There is no independently established error range for an individual address. Historical Toronto population-exposure comparisons are partly fitted and describe distributions, not measured property accuracy. Missing estimates should never be labelled “quiet”.
The quiet score is a 50–100 display scale, not a percentile or health rating. The hosted API serves a combined noise raster; it does not currently identify each source's contribution at a point.
Bring one use case to the pilot.
Send a few example locations, the cities you need and how you want to display noise. We can agree on a useful first integration.
Request a pilot →