Feeds and APIs provide ways for others to access a service and to recombine the data in new and unexpected ways. Ways that have consistently been proven to be beneficial to both parties (which makes google’s increasing antipathy towards them an interesting, not to mention short sighted, trend).

Anyway, it was one morning when I was attempting to find a route to work for my girlfriend which bypassed the numerous arterial route crashes that had happened that morning and I found myself pondering thus…

… wouldn’t it be cool if roads and junctions had permanent URLs, and better yet if you could get a data feed on them?

This would let you do many cool things, for example you could enter your route to work and get a status of the traffic en route – or at the very least attach a particular traffic blackspot (in our case the 13 bends of death on the A4074) to ifttt and get SMS alerts if there was a problem.

Giving roads and junctions addressable urls would be an obvious extension to the google maps API, but given that Google won’t even let you embed a map in a page if it contains a traffic data overlay it seems unlikely they’ll provide such access to their data. Other sources such as the Yahoo’s traffic API has long since been shut down.

So, what alternative traffic data sources could we use?

One possible data source we could use would be to parse a twitter search for the road in question. We both currently use ifttt hookups to get alerts for certain key roads, so the basic concept is sound.

This isn’t perfect, for example there is no understanding of the context of a message – so for example a message saying “No traffic problems on the A4074″ and “Terrible crash on the A4074″ would both trigger the alert, but only the latter would indicate a problem.

The other problem of course is that it also relies on people tweeting, but in effect this would actually pull in quite a diverse range of secondary sources – in my case, for example, it also pulls in any source that feed into the local radio station – which includes reports from their traffic spotter plane.

As an individual without access to data from traffic sensors, or any ability to collect data directly (unlike, say, google who can use position reports from android phones), we are pretty much limited to collecting data from secondary sources as far as I can see.

What other sources could we use?

Unfortunately it would seem that some assumptions made by the designers and the automatic opt-in nature of the service has lead to some serious issues.

For me it underlines some of the problems with entrusting your personal data to the cloud. That is not to say of course that it is a user’s fault that their data gets shared in such a way – everything in the day to day usage of these tools gives the user a reasonable expectation of privacy.

The trouble is, that this expectation is largely an illusion. When using cloud services, you are entrusting them and you hope that they will exercise the same care when dealing with your data as you would – but unfortunately this is rarely the case.

Whether through carelessness or malicious action information has a tendency to leak. Assumptions made by the design team can be proved poor. So in short, never put anything on the internet that you wouldn’t be happy to see on a billboard.

[audio:http://audioboo.fm/boos/97642-the-buzz-around-buzz.mp3]

Judging by the feedback I’ve been getting throughout the day you guys enjoyed it as well, but please let me know if there’s anything that we could do better next year!

Of course the event wouldn’t have been possible without our sponsors… Google who were kind enough to cover the cost of the venue (and thanks to the Oxford Club for being so good to us on the day!). Thanks to our other sponsors – 1000 heads, Proactive, Outmap, Moo and TerminateTheRate.org as well.

Also, thanks to our media sponsors: Global voices, Mashable and JackFM.

Most of all, thanks to all of you who came!

There were plenty of interesting conversations had, and we’ve already spawned a couple of interesting projects – do write in and tell me about yours, we’d love to do a followup!

Check out our flick group, and if you have any photos feel free to upload them to the group pool.

Anyway, I’ve rambled on…see you next year!

This is a fabulous venue (the same one as Barcamp Apache Oxford), directions and other details can be found on our website.

I am also delighted to announce that Google has agreed to be the main sponsor for the event and will be covering the cost of the venue for us! Big thanks to all at Google and our other sponsors for making this event possible!

See you there on the 26th July!