It was great to spend the day in Southampton yesterday at the Ordnance Survey, to preview the new OpenSpace API:
The API has been a long time in the making, having first been announced at the OS Mashup Event last year. The API is based on the OpenLayers Javascript library, an interesting decision in itself and one which should see bug fixes and improvements fed back into OpenLayers.
Essentially, OpenSpace is just another slippy map API, with most of the features everyone’s come to expect and a few features that make it stand out. It uses the OSGB (OSTN02) datum projected onto the British National Grid (transverse mercator) rather than using WGS84 Latitudes and Longitudes and a mercator projection, as most other web mapping APIs use. To ensure compatibility with the growing volumes of geodata based on WGS84, OpenSpace includes Javascript libraries to transform from WGS84 to projected OSGB – which it seems to do pretty accurately.
Another notable point is the cartography. The Ordnance Survery have a far richer dataset at their disposal, so its not surprising that they can produce map tiles like this:
Whilst the “Street View” (the name for the highest zoom levels) cartography has been criticised by some specialists, its undoubtedly an improvement over Google’s. Its going to be interesting to see if the new map content spurs new types of mash-ups – people can now pinpoint the exact position of their houses and countryside users now have, well, something compared to the nothingness of the Google countryside. I spent at least an hour yesterday just browsing around the map – just having a nice, fullscreen slippy map of the UK is really cool. Take a look here
The license is a license, so some people are going to love it, some will hate it and most will just get on with hacking. One thing that the guys from the OS were emphasising yesterday, was that they really want people to consult with them. That’s why we were there yesterday – so that the people who made OpenSpace could see what we thought. I think the desire of the OpenSpace team to listen to people’s feedback and act on it is a genuine one, so maybe we could all try some constructive criticism before trashing it. But hey, this is the internet.
The most interesting thing about OpenSpace is that the OS own the data. Google, Yahoo, MicrosoftMultimap etc all license their data from other providers, which is why they do things like this. Google don’t want you to hate them, they want you to love them and use their services but are restricted from doing so by licensing regimes with data suppliers. The OS shouldn’t have this problem – its their data so they shouldn’t suffer from the problems that Google et al blame on their providers.
During my first play with the OpenSpace API, I stuck a pin on a map to invite you all to the ZXV christmas party, and grabbed an NPE WMS feed from GetMapping, so you can overlay 50 year old mapping onto the latest OpenSpace tiles. Take a look here.
