Python: Difference between revisions
Brian Wilson (talk | contribs) |
Brian Wilson (talk | contribs) m →ESRI |
||
Line 16: | Line 16: | ||
==== ESRI ==== | ==== ESRI ==== | ||
Geoprocessing with ESRI COM dispatch is | Geoprocessing with ESRI COM dispatch is painfully slow on the machine I have here. | ||
This guy seems to have slogged through a lot of development with it: | |||
http://www.ollivier.co.nz/support/python.shtm | http://www.ollivier.co.nz/support/python.shtm | ||
Revision as of 18:11, 23 August 2006
Brian's random notes on Python
Links
Quick links into the official docs
TUTORIAL http://docs.python.org/tut/tut.html
GENERAL http://docs.python.org/
STRINGS http://docs.python.org/lib/string-methods.html
Geoprocessing
ESRI
Geoprocessing with ESRI COM dispatch is painfully slow on the machine I have here.
This guy seems to have slogged through a lot of development with it: http://www.ollivier.co.nz/support/python.shtm
Open source
How about geoprocessing with OGR/GDAL? Will that do it for me?
Getting Python 2.4 and GDAL without disrupting the ESRI installation... See also Howard Butler's site.
Not good enough: FWtools installs a funky GUI called OpenEV_FW and a shell environment. It comes with python 2.3.4 which is old but better than ESRI's 2.1 It does NOT include the pythonwin IDE. How INCORNVENIENT!
23-Aug-2006 Python+OGR probably not worth messing with right now. From the OGR site: The Python API isn't really well documented at this time, but parallels the C/C++ APIs. The interface classes can be browsed in the pymod/ogr.py (simple features) and pymod/osr.py (coordinate systems) python modules. The pymod/samples/assemblepoly.py sample script is one demonstration of using the python API.