[teqc] GLONAS SV ID 255 filter?

Isaac Hoyas Ester isaac.hoyas.ester at rokubun.cat
Fri Jan 12 02:01:29 MST 2018


 

Lou, Evon, appreciated, yes, you are correct, the RINEX file was
generated by TEQC out of ublox raw data, both files (RINEX obs and ublox
UBX) can be downloaded from
https://www.dropbox.com/sh/uchby3qqdqukz76/AAAreomJNy3r8cmoXcSh1K0Xa?dl=0


--- Isaac

A 12.01.2018 12:00 AM, Lou Estey escrigué: 

> Yes, that's right. So 'R255' in an obs file means it breaks the RINEX specification.
> 
> --lou
> 
>> Out of curiosity, isn't the SV designation required to be exactly one letter and two numbers? Evon On Thu, Jan 11, 2018 at 8:08 AM, Lou Estey <lou at unavco.org <mailto:lou at unavco.org>> wrote: Isaac, Did teqc generate the RINEX file with 'R255', as shown below? ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Louis H. Estey, Ph.D. office: [+001] 303-381-7456 <tel:303-381-7456> UNAVCO, 6350 Nautilus Drive <https://maps.google.com/?q=6350+Nautilus+Drive&entry=gmail&source=g [1]> FAX: [+001] 303-381-7451 <tel:303-381-7451> Boulder, CO 80301-5554 e-mail: lou unavco.org <http://unavco.org [2]> "If the universe is the answer, what is the question?" -- Leon Lederman ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ On 11-Jan-18 09:04 AM, Isaac Hoyas Ester wrote: Hello, I have been trying to find instructions on how to use TEQC to filter out GLONASS observations with slot ID 255, this may happen because the Ublox receiver that I'm trying to convert raw data from
may be able to decode data from a GLONASS SV before it can identify the SV. When this occurs UBX-RXM-SFRBX messages will be issued with an svId of 255 to indicate "unknown". Here you have a RINEX observation epoch example showing a GLONASS SV with slot ID 255: 17 12 22 22 9 6.9940000 0 17G24G29G25G31G12G32R08R09G04G02R255R10 R19R20G14R18R16 117546916.037 <tel:117546916.037> 6 22368465.110 40.000 -3572.229 96793892.692 8 18419251.051 49.000 865.332 98761291.535 8 18793667.599 48.000 -530.120 108401382.976 7 20628091.097 44.000 2600.400 106915274.094 7 20345288.104 46.000 -2394.498 110635793.326 6 21053314.460 40.000 -2140.314 117523692.247 5 21946725.423 34.000 -1896.710 94773244.591 7 17748010.382 <tel:17748010.382> 46.000 1014.036 114537730.343 5 21795793.846 34.000 2758.222 113756995.669 7 21647232.534 42.000 -1099.824 108373678.553 7 20316337.163 43.000 4082.983 111241066.317 6 20868543.848 36.000 3423.625 93974283.751 7 17567507.189 45.000 580.784 108749564.993 6 20336700.814
37.000 4121.685 108824714.448 6 20708650.009 40.000 -573.414 104444377.513 6 19565957.947 <tel:19565957.947> 40.000 -3400.356 102423064.459 6 19173840.114 <tel:19173840.114> 40.000 -2393.646 Many thanks for your support. Best Regards Isaac
> 
> _______________________________________________
> teqc mailing list
> teqc at postal.unavco.org
> https://postal.unavco.org/mailman/listinfo/teqc [3]
 

Links:
------
[1]
https://maps.google.com/?q=6350+Nautilus+Drive&entry=gmail&source=g
[2] http://unavco.org
[3] https://postal.unavco.org/mailman/listinfo/teqc
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://postal.unavco.org/pipermail/teqc/attachments/20180112/641279e5/attachment.html>


More information about the teqc mailing list