<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<font size="+1">Hi Thomas!<br>
<br>
<font size="+1"><font size="+1">Y</font>es indeed the RTCM<font
size="+1">3.0 standard allows for a so called "NULLANTENNA"
option in the data streams. This means that as you concluded
the receiver will apply the antenna pattern "on origin"
according to whatever the station operator configures at the
recei<font size="+1">ver and according to whatever a<font
size="+1">ntenna pattern (ANTEX) it loads</font></font> at
that time. <br>
<br>
<font size="+1">Ther<font size="+1">efore it is important for
precise IGS-type (geodetic) work to comply with RINEX
standards and store the phas<font size="+1">e and code
measurements "uncorrected" so that users of the data can
apply the pattern later, otherwise we end up applyi<font
size="+1">ng the pattern twice and destroying the
antenna position</font>. The <br>
stream antenna data will report "NULLANTENNA" when the
pattern is applied by<font size="+1"> the receiver</font>.
<font size="+1">W</font>e have now managed to correct
several stations participating in the IGS Real-Time
service which were causing problems.<br>
<br>
<font size="+1">Finally the NULLANTENNA may be of use
for <font size="+1">surveyors</font>, etc, since a
real-time processing "in the fie<font size="+1">l</font>d"
will not want to have to apply the correction, then it
makes sense that all the data from certain stations
have the antenn<font size="+1">a pattern already
applied, this is fine for those accuracies and while
the <font size="+1">team understands what they are
doing<font size="+1">.</font> <font size="+1">B</font>ut
for other work this is not good! and in any case
the corrected data shall not be stored in RINEX
files and distributed.</font></font></font><br>
<br>
<font size="+1">I hope this is what you asked! let me
know if I can clarify further,<br>
<br>
<font size="+1">sincerely,<br>
<br>
<font size="+1"><font size="+1">N</font>acho</font><br>
</font></font></font></font></font><br>
</font></font></font>
<div class="moz-cite-prefix">On 10/09/2013 02:06, Thomas Yan wrote:<br>
</div>
<blockquote
cite="mid:B20B6097C930D64E9298BB1062FB1C2B18BE89@SRV-QS-MAIL8.lands.nsw"
type="cite">
<meta http-equiv="Content-Type" content="text/html;
charset=ISO-8859-1">
<meta name="Generator" content="Microsoft Word 14 (filtered
medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:Consolas;
panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";
color:black;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
pre
{mso-style-priority:99;
mso-style-link:"HTML Preformatted Char";
margin:0cm;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Courier New";
color:black;}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:Consolas;
color:black;}
span.EmailStyle19
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
<div class="WordSection1">
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Hi
Nacho,<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">I’m
interested in this comment you made, “<i>the data that was
being stored in the RINEX files had the antenna pattern
applied by the tracking receiver</i>”. Are you suggesting
that the GNSS receiver alters the observables based on the
antenna (model) set in the receiver?<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Best
regards,<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Thomas<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><b><span
style="font-size:10.0pt;font-family:"Calibri","sans-serif";color:#1F497D;mso-fareast-language:EN-US"><o:p> </o:p></span></b></p>
<p class="MsoNormal"><b><span
style="font-size:10.0pt;font-family:"Calibri","sans-serif";color:#1F497D;mso-fareast-language:EN-US">Thomas
Yan</span></b><span
style="font-size:10.0pt;font-family:"Calibri","sans-serif";color:#1F497D;mso-fareast-language:EN-US">
| GNSS Technical Officer (CORS Network), Survey
Infrastructure and Geodesy<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:10.0pt;font-family:"Calibri","sans-serif";color:#1F497D;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span
style="font-size:10.0pt;font-family:"Calibri","sans-serif";color:#1F497D;mso-fareast-language:EN-US">Land
and Property Information Division | Department of Finance
and Services <o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:10.0pt;font-family:"Calibri","sans-serif";color:#1F497D;mso-fareast-language:EN-US">Level
2, 1 Prince Albert Road Queens Square NSW 2000<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:10.0pt;font-family:"Calibri","sans-serif";color:#1F497D;mso-fareast-language:EN-US">e:
<a moz-do-not-send="true"
href="mailto:thomas.yan@lpi.nsw.gov.au">thomas.yan@lpi.nsw.gov.au</a>
| t: 02 6332 8389 | f: 02 8258 7555<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #B5C4DF
1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b><span
style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:windowtext"
lang="EN-US">From:</span></b><span
style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:windowtext"
lang="EN-US"> <a class="moz-txt-link-abbreviated"
href="mailto:igsmail-bounces@igscb.jpl.nasa.gov">igsmail-bounces@igscb.jpl.nasa.gov</a>
[<a class="moz-txt-link-freetext"
href="mailto:igsmail-bounces@igscb.jpl.nasa.gov">mailto:igsmail-bounces@igscb.jpl.nasa.gov</a>]
<b>On Behalf Of </b>Nacho Romero<br>
<b>Sent:</b> Tuesday, 10 September 2013 12:15 AM<br>
<b>To:</b> <a class="moz-txt-link-abbreviated"
href="mailto:igsmail@igscb.jpl.nasa.gov">igsmail@igscb.jpl.nasa.gov</a>;
<a class="moz-txt-link-abbreviated"
href="mailto:igsstation@igscb.jpl.nasa.gov">igsstation@igscb.jpl.nasa.gov</a><br>
<b>Subject:</b> [IGSMAIL-6820] recent Rinex 2 station
data file problems from streams ...<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span style="font-size:13.5pt">Dear all,
(sorry for cross-posting!)<br>
<br>
Please note that we had recently incidents with the RINEX
data stored in the BKG repository. Some files coming from
streamed data where stored as hourly and data Rinex 2 files
in the BKG data center something which is not welcomed in
the IGS except in very limited circumstances (some MGEX
Rinex 3 stations)<br>
<br>
Additionally the data that was being stored in the RINEX
files had the antenna pattern applied by the tracking
receiver making the measurements unsuitable for RINEX
storage, and this circumstance caused processing problems at
several IGS ACs in particular for stations KOUC and NRMD.<br>
<br>
The BKG have now addressed this problem and from my recent
spot checks no BNC files are available in their IGS daily
data repository, but before that note that up to 12 stations
could come from "streams" (i.e. for 234 before the data
purge the affected stations were; auck2340.13o azu12340.13o
braz2340.13o chti2340.13o daej2340.13o dund2340.13o
hueg2340.13o kouc2340.13o mobs2340.13o nrmd2340.13o
suwn2340.13o wgtn2340.13o)<br>
<br>
checking for the recent week 1755 the data for KOUC and NRMD
is as follows;<br>
<br>
for wk1755 (d237 -> d243):<br>
<br>
CDDIS; KOUC and NRMD from streams on d241 !!<br>
IGN; KOUC and NRMD from streams on d241 !!<br>
BKG; no KOUC or NRMD data all week.<br>
<br>
the CDDIS and IGN DCs have been warned to remove the d241
files for these two stations and hopefully correct
alternatives can be found.<br>
<br>
Therefore I would recommend that all IGS data users check
their data repository for stations with the string "BNC" in
the header to ensure that they fully understand the source
of the data and in case of doubt re-download the affected
data files. Correct data files are available now in the Data
Centers, and the affected files have been removed from the
BKG repositories. They are implementing procedures to
prevent this problem from happening again.<br>
<br>
This is important to avoid applying the antenna pattern
twice to the affected stations' data. <br>
<br>
please let me know if there is anything else to clarify or
address ... <br>
<br>
</span><o:p></o:p></p>
<pre>-- <o:p></o:p></pre>
<pre>Best regards,<o:p></o:p></pre>
<pre>Nacho<o:p></o:p></pre>
<pre>IGS Infrastructure Committee Chair<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>_______________________________________________________________<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>Ignacio (Nacho) Romero<o:p></o:p></pre>
<pre>Aerospace Engineer, PhD<o:p></o:p></pre>
<pre>SAC @ ESA/ESOC/HSO-GN<o:p></o:p></pre>
<pre>IGS Infrastructure Committee Chair<o:p></o:p></pre>
<pre><a moz-do-not-send="true" href="http://www.canaryadvancedsolutions.com">www.canaryadvancedsolutions.com</a><o:p></o:p></pre>
<pre>_______________________________________________________________<o:p></o:p></pre>
<pre>Este mensaje, y en su caso, cualquier fichero anexo al mismo,<o:p></o:p></pre>
<pre> puede contener informacion clasificada por su emisor como confidencial<o:p></o:p></pre>
<pre> en el marco de su Sistema de Gestion de Seguridad de la<o:p></o:p></pre>
<pre>Informacion siendo para uso exclusivo del destinatario, quedando<o:p></o:p></pre>
<pre>prohibida su divulgacion copia o distribucion a terceros sin la<o:p></o:p></pre>
<pre>autorizacion expresa del remitente. Si Vd. ha recibido este mensaje<o:p></o:p></pre>
<pre> erroneamente, se ruega lo notifique al remitente y proceda a su borrado.<o:p></o:p></pre>
<pre>Gracias por su colaboracion.<o:p></o:p></pre>
<pre>_______________________________________________________________<o:p></o:p></pre>
<pre>This message including any attachments may contain confidential<o:p></o:p></pre>
<pre>information, according to our Information Security Management System,<o:p></o:p></pre>
<pre> and intended solely for a specific individual to whom they are addressed.<o:p></o:p></pre>
<pre> Any unauthorised copy, disclosure or distribution of this message<o:p></o:p></pre>
<pre> is strictly forbidden. If you have received this transmission in error,<o:p></o:p></pre>
<pre> please notify the sender immediately and delete it.<o:p></o:p></pre>
</div>
<font size="1"><font size="2">
<hr>
<p>This message is intended for the addressee named and may
contain confidential information. If you are not the <font
size="2">intended recipient, please delete it and notify
the sender. </font><font size="2">Views expressed in this
message are those of the </font><font size="2">individual
sender, and are not necessarily the views of </font><font
size="2">the NSW Government. </font><font size="2">This
email message has been swept by MIMEsweeper </font><font
size="2">for the presence of computer viruses.</font> </p>
<hr>
<p align="left"><font face="arial,helvetica,sans-serif"><strong>Please
consider the environment before printing this email.</strong></font></p>
</font></font> </blockquote>
<br>
<pre class="moz-signature" cols="72">--
Best regards,
Nacho
_______________________________________________________________
Ignacio (Nacho) Romero
Aerospace Engineer, PhD
SAC @ ESA/ESOC/HSO-GN
IGS Infrastructure Committee
<a class="moz-txt-link-abbreviated" href="http://www.canaryadvancedsolutions.com">www.canaryadvancedsolutions.com</a>
_______________________________________________________________
Este mensaje, y en su caso, cualquier fichero anexo al mismo,
puede contener informacion clasificada por su emisor como confidencial
en el marco de su Sistema de Gestion de Seguridad de la
Informacion siendo para uso exclusivo del destinatario, quedando
prohibida su divulgacion copia o distribucion a terceros sin la
autorizacion expresa del remitente. Si Vd. ha recibido este mensaje
erroneamente, se ruega lo notifique al remitente y proceda a su borrado.
Gracias por su colaboracion.
_______________________________________________________________
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>