Nodabase.net

Traffic and weather livecentre

Description

The BT Traffic and weather livecentre aims to gather data from public authorities, social media and editorial systems to provide insights and real time information in a mobile friendly web application. A custom built framework allows us to easily connect to new public or private data sources, fetch data, parse and transform it to our needs and apply algorithms to prioritize which data to show and how. Data widgets appear automatically when there i.e. is a weather alert in place, or displays a map when there is a power outage somewhere in our region.

Using colors, labels and symbols we try to attract attention to important data. The livecentre is alive even when there is no editorial content being manually added, using rules and algorithms to prioritize and label incoming public data.

The livecentre app has also been used for other data driven live coverage sites, like the US election live coverage, and is constantly being updated to retrieve and display data from new public sources.

Origin

Our region is heavily affected by bad weather and traffic often suffers from that. We wanted to give our readers a one-stop solution where we automatically prioritize and show relevant content related to traffic and weather data. There are multiple sites giving some of this information, but none that gathers it in one place. And none that automatically prioritizes what to show, how and when based on real time events.

We wanted to create both a system for presenting data in a user friendly, simple and mobile friendly way, and a flexible system to fetch data from multiple public APIs and data sources.

By adding such a system we could provide a faster and more updated live experience for our readers and at the same time enabling the journalists to focus more on the big stories and less on short updates from the traffic and weather.

Data

The system fetches data from multiple public sources and private sources. We have set up a flexible harvesting system that cater for most common types of APIs and data formats. The system has configurable scheduling for fetching data, and applies rules and algorithms for data before it is stored for presentation.

Data sources includes traffic messages, road conditions, weather data, webcam data and travel time data via geographical APIs of the Public Roads Administration, weather observation data, weather alerts, and extreme weather alerts from the Meteorological Institute, air quality measurements from Norwegian Institute for Air Research, power outage data from local power grid operator, feeds from internal live blog tools, feeds from internal webcam systems, Twitter and Google maps.

Resources

Two data journalists/developers working with the project as a side/part time project for around 6 months, building the harvesting tool and the livecentre presentation app. This was done parallel to other data journalism work in our small team. One project lead part time (our team leader)

Impact

The project has given the citizens of our region a unique site to get updated on weather and traffic information that impacts on their daily life. The site has attracted a lot of web traffic and is daily one of our top three visited pages. User engagement is high, and the project has received attention from managers of public data for its use of open data.

Internally the project has had a big impact on our newsroom. It has enabled us to have an always up-to-date live coverage using automated data processing. This has made it possible to redirect journalist resources to interacting with users, gathering stories and images not available as data. The system also has an alert module that can alert the newsroom on weather and traffic related events based on the real time data feed/parsing.

Obstacles

Getting access to public data in machine readable formats is always a challenge. Our main obstacle was getting traffic messages in a format that was useable to us. First we tried to parse the complex EU standard DATEX format for traffic information, but after debating with the roads administration we got access to other and better data. Another obstacle was inconsistent data and categories, making it difficult to create rules and triggers. We spent a lot of time inspecting and analyzing data over time to create the best possible rules/algorithms for displaying relevant info and hide “noise”.

We also had a lot of issues with creating a fast and responsive site optimized for mobile phones and at the same time presenting a lot of data in a way that made it relevant for the user. We had to invest a lot of time into learning new web frameworks and methods for presenting data. Getting the end site to work great on slow mobile connections took time, but was an important issue.

Go to case website
Built on WordPress by Smart Media AS

Privacy Policy

The Privacy Statement is about how this website collects and uses visitor information. The statement contains information that you are entitled to when collecting information from our website (Personal Information Act, section 19), and general information about how we treat personal data (Personal Data Act, section 18, first paragraph). The legal owner of the website is the processing officer for the processing of personal data. It is voluntary for those who visit the web sites to provide personal information regarding services such as receiving newsletters and using the sharing and tip services. The treatment basis is the consent of the individual, unless otherwise specified.

1. Web analytics and cookies (cookies)

As an important part of the effort to create a user-friendly website, we look at the user pattern of those who visit the site. To analyze the information, we use the Google Analytics analysis tool. Google Analytics uses cookies (small text files that the site stores on the user's computer), which registers the users' IP address and provides information about the individual user's online movements. Examples of what the statistics give us answers to are; how many people visit different pages, how long the visit lasts, what websites users come from and what browsers are used. None of the cookies allow us to link information about your use of the site to you as an individual. The information collected by Google Analytics is stored on Google servers in the U.S.. The information received is subject to the Google Privacy Policy. An IP address is defined as a personal information because it can be traced back to a particular hardware and thus to an individual. We use Google Analytics's tracking code to anonymize the IP address before the information is stored and processed by Google. Thus, the stored IP address can not be used to identify the individual user.

2. Search

If the webpage has search function, it stores information about what keywords users use in Google Analytics. The purpose of the storage is to improve our information service. The search usage pattern is stored in aggregate form. Only the keyword is saved and they can not be linked to other information about the users, such as the IP addresses.

3. Share / Tips service

The "Share with others" feature can be used to forward links to the site by email, or to share the content of social networking. Tips for tips are not logged with us, but only used to add the tips to the community. However, we can not guarantee that the online community does not log this information. All such services should therefore be used wisely. If you use the email feature, we only use the provided email addresses to resend the message without any form of storage.

4. Newsletter

The website can send out newsletters by email if you have registered to receive this. In order for us to be able to send e-mail, you must register an e-mail address. Mailchimp is the data processor for the newsletter. The e-mail address is stored in a separate database, not shared with others and deleted when you unsubscribe. The e-mail address will also be deleted if we receive feedback that it is not active.

5. Registration, form

The website may have a form for registration, contact form or other form. These forms are available to the public to perform the tasks they are supposed to do. Registration form is for visitors to sign up or register. Contact form is for visitors to easily send a message to the website's contact person. We ask for the name of the sender and contact information for this. Personal information we receive is not used for purposes other than responding to the inquiry. The form is sent as email via Mailgun as a third party solution. The entire submission will be stored at Mailgun for 24 hours. Between 24 hours and 30 days, only mailheader is stored before the submission is deleted after 30 days. The reason for this storage is to confirm whether emails are sent from the website and forwarded to the correct recipient. Once the email is received by the recipient, it is up to the recipient to determine the data processing needs of the email.

6. Page and service functionality

Cookies are used in the operation and presentation of data from websites. Such cookies may contain language code information for languages ​​selected by the user. There may be cookies with information supporting the load balancing of the system, ensuring all users the best possible experience. For services that require login or search, cookies can be used to ensure that the service presents data to the right recipient.

7. How to manage cookies in your browser

On www.nettvett.no, read how to configure your browser to accept / reject cookies, and get tips for safer use of the internet.