Kenmare Bay fishing maps with official survey-backed bathymetry, measured fishing spots, supported fish targets, seasonal forage guidance and explicit quality holds.
2 live sections1 on quality hold2 survey-backed depth maps13 cataloged target species2 official access records
Built for useful map scale
Why Kenmare Bay is split up
Trip-scale operational children keep channels, banks, island passages and access context readable while retaining only official source cells that pass the fixed release gates.
67,372-acre Kenmare Bay — Outer saltwater fishing map with official INFOMAR survey bathymetry, measured-cell fishing spots, official fish evidence, seasonal forage guidance, access context and current-rule links. The outer trip-scale survey reach of Kenmare Bay, retaining only official survey-backed seabed cells that pass the Ireland release gates.
Recorded max
260 ft
Species
European Flounder, Garfish, European Seabass, European Plaice
32,070-acre Kenmare Bay — Middle saltwater fishing map with official INFOMAR survey bathymetry, measured-cell fishing spots, official fish evidence, seasonal forage guidance, access context and current-rule links. The middle trip-scale survey reach of Kenmare Bay, retaining only official survey-backed seabed cells that pass the Ireland release gates.
Recorded max
154 ft
Species
European Flounder, Garfish, European Seabass, European Plaice
These named sections are part of Kenmare Bay but did not pass the release gate, so they have no public map yet.
Inner — Review hold (PR #675): section box lies in Bantry Bay (center 51.70N, -9.56W), not the Kenmare River, and is 98% inside bantry-bay-inner-north-irl.
Choose with the evidence visible
How to compare Kenmare Bay sections
The released set contains 2 survey-backed sections and 0 modeled sections. Their published maximum depths run from 154 to 260 ft, with a median of 260 ft. Those numbers make scale differences visible, but they do not make sections interchangeable: contour provenance, access, species evidence and local structure remain specific to each child map.
Start with the section closest to the water you actually plan to fish. Then compare its depth-data label and species roster with an adjacent section before treating a pattern as system-wide. A survey-backed child is the stronger choice for precise breakline planning; a modeled child is broader reconnaissance and should be checked against sonar and conditions on the water. Return to this overview whenever you cross into another mapped reach, pool or coastal section.
Same child-page contract
What every section keeps separate
Depth provenance: each child discloses whether its contours are survey-backed or modeled; a family card never upgrades that label.
Fishing spots: structure and seasonal recommendations are calculated inside the child boundary so distant reaches are not mixed together.
Fish species: each page keeps its own supported roster rather than inheriting every species found anywhere in the parent system.
Local context: hatch guidance, access, hazards, catches and nearby-water links continue to resolve for the individual child where data is available.
Why is Kenmare Bay divided into separate fishing maps?
Trip-scale operational children keep channels, banks, island passages and access context readable while retaining only official source cells that pass the fixed release gates.
Are these depth maps survey-backed?
2 released maps use surveyed or official agency bathymetry. Each child keeps its own provider, product, datum and not-for-navigation disclosure.
Do fish and access records apply everywhere?
No. Species, forage, access and fishing spots remain scoped to each child map and retain their evidence labels.
