[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[gpsd-dev] RTCM Format Specification in Ntrip Sourcetable
|
From: |
Max Schulze |
|
Subject: |
[gpsd-dev] RTCM Format Specification in Ntrip Sourcetable |
|
Date: |
Thu, 14 Dec 2017 23:47:15 +0100 |
|
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.5.0 |
Hello,
When inspecting the error
gpsd:ERROR: Ntrip stream STR;VRS_3_2G format not supported
for the Casterlist containing
STR;VRS_3_2G;SAPOS_VRS_3;RTCM3.1;1004(1), 1005/1006, 1007/1008, 1012(1),
1021, 1023, 1025, 1030, 1031, 1032,
1033;2;GPS+GLO;AdV;DEU;52.48;13.30;1;1;;none;B;Y;2000;
I found they specify the Stream as ";RTCM3.1;", whereas in net_ntrip.c
gpsd expects "RTCM 3.1" with a space between.
What is the reasoning for gpsd to do so? Does anyone have a copy of the
RTCM standard to look up whats "right"? Should I complain to them or
could gpsd just be made to trim out spaces?
Best regards,
M Schulze
- [gpsd-dev] RTCM Format Specification in Ntrip Sourcetable,
Max Schulze <=