| Age | Commit message (Collapse) | Author |
|
substitution for VERTCON method
|
|
there is no direct transformation
|
|
table, should be considered as known to be sorted first
|
|
the push/pop v_3 operator to preserve the Z component
|
|
from +proj=helmert/molodensky since there are ambiguities
|
|
* Make tmerc an alias for etmerc
This switches the algorithm used in tmerc to the Poder/Engsager
tmerc algorithm. The original tmerc algorithm of Evenden/Snyder
origin can still be accessed by adding the +approx flag when
initializing a tmerc projection. The +approx flag can also
be used when initializing UTM projections, in which case the
Evenden/Snyder algorithm is used as well.
If a tmerc projection is instantiated on a spherical earth
the Evenden/Snyder algorithm is used as well since the
Poder/Engsager algorithm is only defined on the ellipsoid.
+proj=etmerc can still be instantiated for backwards compatibility
reasons.
Co-authored-by: Kristian Evers <kristianevers@gmail.com>
Co-authored-by: Even Rouault <even.rouault@spatialys.com>
|
|
https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=12854. Credit to OSS Fuzz
|
|
bindins terms in generated pipeline (fixes #1232)
|
|
|
|
(fixes #1224)
|
|
parsed appropriately on the reading side
|
|
As discussed in https://github.com/OSGeo/proj.4/issues/1214#issuecomment-452084720,
the introduction of a new PROJ.5 format to export CRS using pipeline/unitconvert/axisswap
as an attempt of improving the PROJ.4 format used by GDAL and other products is
likely a dead-end since it is still lossy in many aspects and can cause confusion
with coodinate operations.
Consequently the PROJ_5 convention will be identical to PROJ_4 for CRS export.
Note: on the import side, I've kept the code that could parse unitconvert and
axisswap when building a CRS definition from a pipeline. It is there as a hidden
feature as it was kind of a tear to remove that code in case it might still be
useful...
|
|
operations when neededs (fixes #1197)
|
|
|
|
|
|
structures
|
|
|
|
have no declared extent
|
|
|
|
2 definitions of PROJCRS that lack it)
|
|
extent of their base CRS)
|
|
projections/ transformations/ tests/ subdirectories
|