Modify ↓
Opened 10 years ago
Closed 8 years ago
#28 closed defect (wontfix)
wrong 1057 message?
| Reported by: | stuerze | Owned by: | stoecker |
|---|---|---|---|
| Priority: | normal | Component: | BNC |
| Version: | Keywords: | ||
| Cc: | stuerze, sarag@… |
Description
Message from Sara Gerrard:
I have been successfully downloading rtcm data, specifically message types 1057 and 1058 from your casters, but there are ways in which the messages seem inconsistent with the expected format
..
I am still, however, interested in why the header appears in the middle of the 1057 message?
..
I have just collected this small data set from products: IGS03. There are two files attached - the full data set and then one with just a 1057 message (first one that appears in full set).
Attachments (2)
Change History (3)
by , 10 years ago
| Attachment: | test_raw_data.txt_140603 added |
|---|
by , 10 years ago
| Attachment: | test_raw_data_JUST_1057.txt_140603 added |
|---|
comment:1 by , 8 years ago
| Resolution: | → wontfix |
|---|---|
| Status: | new → closed |
Note:
See TracTickets
for help on using tickets.
The raw data format from BNC does not take care of the input stream characteristics, but only of the network connection - it does not know about RTCM blocks at this stage. This means headers can also be in the middle of a message. When analysing without BNC to get continous blocks you need to strip the headers and join the matching streams before analysing the contents.