Great Ouse Tidal River fishing maps and mapped reaches
Environment Agency survey-backed fishing maps for the tidal Great Ouse from Denver Sluice through King's Lynn to The Wash.
1 live reach2 on quality hold1 survey-backed depth maps10 cataloged target species1 official access records
Built for useful map scale
Why Great Ouse Tidal River is split up
The current WFD polygon spans nearly 38 miles and extends above the source-documented tidal reach; page-scale children are gated independently so the surveyed lower reach can publish without stretching evidence into unsupported or freshwater reaches.
1,481-acre Great Ouse — King's Lynn to The Wash fishing map with Environment Agency multibeam/SurfZone ODN contours (96.43% measured, 96.43% assessed), four measured spots, exact EA TraC occurrence, three dated survey cards, official access and current GOV.UK/applicable IFCA guidance.
Recorded max
23 ft
Species
Atlantic Herring, European Flounder, European Seabass, Common Sole
These named reaches are part of Great Ouse Tidal River but did not pass the release gate, so they have no public map yet.
Denver to King's Lynn — The exact tidal child is 91.54% measured and assessed, leaving 8.46% unsupported—above the fixed 5% ceiling—so it remains held without a coverage waiver.
Great Ouse upstream of Denver — This upstream remainder is outside the source-documented tidal child release and needs a separate freshwater/navigation boundary, exact-section fish, access and rules review.
Choose with the evidence visible
How to compare Great Ouse Tidal River reaches
The released set contains 1 survey-backed reach and 0 modeled reaches. Their published maximum depths run from 23 to 23 ft, with a median of 23 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.
Planning questions
Frequently asked questions
Why is Great Ouse Tidal River divided into separate fishing maps?
The current WFD polygon spans nearly 38 miles and extends above the source-documented tidal reach; page-scale children are gated independently so the surveyed lower reach can publish without stretching evidence into unsupported or freshwater reaches.
Are these depth maps survey-backed?
1 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.