| Age | Commit message (Collapse) | Author |
|
|
|
|
|
from BoundCRS of projected CRS based on NTF Paris to BoundCRS of geog CRS NTF Paris. Fixes https://github.com/OSGeo/gdal/issues/3273
|
|
The big size of coordinateoperation.cpp could require significant amount
of RAM to build it with -O2 level, and cause compiler crashes in some
environments.
|
|
check it in the code
This is aimed at detecting running a PROJ version against a proj.db that is not
meant to work with it. This happens sometimes in complex setups mixing PROJ
versions. Hopefully this will help spotting the issue earlier.
|
|
as CompoundCRS with a VerticalCRS being an ellipsoidal height, which is
not conformant. But needed for LAS 1.4 that only supports WKT1
This is a partial backport of https://github.com/OSGeo/PROJ/pull/2450,
with only the new ALLOW_ELLIPSOIDAL_HEIGHT_AS_VERTICAL_CRS=YES option
of proj_as_wkt()
|
|
(fixes #2468)
Corrected formula given by @evanmiller
|
|
|
|
output by cct (#2453)
Currently the output of the cct utility is different between radians
and degrees (as expected by cct), because of a bug in cct:
$ printf "1 2\n" | cct -z 0 -t 0 +proj=pipeline +step +proj=unitconvert +xy_in=deg +xy_out=rad
1.0000000000 2.0000000000 0.0000 0.0000
$ printf "1 2\n" | cct -z 0 -t 0 +proj=pipeline +step +proj=unitconvert +xy_in=deg +xy_out=deg
1.0000 2.0000 0.0000 0.0000
The arguments to the printf format string are as follows:
* radians: width 14, precision 10
* degrees: width 13, precision 4 (this is by mistake. bug!)
After the suggested fix has been applied, output will be the same for
both radians and degrees:
$ printf "1 2\n" | cct -z 0 -t 0 +proj=pipeline +step +proj=unitconvert +xy_in=deg +xy_out=rad
1.0000000000 2.0000000000 0.0000 0.0000
$ printf "1 2\n" | cct -z 0 -t 0 +proj=pipeline +step +proj=unitconvert +xy_in=deg +xy_out=deg
1.0000000000 2.0000000000 0.0000 0.0000
The cause of the bug is that cct does test if it "has radians to output",
but "neglects" to test if it "has degrees to output", resulting in using
different arguments to the printf format string in the latter case.
The fix makes cct test if it "has either radians or degrees to output".
|
|
32N' return only the exact match
|
|
WKT1:GDAL/ESRI when GEOGCS UNIT != Degree; morph to ESRI the PRIMEM name on export
|
|
GEOIDMODEL[]
|
|
it work when comparing easting,northing,up and northing,easting,up
|
|
|
|
fix parsing of a ProjectedCRS whose base is a Geocentric CRS
|
|
projected CRS
|
|
of a DerivedGeographicCRS (+proj=ob_tran +o_proj=lonlat +towgs84=....)
|
|
comparing to a DerivedGeographicCRS/DerivedGeodeticCRS
|
|
As result of a modification in logging (adding a line feed),
many changes had to be made in different places of cct.cpp.
However, one missed the line feed in input to cct.
As result of missing this, the output from cct showed a
superfluous empty line after each output line, but only if
the corresponding input line ended with comment.
Replacing the LF in the "comment" string (present if the
input line ended with comment) by a null character ('\0')
solves this issue.
Modification in logging?
https://github.com/OSGeo/PROJ/commit/37da5e243191c04607597f6b8a77acfa017a5c99
( cct: revise end-of-line handling in logging, and always output debug )
See also:
https://github.com/OSGeo/PROJ/issues/1677
( cct outputs excessive whitespace comments are included in input data )
|
|
result as soon as it is produced
This is needed when working with pipes, when stdout is not an interactive terminal,
and thus the behaviour is to have it buffered as a regular file, whereas with
an interactive terminal, each newline character causes an implicit flush.
|
|
|
|
built from EPSG code or WKT1
|
|
|
|
|
|
transformations
|
|
PROJ one
|
|
|
|
|
|
by a number of projected CRS in Colombia (fixes #589)
|
|
|
|
|
|
|
|
|
|
operation +proj=tinshift
|
|
ConcatenatedOperation
|
|
concatenated operation when there is a conversion step
|
|
find a corresponding ellipsoidal vertical datum
|
|
ellipsoidal height
|
|
ellipsoidal height is found
|
|
GEOGCS[...],VERTCS[...]
|
|
ellipsoidal heights
|
|
"PROJCS[...],VERTCS[...]"
|
|
The WKT parser on the second part was called with "RIMEM[...]" (leading P skipped),
which has no visible consequence, as we didn't care about the actual value of the
keyword due to how we used it. But this is better fixing that.
Only applies to recent master changes.
|
|
export to WKT1:ESRI
|
|
whose result is not in the DB but whose horiz and vertical parts are known
|
|
|
|
sphere (fixes GDAL PDS4 tests)
|
|
Fixes #2382
|
|
Add multi-line PROJ string export capability, and use it by default in projinfo (unless --single-line is specified) (fixes #1543)
|
|
'ellipsoid height' as name and 'h' as abbreviation
|