| Age | Commit message (Collapse) | Author |
|
|
|
Database (and tweaks in core): Add Finland tinshift operations
|
|
|
|
operation +proj=tinshift
|
|
ConcatenatedOperation
|
|
to other_transformation table
|
|
Improve the documentation for the Mercator projection
|
|
|
|
concatenated operation when there is a conversion step
|
|
Database: for clarity, put usage records after the object they are for
|
|
|
|
WKT1_ESRI: fix import and export of CompoundCRS
|
|
find a corresponding ellipsoidal vertical datum
|
|
ellipsoidal height
|
|
ellipsoidal height is found
|
|
GEOGCS[...],VERTCS[...]
|
|
ellipsoidal heights
|
|
Also define merc (resp. tmerc) as the conformal projection in which the
equator (resp. a chosen meridan} projects to a straight line at constant
scale.
|
|
"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.
|
|
This addresses item 1 in issue #2387
Things to note:
* I made "editorial" changes to the text. The virtues and vices of
Mercator are a hot topic. So check these out. (I judged that the
text I replaced to be pretty misleading.)
* I include the radius of the sphere/ellipsoid in the formulas (and I
did this also for my mods for tmerc documentation). Surely this is
better than leaving the reader to figure out how this is introduced.
* I include the "old-style" (ca 18th century) formulas and the newer
ones in terms of hyperbolic functions. The former may be the familiar
ones, but the latter are better for computation (more succinct, more
accurate, faster, preserve parity).
* For the inverse ellipsoidal transformation, I just say that the
formula for psi is inverted iteratively. This is probably sufficient,
but it could be expanded later.
|
|
Improve CompoundCRS identification and name morphing in VerticalCRS with ESRI WKT1
|
|
export to WKT1:ESRI
|
|
whose result is not in the DB but whose horiz and vertical parts are known
|
|
|
|
sphere (fixes GDAL PDS4 tests)
|
|
|
|
.travis.yml: re-enable s390x and add arm64
|
|
Fixes #2382
|
|
* Document the default poder_engsager algorithm for tmerc.
* Give exact expression for phi' in terms of phi
* Aadd another datapoint on range of applicability + explanation for
complex numbers.
* Update tmerc figure with one reflecting poder/engsager algo.
Courtesy of @hobu.
Co-authored-by: Charles Karney <charles.karney@sri.com>
|
|
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
|
|
limitation on Mac
|
|
|
|
|
|
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
|
|
test/gigs: 5104 is passing now. Enable it
|
|
|
|
* implement conda package building
* paths
* need libtool
* PLATFORM check
* point to my PROJ feedstock for now
* point to PROJ repos
* plot building and artifact upload
* syntax
* add proj conda package for plotting
* retab
* no doxygen
* syntax
* update docs Makefile
* doc building
* needs
* consolidate doc/plots
* plot updates
* put updated plot output into docs
* register spelling module
* use v2 download-artifact
* artifact upload
|
|
* implement conda package building
* paths
* need libtool
* PLATFORM check
* point to my PROJ feedstock for now
* point to PROJ repos
|
|
|
|
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
|
|
WKT2:2019 import/export: handle DATUM (at top level object) with PRIMEM
|
|
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.
|
|
promoteTo3D(): add a remark with the original CRS identifier (fixes #2368)
|
|
|
|
```
$ projinfo EPSG:32631 --3d
WKT2:2019 string:
PROJCRS["WGS 84 / UTM zone 31N",
[ ...snip ]
REMARK["Promoted to 3D from EPSG:32631"]]
```
|
|
|