 Hello, my name is Yodat. I run OpenSensors.io. We're an ODI incubator startup. We've been around about two years now, and I want to talk about scaling the internet things with open data. Obviously we provide data infrastructure for IoT, private and public data, and I'll touch on why they're kind of the open data side a bit, but I want to start off with, I suppose, a case study and kind of showing you why you open data. As most of you know, the third runway debate has been raiding in the UK for the last year or so, and as a data nerd it actually struck me how the lack of factual information. There's lots of subjective information for pros and cons, but no data available, and people that are living locally have no access to data around air quality and noise pollution and so on, and people that are pushing for it weren't kind of talking in terms of facts. There was a lot of, I suppose, conjecture. With the ODI's summer showcase help, we were able to deploy 20 sensors around Heathrow. We asked for volunteers, mostly through Twitter, thinking that a few people would volunteer, and we were inundated to be frank. So we had to really narrow down the scope, and we deployed 20 air quality and noise sensors, and out of that came breed Heathrow. What we wanted to do was, it's a small scale project, but we wanted to demonstrate methodology, use open data, open hardware so that other people can repeat it. This is not a story that we're trying to own. We want to be able to create community groups around data, around understanding, and this data is freely available with open data licenses. People are still publishing in real time, and you're welcome to get access. Some interesting facts have come out, one of which is actually noise is a huge factor around there, so I think there's something like 54 decibels is the EU threshold for annoyance, and we found that around 15% of the time the noise levels actually peak way past this. It hits about 67 decibels quite regularly. These are facts that no one has, whereas the Heathrow watch, I think, publish means and averages, but actually averages are not what you want. You want to know when the peaks are and understand what the impact will be. This is just with the runways that are currently in existence, so we haven't yet planned for infrastructure and what the impact will be. Going back to why open data for the internet thing, the only way we're going to scale this digitisation of the public world, the cities, is through open data. Hardware is expensive, sensor deployments are expensive to maintain, to deploy initially. In order to get the best return for us as citizens and government projects and smart cities projects, it's quite clear that having some sort of way to share it for people to reuse it in multiple ways is crucial. We currently process around 7 million open data messages, and this is getting traction and people get it. Oesman mentioned air quality egg, we enable air quality egg infrastructure to thrive, lots of earthquake data, lots of people putting up weather stations, but also large scale deployments by smart cities. We'd like to see this thriving, and we're just getting started. If you are thinking about the internet things, come see us, we're going to show off some of the data in the start-up studio this afternoon. One of the lessons that we've learned is actually making the data open isn't enough. For most of the residents, giving them JSON packets in real time and streaming data is actually no use to them whatsoever. The next thing we're thinking about is how do you make this understandable? If I have information from an egg and different things, I want to know how it impacts me, how can I compare it to my neighbours and so on. This is my call to arms, please contact us and we'll be around in the next session.