aboutsummaryrefslogtreecommitdiff
path: root/scripts/build_db.py
AgeCommit message (Collapse)Author
2021-05-27build_db.py: add hack to minimize diff now that we use WITHOUT ROWIDEven 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-11Database: update to EPSG v10.014Even Rouault
2021-02-09Database: update to EPSG v10.013Even Rouault
2021-01-15Database: update to EPSG v10.011Modern Slave
2020-11-18Database: update to EPSG v10.007Even Rouault
2020-10-23Database: add interpolation_crs_auth_name and interpolation_crs_code columns ↵Even Rouault
to other_transformation table
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: avoid importing duplicated alias namesEven Rouault
2020-10-08Database: import datum ensemble accuracy and members (but do not use them)Even Rouault
2020-10-06Database: add a reference_frame_epoch column to the geodetic_datum for ↵Even Rouault
dynamic datums, but not yet used
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-24build_db.py: fix previous commit (those files were transient only)Even Rouault
2020-09-24build_db.py: remove unneeded filesEven Rouault
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: import scope and remarks for conversion (fixes #2237)Even Rouault
2020-05-24Database: add a same_source_target_crs column to supersession tableEven Rouault
This is in preparation for EPSG 9.8.11 import that supersedes a number of grid transformation for US transformations, but the superseded and replacement transformations don't operate on the same (source_crs, target_crs), which is a bit weird. So in that situation, ignores the supersession.
2020-03-12Add proj_get_units_from_database() (fixes #2004)Even Rouault
2020-01-29Add EPSG records for 'Geocentric translation by Grid Interpolation (IGN)' ↵Even Rouault
(gr3df97a.txt) and map them to new +proj=xyzgridshift
2020-01-22Database: update to EPSG v9.8.6Even Rouault
Fixes #1867
2020-01-07Database: fill alias_name with EPSG aliases for CRSEven Rouault
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-10-30Rework importing of Vertical unit change from EPSG db, add support for ↵Even Rouault
Height Depth Reversal and use it in createOperations()
2019-10-27Database: add an auxiliary concatenated_operation_step table to allow ↵Even Rouault
arbitrary number of steps (fixes #1632) EPSG:9103 (NAD27 to ITRF2014 (1)) is now handled. Note:EPSG:9104 (NAD27 to ITRF2014 (2)) is not currently, since it uses for step EPSG:8861 (NAD83(HARN) to NAD83(FBN) (1)) an unsupported transformation method (NADCON5 (3D), EPSG:1075).
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-06-30Database: import scope/remarks for coordinate operation and add C APIEven Rouault
- Import scope and remarks for coordinate operations of the EPSG dataset. Database size goes from 5.2 MB to 5.55 MB - Add proj_get_scope() and proj_get_remarks()
2019-05-08scripts/build_db.py: update to reflect new proj.db structureEven Rouault
2019-03-25Database: add operation_version column to coordinate operation tablesEven 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-12-06Add API to retrieve non-deprecated equivalent of an objectEven Rouault
2018-12-06Take into account supersession information to filter out irrelevant ↵Even Rouault
transformations
2018-12-04Improve recognition of WKT1 datum namesEven 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
generated by cgit v1.2.3 (git 2.25.1) at 2025-12-15 17:46:50 +0000