| Age | Commit message (Collapse) | Author |
|
- Map ESRI 'Local' to +proj=ortho when Scale_Factor = 1 and Azimuth = 0
- Map ESRI 'Orthographic' to a PROJ WKT2 'Orthographic (Spherical)'
which maps to +proj=ortho +f=0 to froce spherical evaluation
|
|
greater 'version numbers' are prefered over other ones, when all other comparison criteria are equal. Helps with Amersfoort RD New to EPSG:4326
|
|
2007 to WGS84 issues) (fixes #2356)
- We make createBoundCRSToWGS84IfPossible() more restrictive. If there are more
than one Helmert transformation from the CRS to WGS 84 covering the area of
use of the CRS, we do not create a BoundCRS / +towgs84
- In createOperations() filtering, we are less aggressive in discarding operations
that have the same area of use but worse accuracy. We do it only if they involve
more transformation steps.
We now get:
```
$ projinfo EPSG:5340 -o PROJ
PROJ.4 string:
+proj=longlat +ellps=GRS80 +no_defs +type=crs
$ projinfo -s EPSG:5340 -t EPSG:4326 --spatial-test intersects --summary
Candidate operations found: 2
EPSG:9264, POSGAR 2007 to WGS 84 (2), 0.5 m, Argentina
EPSG:5351, POSGAR 2007 to WGS 84 (1), 1.0 m, Argentina
```
|
|
+proj=vgridshift
|
|
accuracy, or derive it from the grid name if it is known
|
|
cases where false_easting and false_northing are 0
|
|
instead of +axis=swu (fixes #2299)
|
|
createOperations(): fix transformations between BoundCRS and Geocentric CRS
|
|
Database: register NZGD2000 -> ITRF96 transformation for NZGD2000 database
|
|
|
|
zero. Fixes https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=23239
|
|
registered transformations between compoundCRS and something else
|
|
Geog2D+GravityRelatedHeight (US .gtx)' method used by Slovakian geoids correctly deal with axis order and unit conversion, to be used as 'standalone'. Also improves when using directly 'Geographic3D to GravityRelatedHeight' method
|
|
|
|
BoundCRS in the general case let to 0 result (contributes to fixes #2232)
|
|
case of transformation between Compound of BoundVerticalCRS to GeographicCRS (contributes to fixes #2232)
|
|
a BoundCRS to a GeographicCRS (contributes to fixes #2232)
|
|
of a datum and the same datum (relates to #2232)
|
|
|
|
Inconsistent chainging of CRS (fixes #2232)
|
|
|
|
change (geographic3D horizontal)' operation
|
|
use discard change of ellipsoidal height if a Helmert transformation is involved (fixes #2225)
|
|
|
|
Make projinfo --3d --boundcrs-to-wgs84 better work (fixes #2202)
|
|
|
|
same vertical datum
|
|
|
|
names separated by comma (e.g. '+grids=foo1.gtx,foo2.gtx')
|
|
|
|
Contributes to fixing issue raised in
https://lists.osgeo.org/pipermail/gdal-dev/2020-April/052003.html
|
|
|
|
looks like the one for WGS 84 / Pseudo Mercator (fixes https://github.com/OSGeo/gdal/issues/2433) (#2174)
|
|
Map it to 'Lambert Cylindrical Equal Area' / EPSG:9835 non-spherical
method, when the ellipsoid is not a sphere. And rationalize the
handling of this for other methods with spherical vs non-spherical formulations
|
|
Adams Square II: map ESRI WKT to PROJ string, and implement iterative inverse method
|
|
|
|
grid based operations, even if they cover the whole area of use (fixes #2143)
|
|
(fixes #2115)
|
|
compoundCRS (fixes #2108)
|
|
NAD_1983_HARN_StatePlane_Colorado_North_FIPS_0501 with Foot_US unit (fixes #2086)
|
|
+nadgrids= and +pm= (#1998)
Fixes issue reported at
https://lists.osgeo.org/pipermail/gdal-dev/2020-February/051749.html
The generated pipeline assumes that the input coordinates for the grid transformation
were related to the non-Greenwich based datum, so we must compensate for that and
add logic to go back to Greenwich.
|
|
https://github.com/OSGeo/PROJ-data/pull/13 + handle 'Vertical Offset by Grid Interpolation (BEV AT)' method
|
|
to it (fixes #1982)
|
|
This is the consequence of a private email thread between me, Joel Haasdyk and
Roger Lott. I initially raised that the GDA2020 technical manual advertized the
Helmert transformation between GDA94 to GDA2020 to be a 3D one, with example of
a test point where ellipsoidal heights where modified. It appears this was intended.
The corresponding record in EPSG uses the EPSG:9607 "Coordinate Frame rotation (geog2D domain)"
method between the 2D geographic CRS of GDA94 and GDA2020. From the email exchange,
it appears that there's a lot of legacy explaining that Helmert transformations
are registered only between 2D CRS, which doesn't mean that when applied to the
corresponding 3D CRS, the change in ellipsoidal height should be discarded. Related
to that, the EPSG database, while it has methods flagged "(geog3D domain)" never uses them.
So... this changeset slightly ammends PROJ behaviour to ignore the "(geog2D domain)" flag,
but only consider the dimensionality of the source & target CRS. However, for a EPSG
transformation, those are always 2D CRS, hence introduce the use3DHelmert_ hack when
we know that ultimately the 'real' source & target CRS are 3D.
I wouldn't be surprised if in more complex pipeline the above logic would be lacking.
But it fixes at least simple transformations.
|
|
We required the 'Latitude of natural origin' parameter to be present,
but it is only a GDAL/PROJ specific thing, not a EPSG one.
|
|
(gr3df97a.txt) and map them to new +proj=xyzgridshift
|
|
Implement RFC5: Adopt GeoTIFF-based grids for grids delivered with PROJ
|
|
|
|
|
|
grid_alternatives, fix related entries and simplify/robustify logic to deal with EPSG 'Geographic3D to GravityRelatedHeight' methods
|