On 02/01/2008, <b class="gmail_sendername">Frank Warmerdam</b> <<a href="mailto:warmerdam@pobox.com">warmerdam@pobox.com</a>> wrote:<div><span class="gmail_quote"></span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br>GDAL/OGR includes a script called epsg_tr.py that makes it relatively easy<br>to translate from epsg codes to various formats. </blockquote><div><br>Sweet. I'll have a look. <br></div><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
You will likely want to do this for pcs.csv (all the projected coordinate<br>systems) and gcs.csv (all the geographic coordinate systems). The .csv files<br>are part of the GDAL/OGR source distribution and are often installed in
<br>/usr/local/share/gdal on linux/unix.</blockquote><div><br>And (technically now a gdal question) how do the csv files get produced? ie. from the EPSG dataset available at <a href="http://epsg.org">epsg.org</a> they get loaded into a postgres db and another script gets run to produce the csv files?
<br><br>Thanks,<br><br>Rob :)<br></div></div>