Data Story
The data our team used came from four different sources, Christchurch water zones, ECAN well search, Community drinking water supply points, and Canterbury maps open data. The data came in many forms, from web scraped text/html to JSON.
A combination of this data was used to build a picture of water quality within different zones within Christchurch, and in turn, this was displayed on a map in a web interface.
Some significant issues were apparent within the data, such as large inconsistencies regarding which water sources had water quality data, which wells supplied which areas and some data were several years old.
Due to this, some assumptions had to be made while ensuring our solution was scalable and adaptable once the data was brought up to date and made more complete.
Our map was designed to accept a series of regions to ensure scalability, with the high-level regions being used in the prototype seen. Once lower-level regions are available, these can be added to the used dataset, and the map will update accordingly.
Where data inconsistencies were apparent, a null was used in place, resulting in the ability for the prototype to update the map once this data becomes available automatically.
A combination of this data was used to build a picture of water quality within different zones within Christchurch and in turn this was displayed on a map in a web interface.
Some major issues were apparent within the data such as large inconsistencies regarding which water sources actually had water quality data, which wells supplied which areas and the fact that some data was several years old.
Due to, this some assumptions had to be made while ensuring our solution was scalable and adaptable once the data was brought up to date and made more complete.
To ensure scalability our map was designed to accept a series of regions, with the high level regions being used in the prototype seen. Once lower level regions are available these can simply be added to the used dataset and the map will update accordingly.
Where data inconsistencies were apparent a null was used in place, resulting in the ability for the prototype to automatically update the map once this data becomes available.