346
receiver such as better models of the atmospheric
conditions at timeof measurement.Rover datamay
be used in combination with other data stored at a
basestation.RINEXformatisdesignedtoevolveover
time, adapting to new types of measurements and
newsatellitenavigationsystems.Itenablesstorage
of
rawmeasurementsforallGNSSalongwithdatafrom
SBASsimultaneously.
RINEX Files Classification; RINEX files are
classified into six categories as depicted in Table 1.
Forthisstudy,onlyfirsttwotypesoffileshavebeen
utilized.Infact,atleastthesetwofilesarerequiredto
completely
define the data in RINEX format. Each
observation file and each meteorological data file
containsthedatafromonesiteandonesession.Each
file type consists of a header section and a data
section. The header section contains global
information for the entire file and is pla ced at
beginning of
the file. The header section contains
headerlabelsincolumns61‐80foreachlinecontained
intheheadersection. Theselabelsaremandatoryand
must appear exactly as specified in [19] and [20].
There is no limitation for maximum length of
observationrecords.
Webrieflydescribethetwotypes
offilesusedfor
our study. RINEX observation file (data section)
typically includes number/ type of observations,
epoch time when the measurement was taken,
number of visible satellites, visible satellites ID
commonly referred as Pseudo‐Random Noise (PRN)
code,andnumericalvalueofobservables.ForDGPS
applications, we need to record
observation file
simultaneously at base station and at rover site.
RINEX navigation message file contains the broadcast
ephemeris data. This data is useful for a number of
functionslikecomputationofsatelliteclockerrorand
satellitescoordinatesetc.Ifdatafrommorethanone
receiver have to be exchanged, it
would not be
economicaltoincludetheidenticalsatellitemessages
collected by the different receivers several times.
Therefore the navigation message file from one
receivermaybeexchangedoracompositenavigation
message file may be created containing non‐
redundantinformationfromseveralreceiversinorder
tocontaincompleteinformationin
onefile.ForDGPS
with short baseline (till 10 km), one navigation file
collectedeitheratbasestationoratrovermayserve
the purpose. Every GNSS has its own navigation
messagedata.
Table1.ClassificationofRINEXfiles
_______________________________________________
SNoFileCategoryDescription
_______________________________________________
1 Observationdatafile Containsmeasurementdata
likeGPStime,pseudoranges,
carrierphase,DopplerandSNR
etc.
2 Navigationmessagefile ContainsGPSbroadcast
ephemerisdataand
Ionosphericparameters
3 Meteorologicaldatafile Containmeteorologicaldata
(ambientpressure,temperature
andhumidityetc.)forpost
processingwithhigh
accuracy
4 GLONASSnavigation ContainsGLONASSsatellites
Messagefileephemerisdata
5 GEOnavigation ForWASS/EGNOS
messagefilegeostationarysatellites
6 Satelliteandreceiver Containsclockdata
clockdatafile
_______________________________________________
Conversion of GPS Binary Data to RINEX Format;
GPSbinarydatamaybeconvertedtoRINEXformat
using suitable software like ’teqc’ or ’rtklib’. Many
proprietary formats (like .ubx files of u‐blox GPS
receivers) may be converted to RINEX format using
suchsoftware.Careshould,however, beexercisedto
ensure that proper settings have been made on the
receiver to output both observation as well as
navigationdata.UsercanchoosetheRINEXversion,
as required, provided the software supports the
chosenversion.
4 DGPSSOFTWAREANDSIMULATIONRESULTS
DGPSdatahasbeenpostprocessedusingMathWorks
MATLAB
®
that facilitates matrices handling/
manipulation, as required for this study. DGPS
simulations have been performed with observations
collected at base station and a rover. Differential
correctionfactorscomputedatbasestationhavebeen
exploited for determination of rover accurate
coordinates.
Base station and rover coordinates have been
calculated with iterative
least square method using
pseudoranges from at least four SVs. If more than
four satellites are visible (as mostly is the case for
airbornevehicles orforGPSreceiversinopenarea),it
isrecommendednottoutilizethedatafromthenear‐
horizon satellites. As signals from these satellites
travel
comparatively longer distances through
atmosphere,soaremorepronetoatmosphericeffects.
Itisrecommendedtosettheelevationmasktoatleast
10° to eliminate the most noisy data (but not more
than 15° so that usable data is not lost). Spherical
coordinates of SVs are therefore computed for
determination of corresponding elevation angle. For
ourpresentstudy,wehavesetelevationmask to10°.
Astotaltransmittedpowerfromasatelliteislessthan
50 watts, so GPS signals are relatively weak.
Comparisonof SNR between satellites can show the
sourceofthecleanestdata.Itisimportant
touseonly
that data for computation that does not fall below
acceptableSNR(commonlysetas20‐30dB).Forour
study,thisthresholdissetto20dB.Basestationand
roverdonotseethe same setof satellites for all the
epochs.Mostofthetime,a
newsatelliteappears(or
disappears) at different epochs at base station and
rover. So we make a further criterion of common
satellitestoimprovethepositionaccuracyattherover
side.
For our study, TRIMBLE NETR5 GPS receiver
installed at the German State Survey SAtelliten
POSitionierungs dienst (SAPOS), Stuttgart was
treated as base station. Its GPS receiver antenna
coordinates are exactly known. While data from
Trimble NETR8 GPS receiver, positioned at Institute
ofNavigation, UniversityofStuttgartwastreated as
roverdata.Itscoordinatesarealsoaccuratelyknown.
With this arrangement, we can compare the rover
coordinates (determined by using correction
factors)
with those already known accurately, thereby
verifyingthe efficacy ofdevelopedalgorithm. Rover
coordinates have been computed with and without
applyingcorrectionfactorsforcomparisonpurpose.
Aself‐explanatoryflowchartisshowninFigure1.