2.3.2. The Files Page

This is where a campaign starts: you point the module at the folder your receivers’ data was downloaded into, and it reads every RINEX header it finds.

2.3.2.1. Opening or Creating a Project

The two buttons at the top of the module act on the .adjproj file that everything else is stored in.

Button	Action
New Project…	Creates a new, empty adjustment project. Choose a folder and a name; the extension .adjproj is added for you.
Open Project…	Opens an existing adjustment project. If it already contains GNSS data — scanned files, sessions, solved baselines — all of it comes back exactly as you left it.

Until one of the two has been used, every control on every page is disabled.

2.3.2.2. Scanning a Folder

Scan Folder… asks for a directory and reads every file in it.

The scan is:

• Non-recursive. Only the folder you pick is read, not its subdirectories. Put a campaign’s files in one folder, or scan each subfolder in turn.

• By header, not by extension. Every file in the folder is opened and its header examined. Anything that is not a RINEX observation or navigation file is ignored silently — a .zip, a .txt field note or a photo costs nothing but the time to look at it.

• Repeatable. Scanning the same folder again updates the existing rows instead of duplicating them; files are matched by their full path.

• Robust. A malformed or unreadable file cannot abort the scan. Such files are counted and reported at the end rather than silently skipped.

Re-scan repeats the last scan on the same folder without asking again. Use it after downloading more data into the folder, or after a file was re-generated.

When the scan finishes, a summary dialog reports how many files were indexed and, if any, how many were unreadable.

2.3.2.3. Observation and Navigation Files

The scan indexes both kinds of file:

• Observation files become the rows of the Files grid and are what sessions and baselines are built from.

• Navigation files are indexed too, but do not appear as participants. They are the ephemeris the solver is given.

This distinction matters more than it sounds. A baseline with no ephemeris cannot be solved at all, so navigation files must be scanned along with the observations — the usual cause of “every baseline failed” is a folder that contains no navigation file.

Warning

Not every file that looks like a navigation file is usable ephemeris. An almanac (.ALM) or an SBAS message file (.EMS) passes the same header test a broadcast navigation file does, but degrades a solve instead of helping it — in testing, one stray almanac turned a FIX at ratio 3.2 into a FLOAT at ratio 1.0 with a 34 cm bias.

The module therefore accepts only genuine RINEX 2 and RINEX 3 navigation extensions as ephemeris. Files that fail that test are still indexed and still visible, but are never handed to the solver.

The Recognised, not used list under the grid names every file in the scanned folder that did not become an observation or navigation row — plain non-RINEX files sitting in the folder as well as RINEX-looking files refused as ephemeris. Read it after a scan: a navigation file you expected to be used, appearing in that list, is the explanation for a batch of failed solves.

2.3.2.4. The Files Grid

One row per observation file. Columns:

Column	Editable	Meaning
Point Name	Yes	The survey mark this file was recorded on. Seeded from the RINEX MARKER NAME. This is the name that will appear in the baseline list, in the network sketch and, eventually, as a station in the adjustment — so it is worth getting right before planning.
Marker	No	The raw MARKER NAME from the header, kept for reference so you can always see what the receiver actually wrote.
Receiver	No	Receiver type from the header.
Antenna	No	Antenna type from the header.
ΔH / ΔE / ΔN	No	Antenna delta (height, east, north) from the header, in metres.
Start / End	No	First and last observation time, UTC.
Span	No	End minus start — the length of the occupation.
Interval	No	Observation interval in seconds, from the header.
Systems	No	The constellations present in the file.
Reference	Yes	Tick to treat this file as a base station.

2.3.2.5. Naming the Points

Receivers are rarely configured with the mark name you actually use. Edit the Point Name cell to whatever your project calls the mark.

Two files given the same point name are treated as the same mark — which is exactly what you want when a base station was re-occupied in two sessions, and exactly what you do not want when two different marks were accidentally given the same receiver ID.

Your edits survive a re-scan: only the header-derived columns are refreshed, never Point Name or Reference.

2.3.2.6. Marking Reference Stations

Tick Reference for the files recorded on your base stations — typically the long occupations that ran all day while the rovers moved around.

This matters for the Rover x references planning strategy (see The Sessions and Baselines Page), which ties every rover to every reference. With the Spanning tree strategy the flag is informational.

2.3.2.7. Files That Changed on Disk

The module records a hash of each file’s header and its size. If a file is re-downloaded, re-converted or edited between one scan and the next, the change is detected and any baseline result computed from that file is invalidated rather than left in place.

That is a feature, not a nuisance: a solved baseline whose input file has since changed is a result you can no longer defend. Re-run the affected baselines from the Processing or Results page.