| Age | Commit message (Collapse) | Author |
|
Closes #2667
|
|
|
|
proj_get_crs_info_list_from_database() filter on and return celestial body name
|
|
|
|
different nature, and also adjust the method code/name to the nature of the CRS
|
|
resources
|
|
|
|
|
|
auxiliary DB
|
|
for intermediate objects
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Fixes #2482
And also add proj_context_errno_string()
Revise gie 'expect failure errno XXXX' strings
|
|
The big size of coordinateoperation.cpp could require significant amount
of RAM to build it with -O2 level, and cause compiler crashes in some
environments.
|
|
unused ones
|
|
Add option to allow export of Geographic/Projected 3D CRS in WKT1_GDAL
|
|
Remove proj_api.h
|
|
as CompoundCRS with a VerticalCRS being an ellipsoidal height, which is
not conformant. But needed for LAS 1.4 that only supports WKT1
|
|
|
|
|
|
|
|
|
|
|
|
EPSG_NAME_METHOD_COLOMBIA_URBAN
|
|
Remove 'Local' from list of unsupported ESRI projections
|
|
|
|
|
|
|
|
|
|
to other_transformation table
|
|
|
|
ellipsoidal height
|
|
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
|
|
* implement conda package building
* paths
* need libtool
* PLATFORM check
* point to my PROJ feedstock for now
* point to PROJ repos
|
|
|
|
handle dynamic vertical datums, and instanciate them properly from database
|
|
|
|
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
|
|
|
|
|