The error in TBC's Baseline processor reports is "No valid overlap data could be found." If you look at the timestamps in the RINEX file from the Alloy, each epoch is bang on the second. If you look at the RINEX collected on the phone, the timestamps start of about 0.422 past the second and get worse. I'm not familiar with the Geo++ RINEX Logger app but you might want to check to see if there is some setting to correct for clock dither. As it is I don't think the data is usable.
------------------------------
James McWha
------------------------------
Original Message:
Sent: 07-13-2022 15:36
From: Jesse Kozlowski
Subject: Processing RINEX version 3.03 files in TBC 5.7
I am linking a RINEX version 3.03 file called "1001187T.22o" collected using the Geo++ RINEX Logger app running on a Samsung S22+ Android phone and the NGS CORS files for NJTW. TBC will not process this vector. I am very interested to know why it fails from anyone interested to try it. Thank you.
https://drive.google.com/drive/folders/1P6FvTbm6ziSXkxgRPFQDTjxNv1RODG_T?usp=sharing
------------------------------
Jesse Kozlowski
------------------------------