Wisconsin Lake Explorer

Data & methods

Every fact on this site is bounded to one named published source and its date. Missing values are unpublished, never zero, and no composite score, rating, or ranking is ever derived across sources. Each family below states its publisher, method and scope, coverage, retrieval date, and what a missing record means.

Current sources

Aquatic invasive species occurrences

Original source

Canonical detailed lake dataset (summary-failure fallback)

Original source

Compact filter index (projection)

Original source

Development-density proxies (NLCD + Census)

Field-measured Secchi clarity (WQP/CLMN)

Original source

Fish abundance (DNR lake pages)

Original source

Fish stocking events

Original source

Fisheries adult population estimates

Original source

Fishing limits (adopted DNR ruleset cycle)

Original source

Governed species vocabulary

Original source

Lake directory (names, counties, size, depth, access flags)

Original source

Lake shoreline geometry (DNR 24K hydrography)

Managed public land proximity

Public boat access and shore fishing sites

Original source Original source Original source

Road proximity/density (Census TIGER/Line)

Runtime source catalog (this catalog)

Original source

Satellite water clarity (Landsat estimate)

Original source

Selected-lake profile shards (projection)

Original source

Trophy/special designations

Original source

USFS recreation facilities (Chequamegon-Nicolet)

Original source

Wisconsin origin reference points (Census Gazetteer)

Historical sources

Depth-map links (historical DNR lake maps)

Original source

Search interpretation

The main search applies only deterministic, supported interpretations. A bare number that is a canonical WBIC is always a lake identity, never a ZIP-area point; lake names containing numbers stay ordinary names. Negated criteria ("no musky", "no carry-in access") are refused with an explanation rather than guessed: the public inventories cannot prove absence. Crowd and quietness phrases apply no filter — no crowd data exists. Phrases like "zebra mussels have not been detected" are likewise refused: absence of an occurrence record is never evidence of absence.

Distance from a place

Origins come from the US Census Bureau: 2025 Gazetteer places (cities, villages, and census-designated places), active towns from the 2025 Gazetteer county subdivisions, and ZIP Code Tabulation Area reference points associated to Wisconsin counties by the 2020 relationship file. A ZCTA is an approximate ZIP-area reference point — not a USPS ZIP centroid and not an exact address. Every distance is a straight-line (great-circle) measurement from the Census-published reference point to the lake's published coordinate; it is never travel time, road distance, or the distance to an access point. Radius filters offer a reviewed set of 25, 50, or 100 miles. Only the stable Census identifier and the chosen radius are stored in links — never typed text or coordinates.

Map coordinate review

Published coordinates pass a reviewed statewide bounds gate before a lake is mapped. Records failing the gate (32 at the current baseline, kept as known issues pending an authoritative correction) remain fully searchable with complete report pages; only their map placement is withheld.

Lake report maps

Eligible lake reports add a collapsed inline map only after JavaScript validates the report WBIC and reviewed coordinate. Opening it starts a governed lightweight report renderer, then loads the content-hashed lake outline and the same selected-lake access-evidence shard used by the textual access disclosure. A missing or failed outline falls back to the reviewed lake location. Markers include only reviewed or qualified lake-associated access records with mappable coordinates; the text list remains authoritative, and no published record never means no public access. External tiles begin only after activation, receive an origin-only referrer, and carry no WBIC, filter state, or telemetry value. The main discovery map continues to use Leaflet; the bounded report renderer is report-only.

The same catalog is published machine-readable at /data/source_catalog.json.