WGS84(EPSG:4326) to ETRS84(EPSG:4258) Accuracy

[Tlunch]

I am aiming to transform from the WGS84 datum to the ETRS89 datum with October 2022 data with sub centimeter accuracy but i seem to be getting back data that is still offset by about a meter. What are the best practices for precision and where might I be going wrong?

My CRSs
etrs89_crs = pyproj.CRS.from_authority('epsg', '4258')
wsg84_crs = pyproj.CRS.from_authority('epsg', '4326')

my transformer
wsg84_to_etrs89 = Transformer.from_crs(wsg84_crs, etrs89_crs, only_best=True)

the application of the transformer
out_1, out_2, out_3, year = transformer.transform(first_axis, second_axis, altitude, tt = 2022.0, radians=False)

[snowman2]

With the accuracy property, you can see the expected accuracy of the transformation:

>>> wsg84_to_etrs89.accuracy
1.0

I think this matches up with the 1 meter offset you are seeing.

[Tlunch]

Is there any way to specify a more precise transform? Also my transform description is showing a noop -
<Transformation Transformer: noop>
Description: Inverse of ETRS89 to WGS 84 (1)
does this mean this transform is doing nothing?
If so how do I set it to perform a transform as these datums are almost a meter offset.

[snowman2]

You can see what transformations are available in PROJ using:

• projinfo
• TransformerGroup

[Tlunch]

From my understanding this transform should be available to the module. url

But it seems that the module is using the inverse of this transform. url

Even though that the second has a 1m accuracy and is a noop and the first has a 0.1 accuracy and is an actual operation. This seems like unintended behavior?

I have fixed the problem for my project by implementing the matrix transformation manually.

[Tlunch]

Sorry if the URLs don't work.