Hi guys thanks for the great response. I completely understand the anti-black box sentiment. Having seen Arc* blow up in my face many times, I understand the need to see what’s really going under the hood.
I guess my real desire was to build a scripting library, maybe a DSL, that allow me to do geoprocessing without arc. Confession, I am not a computer scientist and my background is in planning. GIS, to me, is a set of tools that allows people do complex processing easily. What excites me the most is that as a discipline GIS allows me to ask questions like, “How does distance from a power planet affects cancer rates in a specific population” and so forth. I don’t want to always have to thinking about the details of my processing operations. So I guess I will look into wrapping gdal’s python bindings into something that’s easier to use and go from there. If anyone has thoughts or suggestions, please drop me an email. Sean and Francis if you don’t mind including me on the future of worldmill, is would be great! Again, thanks for everyone’s ideas and time. Ivan On Sun, May 2, 2010 at 4:18 AM, Sean Gillies <[email protected]> wrote: > Hi Francis, > > Maybe we can collaborate on a common interface for our projects? So as > not to drag this thread any further off track, let's discuss via email > off-list. > > Cheers, > > On Sat, May 1, 2010 at 3:57 AM, Francis Markham <[email protected]> > wrote: > > What do you see as being the future of WorldMill? My current GDAL (not > OGR) > > based project has resulted in my writing a small but nonetheless > > time-consuming python wrapper in order to reduce the tedium of using it. > If > > WorldMill became read/write, I can see it getting a lot more adoption... > > > > -Francis > > > > On 30 April 2010 22:38, Sean Gillies <[email protected]> wrote: > >> > >> Except that WorldMill is currently read-only. It's a demonstration of > >> a cleaner interface to OGR, and I'm not certain about its future. > >> > >> -- > >> Sean > > > > >
