aboutsummaryrefslogtreecommitdiff
path: root/test/cli/testprojinfo
AgeCommit message (Collapse)Author
2022-03-16Transformation: no longer do vertical trasnformation when doing compound CRS ↵Even Rouault
to 2D CRS / add --3d to cs2cs Previously, when computing transformation between a compound CRS and a geographic/projected 2D CRS, the behaviour was similar to implicitly promoting the 2D CRS to 3D CRS in the pipeline computation logic, hence a geoid model could be applied. But note that when doing a geographic 3D to geographic/projected 2D CRS transformation, we *did* not do this implicit promotion and if a Helmert transformation existed between the datums, it was done only in 2D. So this is a bit inconsistent and triggered the comment in https://github.com/OSGeo/PROJ/issues/2318#issuecomment-1068924513 With this commit, we no longer do any vertical transformation when doing compound CRS to the 2D CRS, but just take the transformation of the horizontal part of the compound CRS to the 2D CRS. Said otherwise, NAD83+NAVD88 to NAD83 will no longer lead to the application of the geoid model. Unless you explicitly ask for the promotion NAD83 to 3D. Also related, in https://github.com/OSGeo/PROJ/issues/1563 that went to 6.3.0, I changed cs2cs to automatically promote to 3D the CRS as soon as one of them was compound, for the sake of being consistent with the past behaviour. But it then becomes difficult to predict PROJ behaviour depending on which level of it you consider... This commit undoes that and adds an explicit --3d switch to cs2cs, similarly to projinfo, to ask for promotion. Other bug fix found in the process, when using legacy syntax, +init=epsg:4979, (WGS 84 3D), the resulting CRS was 2D and not 3D.
2021-09-15Database: update to EPSG v10.035Even Rouault
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.
2021-07-20createOperations(): fix SourceTargetCRSExtentUse::NONE modeEven Rouault
Fix issue reported in https://lists.osgeo.org/pipermail/proj/2021-July/010318.html
2021-04-12Merge pull request #2659 from rouault/fix_2603Even Rouault
CRS::normalizeForVisualization(): propagate domains/extent of original CRS (fixes #2603)
2021-04-11projinfo --list-crs --area: make it work when multiple areas matches the ↵Even Rouault
specified name
2021-04-11projinfo: add option --list-crs (#2663)Javier Jimenez Shaw
2021-04-11projinfo: add a --normalize-axis-order undocument switchEven Rouault
2021-03-28createOperation(): make sure no to discard deprecated operations...Even Rouault
if the replacement uses a grid unknown to us. Fixes issue reported at https://lists.osgeo.org/pipermail/gdal-dev/2021-March/053771.html The issue comes from the fact that EPSG has created 2 transformations using grids BALR2009.gsb ad PENR2009.gsb that supersede the one which uses the single grid SPED2ETV2 we have in PROJ-data.
2021-03-15Add support for PROJ_AUX_DB environment variable to set the path to one or ↵Even Rouault
several auxiliary DBs
2021-03-15projinfo: add a --dump-db-structure switchEven Rouault
2021-03-15SQL output: add capability to restrict the authorities into which to look ↵Even Rouault
for intermediate objects
2021-03-15projinfo: add a '-o SQL --output-id AUTH:CODE' SQL outputEven Rouault
2021-03-11Database: fix NKG transformationsEven Rouault
2021-02-09Database: update to EPSG v10.012Nyall Dawson
2020-12-15projinfo: add a --accuracy option to define the minimum accuracyEven Rouault
2020-11-01projinfo / createObjectsFromName(): support returning a datum ensembleEven Rouault
2020-10-23Database: add Finland tinshift operationsEven Rouault
2020-10-23Database: import ESRI VERTCS that uses a (geodetic) datum to express ↵Even Rouault
ellipsoidal height
2020-10-16Add multi-line PROJ string export capability, and use it by default in ↵Even Rouault
projinfo (unless --single-line is specified) (fixes #1543)
2020-05-30Database: add concatenated operations for NZGD2000 -> ITRF97/2000/2005/2008/2014Even Rouault
2020-04-04projinfo: add a --hide-ballpark optionEven Rouault
2020-01-27projinfo: add --remote-data switchEven Rouault
2020-01-27projinfo: add --searchpaths switchEven Rouault
2020-01-07projinfo: support -k datumEven Rouault
2019-12-03Database: register AUSGeoid09 and AUSGeoid2020Even Rouault
Related to https://github.com/OSGeo/proj-datumgrid/pull/66 Tune operation search so that it can work with Geog2D <--> VertCS for commandline niceness
2019-12-02Database: register the BWTA2017.gsb grid (DHDN->ETRS89 for Baden-Wurtemberg)Even Rouault
Relates to https://github.com/OSGeo/proj-datumgrid/pull/65 , https://github.com/OSGeo/proj-datumgrid/issues/22 As EPSG has no entry for it, we create a grid_transformation, as well as a dedicated area of use based on the extent of the grid, under the PROJ authority. With the hope to be able to remove it once EPSG has an entry...
2019-11-19createOperations(): in some situations, consider when going from A to D ↵Even Rouault
intermediates B and C, such there's a A->B operation and C->D operation, and A and C are not exactly the same CRS but use the same geodetic datum
2019-11-18createOperations(): fix so that GDA94 -> WGS 84 (G1762) still include a ↵Even Rouault
result through ITRF2008. Was broken in master by the addition of the 'WGS84 -> WGS 84 (Gxxx)' null operations in the PROJ authority
2019-10-12createOperations(): allow transforming from a compoundCRS of a bound ↵Even Rouault
verticalCRS to a 2D CRS
2019-09-24createOperations() sorting: sort operations that cannot be exported as PROJ ↵Even Rouault
pipelines at end
2019-09-23Document the autopromotion to 3D when mix of 2D/3D CRS in ↵Even Rouault
createOperations(), and test it (fixes #1623)
2019-09-11API: add CRS::promoteTo3D(), proj_crs_promote_to_3D() and ↵Even Rouault
proj_crs_create_projected_3D_crs_from_2D() (fixes #1587) Also add a --3d switch to projinfo
2019-09-08Use in API and utilities WKT2_2019 instead of WKT2_2018 (fixes #1518)Even Rouault
- C API: PJ_GUESSED_WKT2_2019 is added, PJ_GUESSED_WKT2_2018 aliased to it - C API: PJ_WKT2_2019[_SIMPLIFIED] is added, PJ_WKT2_2018[_SIMPLIFIED] alias to it - C++ API: similarly for WKTFormatter::Convention::WKT2_2019[_SIMPLIFIED] Those above changes should be fully backward API and ABI compatible. projinfo changes: - accept WKT2_2019 as value for -o switch. WKT2_2018 is still accepted (undocumented) - output now uses 'WKT2_2019 string:', so might break scripts that would rely on that. Other internal code references to WKT2_2018 changes to WKT2_2019, included in tests.
2019-04-22Database: use non-deprecated code for SWEREF99 for 'RH2000 height to ↵Even Rouault
SWEREF99' transformation
2019-02-24Fix data path used by cli tests (#1288)Elliott Sales de Andrade
All other tests use PROJ_LIB, and allow it to be overridden from the command-line, so do the same here.
2019-02-22proj.db: tune so that 'NGF IGN69 height to RGF93' uses the RAF09.gtx gridEven Rouault
2019-02-21Geog2D+Height -> Geog3D of same datum: avoid inserting a useless ballpark ↵Even Rouault
horizontal transformation
2019-02-21projinfo: add information about missing gridsEven Rouault
2019-02-21proj.db: add custom entry for 'RH2000 height to SWEREF99'Even Rouault
2019-02-20projinfo: advertize the use of '--spatial-test intersects' when it can bring ↵Even Rouault
more results
2019-01-15projinfo: output WKT2_2018 by default (fixes #1187)Even Rouault
2019-01-08projinfo: use PROJ.4 label for CRS, and PROJ otherwise. Add test case for ↵Even Rouault
CRS with towgs84 keyword
2018-12-17Add WKT1 grammar validation; change prototype of proj_obj_create_from_wkt()Even Rouault
2018-12-06projinfo: display deprecation infoEven Rouault
2018-12-03projinfo: add a --area option (refs #1188)Even Rouault
2018-12-01Add testing of projinfo utilityEven Rouault