Extra field in NTRIP source table
Quote from Matthew on July 11, 2024, 1:04 amThere appears to be an additional field for each mountpoint in the source table between the "carrier" and "nav-system" fields (highlighted in red in the block below); this doesn't match the expected NTRIP source table format (see Table 1) so raises errors in certain NTRIP client libraries. Is there any documentation available around this, or is it possible it's a duplication of the "carrier" field that's been added erroneously?
CAS;caster.canadagps.ca;2101;CANADAGPS;CANADAGPS;0;CAN;51.5;7.5;http://caster.canadagps.ca:2101/home NET;CANADAGPS;CANADAGPS;B;N;http://caster.canadagps.ca:2101/home;none;info@canadagps.ca;none STR;navisysRTK;Hsinchu;RTCM 3.3;1005(1),1077(1),1087(1),1097(1),1127(1),1230(8);2;2;GPS+GLO+GAL+BDS;CanadaGPS;TWN;24.806500;120.970600;1;0;sNTRIP;none;B;N;4380;none STR;MPjack;Stouffville;RTCM 3.3;1005(1),1077(1),1087(1),1097(1),1127(1),1230(8);2;2;GPS+GLO+GAL+BDS;CanadaGPS;CAN;43.967100;-79.242300;1;0;sNTRIP;none;B;N;4380;none STR;MP982872;Grants Pass;RTCM 3.3;1005(1),1077(1),1087(1),1097(1),1127(1),1230(8);2;2;GPS+GLO+GAL+BDS;CanadaGPS;USA;42.395600;-123.352800;1;0;sNTRIP;none;N;N;4380;none ENDSOURCETABLE
There appears to be an additional field for each mountpoint in the source table between the "carrier" and "nav-system" fields (highlighted in red in the block below); this doesn't match the expected NTRIP source table format (see Table 1) so raises errors in certain NTRIP client libraries. Is there any documentation available around this, or is it possible it's a duplication of the "carrier" field that's been added erroneously?
CAS;caster.canadagps.ca;2101;CANADAGPS;CANADAGPS;0;CAN;51.5;7.5;http://caster.canadagps.ca:2101/home NET;CANADAGPS;CANADAGPS;B;N;http://caster.canadagps.ca:2101/home;none;info@canadagps.ca;none STR;navisysRTK;Hsinchu;RTCM 3.3;1005(1),1077(1),1087(1),1097(1),1127(1),1230(8);2;2;GPS+GLO+GAL+BDS;CanadaGPS;TWN;24.806500;120.970600;1;0;sNTRIP;none;B;N;4380;none STR;MPjack;Stouffville;RTCM 3.3;1005(1),1077(1),1087(1),1097(1),1127(1),1230(8);2;2;GPS+GLO+GAL+BDS;CanadaGPS;CAN;43.967100;-79.242300;1;0;sNTRIP;none;B;N;4380;none STR;MP982872;Grants Pass;RTCM 3.3;1005(1),1077(1),1087(1),1097(1),1127(1),1230(8);2;2;GPS+GLO+GAL+BDS;CanadaGPS;USA;42.395600;-123.352800;1;0;sNTRIP;none;N;N;4380;none ENDSOURCETABLE
Quote from GeoAstra Official on July 11, 2024, 1:22 pmThank you for reporting the issue (the duplicated “carrier” field in the source table)! The issue has been fixed. Could you please try again?
Thank you for reporting the issue (the duplicated “carrier” field in the source table)! The issue has been fixed. Could you please try again?
Quote from Matthew on July 11, 2024, 6:44 pmAnother question about the source table: we've noticed that a mountpoint we're trying to connect to has an authentication value of "N" indicating there's no access protection (highlighted in red in the block below), but we expect this to be "B" similar to the other mountpoints listed. Is this related to how the mountpoint was setup?
CAS;caster.canadagps.ca;2101;CANADAGPS;CANADAGPS;0;CAN;51.5;7.5;http://caster.canadagps.ca:2101/home NET;CANADAGPS;CANADAGPS;B;N;http://caster.canadagps.ca:2101/home;none;info@canadagps.ca;none STR;navisysRTK;Hsinchu;RTCM 3.3;1005(1),1077(1),1087(1),1097(1),1127(1),1230(8);2;GPS+GLO+GAL+BDS;CanadaGPS;TWN;24.806500;120.970600;1;0;sNTRIP;none;B;N;4380;none STR;MPjack;Stouffville;RTCM 3.3;1005(1),1077(1),1087(1),1097(1),1127(1),1230(8);2;GPS+GLO+GAL+BDS;CanadaGPS;CAN;43.967100;-79.242300;1;0;sNTRIP;none;B;N;4380;none STR;MP982872;Grants Pass;RTCM 3.3;1005(1),1077(1),1087(1),1097(1),1127(1),1230(8);2;GPS+GLO+GAL+BDS;CanadaGPS;USA;42.395600;-123.352800;1;0;sNTRIP;none;N;N;4380;none ENDSOURCETABLE
Another question about the source table: we've noticed that a mountpoint we're trying to connect to has an authentication value of "N" indicating there's no access protection (highlighted in red in the block below), but we expect this to be "B" similar to the other mountpoints listed. Is this related to how the mountpoint was setup?
CAS;caster.canadagps.ca;2101;CANADAGPS;CANADAGPS;0;CAN;51.5;7.5;http://caster.canadagps.ca:2101/home
NET;CANADAGPS;CANADAGPS;B;N;http://caster.canadagps.ca:2101/home;none;info@canadagps.ca;none
STR;navisysRTK;Hsinchu;RTCM 3.3;1005(1),1077(1),1087(1),1097(1),1127(1),1230(8);2;GPS+GLO+GAL+BDS;CanadaGPS;TWN;24.806500;120.970600;1;0;sNTRIP;none;B;N;4380;none
STR;MPjack;Stouffville;RTCM 3.3;1005(1),1077(1),1087(1),1097(1),1127(1),1230(8);2;GPS+GLO+GAL+BDS;CanadaGPS;CAN;43.967100;-79.242300;1;0;sNTRIP;none;B;N;4380;none
STR;MP982872;Grants Pass;RTCM 3.3;1005(1),1077(1),1087(1),1097(1),1127(1),1230(8);2;GPS+GLO+GAL+BDS;CanadaGPS;USA;42.395600;-123.352800;1;0;sNTRIP;none;N;N;4380;none
ENDSOURCETABLE
Quote from GeoAstra Official on July 12, 2024, 10:57 amWhen the mount point is created, the default value for the Authentication field is set to “B”. However, the mount point owner can update any field in the source table. I believe the “N” value was manually updated by the mount point owner.
To update the mount point fields, please refer to the step-by-step demo in the screenshot below.
When the mount point is created, the default value for the Authentication field is set to “B”. However, the mount point owner can update any field in the source table. I believe the “N” value was manually updated by the mount point owner.
To update the mount point fields, please refer to the step-by-step demo in the screenshot below.
