Computing, GIS and Archaeology in the UK

I attended (and spoke at) the Association for Geographic Information (AGI) Technical Special Interest Group Open Source Event yesterday- down at the British Antarctic Survey headquarters in Cambridge (I want to work there, they have skiddoos parked in their carpark). The event was designed to kick off the newly invigorated Tech SIG, after a hiatus of several years. I can understand why there was a hiatus- the other SIGs have a more defined focus, such as the Environment, or Crime and Disorder and so on. The Technical SIG covers all areas, from a methodological point of view at least, and yet doesn’t want to tread on the other group’s feet.

Anyhow, the Open Source event was fairly well attended- with 30-odd people there, most of whom were new to the group, which bodes well. Alongside my own talk (on “Going Open-available on the talks page), there were talks from Paul Cooper (a roadmap of Open Source components for GIS web services and clients, and the South Georgia GIS) and Andrew Fleming from the BAS (access and delivery of Polar Satellite Imagery), Andrew Mackay from IPL (Using Open Source software in operational systems) and Gillan Arnold and Egbe Equavoen from the Ordnance Survey (OS Web Map tools).

A general observation- almost everyone talked about using some combination of geoserver/postgresql/openlayers. Other packages were mentioned in passing, but these were the big 3, the packages du jour. That’s not to say that there aren’t perfectly viable alternatives, but these ones definitely seem to have the momentum at the moment. It was nice to spread the word about mapfish though, which most people hadn’t heard of!

Andrew Mackay talked about using open source to deliver crime mapping to Kent Police. The thing about Andrew’s talk that stood out was the discussion about software development cycles. At first glance this seems like overkill for the majority of small-scale mapping applications. But then IPL are involved in some very large-scale application development, and probably understand more than most the need to get it exactly right.  I did begin to think that a little more discipline in my software development would be a good idea, even if the full cycle as per the textbook is a little too much!

Andrew Fleming’s talk about Polar satellite imagery was interesting. He raised a lot of issues around the delivery of the imagery, as near to real-time as possible, with less than brilliant communication lines (not much broadband in Antarctica).  For their needs, georss was a better bet than wms, due to speed and the size of the data set. They are still looking for a solution for deploying 3D and radar data, but have yet to come up with an optimal solution. Answers on a penguin to…

The demo of the Ordnance Survey’s web mapping tools was interesting, but ultimately frustrating because whatever you do with it you’re still hamstrung by the data license. The basic tool itself is a integrated postgresql/openlayers setup, with some nice extras for cutting their mapping tiles into handy chunks, and built-in geocoding (if you have the license…). I was hoping to hear that they are ready to start rolling out wms access to their data with an innovative new pricing structure, but no, so I’ll keep waiting for that.

The end discussion revolved around people’s concerns over the “risk” of open source either in general or in their organisation, and the need for traditional support agreements. In simple terms there was a basic division between those organisations with in-house IT staff who were quite flexible and willing to try out, or see the advantage of, open source tools, versus those who had out-sourced their IT to external companies with 3 or 5 year contracts to use particular packages. It’s a chicken and egg scenario put far more succinctly by other people than I ever can- but basically without the critical mass of open source adopters, how can large “traditional support companies” be supported?

All in all, an enjoyable and informative day.

If you read anything about blogging you’ll know that you’re not supposed to apologise for not posting, but umm, sorry for not posting for a couple of weeks. Oops, there goes my blogging credentials down the drain!

Anyhow, the last couple of weeks have been a bit of a learning experience. A major IT mishap, which I could have handled better and possibly prevented, coupled with lots of commitments and deadlines, meant that I just had to get my head down and get through each day an hour at a time. Some people might be fine with that kind of stress, but I learnt that I am not one of those people. Thank goodness for lovely husbands who not only understand, but get tea ready for you when you do a 12 hour day in the office.

Back when I started this blog, I used to post occasionally on time management, and Getting Things Done (GTD). I don’t post as much about it now, as I have a system that sort of works for me (a hybrid moleskine/Remember The Milk setup if you’re interested), but one of the key things that has really been hammered home over the last couple of weeks is the need for some kind of weekly review of commitments and tasks. That has just about kept me on target, even though it takes a good couple of hours per week to complete. Just being sure that all the tasks are written down, and therefore not clamouring for head-space, is incredibly helpful in keeping stress to a minimum.

The final things that I should know already, but ignored in a slightly gung-ho style: Never Ever believe that things will “Just Work”, and Never Ever mess with the computers without doing a full backup first. ‘Nuff said. I am chastened.

So- I’m off to Cambridge this afternoon as I’m speaking at the Association for Geographic Information Technical Special Interest Group Open Source Event tomorrow, but hopefully normal service (such as it was) should resume after that. Look forward to my slightly belated take on the whole file formats for spatial data storage and transfer issue, some news about the UK Local Chapter of OSGeo, and perhaps even an announcement on Portable GIS in the coming weeks.