The local coordinate file was added ~ version 3.6.4. It is used in the following cases:
nmea2snr requires apriori coordinates to compute elevation and azimuth angles - but does not read them from the NMEA file. you used to have to add it on the command line. now it can also be read from the local coordinate file.
gnssir_input reads the coordinates for most archive GNSS sites from a database. For your own sites you used to have to enter the coordinates on the command line. It will now read them from the local coordinate file. These coordinates are used in computing the refraction correction. They are not used for any other reason.
the refraction correction was never used in quickLook because that requires coordinates (which may or may not exist when you are running quickLook). since the local coordinate file is now an option, if the coordinates are found, the quickLook code will use them to make teh refraction correction. They are not used for any other reason.
What about rinex2snr? This code does NOT use the local coordinate file because your RINEX file should have that information in the header. This has always been the rinex2snr behavior. In principle one could use the local coordinate file to provide the information to rinex2snr if a RINEX file was missing coordinates in the header. I am fine with allowing this if someone else writes the code. But be warned - the code that needs to change is Fortran.
The format of the local coordinate file is provides in the File Formats section of the online documentation.
The local coordinate file was added ~ version 3.6.4. It is used in the following cases:
nmea2snr requires apriori coordinates to compute elevation and azimuth angles - but does not read them from the NMEA file. you used to have to add it on the command line. now it can also be read from the local coordinate file.
gnssir_input reads the coordinates for most archive GNSS sites from a database. For your own sites you used to have to enter the coordinates on the command line. It will now read them from the local coordinate file. These coordinates are used in computing the refraction correction. They are not used for any other reason.
the refraction correction was never used in quickLook because that requires coordinates (which may or may not exist when you are running quickLook). since the local coordinate file is now an option, if the coordinates are found, the quickLook code will use them to make teh refraction correction. They are not used for any other reason.
What about rinex2snr? This code does NOT use the local coordinate file because your RINEX file should have that information in the header. This has always been the rinex2snr behavior. In principle one could use the local coordinate file to provide the information to rinex2snr if a RINEX file was missing coordinates in the header. I am fine with allowing this if someone else writes the code. But be warned - the code that needs to change is Fortran.
The format of the local coordinate file is provides in the File Formats section of the online documentation.