The internet has always inspired us. We've always considered it a place for sharing information of all kinds. We wanted to create a solution that enables people to inform themselves about important things that are going on around them. We in team Wärket set out to visualize the locations of different emergencies that can occur. In these instances, lots of questions will be raised and our vision is to gather this information in a single place. Kriskartan.

What it does

Our solution gathers alert-information from SMHI and and pins the location of the city, municipality or county on a map of Sweden. Krisinformation provides a wealth of different emergencies like polluted water, gas leakage, radiation and terrorist attacks for example. The feed is sorted by alert severity and there is also a filter which right now does nothing.

How we built it

We built the back-end solution in Java as a maven-project. We're hosting our own server (locally) with a JBoss EAP 6.2 runtime and the GUI is built using Javascript, CSS and HTML. The underlying database is Postgres. The server can collect information from the available APIs provided by SMHI and and the GUI renders the information and locations in a web-browser.

Challenges we ran into

The team was split in two: the back-end people and the front-end people. Back-end challenges: - Working with maven and setting up the server. Getting the server to work was probably the hardest part for the back-end group, there are many dependecies, settings and configurations in a maven project and finding the issue took longer than expected. - Transforming polygons into JSON proved to be a challenging task indeed. - Maintaining the domain driven architecture. Front-end challenges: - Extract the polygon from JSON objects. - Establish a connection between the feed-items with the map visualization.

Accomplishments that we're proud of

Creating the framework of this solution seemed at first a daunting task, but with planning, good communication and preparation we've managed to create a scalable solution where we can add new types of alerts and information without too much effort. We've also managed to keep the morale high throughout the process, which is something we're very proud of as a team.

What we learned

- Working more closely as a team. Stress can sometimes be very good.
- We learned that there really should be a standard to follow when creating an API. 
- Risk of grass fires seems to be REALLY dangerous according to SMHI.
- Crowd-sourcing alerts is a really good idea.

What's next for Kriskartan

The possibilities are endless. We want to make it easy for everyone to contribute to Kriskartan. So the next step for kriskartan is to create a simple interface where people can push alerts to Kriskartan, in case of an emergency. When crowd-sourcing is done right it can be a powerful thing. We also want Kriskartan to be able to display important information even when offline. Such as the location of shelters, drinkable water and public aid facilites.

Share this project: