Re: [gpsd-dev] RTCM Format Specification in Ntrip Sourcetable

[Gary E. Miller]

Yo Max!

On Thu, 14 Dec 2017 23:47:15 +0100
Max Schulze <address@hidden> wrote:

> 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.

Ouch.

> 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?

Here is a link to RTCM 3.1

https://www.scribd.com/document/118478603/RTCM-3-1

gpsd is worried less about the 'right' format than about supporting
real world data streams.

Can you send a typical RTCM stream you are seeing?  Maybe 50 lines or
so.  Then it can be added to the gpsd regressions and support for it can
added.

RGDS
GARY
---------------------------------------------------------------------------
Gary E. Miller Rellim 109 NW Wilmington Ave., Suite E, Bend, OR 97703
        address@hidden  Tel:+1 541 382 8588

            Veritas liberabit vos. -- Quid est veritas?
    "If you can’t measure it, you can’t improve it." - Lord Kelvin

pgplAEEZe4Oqe.pgp
Description: OpenPGP digital signature