James Macgill


User Name: jmacgill
Full Name: James Macgill

Bio.

I'm a research scientist at the GeoVISTA center - Penn State University where I work on creating new GeoVisualization tools within the GeoVISTA Studio project.

I earned my PhD at Leeds University where I worked on a fun blend of ALife technologies to search for patters in large space time attribute datasets. Prior to that I did a MA in GIS (yes apparently back then GIS was an art not a science) all all of this geospatial interest stemed from a BSc in Evnironmental Science.

Of the projects here on codehaus I'm involved with all of the geospatial ones to some degree or other, but especialy GeoTools which I founded back in 1996.

jmacgill
(jmacgill)
Where 2.0 Java BOF

With OSG'05 out the way, the next big conference looms. Where 2.0 is next week and I've just recived confirmation that my BOF session is going ahead. It's another chance to bring Java Open Source types together, perhaps for a bit of future speculation and planning, and it's also a chance to bring in some new developers.

Their was a lot of talk about Java (and other language) bindings / bridges at OSG'05. GDAL / OGR in particular, but also improvments to the SWIG based bindings for MapScript. So if you an't a Java hack but want to look at how we can work together better then feel free to drop in.

With JavaOne happening at the same time as Where 2.0 but so close by its hard to say if the BOF will be empty or if a ton of Java developers will be kicking about. Looking at the BOF list so far their isn't a general 'open source' so if I'm all on my own at I'll run round and cross Java off the signs :)

Open Source Geospatial '05

I've just returned from one of the best conferences I've ever been to, well if not best then most different.

It was the first 'open source' conference that I have been to (humm, unless you count 'SwarmFest...') and it made a refreshing change from academic conferences. It was wired being somewhere where 90% of the attendees where hackers/geeks. (Thats hackers in the old fashond nice way, not the media adopted criminal meaning).

In particular it was nice to finaly meet some of the developers who I have been collaborating with on GeoTools for so long and never met. I spent the night before the conference started talking well into the night with Dave Blasby, the GeoServer leed when I should have been finishing of my talk for the EoGEO session the next day, so not much sleep, but the presentation seemd to go well.

The conference included a set of lighning talkes that were only 5mins each, they were fantastic, just enough info to get you interested in a project but not enough to send you to sleep.


1) Javascript is back, technologies like AJAX mean that interactive javascript pages (where the 'refresh button' is a thing of the past) are becoming an attractive way to develop pages. That and the javascript console in mozila browsers of course. I feel that google are in part responsible for this resergence, showing just what can be done with google maps, google suggest and even the gmail interface.

2) The clients have arrived! For a while now projects like GeoServer and MapServer have been serving standards based content using the WMS and WFS spects to fairly dumb clients, but projects like MapBuilder and MapBlender open up a LOT of exciting oportunities.

3) GeoSpatial is everywhere and it is becoming big business (look at the upcomming Where 2.0 conference for example). It was interesting to see that ESRI had sent a rep to take a look round and a good few other organizations were seeing if Open Source was right for them.

4) The apache model is not for all. The closing keynote from apache presidnet Dirk-Willem van Gulik was very interesting. He gave an overview of the Apache Foundation, how it worked and what it did and what we, in the geospatial community could learn from it without copying it wholesale. In particular a lot of the Apache foundations life revolves around legal issues to prevent people from suing each other! In a nutshell, we should all know where our code comes from and we should try to be as modular as possible so that we are isolated from the effects of loosing a developer or from experimental code.

There are about a dozen ideas I want to follow up on, I'll write about some of them in upcomming blogs. For another perspective on the conference from a non-map-hacker take a look at O'Reilly Radar > Nathan Torkington's blog