<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p>Dear IC and DC members,</p>
<p>We need your comments and advice . DLR has been producing the
brdm/brdx files for a long time and they are stored in the MGEX
data directory using short names. In the effort to implement
recommendations 2018-5 & 2018-7 we need the campaign/mgex data
directories in all the Data Centers to stop growing and the
brdm/brdx will have to stop.</p>
<p>CDDIS and the DLR (Peter Steigenberger and Oliver Montenbruck)
have agreed to start publishing longname brdm/brdx files in the
full repository as well as short name files in the campaign/mgex
as before. It is DLR's intention to dual submit the files until
the end of January 2020 and then submit just the longname files.</p>
<p>I need to ask for your agreement and insights moving forward
about discontinuing the brdm/brdx in 02/2020 and the integration
of the files with longnames into the normal /brdc directory in
parallel with the other files, you can find the BRDM00DLR and
BRDX00DLR in the normal brdc location, at cddis; <br>
</p>
<p><a class="moz-txt-link-freetext" href="ftp://cddis.nasa.gov/gnss/data/daily/2019/brdc/">ftp://cddis.nasa.gov/gnss/data/daily/2019/brdc/</a></p>
<p>and by sync at the GSSC;</p>
<p><a class="moz-txt-link-freetext" href="ftp://gssc.esa.int/gnss/data/daily/2019/brdc/">ftp://gssc.esa.int/gnss/data/daily/2019/brdc/</a></p>
<p><br>
</p>
<p>The brdm/brdx files will still be stored at the normal place at
BKG and IGN I suppose;</p>
<p>IGN: <a class="moz-txt-link-freetext"
href="ftp://igs.ign.fr/pub/igs/data/campaign/mgex/daily/rinex3/2019/330">ftp://igs.ign.fr/pub/igs/data/campaign/mgex/daily/rinex3/2019/330</a>
<br>
<br>
BKG: <a class="moz-txt-link-freetext"
href="https://igs.bkg.bund.de/root_ftp/MGEX/BRDC_v3/2019/330/">https://igs.bkg.bund.de/root_ftp/MGEX/BRDC_v3/2019/330/</a></p>
<p><br>
</p>
<p>I am assuming that by sync the BRDM00DLR/BRDX00DLR will find
their way to the normal /brdc storage at all Data Centers but
please confirm to DLR (in cc) in case they should proceed in a
specific way as DLR uploads to BKG and IGn directly these files .
Thanks. <br>
</p>
<p>For BKG since their own product merged navigation product
BRDC00WRD (as well as legacy brdc files for GPS and GLONASS) is
available at <a class="moz-txt-link-freetext"
href="https://igs.bkg.bund.de/root_ftp/IGS/BRDC/2019/330/">https://igs.bkg.bund.de/root_ftp/IGS/BRDC/2019/330/</a>
so this might be a good place also for BRDM00DLR.</p>
<p>If there is any concern with this please let all of us know or at
least Peter S. in cc. Thanks.</p>
<p>We are also starting to plan how to move pre-2016 station data
files from the campaign/mgex directories into the regular
repository (after renaming them correctly with longnames as needed
of course). This is a more tricky affair than initially thought so
I wanted to get agreement on the brdm/brdx issue and if no
objection is raised then we move on to the other issue. <br>
</p>
<p>Thanks again.<br>
</p>
<pre class="moz-signature" cols="72">--
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
<a class="moz-txt-link-abbreviated" href="http://www.navigation-office.esa.int">www.navigation-office.esa.int</a>
<a class="moz-txt-link-abbreviated" href="http://www.canaryspaceconsulting.co.uk">www.canaryspaceconsulting.co.uk</a>
_______________________________________________________________
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.</pre>
</body>
</html>