You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If I understand this properly, it is getting the input in feet, but giving the output in meters, when I expect the output also in feet, the target CRS.
(I do not care about geoid models so far)
If source or destination is in meters and the other in feet, it works in these two scenarios:
Here it's giving the output in meters, not in US survey feet. I would expect not doing +z_in=ft +z_out=m (leaving the scale for the parameter s33), or doing only +z_in=ft +z_out=us-ft without affine pipeline. More or less as in
Let's say we have a Geographic3D CRS, with the vertical axis in foot (in the file geog3d.txt):
When I try to convert it to a compound system with the vertical in feet, it does no apply correctly the units conversion:
If I understand this properly, it is getting the input in feet, but giving the output in meters, when I expect the output also in feet, the target CRS.
(I do not care about geoid models so far)
If source or destination is in meters and the other in feet, it works in these two scenarios:
However it applies the unit conversion twice in this case:
Other wrong case I found is going to US survey foot:
Here it's giving the output in meters, not in US survey feet. I would expect not doing
+z_in=ft +z_out=m
(leaving the scale for the parameters33
), or doing only+z_in=ft +z_out=us-ft
without affine pipeline. More or less as inHelper names:
EPSG:6318
: NAD83(2011) - 2DEPSG:6319
: NAD83(2011) - 3DEPSG:8228
: NAVD88 height (ft)EPSG:6360
: NAVD88 height (ftUS)EPSG:5703
: NAVD88 height(Note: my real use case is with a compound system with a derived vertical using the "ellipsoid" datum, but I tried to simplify the tests)
Expected behaviour
The vertical units from source and destination are consistent in the transformations.
Environment Information
proj
) : 9.3.0Installation method
The text was updated successfully, but these errors were encountered: