What type of RINEX Base GNSS data is needed for processing in ROCK Desktop?

When importing into ROCK Desktop, you must place the following files together in the same folder:

• Observation file
  Extensions: .O, .obs, .##O (e.g., .24O or .250)

• Navigation file
  Extensions: .N, .nav, .##N (e.g., .24N or .25N)

• Optional but recommended

  • .P (pseudo‑range)

  • .B (broadcast ephemeris)

  • .rtcm3 (real‑time corrections)

Andrew’s tip: “All three core files (obs, nav, optional rtcm3) must live in one folder for ROCK Desktop to process—if you open only the .obs file in Notepad++, you can still verify everything you need.”

2. Supported RINEX Sources & Examples

A. On‑site GNSS Receiver (e.g., EMLID Reach RS2)

1. Set up your base to log at 1 second intervals and track all available constellations (GPS, GLONASS, BEIDOU, GALILEO).

2. Export and you’ll see files like Golden5.24B, Golden5.24O, Golden5.24P (the two‑digit prefix reflects the year).

3. Verify in Notepad++:

   • Header shows “RINEX VERSION / TYPE 3.03” and your station ID.

   • Look for the line listing systems and counts—e.g. “G R E J C  8 observations” (eight constellations).

   • Lines 18–19 report start/end UTC timestamps:

      

     2024-09-27 15:23:21 … ← first obs (UTC)
2024-09-27 17:17:34 … ← last obs (UTC)


   • Scroll down: you should see obs every second—15:23:22, 15:23:23, etc.

4. Why it matters: ROCK Desktop wants a continuous 1 Hz record spanning before, during, and after your LiDAR run.

B. ROCK RTK Network Download

1. Download from our network—files will include .obs, .nav, and .rtcm3.

2. Inspect the .obs in Notepad++:

   • Header shows your RINEX version and “PROVIDED BY GeoNet.”

   • Systems line: e.g. “G R E C” with counts (12, 6, 12, 6 satellites).

   • Lines 18–19:

      

     2025-04-02 15:00:00 … ← first obs (UTC)
2025-04-02 15:59:59 … ← last obs (UTC)


   • Verify 1 Hz: 15:00:00, 15:00:01, 15:00:02…

3. Best practice: Confirm you’ve downloaded the base station closest to your survey area, and that data spans your flight window.

C. CORS (Continuously Operating Reference Station)

1. Request U.S. CORS data (or local equivalent abroad) in RINEX format at 1 second intervals.

2. You’ll typically get a small set of text files (.log, README) plus .25G, .25N, .250.

3. Open the .250 in Notepad++:

   • Header lists the number and type of observations—e.g., 11 satellites total.

   • Lines 18–19:

      

     2025-04-02 05:00:00 … ← first obs (UTC)
2025-04-02 05:59:59 … ← last obs (UTC)


   • Check obs every second: 05:00:01, 05:00:02…

4. Caveat: CORS often yields fewer satellites (e.g., 11 vs. ~30), which can reduce final point‑cloud accuracy. But it’s a fallback if on‑site or ROCK Network data aren’t available.

3. How to Verify RINEX Quality

Open any .O or .obs file in a text editor (Notepad++, Sublime, etc.) and check:

1. RINEX Version

   • Look for “RINEX 3.03” (or newer) in the header.

2. Observation Types & Constellations

   • Header abbreviations (“G R E C J …”): confirm multiple systems.

3. Start & End Times (Lines 18–19)

   • Ensure UTC timestamps overlap your LiDAR collection window.

4. Interval

   • Scroll through successive timestamps to confirm a 1 Hz cadence.

Andrew’s reminder:

• Timestamps are always UTC—convert to local if needed.

• If you get “base not overlapping” or “insufficient satellites” errors in ROCK Desktop, revisit these checks.

4. Additional Notes

• All timestamps shown above are in UTC—apply your local‐time conversion based on your time zone.

• Need more help? See our guide on [What to Do With RINEX Files], or email support@rockrobotic.com.

• “RINEX data must include 1‑second interval observations and multiple satellite constellations for optimal processing results.”

By following these steps—and using Andrew’s three real‑world examples—you’ll ensure ROCK Desktop has the high‑quality base data it needs for accurate PPK trajectory generation.