| Age | Commit message (Collapse) | Author |
|
Name was erroneously set (since 8.2.0) to SOURCECRS.
Raised in https://lists.osgeo.org/pipermail/gdal-dev/2021-November/054944.html
|
|
(and thus extrapolating a VERTCS) (fixes #2757)
|
|
EPSG equivalent and have parentheses in their name
|
|
(fixes #2886)
|
|
EQUIVALENT mode if one of them is lacking an explicit CS order (refs #2886)
|
|
Add IAU_2015 CRS definitions
|
|
PROJ string with just the ellipsoid
|
|
refs OSGeo/gdal#3927)
|
|
IAU_2015:xxxx transparently
|
|
This seriously impacts French CRS users with the introduction of new
datums, geodetic CRS and projected CRS based on "RGF 93 v2" and "RGF 93 v2b",
and the previous single "RGF 93" being renamed as "RGF 93 v1".
To be noted too, the addition of a null transformation between NAD83(2011)
and WGS 84, which impacts a number of tests in the test suite.
|
|
(fixes #2822)
|
|
scope/area/extent/id attributes (fixes #2813)
For PROJJSON only, also accept the ``name`` attribute.
|
|
|
|
export (fixes OSGeo/gdal#3958)
|
|
Height/Depth reversal methods
- For instantiation from urn combined references, create a better name,
using conventions of EPSG vertical CRS
- For exportToWKT(), allow export in WKT < WKT2 for such
DerivedVerticalCRS
|
|
(fixes #2603)
|
|
|
|
|
|
Add option to allow export of Geographic/Projected 3D CRS in WKT1_GDAL
|
|
WKT1:GDAL/ESRI when GEOGCS UNIT != Degree; morph to ESRI the PRIMEM name on export
|
|
as CompoundCRS with a VerticalCRS being an ellipsoidal height, which is
not conformant. But needed for LAS 1.4 that only supports WKT1
|
|
it work when comparing easting,northing,up and northing,easting,up
|
|
comparing to a DerivedGeographicCRS/DerivedGeodeticCRS
|
|
built from EPSG code or WKT1
Related to https://github.com/OSGeo/gdal/issues/3144
|
|
export to WKT1:ESRI
|
|
whose result is not in the DB but whose horiz and vertical parts are known
|
|
|
|
verticalCRS/compoundCRS such as EPSG:4326+5773 and EPSG:4326+3855
|
|
2007 to WGS84 issues) (fixes #2356)
- We make createBoundCRSToWGS84IfPossible() more restrictive. If there are more
than one Helmert transformation from the CRS to WGS 84 covering the area of
use of the CRS, we do not create a BoundCRS / +towgs84
- In createOperations() filtering, we are less aggressive in discarding operations
that have the same area of use but worse accuracy. We do it only if they involve
more transformation steps.
We now get:
```
$ projinfo EPSG:5340 -o PROJ
PROJ.4 string:
+proj=longlat +ellps=GRS80 +no_defs +type=crs
$ projinfo -s EPSG:5340 -t EPSG:4326 --spatial-test intersects --summary
Candidate operations found: 2
EPSG:9264, POSGAR 2007 to WGS 84 (2), 0.5 m, Argentina
EPSG:5351, POSGAR 2007 to WGS 84 (1), 1.0 m, Argentina
```
|
|
candidate for 'RGF93_Lambert_93' (contributes to fixes https://github.com/qgis/QGIS/issues/32255) (#2315)
|
|
RSPS2000)
Fixes #2254
|
|
Fixes https://github.com/qgis/QGIS/issues/36111
|
|
|
|
'LKS92_Latvia_TM' name, and other cleanups/improvements (fixes #2214)
|
|
and handle +czech correctly (fixes #2199) (#2200)
* createFromProjString(): handle default parameters of '+krovak +type=crs', and handle +czech correctly (fixes #2199)
* Doc: add default values for Krovak
|
|
LCC_2SP (#2150)
As switching the 2 standard parallels for Lambert Conformal Conic 2 standard
parallels result in a equivalently numerical projection definition, take
that into account when querying the database.
|
|
geographic CRS as 3D (fixes #2122)
|
|
possible (fixes #2116)
|
|
equal to a ESRI alias (fixes #2099)
|
|
https://github.com/OSGeo/gdal/issues/2347)
|
|
NAD_1983_HARN_StatePlane_Colorado_North_FIPS_0501 with Foot_US unit (fixes #2086)
|
|
representation of EPSG:2193
Adresses https://github.com/OSGeo/gdal/issues/2303 by raising the
identification confidence from 25% to 90% (90% means equivalent for
all purposes, but name not strictly the EPSG official one)
|
|
|
|
19111
|
|
Fix identification of ESRI-style datum names starting with D_ but without alias
|
|
Fixes #1911
|
|
Fixes #1913
AuthorityFactory::createBetweenGeodeticCRSWithDatumBasedIntermediates() issued
a complex SQL query that pushes the SQLite3 query plan optimizer to its limits.
Was working reasonably with sqlite 3.11, but not with later versions.
So put less constraints in the main query and do post-processing checks and
auxiliary requests to avoid such issues.
For some unknown reason, this slightly slows down a bit execution time of the
whole test_cpp_api binary (~ 10%), but couldn't come with something better,
despite trying many variations of the main SQL query. It seems that in the
general case the non-filter LEFT JOIN on the supersession table helped,
except on this EPSG:7842 case.
|
|
to units
Fixes bug reported in https://lists.osgeo.org/pipermail/gdal-dev/2020-January/051481.html
|
|
WKT1_GDAL export: limit datum name massaging to names matching EPSG (fixes #1835)
|
|
#1835)
|