Operator by Fibric
Field Dispatch
Gets the right person to the right place: reads the live picture, plans the route, and dispatches the team that can fix it.
View details
← Marketplace
Commons signalFree
Tides & Water Levels
NOAA's tide stations, governed: water level and timing signals for waterfront operations.
Ask how Tides & Water Levels fits what you run.
Answers are based on this listing. For anything it can't answer, our team can.
For anything this page can't answer, talk to us.
About
This Commons feed reads NOAA's Center for Operational Oceanographic Products and Services: observed water levels, tide predictions, and station meteorology for the stations near your operation. Venue scheduling, harbor logistics, and flood-adjacent facilities all run on the same question: what will the water do, and when.
The upstream is free and public with no key. Observed levels and predictions arrive as separate, clearly-labeled series, so an operator never confuses a forecast with a measurement.
Highlights
- Free public feed, no key required
- Observed levels and predictions kept honestly separate
- Station-level signals for venue and harbor timing
- Kind
- Commons signal
- Category
- Commons signals
- Publisher
- Fibric Commons
- Upstream
- NOAA CO-OPS (tidesandcurrents.noaa.gov)
- Feed health
- Feed live, data flowing (121ms, checked 2026-07-06T23:28Z)
- Availability
- Early access
- Delivery
- Managed by Fibric; nothing to install
- Data direction
- Read-only
- Pricing
- Free
- Sold by
- Fibric
- Support
- Developed and supported by Fibric
- Tags
- tides, marine, commons, free
Authentication
None. NOAA CO-OPS data is free and public.
What it reads
- Observed water levels from your chosen stations
- Tide predictions with high and low water times
- Station meteorology: wind, air and water temperature where available
What it can do
This is a sensing source: it reads, it does not write. Operators act through the write-capable connectors alongside it.
How it works
1
Sense
Observed water levels from your chosen stations.
2
Reason
Operators reason over this connector's signals next to the rest of your stack, so decisions are grounded in the same records you run on.
3
Act
Nothing. This is a sensing source; operators act through the write-capable connectors alongside it.
Pricing
Free, part of the Commons
Commons signal feeds are free with every Fibric plan. The upstream data is public; Fibric adds the governance: provenance on every event, deduplication, and receipts when an operator acts on it. You pay for operators, never for signals.
- Deployment engineer
- Wires and verifies the integration with you during onboarding
- Propose-only mode
- See every action it would take before it takes one
- Receipts and audit trail
- Every read and write on the record, exportable any time
- Support from the builders
- Developed, run, and supported directly by Fibric
Requirements
- The NOAA station IDs near your operation
Your deployment engineer verifies each line with you during onboarding.
Support and resources
Supported by the people who built it
This signal feed is developed, run, and supported by the same Fibric team. Support starts during onboarding with a named deployment engineer and doesn't hand you off afterward.
Works with
The connectors and operators this pairs with in production.
Support & comms connector
Microsoft Teams
Routes approvals and alerts to the channel that owns the call. One confirm in Teams turns a proposed plan into a vetted action.
View details
Data & events connector
Webhook Ingest
A signed endpoint for any system that can POST: verifies the HMAC, stamps the tenant, and turns the payload into a governed event.
View details
This Commons signal feed is developed, published, and supported by Fibric. It reads public data published by NOAA CO-OPS (tidesandcurrents.noaa.gov). Upstream agencies and projects are the property of their respective owners, who are not affiliated with Fibric and do not sponsor or endorse this listing. Trademark policy
Bring Tides & Water Levels into your early-access deployment
Early access means a deployment engineer wires this with you, and it runs propose-only until you approve live actions.