aboutsummaryrefslogtreecommitdiff
path: root/data/sql/projected_crs.sql
AgeCommit message (Collapse)Author
2022-03-09Database: update to EPSG v10.055Even Rouault
2022-02-13Database: update to EPSG v10.054Even Rouault
2022-01-04Database: update to EPSG 10.044Even Rouault
2021-11-04Database: update to EPSG v10.039Even Rouault
2021-10-07Database: update to EPSG v10.037Even Rouault
2021-09-27Database: update to EPSG v10.036Even Rouault
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-08-28Database: update to EPSG v10.033Even Rouault
2021-07-08Database: update to EPSG v10.028Even Rouault
2021-06-19Database: update to EPSG v10.027Even Rouault
2021-06-10Database: update to EPSG v10.026Even Rouault
2021-05-16Database: update to EPSG v10.022Even Rouault
2021-04-23Database: update to EPSG v10.019Even Rouault
Non-trivial updates: - some vertical CRS are now encoded as DerivedVerticalCRS. e.g EPSG:8228 "NAVD88 height (ft)", with base EPSG:5703 "NAVD88 height". As we don't have support in our PROJ db model for DerivedVerticalCRS, modify the import script to 'resolve' the derivation up to the original datum. - Method EPSG:1069 'Change of Vertical Unit' is no longer used. It is replaced by a generic-purpose EPSG:1104 method that doesn't take any conversion factor. And generic conversions EPSG:7812 and EPSG:7813 are now used in concatenated operations, which require code changes as well.
2021-04-01Database: update to EPSG 10.017Even Rouault
2021-02-09Database: update to EPSG v10.013Even Rouault
2021-01-15Database: update to EPSG v10.011Modern Slave
2020-12-16Database: update to EPSG v10.008Even Rouault
2020-11-18Database: update to EPSG v10.007Even Rouault
2020-10-23Database: for clarity, put usage records after the object they are forEven Rouault
2020-10-06Database: "minimal" update to EPSG v10.003Even Rouault
Content mostly unchanged since v9.9 This update is "minimal" in that it mostly reflects the removal of the 'area' table, replaced now by 'extent', 'scope' and 'usage' Other new aspects of EPSG v10 are left aside.
2020-09-09Database: update to EPSG 9.9Even Rouault
2020-08-02Database: update to EPSG v9.8.15 databasejmckenna
Co-authored-by: jmckenna <jmckenna@gatewaygeomatics.com> Co-authored-by: Javier Jimenez Shaw <j1@jimenezshaw.com> Co-authored-by: Even Rouault <even.rouault@spatialys.com>
2020-06-19Database: update to EPSG v9.8.12Even Rouault
2020-05-24Database: update to EPSG v9.8.11Even Rouault
2020-04-07Database: update to EPSG v9.8.9Even Rouault
2020-01-22Database: update to EPSG v9.8.6Even Rouault
Fixes #1867
2019-09-23Database: update to EPSG 9.8.2Even Rouault
With limitation of https://github.com/OSGeo/PROJ/issues/1632 regarding concatenated operations with more than 3 steps.
2019-07-25Database: update to EPSG 9.7.0Even Rouault
2019-05-25Database: update to EPSG v9.6.3Even Rouault
2019-03-25Database: update to EPSG v9.6.1Even Rouault
2018-11-14Implement RFC 2: Initial integration of "GDAL SRS barn" workEven Rouault
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