[PROJ] NATRF2022 in PROJ

[Javier Jimenez Shaw]

Now also with the geoid model SGEOID2022, and you can access it remotely
(you don't have to download it) !

It includes:
    Geographic CRSs for {N,P,C,M}ATRF2022 in the 3 flavours: geocentric,
geographic 3D and 2D.
    Vertical systems NAPGD2022 height and NAPGD2022 height (ft).
    Transformations from ITRF2020 to {N,P,C,M}ATRF2022 using a Helmert
transformation with the EPP.
    SGEOID2022 North America as GeoTIFF. It is stored as int16 to make is
smaller than 100MB. The max error is 1.1 mm. (no velocities included!)
    Transformation from ITRF2020 to NAPGD2022 height using that geoid model
and linear interpolation.
    All state planes from SPCS2022 in meters and international feet.

Check use usage in the examples in the README at
https://github.com/jjimenezshaw/NSRS-2022-PROJ

I am happy that this project is helping to find bugs, both in NGS data
(some duplicated names in SPCS) and in PROJ (corner cases when using
auxiliary database).
Thanks Even for the quick fixes, that are already in master.
It works with pyproj! At some point I will add tests ;)

As always, you can just use it, or clone and change it on your own
convenience. The generation scripts are there.

Cheers
Javier.

On Thu, 24 Apr 2025 at 17:15, Javier Jimenez Shaw <j1 at jimenezshaw.com>
wrote:

> Here you have a first version.
>
> https://github.com/jjimenezshaw/NSRS-2022-PROJ
>
> still things to improve and things to add.
>
> It is something to play with. It has a expiry date: when things are
> published in EPSG.
>
> Best regards,
> Javier.
>
> On Wed, 23 Apr 2025 at 21:25, Javier Jimenez Shaw <j1 at jimenezshaw.com>
> wrote:
>
>> Hi
>>
>> Some people in the "NGS & CGS Binational Geospatial Software Developers
>> Summit" asked about having the new reference systems (and transformations)
>> in PROJ.
>>
>> They will be there once they are published in EPSG (at least the
>> compatible pieces).
>>
>> In the meantime we thought that including some of that stuff in an
>> auxiliary database could be doable. That would be out of any release, but
>> will let some people to test it in PROJ. At least what is doable with the
>> current PROJ source code (for instance, the dynamic part of the geoid model
>> cannot be represented with the current code).
>>
>> I am working on a branch with such auxiliary db. I will write here soon
>> telling where exactly.
>> It will be completely unofficial, will not be included later in a
>> release, and may change at any time. As always, open source, so you can
>> play with it if you need/want.
>>
>> Cheers
>> Javier.
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/proj/attachments/20250428/2d4cbd8c/attachment.htm>