PROJ - Forked from https://github.com/OSGeo/PROJ

Age	Commit message (Collapse)	Author
2021-09-17	Database: add a 'anchor' field to geodetic_datum and vertical_datum tables	Even Rouault
	Update database layout version number to 1.2 consequently This new capability will be used by IAU planetary CRS (refs #2601)
2021-04-06	Database: do not create Helmert transformations in IGNF between CRS of ↵	Even Rouault
	different nature, and also adjust the method code/name to the nature of the CRS
2021-04-06	Database: minor refresh of ignf.sql and import script with new locations of ↵	Even Rouault
	resources
2020-10-23	Database: add interpolation_crs_auth_name and interpolation_crs_code columns ↵	Even Rouault
	to other_transformation table
2020-10-11	Database: 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-08	Database: import datum ensemble accuracy and members (but do not use them)	Even Rouault

2020-10-06	Database: add a reference_frame_epoch column to the geodetic_datum for ↵	Even Rouault
	dynamic datums, but not yet used
2020-10-06	Database: "minimal" update to EPSG v10.003	Even 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-01-25	Implement RFC 5	Even Rouault

2020-01-23	Database: add a geoid_like value for proj_method column of ↵	Even Rouault
	grid_alternatives, fix related entries and simplify/robustify logic to deal with EPSG 'Geographic3D to GravityRelatedHeight' methods
2019-12-10	Database: update to IGNF v3.1.0	Even Rouault

2019-11-18	Database: add a publication_date column to geodetic_datum and vertical_datum	Even 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-27	Database: 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-04-22	Database: make conversion & helmert_transformation updatable views	Even Rouault
	- Transform conversion as a view, and when inserting into it, actually insert into 3 tables: conversion_table, conversion_method and conversion_param, so that method and parameter names are not repeated each time. - Similarly for helmert_tranformation, insert into helmert_transformation_tabl and coordinate_operation_method. This reduces the db size from 6 344 704 bytes to 5 853 184 bytes, without significant slowdown for queries.
2019-03-25	Database: add operation_version column to coordinate operation tables	Even Rouault

2019-03-25	Database: update to IGNF v3.0.3	Even Rouault

2018-11-20	Database: use official IGNF.xml registry to create content from the IGNF ↵	Even Rouault
	authority Up to now, we re-processed the data/IGNF PROJ.4 definition to ingest it into proj.db, but this file originally come from a processing of IGNF.xml ( http://librairies.ign.fr/geoportail/resources/IGNF.xml ) The end result is not strictly equivalent, as data/IGNF has some 'magic' to create towgs84 / nadgrids, since IGNF.xml doesn't necessary contain all transformations from its geodetic systems to WGS84. I've tried to re-add some of those missing transforms (null Helmert transforms), so it can be used for pivoting, but that might be incomplete.
2018-11-14	Implement RFC 2: Initial integration of "GDAL SRS barn" work	Even 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