| Age | Commit message (Collapse) | Author |
|---|
|
|
|
RFC3: Dependency management
|
|
Added Fortran-Proj, bindings for PROJ in Fortran.
|
|
|
|
sweep parameter depending on the satellite (fixes #1179)
|
|
squashed cherry-picking of master commits:
be58913801f400d9b00c8c3e8cdecb7e5fa89d38
5511ab8f4d75d7df6712619c77d2fa3e5dc07f1c
1b5e8db29f58627cdb722a6083348486e78bc4b0
9ae6713916f495b6f150915609a545275c5de699
0196fc54f779ef3a8045af0a3650b21908a178d2
ed0ee0bc9f0bada66eb42f6d0ed602d12558cf7c
2f48fe12dbd9be9075ea1359f01b4243b6e415bb
|
|
Closes #1159
|
|
|
|
|
|
These are included with proj-datumgrid:
- Australia
- Canada: ntv2_0.gsb
- Germany: BETA2007.gsb
|
|
|
|
|
|
|
|
|
|
This removes some questions that are no longer valid
(covered elsewhere in the docs), adjusts the wording in other questions
and fixes formatting and making it proper rst/sphinx syntax.
With this, #1070 is almost fixed.
|
|
|
|
|
|
|
|
Any text written after the coordinate input will automatically be
forwarded to the output stream. Text in columns before the coordinate
input is discarded in the output. This works for any combination of -c, -t
and -z parameters:
$ echo 12 56 100 2018.0 comment comment | cct +proj=merc
1335833.8895 7522963.2411 100.0000 2018.0000 comment commen
$ echo text 12 56 100 2018.0 comment | cct -c 2,3,4,5 +proj=merc
1335833.8895 7522963.2411 100.0000 2018.0000 comment
$ echo text 12 56 comment | cct -c 2,3 -t0 -z0 +proj=merc
1335833.8895 7522963.2411 0.0000 0.0000 comment
$ echo 12 56 comment | cct -t0 -z0 +proj=merc
1335833.8895 7522963.2411 0.0000 0.0000 comment
Closes #918
|
|
Added the version of introduction and removed comment about angular and
linear output (it's an internal implementation detail that users doesn't
need to be aware of).
|
|
Specify number of decimals to display when transforming coordinates with either proj, cs2cs or cct.
|
|
image to caption
|
|
[BREAKING] Helmert: add +convention=position_vector/coordinate_frame, forbids +transpose (fixes #1091)
|
|
|
|
proj only does projections, hence we should use the word conversion instead of transformation in this context.
|
|
|
|
added usage example
|
|
|
|
bug in example - changed +t_in=gpsweek to +t_in=gps_week
|
|
Fixes for webmerc projection (fixes #1078)
|
|
forbids +transpose (fixes #1091)
As identified in #1091, Helmert implementation in PROJ 5.0 and 5.1 is confusing.
It happens that by default it used the coordinate_frame convention, contrary to
the position_vector convention used traditionaly for +towgs84. The documentation
of Helmert was also wrongly specifying that the default convention was
position_vector.
This commit:
- bans the confusing +transpose parameter
- removes the concept of a default convention, since in practice both are
equally found, and requires +convention as soon as a rotational term parameter
is present.
For translation only, convention is ignored and optional, as having no effect.
- fixes all the identified uses of proj=helmert in code, doc and tests
This is obviously a breaking change:
- users will have to adapt their pipeline expressions
- in particular, init files that would use helmert must be adapted
However, as designed, the break will be explicit, and not silent.
|
|
This is intended to supersed https://github.com/OSGeo/proj.4/pull/1080
with a number of differences.
What is kept from #1080 is not forcing the ellipsoid_params to be the one
of a sphere. This is not required for correct coordinate computation and
avoid lying on the various distorsion parameters.
For better interoperability with EPSG, we also no longer force the
lam0 parameter to 0, because
https://www.epsg-registry.org/export.htm?gml=urn:ogc:def:method:EPSG::1024
has a provision for it, even if in practice they will always be zero
phi0 should always be zero and is not used by the formulas.
Another difference with the #1080 approach is that we do not force the
WGS84 ellipsoid. Perhaps someone will use webmerc for another planet,
even if that is a crazy idea...
|
|
|
|
|
|
|
|
|
|
Implement the Equal Earth projection (closes #1085)
|
|
|
|
|
|
|
|
|
|
As mentionned in #1071, it is often unclear how the offset of a vertical grid
is applied.
|
|
|
|
Closes #981
|
|
This was left out when documented the various proj_create_*
functions. Added proj_context_errno description as well
since it was undocumented and is needed when creating PJs
for a specific context.
|
|
|
|
|
|
|
|
HOWTO-RELEASE updated accordingly.
|
|
Internally PROJ uses radians so of course that is what we
need to convert our input coordinates to before processing
with proj_trans().
|
