geoprimsField-grade geospatial math

OPUS session planning

Which processing a planned GNSS session gets (rapid-static or static), whether its length qualifies, and the file name for the day.

A published result changed on 2026-10-13: OPUS session planning (version 1.1.0) is now stable and fixes partial-day RINEX 2 names. Changelog

rapid static

OPUS runs a session this long as rapid static.

NGS software
Data requirements
RINEX 2 file name
Day of year
Provenance
Computed by
survey.gnss.opus-plan 1.1.0, core 0.1.0
Model
OPUS accepts 15 minutes to 48 hours of data; files under 2 hours go to RSGPS rapid-static processing and files from 2 to 48 hours go to PAGES static processing (NGS OPUS page, last modified 2026-09-09). The RINEX 2 short name is the 4-character station, day of year, UTC start-hour letter (a = 00 through x = 23, or 0 for a 24-hour data set), two-digit year, and o for observations
Accuracy
NGS guidance as of the date shown; check the OPUS page before a job. Rapid-static processing needs continuous data and good geometry and may not work in remote areas
Notes
None
Cites
NOAA National Geodetic Survey, OPUS: Online Positioning User Service, About; NOAA National Geodetic Survey, OPUS Projects User Guide: RINEX Files Naming Convention for GNSS Observations

Something look off?

Your values

Showing an example. Change anything.
Run many at once from a CSV

Loading…

How we got thisFormula, worked example, sources, and proof

Model: OPUS accepts 15 minutes to 48 hours of data; files under 2 hours go to RSGPS rapid-static processing and files from 2 to 48 hours go to PAGES static processing (NGS OPUS page, last modified 2026-09-09). The RINEX 2 short name is the 4-character station, day of year, UTC start-hour letter (a = 00 through x = 23, or 0 for a 24-hour data set), two-digit year, and o for observations

Show your work

  1. Session length

    15 minutes to 48 hours

    60 min = accepted

  2. Processing

    under 2 hours: rapid-static; 2 hours or more: static

    60 min = rapid static

The same steps an agent gets from the MCP server with explain: true.

Accuracy: NGS guidance as of the date shown; check the OPUS page before a job. Rapid-static processing needs continuous data and good geometry and may not work in remote areas

When to use this: Use this when you are planning a static GNSS session to send to NGS OPUS. Enter the session length. To build the RINEX 2 short name, also enter the UTC start date, four-character station name, and UTC start hour. The tool tells you whether OPUS will run the file as rapid static or static, which NGS software handles it, and the data rules NGS lists.

Limitations: The rules come from the NGS OPUS page as of the date shown, and NGS can change them, so check that page before a job. The tool checks length only. It cannot tell whether your data is continuous, has enough satellites, or will solve, and rapid static may fail in remote areas. File names use the RINEX 2 short form, not the longer RINEX 3 form.

Worked example: The NGS RINEX naming example in a 60-minute session. Source: NOAA NGS OPUS Projects User Guide v2.0, section 5.1: the published file-name example is g287009q.23o. It is golden test vector v026, and every build checks the tool still gives its answer within its tolerance.

You enter

Date (UTC)
2023-01-09
Session length
60 min
Start hour
16
Station name
g287

You get

OPUS processing
rapid static
NGS software
RSGPS rapid-static software
Data requirements
Dual-frequency GPS (L1/L2) carrier phase recorded at 1, 2, 3, 5, 10, 15, or 30 s, crossing UTC midnight at most once; files under 2 hours need P2 and P1 or C1 observables. NGS OPUS page, last modified 2026-09-09.
RINEX 2 file name
g287009q.23o
Day of year
9

Review: Not yet independently reviewed by a licensed surveyor.

Last verified: 2026-10-13, when a maintainer last confirmed this tool's sources at the issuer. See the sources ledger.

Status: version 1.1.0, core 0.1.0. See this tool in the verification report.

Changes

Checked against: 25 golden test vectors (download the test vectors, each with its source and tolerance). See how results are checked and every source.

Sources

Terms

NGS: National Geodetic Survey
The NOAA office that defines the US National Spatial Reference System: datums, geoid models, and state plane coordinates. Source: State Plane Coordinate System of 1983 (NOAA Manual NOS NGS 5)
OPUS: Online Positioning User Service
The free NGS service that computes a precise position from GNSS data you upload, tied to nearby continuously operating reference stations. Source: OPUS: Online Positioning User Service, About
RINEX: Receiver Independent Exchange Format
The standard text format for GNSS receiver observations. Daily files are named by station, day of year, and year, so any processing service can read them. Source: RINEX: the Receiver Independent Exchange Format
UTC: Coordinated Universal Time
The world's civil time standard, kept within 0.9 s of Earth's rotation by leap seconds. Aviation calls it Zulu time, written with a Z. Source: IERS Bulletin C (leap seconds)

NGS — National Geodetic Survey

The NOAA office that defines the US National Spatial Reference System: datums, geoid models, and state plane coordinates.

Source: State Plane Coordinate System of 1983 (NOAA Manual NOS NGS 5)

OPUS — Online Positioning User Service

The free NGS service that computes a precise position from GNSS data you upload, tied to nearby continuously operating reference stations.

Source: OPUS: Online Positioning User Service, About

RINEX — Receiver Independent Exchange Format

The standard text format for GNSS receiver observations. Daily files are named by station, day of year, and year, so any processing service can read them.

Source: RINEX: the Receiver Independent Exchange Format