[IGS-DCWG-176] Rinex 2 and Rinex 3 'brdc' and 'BRDC00' files

[Nacho Romero]

Dear Data Centers,

Please let Carey and I know as soon as possible how you are currently 
generating the 'brdc' and 'BRDC00' files at your Data Center. Are you 
merging all the '18n', '18g' , '_MN'  station navigation files with your 
own tools? with teqc? with someone else's tool?

for example at CDDIS for Rinex 2 they use the CCRINEXN and CCRINEXG 
fortran programs for Rinex 2, and a new Rinex 3 merging script for the 
'BRDC00IGS',

what do IGN, BKG, SIO, GSSC, etc use? who simply copies the brdc from 
some other DC? we need to know the details as we have detected some 
issues with the 'merged' navigation files which leads me to the second 
point below ...


URGENT - Please exclude the following stations from your RINEX 2 
navigation file merging process since these stations are mixing CNAV and 
LNAV navigation messages which create inconsistent files for the final 
users:

AREQ
ARHT
BOGT
FAIR
GLPS
HRAO
MOIU


Thanks for your collaboration,

Nacho Romero, Infrastructure Committee Chair
Carey Noll, Data Center Working Group Chair
David Maggert, IGS Network Coordinator
  

-- 
Best regards,
Nacho
_______________________________________________________________

Ignacio (Nacho) Romero
Aerospace Engineer, PhD
CSC Ltd @ ESA/ESOC/OPS-GN
Satellite Navigation Engineer @ ESOC Navigation Support Office
IGS Infrastructure Committee Chair
www.navigation-office.esa.int
www.canaryspaceconsulting.co.uk
_______________________________________________________________
This message including any attachments may contain confidential
information, according to our Information Security Management System,
  and intended solely for a specific individual to whom they are addressed.
  Any unauthorised copy, disclosure or distribution of this message
  is strictly forbidden. If you have received this transmission in error,
  please notify the sender immediately and delete it.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.igs.org/pipermail/igs-dcwg/attachments/20180803/5c0d6bc7/attachment.html>