| Age | Commit message (Collapse) | Author |
|
Breathe 4.12.0 (as pulled by MacOSX builds such as
https://travis-ci.com/OSGeo/proj.4/jobs/185395222)
does not seem to like default initialization in documented C++ structs (regression/bug)
/Users/travis/build/OSGeo/proj.4/docs/source/development/reference/cpp/io.rst:6:Parsing of expression failed. Using fallback parser. Error was:
Error in postfix expression, expected primary expression or type.
If primary expression:
Invalid definition: Expected identifier in nested name. [error at 67]
std::string osgeo::proj::io::AuthorityFactory::CRSInfo::authName = {}
-------------------------------------------------------------------^
If type:
Invalid definition: Expected identifier in nested name. [error at 67]
std::string osgeo::proj::io::AuthorityFactory::CRSInfo::authName = {}
-------------------------------------------------------------------^
|
|
By mistake the second eccentricity was used in a few places in the
Molodensky transform. According to the literature the first eccentricity
should always be used in the eccentricity.
This only affects the output slightly. Reported test coordinates
differed by less than a millimeter.
Fixes #1321
|
|
Fixes https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=11699
Credit to OSS Fuzz
|
|
|
|
Fixes https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=11893
Credit to OSS Fuzz
|
|
A division by zero caused NaN values to be returned.
Fixes https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=12062
Credit to OSS Fuzz
|
|
Fixes https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=12799
Credit to OSS Fuzz
|
|
Fixes https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=12909
Credit to OSS Fuzz
|
|
Fixes https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=13028
Credit to OSS Fuzz
|
|
Molodensky: avoid division by zero
|
|
Fixes https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=13069
Credit to OSS Fuzz
|
|
Valid eccentricity should be between 0 (included) or 1 (excluded)
Fixes https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=13665
Credit to OSS Fuzz
|
|
The commands crs_src and crs_dst are introduced to allow operation
initialization with proj_create_crs_to_crs. This has the benefit of
using proj.db to select the proper operation. Additionally axis order is
respected for the coordinate systems that are tested. This is beneficial
when running the GIGS test suite for instance.
|
|
|
|
|
|
And publish link to corresponding promoted and public OGC doc:
http://docs.opengeospatial.org/as/18-005r4/18-005r4.html
|
|
|
|
Counter-intuitively, this means removing checks for nullptr. The
compiler sees these checks and thinks the one remaining dereference is
missing a check. However, since pj_get_default_ctx cannot return
nullptr, these tests are redundant.
|
|
|
|
|
|
behaviour, for example on netBSD 8
|
|
on netBSD 8 and is useless on Linux
|
|
#1172), and fix inaccurate inverse method
|
|
Doc: add minimal documentation for patterson, compact miller, misrsom, natearth2, sch and times projections
|
|
-D_GLIBCXX_ASSERTIONS on WKT with PARAMETERFILE (fixes #1290)
|
|
|
|
|
|
transformations between geographic CRS of same datum (typically 3D to 2D)
|
|
horizontal transformation
|
|
|
|
|
|
used to know if it includes a very approximative transformation term
|
|
name we are lacking an ellipsoid height to vertCRS height correction
|
|
swap/unitconvert to avoid useless simplification rules
|
|
more results
|
|
|
|
|
|
|
|
transformation when needed, and also sort Null geographic offset transformation in last
|
|
from X to X' in transformation name
|
|
values in the grids with US VERTCON grids that are in millimeters
|
|
substitution for VERTCON method
|
|
Relax tolerances in a few unit test, and in laea code.
Seen with gcc 5.3 and also 7.1
Related to the use of the 387 floating-point math, since they
disappear with gcc 7.1 if using non-default -mfpmath=sse -msse
|
|
there is no direct transformation
|
|
PJ object returned by proj_create_crs_to_crs() when there are several alternatives
|
|
proper CoordinateOperation so that we can call proj_get_source_crs() on it for example
|
|
|
|
Clean up time handling in helmert and deformation
|
|
table, should be considered as known to be sorted first
|
|
The +t_obs parameter was confusing for users since it effectively
overwrote the observation time in input coordinates. To make it more clear
what is the operation is doing, users are now required to directly specify
the time span for which they wish to apply a given deformation. The parameter
+dt has been added for that purpose. The new parameter is mutually
exclusive with +t_epoch. +dt is used when deformation
for a set amount of time is needed and +t_epoch is used (in
conjunction with the observation time of the input coordinate) when
deformation from a specific epoch to the observation time is needed.
|