Closed filipkral closed 3 years ago
Not a bug. I'm building these packages from original sources using the release branch.
Just checked via docker run
and the result from test matches with output. So maybe, there is some error in the web implementation.
Anyway, if you do not mind, I will add your test to this repo for coverage.
docker run --rm osgeo/proj /bin/bash -c "echo 826158.063 2405844.125 | cs2cs +init=epsg:27700 +to +init=epsg:3035"
Output (docker): 4316331.55 5331101.98 0.00
OK, I took it with https://github.com/OSGeo/PROJ/issues/2955
Describe the bug I'm getting unexpected results when projecting from British National Grid to Lambert Equal Area (on ETRS1989 datum).
To Reproduce Explore the values asserted in this code
The expected projected coordinates come from: https://epsg.io/transform#s_srs=27700&t_srs=3035&x=826158.0630000&y=2405844.1250000 The expected projected coordinates were also retuned from another, proprietary. transformation library I used.
Environment information:
Additional context This may be ultimately a PROJ issue, but I'm using it through
MaxRev.gdal
so this seems to be the right place to start. I've been researching about PROJ (and the changes in version 4, 6, and onwards), but nothing really explained this discrepancy. I suspect the datum transformation is not applied because when I changed the TOWGS parameters of the British National Grid WKT string to all zeros, I got exactly the same results. Also theSetAxisMappingStrategy
calls have no impact in this case. It may also be that we are missing the transformation grids needed for this transformation. But how do we install grid shift files withMaxRev.gdal
?