Hello Mark,
The OS zip download contains data in both RINEX version 2 and version 3 format (.rnx extension). You can use either type with more recent versions of TBC, so you have to pick which file type you wish to use. if you have an older copy of TBC it may not support the newer .rnx file type.
Although you can bring zip files into TBC, I prefer unzipping first and then dragging in only the files required.
The data processing time must be down to the process you are applying and the PC specification. More info would be need on that in order to provide any advice.
From the OS web site:
RINEX file naming conventions
RINEX 2 format files
nnnnDDDS.YYt[.cmp]
where:
nnnn = 4 character station ID
DDD = 3 digit day of year (inc. leading zeros) of first epoch of data in the file
S = Hourly session ID letter corresponding to first epoch of data in the file.
"a" = 00:00:00 - 00:59:59 (GPS time); "b" = 01:00:00 - 01:59:59; …. ;
"x" = 23:00:00 - 23:59:59
YY = 2 digit year (inc. leading zero) of first epoch of data in the file
t = File contents indicator. "o" = observations; "d" = Hatanaka compacted observations;
"n" = GPS orbits; "g" = GLONASS orbits
cmp = [Optional] Compression method. E.g. "zip", "gz"
RINEX 3 format files
nnnnMRCCC_S_YYYYDDDHHMM_PPU_FFU_CT.fmt[.cmp]
where:
nnnn = 4 character station ID
M = Monument number. Currently only zero (0) is used
R = Receiver number. Currently only zero (0) is used
CCC = ISO country code (GBR)
S = Data source. "R" = receiver; "S" = stream; "U" = unknown
YYYY = 4 digit year of first epoch of data in the file
DDD = 3 digit day of year (inc. leading zeros) of first epoch of data in the file
HH = 2 digit hour (inc. leading zero) of first epoch of data in the file (GPS Time)
MM = 2 digit minute (inc. leading zero) of first epoch of data in the file (GPS Time)
PP = 2 digit file period (inc. leading zero)
U = Units of period PP. "M" = min; "H" = hour, "D" = day; "Y" = years;
"U" = unspecified
FF = 2 digit frequency of the observations (inc. leading zero)
U = Units of frequency FF. "C" = 100Hz; "Z" = Hz; "S" = sec; "M" = min;
"H" = hour; "D" = day; "U" = unspecified
NB - _FFU is omitted for files containing navigation data
C = Constellation indicator. "M" = mixed; "G" = GPS; "E" = Galileo;
"R" = GLONASS; "C" = Beidou; "J" = QZSS; "I" = IRNSS; "S" = SBAS
T = Data type indicator. "O" = observations; "N" = navigation;
"M" = meteo (no associated constellation so MM)
fmt = File format indicator. "rnx" = RINEX; "crx" = Hatanaka compacted RINEX
cmp = [Optional] Compression method. E.g. "zip", "gz"
Example
One hour of data from station LEED, 29th July 2021 (DoY 210), starting 09:00 (GPS time), 30 second data rate,
mixed constellation, zip compressed.]
RINEX 2 filename = LEED210j.21o.zip
RINEX 3 filename = LEED00GBR_S_20212100900_01H_30S_MO.rnx.zip
------------------------------
Richard Selby
------------------------------
Original Message:
Sent: 10-16-2022 00:37
From: Mark Atkinson
Subject: Importing Rinex data from Ordnance Survey in the UK
Recently the OS has changed the way it formats Rinex data.
It now supplies it in 1 hour segments per base.
When you drag the Rinex data into a job it hangs up unless you strip the .rnx files from the Rinex zip file.
Once you have stripped the zip file and dragged it onto the project it works.
However once it gets past the initial screen of showing what it is importing it takes an age to import the data.
I have had to wait almost an hour to import it into a project containing 7000 points taken with an R10 receiver.
Anybody have any ideas why the import and application of the Rinex zip file is taking so long ???
Any help would be appreciated
------------------------------
Mark Atkinson
------------------------------