Start with the trip, then choose the reference
Write down where you will launch or arrive, where you plan to spend time, and how you will return. A St. Augustine trip might stay within the Matanzas River, reach a tidal creek, or include exposed Atlantic water. Those are different planning questions. A station suitable for organizing a local water-level schedule does not also supply a navigation assessment of the inlet or an offshore wave forecast.
Outgoing Tide starts with St. Augustine City Dock, NOAA station 8720576, and provides a broader coastal station search. Use the station name and ID as a reference you can verify at NOAA. Search results help you find data; they do not certify that the selected reference is representative of every place nearby.
Look at water connection, not just distance
A straight-line distance crosses land as readily as water. The tide travels through a connected system shaped by inlets, channels, shoals, and the geometry of the estuary. A physically nearby point across a barrier may respond differently from your destination. An inland reach can have a different timing relationship from a point closer to the ocean.
Compare the station location with your intended waterway on appropriate geographic and nautical references. Do not use a map pin to invent a fixed delay. If official predictions exist for your actual location, consult those. If they do not, describe the uncertainty honestly and avoid extending a reference table into a precise local schedule.
Check which products actually exist
Tide predictions, observed water level, water temperature, and current predictions are distinct products. A station can have useful predictions without all the other measurements. Outgoing Tide may identify another source for a product that the selected tide station does not supply. Read each panel's source instead of assuming that the station selected at the top supplied every value.
In particular, the Currents panel identifies a separate current-prediction station when coverage is available. Its distance and location matter. The closest compatible prediction may still be regionally distant. A current value from that station is not a measurement at Homebase or at your boat. Water-temperature sources likewise describe a sensor location, not a uniform temperature across the surrounding map.
A real interface example: two station identities
The dated chart example in the tide guide shows Mayport (Bar Pilots Dock), NOAA #8720218, in Predicted vs Preliminary. A visitor can have St. Augustine (City Dock), #8720576, selected for the tide calendar while the comparison uses a different observing station. These names refer to different places; the comparison is not a sensor reading at City Dock.
Use the calendar's station name for its high/low predictions. Use each comparison series label for its observations and residual. If you need to evaluate Matanzas water levels, first decide whether the identified observation station can answer that local question. The screenshot records an interface example from September 24, 2026; it does not establish which station will be available on your next visit.
Confirm the settings before comparing tables
Record the station ID, intended date, displayed time convention, and height units. Check the datum when comparing heights between providers. A tide prediction expressed relative to one datum should not be subtracted directly from a height expressed relative to another. A familiar-looking name or identical date is not enough to establish comparability.
When sharing a plan with another person, send the station ID and link with the time you mean. Saying “high tide is in the afternoon” hides which place and which day you checked. Clear references are especially useful when a group contains boaters, paddlers, and shoreline anglers starting from different access points.
Hypothetical planning example: two nearby pins
Imagine two search results near a proposed kayak route. One lies closer in straight-line distance but across a barrier; the other is farther away along the same connected estuary. The paddler examines official station locations, available products, and the route's exposure. They use the connected station as a reference only after checking its relevance, and they avoid assuming an exact arrival time for high water at the launch.
They also check whether the return would require paddling against wind or current. If that question cannot be resolved with suitable local information, choosing a shorter or different route is more useful than selecting whichever station gives the most convenient tide. The example does not establish that the farther station is always better; it shows why distance alone cannot make the decision.
Build a small, traceable planning note
A useful note has five items: the selected station and ID, why it relates to the route, the products you used, their timestamps or forecast dates, and the remaining uncertainties. Keep separate entries for a temperature sensor or current station. This takes little space and makes later comparisons less confusing.
After a trip, observations you personally make can help you ask better questions next time, but one visit does not establish a permanent tide offset. Do not publish a guessed adjustment as official data. For navigation, use current charts and official tide and current publications, and account for conditions beyond the station's prediction. Report a suspected mismatch to Outgoing Tide with the station ID, panel, date, and source link so it can be investigated.
References and data sources
Sources support the physical concepts and data definitions. Planning examples are hypothetical, not field reports or forecasts for a particular day.