| Age | Commit message (Collapse) | Author |
|
|
|
This adds the NKG 2008 and 2020 transformations to proj.db. The NKG
transformations offers transformations between global reference frames
and the national realisations of ETRS89 in Denmark, Estonia, Finland,
Latvia, Lithuania, Norway and Sweden.
The 2008 transformations are already implemented in the NKG 2008 file
but will now be more accessible with the modern API.
The 2020 transformations are new to PROJ and offers and updated version
of the 2008 transformations using a new and improved deformation model
(eu_nkg_nkgrf17vel.tif). A 2020 version of the NKG transformations are
currently not available for Norway but will in all likelyhood be
included at a later point in time.
|
|
from BoundCRS of projected CRS based on NTF Paris to BoundCRS of geog CRS NTF Paris. Fixes https://github.com/OSGeo/gdal/issues/3273
|
|
|
|
|
|
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
|
|
|
|
built from EPSG code or WKT1
|
|
transformations
|
|
PROJ one
|
|
by a number of projected CRS in Colombia (fixes #589)
|
|
|
|
|
|
to other_transformation table
|
|
find a corresponding ellipsoidal vertical datum
|
|
ellipsoidal height
|
|
ellipsoidal height is found
|
|
GEOGCS[...],VERTCS[...]
|
|
ellipsoidal heights
|
|
"PROJCS[...],VERTCS[...]"
|
|
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
|
|
|
|
projinfo (unless --single-line is specified) (fixes #1543)
|
|
Update to EPSG 10.003 and make code base robust to dealing with WKT CRS with DatumEnsemble
|
|
|
|
|
|
AuthorityFactory::ObjectType::DYNAMIC_GEODETIC_REFERENCE_FRAME and DYNAMIC_VERTICAL_REFERENCE_FRAME, and make corresponding C API work
|
|
handle dynamic vertical datums, and instanciate them properly from database
|
|
This is a peculiarity of the WKT grammar. Despite ISO 19111 saying that the
prime meridian is a component of the datum, in WKT, they are placed at the
same level, for backward compatibility with earlier WKT versions. So handle
exporting and importing that. The fix is only for situation where DATUM is
the top level object (was working fine otherwise), which is a uncommon use
case. And to limit the amount of issue, on export emit the prime meridian only
if it is not Greenwich.
|
|
```
$ projinfo EPSG:32631 --3d
WKT2:2019 string:
PROJCRS["WGS 84 / UTM zone 31N",
[ ...snip ]
REMARK["Promoted to 3D from EPSG:32631"]]
```
|
|
Add:
- proj_crs_get_datum_ensemble()
- proj_crs_get_datum_forced()
- proj_datum_ensemble_get_member_count()
- proj_datum_ensemble_get_accuracy()
- proj_datum_ensemble_get_member()
Make proj_create_geographic_crs_from_datum() and
proj_create_geocentric_crs_from_datum() accept a datum ensemble.
|
|
|
|
|
|
to allow exporting DatumEnsemble to WKT < 2019.
|
|
from ObjectUsage
as mandated by ISO 19111:2019
|