PROJ/include/proj, branch 7.2.0

build_esri_projection_mapping.py: use symbolic name EPSG_NAME_METHOD_COLOMBIA_URBAN

2020-10-25T23:31:13+00:00

Map ESRI IGAC_Plano_Cartesiano to EPSG Colombia Urban (refs #2395)

2020-10-25T23:17:13+00:00

Add +proj=col_urban projection, implementing a EPSG projection method used by a number of projected CRS in Colombia (fixes #589)

2020-10-25T20:17:29+00:00

Add logic to handle interpolationCRS in PROJBasedOperation and ConcatenatedOperation

2020-10-23T15:44:07+00:00

Improve identification of compound CRS from ESRI WKT1, and for compound CRS whose result is not in the DB but whose horiz and vertical parts are known

2020-10-20T19:14:30+00:00

Add multi-line PROJ string export capability, and use it by default in projinfo (unless --single-line is specified) (fixes #1543)

2020-10-16T16:49:58+00:00

Merge pull request #2370 from rouault/epsg10

2020-10-16T16:26:09+00:00

Update to EPSG 10.003 and make code base robust to dealing with WKT CRS with DatumEnsemble

Database query: add AuthorityFactory::ObjectType::DYNAMIC_GEODETIC_REFERENCE_FRAME and DYNAMIC_VERTICAL_REFERENCE_FRAME, and make corresponding C API work

2020-10-11T18:01:29+00:00

WKT2:2019 import/export: handle DATUM (at top level object) with PRIMEM

2020-10-10T12:23:50+00:00

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.

Make GeographicCRS::is2DPartOf3D() work with DatumEnsemble

2020-10-08T15:31:57+00:00