Hi Javier,
I find your project a valuable initiative. I see it mostly as a verification
tool, not as an automatic CRS selection tool. In most cases the CRS selection
is imposed by other considerations and the NTRIP corrections have to match that
selection.
In regard to other comments on the list: the way I see it, information about
the CRS associated with a corrections stream should have been included in NTRIP
protocol. The fact that now it exists in RTCM 3.4, is good but it's not the
proper place. Once you have selected a corrections stream you can only check
that corrections match your intended CRS. Besides, what if you need corrections
in a different format (CMR or something else)? My view is that this information
should be provided by the NTRIP casters.
I think NTRIP 2.0 (aka RTCM 10410.1) is becoming a little long in tooth and
maybe a new version would improve on the format of the casters source table
replacing the current CSV format with something more structured like JSON.
In the meantime, your tool can provide this missing information.
Cheers,
Mircea
---- On Thu, 20 Mar 2025 10:01:27 -0400 Javier Jimenez Shaw via PROJ
<proj@lists.osgeo.org> wrote ---
Hi
This is not exactly a PROJ topic, but it's very related to CRS.
(I go to FOSSGIS in Münster next week, in case anybody want to talk with me
directly. To Mostar in July as well)
TL;DR
If you are an NTRIP provider or developer of a NTRIP software, go to the link
below. If you know somebody that is, please forward them this email. If none
of the above, probably you do not care (but you can keep reading ;).
https://github.com/Pix4D/ntrip-catalog
I have been developing this open source / open data project to properly and
easily identify the CRS for an NTRIP provider. The idea is that the providers
(or people with that knowledge) add the information to this repository.
Software that is using an NTRIP connection uses that information. And then
everything works automagically for the user, that does not have to select
anything (because they usually they don't know what to select, and do something
wrong).
So far there are the json schema, some examples, scripts, documentation, tests
(I want to add more). We developed it based on our own experience, but we know
there are many, many corner cases. I would like to hear comments and proposals
to improve it... in addition to more NTRIP provider information ;)
This is the typical win-win (open source) project that works when many parts
contribute. Please, share this email if you know anybody that could be
interested or has useful information.
When the project gets some traction the plan is to move it to the OSGeo Github
organization, if they accept it.
Thank you,
Javier.
_______________________________________________
PROJ mailing list
mailto:PROJ@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/proj
_______________________________________________
PROJ mailing list
PROJ@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/proj
