aboutsummaryrefslogtreecommitdiff
path: root/data/sql/vertical_datum.sql
AgeCommit message (Collapse)Author
2020-10-23Database: for clarity, put usage records after the object they are forEven Rouault
2020-10-11Database: add a frame_reference_epoch column in vertical_datum to be able to ↵Even Rouault
handle dynamic vertical datums, and instanciate them properly from database
2020-10-08Database: import datum ensemble accuracy and members (but do not use them)Even 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-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-11-18Database: add a publication_date column to geodetic_datum and vertical_datumEven Rouault
Populated from realization_epoch column from EPSG The 'publication_date' naming is from OGC Topic 2, and hasn't been yet adopted by the EPSG dataset. See http://docs.opengeospatial.org/as/18-005r4/18-005r4.html , Annex G, clause 11 and https://32zn56499nov99m251h4e9t8-wpengine.netdna-ssl.com/wp-content/uploads/2019/09/EPSG-relational-data-model-changes_2019-09-18.pdf
2019-11-12Database: update to EPSG v9.8.4Even Rouault
2019-07-25Database: update to EPSG 9.7.0Even Rouault
2019-03-25Database: update to EPSG v9.6.1Even Rouault
2019-02-22proj.db: update to EPSG 9.6.0Even Rouault
Minor update w.r.t 9.5.5 that adds a few new coordinate operations.
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
generated by cgit v1.2.3 (git 2.25.1) at 2025-12-26 11:59:07 +0000