| Age | Commit message (Collapse) | Author |
|---|
|
grid_alternatives.sql: reference AGQG_20201120.gsb
|
|
|
|
|
|
|
|
|
|
|
|
|
|
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.
|
|
Database: decrease db size
|
|
|
|
We never select by those columns, so don't set them. Reduce from 8.4 to
7.9 MB.
Upgrade the minor version of the database layout. (that database can
still be read by PROJ 8.0)
|
|
grid_transformation
|
|
different nature, and also adjust the method code/name to the nature of the CRS
|
|
resources
|
|
Database: add a PROJ.VERSION metadata entry
|
|
Most codes (especially *all* in EPSG) are integers. As integers are
stored as variable-length in the db, it is preferable to store them as
such when possible.
So use a special INTEGER_OR_TEXT data type. This is a
"non-standard" type declaration, but this is perfectly legal as SQLite is
loosely typed.
As this declaration contains the string INT, it is assigned INTEGER affinity.
Which means that values provided either as text (that contains integer value)
or integer will be stored as integers, whereas text values will be stored as
text. See paragraph 3 and 3.1 of https://www.sqlite.org/datatype3.html.
The "INTEGER_OR_TEXT" name is a hint for the user, and software like
GDAL (>= 3.3) to expose the column as string...
The effect of using this rather than TEXT is making the DB size go from
9 MB to 8.4.
There is no need to change the DATABASE.LAYOUT version numbering as this
is completely forward and backward compatible.
|
|
grid_transformation and other_transformation. No practical impact
|
|
|
|
Just fixes 4 wrong transformations of v10.017
|
|
extent of the source and target CRS
|
|
transformations
|
|
create less synthetic 'Geographic3D to GravityRelatedHeight' synthetic transformations
|
|
|
|
|
|
- change foreign key check, so that it is enabled outside of the
transaction where we insert things, and can make the sqlite3
process fail in case of violations, without the postcheck done
in the autoconf build
- autoconf and cmake builds: simplification related to the above
(which also means that cmake builds now have the fkey check, which
was omitted until now)
|
|
ch_swisstopo_chgeo2004_ETRS89_LHN95 and ch_swisstopo_chgeo2004_ETRS89_LN02 (#2584)
|
|
|
|
conversion method in the PROJ namespace
Helps for example to use CRS definitions using the non-EPSG codified
Sinusoidal method.
|
|
|
|
|
|
* Correction grid NKG:ETRF14 to EPSG:7922
* Added NKG:ITRF_TO_NO GIE test
* Correction grid no_kv_NKGETRF14_EPSG7922_2000 added to grid_alternatives.sql
* proj_method 'velocity_grid' added in check_grid_alternatives_proj_method. NKG velocity grid added to grid_alternatives.sql
Co-authored-by: Even Rouault <even.rouault@spatialys.com>
|
|
transformation (#2554)
|
|
|
|
|
|
|
|
|
|
|
|
Better grid_alternatives entries to include 'GDA94 to AHD (Tasmania) height' using 'au_ga_AUSGeoid98.tif'
|
|
|
|
|
|
table (#2359)
|
|
This adds the NKG 2008 and 2020 transformations to proj.db. The NKG
transformations offers transformations between global reference frames
and the national realisations of ETRS89 in Denmark, Estonia, Finland,
Latvia, Lithuania, Norway and Sweden.
The 2008 transformations are already implemented in the NKG 2008 file
but will now be more accessible with the modern API.
The 2020 transformations are new to PROJ and offers and updated version
of the 2008 transformations using a new and improved deformation model
(eu_nkg_nkgrf17vel.tif). A 2020 version of the NKG transformations are
currently not available for Norway but will in all likelyhood be
included at a later point in time.
|
|
https://github.com/OSGeo/PROJ-data/pull/53
|
|
|
|
That is the option to make SQLite reject misuses of double quotes instead
of single quotes. Most SQLite builds are forgiving, but some forks proposing
a CMake build system default to SQLITE_DQS=0
|
|
check it in the code
This is aimed at detecting running a PROJ version against a proj.db that is not
meant to work with it. This happens sometimes in complex setups mixing PROJ
versions. Hopefully this will help spotting the issue earlier.
|
|
|
|
|
|
|
|
other_tranformation_custom.sql
|
