@Dzertanoj you know the CRS of ORGN, and you have to introduce it manually to postprocess the data. Be sure that many users do not know about it, or they don’t care. Wouldn’t it be much better if the software were tagging automatically the coordinates? That is less error prone. That’s the purpose of https://ntrip-catalog.org As an open source/data project, it needs the contribution of the NTRIP providers. Do you know how they are going to do with NATRF2022?

@StephaneP I mentioned your article in this talk in FOSS4G: https://www.youtube.com/watch?v=M2ck3cAGvhg , in the slide 35

Hi. I’m the main contributor of ntrip-catalog.org , an open source/data repository to automatically find that information that is missing: the CRS of the NTRIP provider. Looks like you suffered that too. Please, help us to contact more providers to contribute to the repository with their data. Thanks!

PS next year it is going to be fun having in parallel NAD83(2011) and NATRF2022