Open Source Computing and GIS in the UK

You might have seen this post last week about how the Ordnance Survey once again saved the universe from un-approved uses of “their” data, by blocking an incredibly useful application that overlays Ordnance Survey mapping over Google Earth. You might have seen this post about it too. You might even have written to the Ordnance Survey to complain about it.

However, unless, like me, you had these posts tagged in your feed reader ready to write something about them, you might not have realised that the Ordnance Survey have (sort of) relented.  I say “sort of”, because apparently there’s still an issue between the terms of Google Earth’s license and that of the Ordnance Survey, but at least Gavin gets his API key back again.

Power to the people!

Time for another round-up…

• The Ordnance Survey have revised the terms and conditions of using their OpenSpaces mapping API (via Mapperz), which is a step in the right direction, since they now allow adverts on your site. There’s still a daily limit to the number of views/address lookups that you can do too. However, there are a couple of points that need mentioning/clarifying… firstly there’s a strange condition that you can’t use this for “internal business administration”. Not sure what that really means, but I assume it’s so you don’t stick it behind a firewall and stop OS counting your number of page views or something. Furthermore, there’s nothing obvious on the site about whether you need a license to use the data still, in which case it’s still a show-stopper. I’ve emailed them for clarification about that, so watch this space…
• Tyler Mitchell has an article in Direction Magazine about “Reassuring End Users of Open Source“.  I’m uneasy about the term “Reassuring”, as it has slightly negative connotations (“don’t worry!”, “worry, who said anything about worrying?”), but the article is well worth a read with some useful comments on the advantage of open source for businesses and the role of OSGeo.
• No doubt everyone already knows about the OpenGeo Architecture White Paper. Personally I think it’s another good paper to have around and quote from (or steal slides from) when trying to convince people that using open source geospatial software  is a more flexible and all round sensible approach to your geospatial stack.
• OStatic have an article about Open Source software at NASA. Not so much geospatial stuff going on there, but it’s good to see the top two reasons why NASA go for Open Source:

To increase NASA software quality via community peer review

To accelerate software development via community contributions

It’s good to see “quality” as an argument for choosing Open Source, rather than “saving money”!

Via the Guardian’s Free Our Data Blog, but with remarkably little fanfare elsewhere- the UK Government have released their new strategy for the Ordnance Survey. The results have the potential to be really good, but might also be a bit of a damp squib. The big concession is an extended OS OpenSpace service:

It will provide greater access to free use of a number of Ordnance Survey products from 1:10,000 scale through to 1:1 million scale. It will also include official boundaries information.

This is good news, though not as forward thinking as I’d like, unless the terms and conditions for the use of Open Space change dramatically. In my dreams, they are going to release their mapping via WMS- after all it would save them having to ship out all those update cds every year…

The new pricing strucure for full data access will be out in October, apparently. I’m not holding my breath for any nice friendly educational-charity fee structures though, since the whole document seems to assume you’re either an individual (read hobbyist) or a commercial company, and the trouble with educational charities is that we don’t really fit into a sensible box like that.

What’s nice though, is that the whole document is available online as a commentable document. Not sure how much notice will be taken of feedback, but it’s a start!

I started off this week with the intention of resurrecting and upgrading a demo openlayers map of all our sites, that had been stuck in a sorry corner of our corporate website being neglected. This tied in with moving the map to a different server, upgrading all the components, and generally giving it a shave and a haircut (it is male, that’s for certain). For those people interested in our wms and wfs data- these will be online again soon, I promise.

While I now have a site up again, pretty much ready to go bar the shouting, I’ve had an interesting time playing with some new toys in the process, so here’s a quick run-down:

• Mapfish and GeoadminSuite: A funky framework for widgetising openlayers. Geoadminsuite connects mapserver, openlayers and mapfish to manage data and create really nice mapfish applications. Way cool. Progress so far- it’s all up and running, though GeoadminSuite had teething troubles that have hopefully been sorted in the latest svn release.
• Openlayers: OK, so I’m just catching up with the latest release after ducking out for a while to do “real work”, but I have to say I like the new(er) features. It was nice to be able to do popups without needing to re-write the code for every version of every flavour of browser. That’s not openlayers’ fault of course, just issues with “standards” for things like DOM, which I don’t claim to understand.
• Openstreetmap WMS data from Wheregroup: Comes in free and paid-for flavours though details on pricing and terms of service for the commercial version were sketchy on a first skim of the website. This could be really handy to use as background mapping data for web maps, although there are issues of completeness (as always) and it probably needs running through our own mapserver to sort out the styling. This is definitely a goer- I just need to figure out which of the 50 or so layers they publish are really necessary and at what scale. And some kind of completeness metric, so we know how reliable the data is for a given area…
• Openstreetmap shapefiles from Cloudmade: A reduced dataset for the UK, with less layers. This might be a better option for us to use as we can control the styling better at the source. As a cheat, I’m going to load it all up in Quantum GIS, style it there, and use the mapserver export plugin to quickly build my map file.
• Mapnik: One of my colleagues would very much like us to create our own openstreetmap wms server, and use mapnik. I’d love to, as the cartography is really good, but after diving into it today, I have to say I think I need some hand holding before I can actually make it serve maps. We’ll see…

Also rans:

• Ordnance Survey have changed the licensing for their OpenSpace product: You still need a license to use their data, but you can download the development kit from sourceforge. The license has also been changed to have more “clarity” in terms of the ownership of derived data. It would be churlish to suggest that this has anything to do with the “Show Us a Better Way” mess up, wouldn’t it? The problem is, you still need to pay for the background data, so we’re back up to points 2 and 3 above…
• Amazon launches public datasets: This, in my limited experience, seems to be a duplication of ideas that are already out there. That’s fine when it’s software, and you want to stomp all over your rivals, but wouldn’t it have been nice for them to give their support to an existing data repository?

Things to play with next:

• Openaerialmap: Also has a wms service…