just brew it! wrote:
If you can give a little more detail regarding the project you're thinking of using Python for, I may be able to direct you towards more specific information.
Glorified shell scripting that I might throw a GUI on top of. Lots of calls to external programs that I need to generate programatically and execute. Hackjob glue to hold together 2-3 other hackjobs
Currently using OGR2OGR
to merge and combine shapefiles, along with a build of gpsbabel
that I've modified to have more functionality (and fixed broken stuff) with Delorme .an1 files while actually working. I'm also probably going to hack on shp2txt
to get a command-line program that does what I current'y only have someone else's GUI for (write text files in Delorme's text format for areas/polygons). Overall, it's a huge mishmash of working with 2-3 different applications that either do what I want done or can be easily modified to do so, because I don't want to go through the effort of developing a full application. The easiest way forward seems to be modifing multiple programs to take advantage of the "low hanging fruit" that each offers, and then glue them together with some bubble gum. Python seems like a good option for this convoluted cluster of a task, plus it ships with the normal
way of obtaining binaries of the ogrtools so if I get a useful tool and distribute it to others, using python doesn't add an additional requirement. As a hackjob, functionality and implementation is probably going to bounce around - I need something that works, not necessarily something that works elegantly.
The end goal is to develop an easy workflow to move specific data between usgs large scale DLGs and Canadian 50k vector topo maps and Delorme software (and thus to my GPSr). I'd also probably throw in conversion from jp2 to geotiff using GDAL, as Delorme software doesn't speak jp2 and some data that I get is in that format. The volume of this sort of data in file size and/or numbers can add up fast, and managing it can be a challenge.