<html><head><style type="text/css"><!-- DIV {margin:0px;} --></style></head><body><div style="font-family:times new roman, new york, times, serif;font-size:8pt"><div style="font-family: times new roman,new york,times,serif; font-size: 8pt;">Thank you Howard! No this does not help my immediate situation, but it sounds like it is not far off, and I don't have the skills to do what the programming group is doing so I can't complain.<br><br>Has anyone used PIL (python imaging library)? I am guessing this does not give me nearly as much of the functionality that comes with gdal/osr, especially how to embed the spatial reference tags, but I recently stumbled across this.<br><br>michael<br><br><br><div style="font-family: times new roman,new york,times,serif; font-size: 12pt;">----- Original Message ----<br>From: Howard Butler <hobu.inc@gmail.com><br>To: Michael ODonnell <odonnems@yahoo.com><br>Cc: gdal-dev@lists.osgeo.org<br>Sent: Friday, December
7, 2007 1:43:13 PM<br>Subject: Re: [gdal-dev] gdal and python 2.5<br><br>
<br>On Dec 7, 2007, at 2:30 PM, Michael ODonnell wrote:<br><br>> Hi, I am new to this group and a relatively new user of gdal and <br>> python. I have been using a gdal python binary with python 2.4.1 on <br>> Windows XP, but I was forced to upgrade to 2.5.1 python. I have seen
<br>> a couple postings in the last few months (gdal discussion list) on <br>> this topic and I was curious if anyone has built gdal binaries for <br>> python 2.5.1?<br>><br>> Is this possible without making a lot of changes to gdal and is <br>> numeric still required or has gdal switched over to numpy entirely?<br><br><a href="http://trac.osgeo.org/gdal/wiki/GdalOgrInPython#the-history-of-using-gdal-ogr-in-python" target="_blank">http://trac.osgeo.org/gdal/wiki/GdalOgrInPython#the-history-of-using-gdal-ogr-in-python</a> <br> describes the current situation. For GDAL 1.5, the Python bindings
<br>will be numpy only, and Numeric support is not provided. Your code <br>may require some minor tweaks to be able to use numpy, but none of the
<br>scripts I have ported for use in the GDAL project required significant
<br>changes.<br><br><br>><br>><br>> What version of VS would be required?<br>><br><br>"Stock" Python 2.5 from <a target="_blank" href="http://python.org">python.org</a> and ActiveState use 2003. If we <br>are to provide pre-built bindings, they must use msvc2003.<br><br>It is my intention that we (the GDAL project) will provide Python <br>bindings (2.3, 2.4, and 2.5) in the form of eggs and windows <br>installers on <a href="http://pypi.python.org/pypi/GDAL/" target="_blank">http://pypi.python.org/pypi/GDAL/</a> that will be expected <br>to be used with our "official" binaries that we will make available on
<a href="http://download.osgeo.org/gdal/win32/" target="_blank">http://download.osgeo.org/gdal/win32/</a> <br> for the GDAL 1.5 release. We haven't gotten our story straight on <br>what the official binaries will look like quite yet, however. I know <br>this story doesn't quite help your immediate problem.<br><br>If we make a 1.5 beta binary in a few days, I will upload a <br>corresponding egg/.exe to pypi to match them. If it doesn't happen <br>right away, please note that the 1.5 will be happening by the end of <br>the month, so we should at least have something by then.<br><br>As a side note, I expect the official GDAL binaries will be compiled <br>with msvc2005, but it shouldn't be a problem to have the Python <br>bindings that were built with 2003 link against them now that the <br>Python bindings in 1.5 no longer use and C++ API.<br><br>Hope this
helps,<br><br>Howard<br></div><br></div></div><br>
<hr size=1>Never miss a thing. <a href="http://us.rd.yahoo.com/evt=51438/*http://www.yahoo.com/r/hs"> Make Yahoo your homepage.</a>
</body></html>