OpenTideConstants
No liveness check has reached it yet; it is registered on GitHub and has been in the index since 8 Oct 2026. How this is checked
OpenTideConstants combines official agency, gauge-fitted, and tide-model harmonic constants into a consistent dataset. It documents conventions, provenance, validation, accuracy, and release data for researchers, coastal engineers, and developers working with tides.
Inferred · not functionally tested
Overview
6 featuresPurpose: Combining tidal harmonic constants from agencies, gauge fits, and models into one consistent, validated dataset.
Inferred · not functionally tested
Audience: oceanographers, coastal engineers, and tide-data developers
Inferred · not functionally tested
Functions: data_extraction
Inferred · not functionally tested
Interfaces: API: indicated (inferred, not tested) · MCP: unknown · CLI: unknown · Self-hosting: unknown
Recorded constraints: pricing: free · license: Proprietary · platforms: WEB · deployment: browser, api_only, cloud_managed
Constraint provenance is unknown; confirm requirements with the publisher.
Record sources: opentideconstants.org · rubygems.org · github.com. These links do not verify the individual claims.
OpenTideConstants sits in PulseGate's Data integration & ETL category. Inferred · not functionally tested: It focuses on combining tidal harmonic constants from agencies, gauge fits, and models into one consistent, validated dataset. Inferred · not functionally tested: OpenTideConstants is an open-source project aimed at oceanographers, coastal engineers, and tide-data developers. Basis unknown · not verified: OpenTideConstants costs nothing to use. Basis unknown · not verified: OpenTideConstants is available on the web and API.
OpenTideConstants builds and maintains OpenTideConstants, and it first shipped in 2026. The project is developed in the open on GitHub with 30 commits in the last 90 days. Inferred · not functionally tested: Among its 6 catalogued features are unified data format, source provenance, and accuracy reporting.
Summary written by a language model from the project’s public pages.
Tasks: Inferred · not functionally tested
- Unified data format
- Source provenance
- Accuracy reporting
- Data validation
- Declared conventions
- Automated rebuilds
Topics: Inferred · not functionally tested
Built with & integrations
- Claude Code
- commit 2006ba0dd7a6 · since Oct 2026
- Cloudflare
- cf-ray header · cf-cache-status header
Trust & compliance
Indexing history
1What PulseGate has recorded for this listing
- Indexed8 Oct · 06:31 UTCopentideconstants seen via RubyGems newly publishedSource: RubyGems newly published · Open
Frequently asked questions about OpenTideConstants
- What does OpenTideConstants do?
- Inferred · not functionally tested: OpenTideConstants focuses on combining tidal harmonic constants from agencies, gauge fits, and models into one consistent, validated dataset. It is catalogued under Data integration & ETL on PulseGate.
- Who is OpenTideConstants for?
- Inferred · not functionally tested: OpenTideConstants is an open-source project built for oceanographers, coastal engineers, and tide-data developers.
- Is OpenTideConstants free?
- Basis unknown · not verified: Yes — OpenTideConstants is free to use.
- What platforms does OpenTideConstants run on?
- Basis unknown · not verified: OpenTideConstants runs on the web and API.
- Is OpenTideConstants still maintained?
- The GitHub repository shows 30 commits in the last 90 days.
- What are alternatives to OpenTideConstants?
- Similar projects tracked by PulseGate include locaihost data, bbo-tap, and HKEx Filings.locaihost databbo-tapHKEx Filings
- Who develops OpenTideConstants?
- OpenTideConstants is developed by OpenTideConstants.
- How long has OpenTideConstants been around?
- OpenTideConstants first shipped in 2026.
Also in Data integration & ETL
Same category — not a similarity match