[gdal-dev] a complete list of GDAL supported EPSG codes

[Maciej Sieczka]

Maciej Sieczka pisze:
> Frank Warmerdam pisze:
>> Maciej Sieczka wrote:

>>> how do I best fetch the list of *real* EPSG codes that my instalation 
>>> of GDAL is able to recognize? Is extracting them from pcs.csv and 
>>> gcs.csv a good approach?

>> Yes

> Cool. I only have a following problem - as I parse the pcs.csv and
> gcs.csv like this [1], the following codes:
> 
> 2218 2221 2296 2297 2298 2299 2300 2301 2302 2303 2304 2305 2306 2307
> 2963 2985 2986 3052 3053 3139 3144 3145 3173 3295 3410 3993 32600 32700
> 
> yield:
> 
> ERROR 6: EPSG PCS/GCS code <code goes here> not found in EPSG support
> files. Is this a valid EPSG coordinate system?

An example:

$ grep "^2218," /usr/local/share/gdal/pcs.csv

2218,"Scoresbysund 1952 / Greenland zone 5 
east",9001,4195,18425,9826,1,0,8801,70.3,9110,8807,0,9001,8805,1,9201,8802,-24,9110,8806,0,9001,,,,,,

$ epsg_tr.py 2218

ERROR 6: EPSG PCS/GCS code 2218 not found in EPSG support files.  Is 
this a valid
EPSG coordinate system?
PROJCS["Scoresbysund 1952 / Greenland zone 5 east",
     GEOGCS["Scoresbysund 1952",
         DATUM["Scoresbysund_1952",
             SPHEROID["International 1924",6378388,297,
                 AUTHORITY["EPSG","7022"]],
             TOWGS84[105,326,-102.5,0,0,0.814,-0.6],
             AUTHORITY["EPSG","6195"]],
         PRIMEM["Greenwich",0,
             AUTHORITY["EPSG","8901"]],
         UNIT["degree",0.01745329251994328,
             AUTHORITY["EPSG","9122"]],
         AUTHORITY["EPSG","4195"]],
     UNIT["metre",1,
         AUTHORITY["EPSG","9001"]]]

> I expected that a code extracted from pcs/gcs.csv should be valid for
> GDAL. What am I missing?
 >
 >
> Also, a couple of codes yield:
> 
> ERROR 6: No translation for Tunisia_Mining_Grid to PROJ.4 format is known.
> 
> ERROR 6: No translation for Transverse_Mercator_South_Orientated to
> PROJ.4 format is known.
> 
> ERROR 6: No translation for Laborde_Oblique_Mercator to PROJ.4 format is
> known.
> 
> I found a reference for that [2], so I briefly understand what's the
> culprit and that we are just to ignore the problem for now. Out of
> curiosity anyway - has there been any progress on the issue?
 >
> [1]
> for i in `awk 'NR>1' /usr/local/share/gdal/pcs.csv | cut -d, -f1`; do
> printf "$i "; epsg_tr.py -proj4 $i; done
> 
> for i in `awk 'NR>1' /usr/local/share/gdal/gcs.csv | cut -d, -f1`; do
> printf "$i "; epsg_tr.py -proj4 $i; done
> 
> [2]http://lists.osgeo.org/pipermail/gdal-dev/2008-February/016249.html

Maciek

-- 
Maciej Sieczka
www.sieczka.org