Opened 7 years ago

Closed 7 years ago

Last modified 7 years ago

#6772 closed enhancement (fixed)

Update to EPSG registry v9

Reported by: ndawson Owned by: warmerdam
Priority: normal Milestone: 2.2.0
Component: default Version: unspecified
Severity: normal Keywords:
Cc:

Description

The EPSG registry v9 is now available (although the page at http://www.epsg.org/EPSGDataset/WhatIsNew lists an incorrect release date).

This release includes some critical changes for Australian users.

Note: I'm willing to tackle these changes myself if I can get some pointers from the GDAL maintainers. Is there a script/documented process which was used to handle updates like https://github.com/OSGeo/gdal/commit/3a316f2158090ba5123692e21f3dd46ce9279fe2 ?

Change History (6)

comment:1 by Even Rouault, 7 years ago

Resolution: fixed
Status: newclosed

In 37081:

Update to EPSG v9.0 database + datum shift overrides for EPSG:4149 (CH1903), EPSG:3844 (Pulkovo 1942(58) / Stereo70 Romania), EPSG:31251,31252,31253 (MGI (Ferro) / Austria), EPSG:2397/2398/2399 (Pulkovo 1942(83) / 3-degree Gauss-Kruger zone 3,4,5), EPSG:2065 (S-JTSK (Ferro) / Krovak) (fixes #4762, #6772)

comment:2 by Even Rouault, 7 years ago

Corresponding tickets for upstream and downstream projects :

Last edited 7 years ago by Even Rouault (previous) (diff)

comment:3 by Even Rouault, 7 years ago

Milestone: 2.2.0

comment:4 by Even Rouault, 7 years ago

In 37083:

Adjust expected result after EPSG upgrade (refs #6772)

comment:5 by ndawson, 7 years ago

Thanks Even! Are these database upgrades valid for backporting too?

in reply to:  5 comment:6 by Even Rouault, 7 years ago

Replying to ndawson:

Thanks Even! Are these database upgrades valid for backporting too?

I don't think we have ever backported EPSG upgrades in stable releases. As there are changes to existing codes, that could easily break downstream software (for example I had to change a expected result in GDAL autotest suite).

Note: See TracTickets for help on using tickets.