[IGSMAIL-6821] Re: recent Rinex 2 station data file problems from streams ...

[Nacho Romero]

Hi Thomas!

Yes indeed the RTCM3.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 receiver and according 
to whatever antenna pattern (ANTEX) it loads at that time.

Therefore it is important for precise IGS-type (geodetic) work to comply 
with RINEX standards and store the phase and code measurements 
"uncorrected" so that users of the data can apply the pattern later, 
otherwise we end up applying the pattern twice and destroying the 
antenna position.  The
stream antenna data will report "NULLANTENNA" when the pattern is 
applied bythe receiver. We have now managed to correct several stations 
participating in the IGS Real-Time service which were causing problems.

Finally the NULLANTENNA may be of use for surveyors, etc, since a 
real-time processing "in the field" will not want to have to apply the 
correction, then it makes sense that all the data from certain stations 
have the antenna pattern already applied, this is fine for those 
accuracies and while the team understands what they are doing. But for 
other work this is not good! and in any case the corrected data shall 
not be stored in RINEX files and distributed.

I hope this is what you asked!  let me know if I can clarify further,

sincerely,

Nacho

On 10/09/2013 02:06, Thomas Yan wrote:
>
> Hi Nacho,
>
> I'm interested in this comment you made, "/the data that was being 
> stored in the RINEX files had the antenna pattern applied by the 
> tracking receiver/". Are you suggesting that the GNSS receiver alters 
> the observables based on the antenna (model) set in the receiver?
>
> Best regards,
>
> Thomas
>
> **
>
> *Thomas Yan*| GNSS Technical Officer (CORS Network), Survey 
> Infrastructure and Geodesy
>
> Land and Property Information Division | Department of Finance and 
> Services
>
> Level 2, 1 Prince Albert Road Queens Square NSW 2000
>
> e: thomas.yan at lpi.nsw.gov.au <mailto:thomas.yan at lpi.nsw.gov.au> | t: 
> 02 6332 8389 | f: 02 8258 7555
>
> *From:*igsmail-bounces at igscb.jpl.nasa.gov 
> [mailto:igsmail-bounces at igscb.jpl.nasa.gov] *On Behalf Of *Nacho Romero
> *Sent:* Tuesday, 10 September 2013 12:15 AM
> *To:* igsmail at igscb.jpl.nasa.gov; igsstation at igscb.jpl.nasa.gov
> *Subject:* [IGSMAIL-6820] recent Rinex 2 station data file problems 
> from streams ...
>
> Dear all, (sorry for cross-posting!)
>
> 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)
>
> 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.
>
> 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)
>
> checking for the recent week 1755 the data for KOUC and NRMD is as 
> follows;
>
> for wk1755 (d237 -> d243):
>
> CDDIS; KOUC and NRMD from streams on d241 !!
> IGN;   KOUC and NRMD from streams on d241 !!
> BKG;   no KOUC or NRMD data all week.
>
> the CDDIS and IGN DCs have been warned to remove the d241 files for 
> these two stations and hopefully correct alternatives can be found.
>
> 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.
>
> This is important to avoid applying the antenna pattern twice to the 
> affected stations' data.
>
> please let me know if there is anything else to clarify or address ...
>
> -- 
> Best regards,
> Nacho
> IGS Infrastructure Committee Chair
>   
> _______________________________________________________________
>   
> Ignacio (Nacho) Romero
> Aerospace Engineer, PhD
> SAC @ ESA/ESOC/HSO-GN
> IGS Infrastructure Committee Chair
> www.canaryadvancedsolutions.com  <http://www.canaryadvancedsolutions.com>
> _______________________________________________________________
> 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.
> ------------------------------------------------------------------------
>
> This message is intended for the addressee named and may contain 
> confidential information. If you are not the intended recipient, 
> please delete it and notify the sender. Views expressed in this 
> message are those of the individual sender, and are not necessarily 
> the views of the NSW Government. This email message has been swept by 
> MIMEsweeper for the presence of computer viruses.
>
> ------------------------------------------------------------------------
>
> *Please consider the environment before printing this email.*
>

-- 
Best regards,
Nacho
_______________________________________________________________

Ignacio (Nacho) Romero
Aerospace Engineer, PhD
SAC @ ESA/ESOC/HSO-GN
IGS Infrastructure Committee
www.canaryadvancedsolutions.com
_______________________________________________________________
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.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.igs.org/pipermail/igsmail/attachments/20130910/fc6cca8f/attachment.html>