[MetaCRS] EPSG Database Update Mechanism for libgeotiff, GDAL, PROJ.4, and PostGIS

[Mikael Rittri]

PS.

I wrote: 
> By the way, I think the libgeotiff/csv README file is wrong, where it
claims that
>   "All EPSG tables have been dumped to csv." 
> ( http://svn.osgeo.org/metacrs/geotiff/trunk/libgeotiff/csv/README )
 
What's more, the claim that 
    "The current version of the EPSG database dumped is 7.1"
seems to be wrong at least for area.csv. In the REVISION_DATE column, 
the most recent date in area.csv is 22 Sep 2003.

So, I'll add an update of area.csv to my wish list. It is not 
terribly important, but the AREA table does evolve over time. 
For example, area.csv lacks
   3313, "Sweden - onshore", revision date 1 Feb 2006
and 
   3408, "Sweden - Stockholm", revision date 20 July 2006

And for area 1298 in area.csv ("Europe - ETRS89"), the description 
text is lacking a lot of countries like Andorra, Bulgaria, Greece,
Ireland, Malta and Serbia, which have been added later than 2003. 

Best regards,

--
Mikael Rittri
Carmenta AB
SWEDEN
www.carmenta.com

-----Original Message-----
From: metacrs-bounces at lists.osgeo.org
[mailto:metacrs-bounces at lists.osgeo.org] On Behalf Of Mikael Rittri
Sent: den 2 december 2009 09:32
To: Frank Warmerdam
Cc: metacrs at lists.osgeo.org
Subject: RE: [MetaCRS] EPSG Database Update Mechanism for libgeotiff,
GDAL,PROJ.4, and PostGIS

Hello,

About converting the EPSG tables to csv form, Frank wrote:

> Currently it looks like I'm capturing 12 tables as operated on by the
script:
>
>   
> http://svn.osgeo.org/metacrs/geotiff/trunk/libgeotiff/csv/pg_to_csv.py
>
> It would be easy to extend it to capturing them all though I don't 
> really use a number of them in libgeotiff and related tools.  The 
> current csv files are available in
http://svn.osgeo.org/metacrs/geotiff/trunk/libgeotiff/csv.
(quoted from
http://lists.osgeo.org/pipermail/metacrs/2009-June/000264.html)

Nice work. May I put some more EPSG tables on the wish list:

* The supersession table for datum transforms, which
  tells whether a datum transform is retired or superseded
  (see EPSG Guidance note 7.1, section 5.6).
  
* The table that gives the bounding rectangle coordinates for
  an area of use. (These are not in area.csv, as far as I can see.)

By the way, I think the libgeotiff/csv README file is wrong, where it
claims that "All EPSG tables have been dumped to csv." 
( http://svn.osgeo.org/metacrs/geotiff/trunk/libgeotiff/csv/README )

Regards,

--
Mikael Rittri
Carmenta AB
SWEDEN
www.carmenta.com
-----Original Message-----
From: metacrs-bounces at lists.osgeo.org
[mailto:metacrs-bounces at lists.osgeo.org] On Behalf Of Frank Warmerdam
Sent: den 5 juni 2009 03:55
To: Norm Olsen
Cc: Paul Ramsey; metacrs at lists.osgeo.org
Subject: Re: [MetaCRS] EPSG Database Update Mechanism for libgeotiff,
GDAL,PROJ.4, and PostGIS

[-- text deleted --]
_______________________________________________
MetaCRS mailing list
MetaCRS at lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/metacrs