CONSERVATION · LOCATION PRIVACY
You can tell the whole story and still keep the pin.
What the water was doing, what you tried, what changed — that’s the part another angler can use. The coordinates mostly just move traffic.
Small water can’t absorb a crowd.
One photo with a recognizable ridge in it can put a small creek on a map it was never on. That doesn’t mean every water needs handling like a state secret. Big reservoirs, public piers, well-known rivers, established destinations — naming those is usually the useful move, because the location is part of the context a reader needs.
It changes when the water is small, when the habitat is sensitive, when access is informal or private, when fish stack into one place for part of the year, or when the exact spot adds nothing to the thing you were trying to explain. That’s where precision buys pressure and pays back nothing.
So the question is which details are teaching and which are just giving directions. The directions are the part you can drop without hurting the piece.
Four ways it leaks.
Text
Road names, small tributaries, bridge numbers, turnouts, gate descriptions, trail directions, named coves. Three landmarks in the same paragraph will do it with no coordinates anywhere in the piece.
Photos
Marina signs, a mountain profile, a distinctive dock, road markers, bridge structure, a skyline, a shoreline somebody has seen before. The photo tells on the caption.
Screens
Sonar, mapping, weather and navigation screenshots carry waypoints, track lines, lake names, contour shapes, and sometimes latitude and longitude sitting right in a corner.
Timing
Posting live says where the fish are right now. It also says where your truck, your camp and your house currently aren’t being watched.
The part that teaches.
Leaving the pin out doesn’t make a story vague. Usually it does the opposite, because now the writing has to carry the explanation by itself.
Start with the kind of water and the structure, plus relative depth if depth was the thing. Then whatever the current, wind, light, vegetation, temperature trend, forage or bottom transition was doing while you were there — and what you threw first, what failed, what you changed, and what the fish did about it.
The fish were on the outside weed edge where the flat dropped off fast is portable — somebody can go look for that on their own lake tomorrow. Third cottonwood past the green gate teaches exactly one thing, and it’s traffic.
Presentation stays specific too. Lure class, weight, retrieve, casting angle, leader, line control, pause length, drift and depth all travel further than a waterbody name does. If a brand genuinely mattered, name the physical property that mattered, because that’s the part a reader can match with something already in their box.
Some places take attention worse than others.
Small wild-fish streams. Thermal refuges. Spawning concentrations, restoration areas, rare-species habitat, vulnerable seasonal aggregations, and anything you reach through three parking spots and an informal pull-off. There isn’t much slack in any of those.
And the pressure isn’t only fishing pressure. It arrives as trampled banks, damaged vegetation, cars parked where cars shouldn’t be, trespass, litter, unsafe roadside behavior, and a land manager or a landowner who has finally had enough. A place can lose its access long before it loses its fish.
When the exact location would add pressure to something biologically or socially fragile, wider geography usually carries the lesson fine — region, watershed type, elevation band, habitat type, a general public area. Go as broad as you can while the point still lands.
Permission doesn’t transfer.
If a landowner, a guide, a lodge, a friend or somebody local let you in, that was for you. The route, the gate code, the parking arrangement, the landowner’s name, the unmarked crossing — none of it goes in the piece unless the person who controls that access says plainly that they want it public.
Don’t write a route that only works through trespass, a shaky easement, or the assumption that a mapping app knows where the property lines are. It doesn’t, and access law is complicated and different in every jurisdiction. When a piece sends readers to a named public destination, send them to the current official access source too, and put the restrictions where they’ll actually see them.
One thing this is never for: hiding a closure, a hazard, a permit requirement or an access restriction. Nobody gets to call that location privacy.
Read the whole frame.
Before a screenshot goes up, look at all of it, not the part you meant to show. Waypoint names, route traces, coordinates, map shapes, launch names, depth contours, a recent-locations panel sitting off to one side. Crop down to the thing you’re explaining when the map around it isn’t doing any work.
Photos get the same pass. A fish can fill the frame and the background can still name the place. Pick a different image or crop the clue out. What you don’t do is invent a different location in the caption — that’s a worse problem than the one you were solving.
Image files can also carry location and device metadata depending on how they were shot and handled. Some publishing services strip some of it. Not all of them strip all of it. When the water or the access is sensitive, check the privacy settings and pull the location data yourself.
Post it tomorrow.
There’s almost never a reader who needed to hear about a bite while it was still happening. Waiting until you’re off the water takes the live pressure off and stops broadcasting where you are. On a big public fishery the timing is usually harmless and sometimes genuinely useful. On a small one, a same-day post can turn a two-hour window into a parking problem.
If live coverage is part of a guide trip, a tournament, an event or a media agreement, settle the location boundary before the first post goes out. Whoever handed you the access or the local knowledge shouldn’t learn what you published by seeing it online.
Field Ops Desk holds the same line.
The tools compare public water, tackle, presentation, forage clues and measurements, and none of that requires handing over a spot. Leave coordinates and private-access details out when the decision doesn’t need them.
What a motivated stranger could rebuild.
Before it publishes, add the whole thing up at once — the title, the text, the photos, the screenshots, the timing, the tags, the map fragments and the contributor credits, read the way somebody determined to find that place would read them. Not one sentence at a time.
Then the second question, which is the more useful one. Pull the exact location out. Does the reader still understand what made the fishing work?
If they do, the pin wasn’t carrying anything. If they don’t, decide whether the public value is worth the pressure and the access risk you’re adding. Sometimes it clearly is. More often the fix is explaining the water better.
Enough of the story to teach the fishing.
Readers should get real detail — the relationship, the conditions, the presentation, what you adjusted, what happened. Sensitive coordinates, private permissions, live timing nobody needs and identifying details buried in the media stay out unless there’s a clear reason they’re in.
Mostly this is just being decent to a piece of water and to whoever is standing on it next month. It costs a sentence or two of precision, and that’s a cheap trade.
Tell the Fishing Story. Keep the Spot Out of It. is the practical, sentence-by-sentence version of this one. Stewardship covers the rest of the field standard.