The Neighbourly Fisheries Management Zones API returns the boundaries of Ontario's 20 Fisheries Management Zones (FMZs) as GeoJSON. Find the zone for any lake, property or map view and match it to that zone's seasons and limits in the provincial regulations.
Ontario is divided into 20 Fisheries Management Zones, numbered 1 to 20. Fishing seasons, catch and possession limits and size rules are set by zone, so knowing which FMZ a lake is in is the first step to knowing the rules on it. This API returns each zone's boundary and number, ready to intersect with a coordinate, a lake or a map view.
Send a small viewport around a coordinate and get back its zone. Run it in bulk to tag every lake or listing in your database with its FMZ.
Boundaries are stored as pre-computed GeoJSON with a bounding box, so a province-wide zone overlay loads in one request.
The zone number is how Ontario's fishing regulations summary is organized, so it is a clean join key for showing the right seasons and limits.
These are the fields the API returns for this layer. Field names match the JSON response exactly.
| Field | Type | Description |
|---|---|---|
| id | integer | Stable Neighbourly zone ID |
| fisheries_management_zone_id | integer | Zone number, 1–20 |
| location_descr | string | Location description, where published |
| bbox_west … bbox_north | float | Bounding box |
| ogf_id | integer | Source feature ID |
| business_effective_date | datetime | Effective date of the boundary |
| boundary_geojson | GeoJSON | MultiPolygon geometry |
All requests go to https://api.neighbourly.io and send your key in the Api-Key header. A viewport is a JSON bounding box, {"southWestLat":…,"southWestLon":…,"northEastLat":…,"northEastLon":…}, URL-encoded.
Live response, trimmed. Add includes_boundaries=true for the zone polygon.
[
{
"id": 15,
"ogf_id": 211300015,
"fisheries_management_zone_id": 15,
"location_descr": null
}
]
Resolve a user's location or chosen lake to its FMZ, then show that zone's seasons and limits from the official summary.
Tag waterfront properties with their FMZ so anglers know which regulations apply.
Organize lake guides and fishing packages by the zone they fall in.
Tag thousands of lakes, sites or customers with their FMZ in a batch job using one consistent boundary source.
Every environmental layer shares the same API key, coordinate system and response conventions. Combine them in one integration.
Common questions about the Fisheries Management Zones API.
Twenty, numbered 1 to 20. All 20 are in the API.
No. It returns zone boundaries and numbers. Seasons and limits change, so match the zone number to the current Ontario Fishing Regulations Summary.
Ontario Ministry of Natural Resources Fisheries Management Zone boundaries, published through Ontario GeoHub.
Fetch the lake from the Lake Data API and send its bounding box as the viewport. A large lake can touch two zones, so check every zone returned.
Not today. This layer is Ontario's FMZ system.
Request an API key from the dashboard or book a demo. Every request sends the key in the Api-Key header. Pricing is usage-based.
Neighbourly normalizes public open data into one schema. Source licences and attribution apply; see our terms.
Get an API key and query this layer today, or talk to us about coverage and volume.