Process static GPS/GNSS observations for high-precision coordinates via NOAA's OPUS service
domain: geodesy.noaa.gov · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Collect a dual-frequency static GPS (L1/L2) observation file, 2 to 48 hours in duration, in a supported raw or RINEX format
Go to the OPUS upload page and submit the observation file
Select the antenna model used and its height above the survey mark
Choose static processing mode and supply an email address to receive results
OPUS computes coordinates as the average of three independent double-difference baseline solutions against nearby CORS stations, then emails the results
Known gotchas
OPUS static mode requires 2-48 hours of dual-frequency data — shorter or single-frequency files don't qualify
This is primarily a web upload/email workflow rather than a synchronous REST API; a separate 'OPUS API' exists but only queries already-shared historical OPUS solutions (PID/radial/bounding-box lookup) — it does not support submitting jobs or checking processing status of a new submission.
Accuracy depends on baseline distances to the three nearest CORS stations, which varies by region and can degrade in CORS-sparse areas
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?