You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
GnssLogger, GPSTest, and maybe other apps, create log files that appear to be a mashup of observations, nav messages, etc. They are not in the industry-wide format used by surveying programs by GNSS manufactures like Javad, Topcon, Trimble, etc, that allow ingestion and post-processing of RINEX files derived from smartphones.
Please consider adoption of RINEX v3.05 formatting and file naming schema for files produced by android_rinex. Or as a minimum, consider the following essential bits:
STATION NAME
Logging apps like GnssLogger and GPSTest would be improved tremendously if the user was optionally able to provide the name of the occupied station, marker, or monument; e.g., SINCLAIR A, AL7621, XACT 2, DG8939. This is a basic standard naming convention and a good place to begin.
START TIME
Following the station name and separated by an underscore_ the start time of the RINEX file YYYYDDDHHMM where DDD is the day of the year.
CONTENT TYPE
Following the start time and separated by an underscore_ the content type represented by 2 characters; i.e.,
Two uppercase characters represent the data type:
GO - GPS Obs.
RO - GLONASS Obs.
EO - Galileo Obs.
JO - QZSS Obs.
CO - BDS Obs.
IO – NavIC/IRNSS Obs.
SO - SBAS Obs.
MO - Mixed Obs.
GN - Nav. GPS
RN - GLONASS Nav.
EN - Galileo Nav.
JN - QZSS Nav.
CN - BDS Nav.
IN – NavIC/IRNSS Nav.
SN - SBAS Nav.
MN – Mixed Nav. (All GNSS Constellations)
MM-Meteorological Observation
EXTENSION
Following the content type and separated by the decimal . rnx for all RINEX files.
This is not by any means the full-on OCD RINEX file naming schema of IGS, as is more fully detailed in RINEX v. 3.05 and the RINEX Formating standards leading up last December's major restructuring. There may be softwares available to help in generating RINEX 3.xx long filenames.
Thank you for any consideration.
The text was updated successfully, but these errors were encountered:
FYI & FWIW - Thanks to Sean Barbeau, and his GPSTest Database, not all smartphones/ OEMs support nav messages, as I recently found out in the case of my phone, the Samsung A71.
GnssLogger, GPSTest, and maybe other apps, create log files that appear to be a mashup of observations, nav messages, etc. They are not in the industry-wide format used by surveying programs by GNSS manufactures like Javad, Topcon, Trimble, etc, that allow ingestion and post-processing of RINEX files derived from smartphones.
Please consider adoption of RINEX v3.05 formatting and file naming schema for files produced by android_rinex. Or as a minimum, consider the following essential bits:
STATION NAME
Logging apps like GnssLogger and GPSTest would be improved tremendously if the user was optionally able to provide the name of the occupied station, marker, or monument; e.g., SINCLAIR A, AL7621, XACT 2, DG8939. This is a basic standard naming convention and a good place to begin.
START TIME
Following the station name and separated by an underscore_ the start time of the RINEX file YYYYDDDHHMM where DDD is the day of the year.
CONTENT TYPE
Following the start time and separated by an underscore_ the content type represented by 2 characters; i.e.,
Two uppercase characters represent the data type:
GO - GPS Obs.
RO - GLONASS Obs.
EO - Galileo Obs.
JO - QZSS Obs.
CO - BDS Obs.
IO – NavIC/IRNSS Obs.
SO - SBAS Obs.
MO - Mixed Obs.
GN - Nav. GPS
RN - GLONASS Nav.
EN - Galileo Nav.
JN - QZSS Nav.
CN - BDS Nav.
IN – NavIC/IRNSS Nav.
SN - SBAS Nav.
MN – Mixed Nav. (All GNSS Constellations)
MM-Meteorological Observation
EXTENSION
Following the content type and separated by the decimal . rnx for all RINEX files.
This is not by any means the full-on OCD RINEX file naming schema of IGS, as is more fully detailed in RINEX v. 3.05 and the RINEX Formating standards leading up last December's major restructuring. There may be softwares available to help in generating RINEX 3.xx long filenames.
Thank you for any consideration.
The text was updated successfully, but these errors were encountered: