PROJ/src/proj.def, branch inverse-fix

Implement RFC 2: Initial integration of "GDAL SRS barn" work

2018-11-14T21:48:29+00:00

This work mostly consists of:
- a C++ implementation of the ISO-19111:2018 / OGC Topic 2
  "Referencing by coordinates" classes to represent Datums,
  Coordinate systems, CRSs (Coordinate Reference Systems) and
  Coordinate Operations.
- methods to convert between this C++ modeling and WKT1, WKT2
  and PROJ string representations of those objects
- management and query of a SQLite3 database of CRS and Coordinate Operation definition
- a C API binding part of those capabilities

This is all-in-one squashed commit of the work of
https://github.com/OSGeo/proj.4/pull/1040

Remove proj_geocentric_latitude from public API

2018-11-10T15:35:42+00:00

Closes #1107

Move struct definitions for proj_list_* functions to proj.h

2018-10-16T19:32:00+00:00

With projects.h not being available to outside users anymore we need to
define PJ_UNITS, PJ_ELLPS, PJ_PRIME_MERIDIANS and PJ_OPERATIONS
elsewhere.

Related pj_get_*_ref() functions have been removed in favour
of their proj_ namespaced counterparts.

char pointers have been changed to const char pointers.

Resolves #983
Resolved #1147

Make char pointers const

Add proj_errno_string() to proj.def

2018-06-20T09:47:31+00:00

Add pj_isnan to proj.def to avoid linking errors for some MSVC versions

2018-05-23T15:20:20+00:00

Add proj_context_errno to API and missing proj_geod to proj.def (#791)

2018-02-10T23:42:05+00:00

expand proj_geoc_lat to proj_geocentric_latitude (#751)

2018-02-01T15:52:10+00:00

Remove unnecessary functions and restructure proj.def. Closes #728

2018-02-01T13:14:15+00:00

Introduce compatibility for cs2cs-style proj-strings into the 4D API.

2018-01-31T15:25:32+00:00

Parameters such as towgs84, nadgrids and geoidgrids was previously only
handled by pj_transform(). This commit add a compatibility layer in
proj_create() by calling the pj_cs2cs_emulation_setup() function. This
function sets up a handful of predefined transformation objects on the
PJ object that is being created. Each of these transformation objects
are related to the cs2cs-style parameters we are trying to emulate in
the 4D API. That is, if the +towgs84 parameters is used we create
P->helmert with the parameters specified in +towgs84. Similarly for
+axis, +nadgrids and +geoidgrids. When these transformation objects
exists we use them in the prepare and finalize functions in pj_fwd/
pj_inv. If no cs2cs-style parametes are specified we skip those
parts of the prepare and finalizing steps.

Co-authored-by:Thomas Knudsen 
Co-authored-by:Kristian Evers

Add pj_has_inverse().

2018-01-31T09:56:11+00:00

With the introduction of the "inverted" flag on PJ objects
you can no longer rely on checking that the inv, inv3d and inv4d
functions are available on said PJ object. The function is used
internally a few places and otherwise exposed in proj_api.h to
ensure that users of the old programming interface can safely
check if an operation has an inverse.