Description

Our system is set up so that it can take a huge variety of data. Spatial scales range from city-wide to company-specific, and anything in between. The nature of our datasets also vary hugely: we collect data on material any type of resource flow or stock. From fossil fuel consumption to building stock, and from plastic recycling to agricultural production.

All data is recorded in a single database structure. This has allowed us to create visualization tools that can be applied across the board. For all our datasets we have a number of graphs available. An example can be seen here:

Example A
(click on the different chart icons to view some of them)

We also use a variety of georeferenced data. This allows us to create maps like these:

Example 1

Example 2

Choropleth maps are another example of maps that are possible (currently under development).

However, what we do NOT have are sector- or scale-specific visualizations. It could very well be that there are interesting visualizations to be made for the water sector (e.g. a visualization of the water cycle), for instance. Or we may be able to do interesting things with neighborhood-specific data. We also have not yet looked into how to visualize an entire system (a full MFA/mass balance). Sankeys are a logical possibility but we may be able to innovate a bit.

We are looking for someone who can take our visualizations to the next level. Any idea that can further the situation described above is welcome. Focusing on one particular element is absolutely fine. There are a few parameters to take into account:

• When using external libraries or services, we strongly prefer open source software over commercial tools


• We want to be able to automate whatever solution is built. It should not require manual work every time a new visualization is rendered - instead we should be able to populate the system with data that is generated dynamically through a database query on our side, so that the visualizations can be generated on the fly.


• There are a variety of different users who will want to re-use these visualizations. Being able to export or save them in a commonly used format is ideal (SVG, PDF, JPG, etc).


• The more appealing, the better. There is a certain degree of subjectivity here, but the more impressed our visitors are, the better.


• Think about maintenance and durability. The simpler to maintain, the better.

To get started with this task, please let our team know what you have in mind. Development should take a phased approach, in coordination with our Programming Task Force. We are glad to try and assist you where we can