[gdal-dev] Requesting gdal update to at least EPSG v8.6

[Mary Jo Brodzik]

Bonjour, Even,  Merci for the quick response!

Unfortunately, I don't think v8.5 is good enough.  I worked with Roger 
Lott late last year, and he made several corrections, including:

1) New projection Conversion codes 6928, 6929, 6930
2) New ProjectedCRS codes 6931, 6932 and 6933
3) Changed the state of deprecated codes 3973, 3974, 3975 to "Invalid" 
because they were incorrect
4) Edited descriptions for 3408, 3409 and 3410 to indicate they are 
now superceded.

Roger did indicate that he had some of these in a patch release of EPSG 
v.8.5.4, but that there were still some names and metadata that were 
incorrect in 8.5.4 that were correctly released in v8.6.  From Roger:

> As far as the projection and CRS definitions are concerned everything is 
> already OK in v8.5.4 in that coordinate conversions using CRSs 6931-33 
> will be correctly implemented. It is only metadata (projection [but not 
> CRS] names and projection and CRS remarks) that will change. As soon as 
> we publish v8.6, v8.5.4 will no longer be available and the metadata you 
> consider wrong will be lost to posterity.

Mary Jo

On Wed, 6 May 2015, Even Rouault wrote:

> Date: Wed, 6 May 2015 17:48:34 +0200
> From: Even Rouault <even.rouault at spatialys.com>
> To: Mary Jo Brodzik <brodzik at nsidc.org>
> Cc: gdal-dev at lists.osgeo.org
> Subject: Re: [gdal-dev] Requesting gdal update to at least EPSG v8.6
> 
> Le mercredi 06 mai 2015 17:24:57, vous avez écrit :
>> Hello,
>>
>> I would like to request that gdal be updated to use the latest EPSG codes.
>>
>> I worked with EPSG last year to correct some obsolete ProjectedCRS
>> definitions for some products I am developing, and I understand that the
>> corrected definitions were included in EPSG v8.6, released in Nov 2014.
>>
>> I am unsure how to actually confirm the EPSG version included with gdal,
>> but I did find this trac ticket (http://trac.osgeo.org/gdal/ticket/5462)
>> that looks like you upgraded to epsg v8.4 in May 2014.
>
> Mary,
>
> GDAL 2.0 (currently in beta1) has been upgraded to EPSG v8.5. Isn't that good
> enough ? Which EPSG codes are you interested in ?
>
> Even
>
>>
>> The EPSG web site at www.epsg-registry.org seems to indicate the latest
>> version may be 8.7.  I don't know what is new.  For my purposes and to let
>> my users know, v8.6 or better is what I need.
>>
>> Thank you,
>> Mary Jo Brodzik
>>
>> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>> Mary Jo Brodzik, Senior Associate Scientist, 303-492-8263
>> NSIDC/CIRES, Univ. of Colo. at Boulder, 449 UCB, Boulder, CO 80309-0449
>> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>> _______________________________________________
>> gdal-dev mailing list
>> gdal-dev at lists.osgeo.org
>> http://lists.osgeo.org/mailman/listinfo/gdal-dev
>
> -- 
> Spatialys - Geospatial professional services
> http://www.spatialys.com
>

^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Mary Jo Brodzik, Senior Associate Scientist, 303-492-8263
NSIDC/CIRES, Univ. of Colo. at Boulder, 449 UCB, Boulder, CO 80309-0449
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^