This is the second post in a three-part blog series on data management. This post will focus on the data handling processes involved in the development of the EFC’s Revenueshed tool.
As mentioned in the first part of this blog series If you build the data platform, will they come?, EFC’s design team regularly asks the following three questions when creating a new tool.
(1) Who are the users?
(2) What is the project’s purpose?
(3) What data exists to support this purpose?
What is a revenueshed?
A revenueshed is the geographic area within which revenue is generated for a defined purpose. It’s a play on words of watershed, an area that drains all water to a common outlet. The purpose of the revenueshed is to model methods of revenue generation for a designated funding goal using new and existing mechanisms. The revenueshed also expands those who pay beyond the traditional polluter pays model by incorporating additional beneficiaries into the model. For example, rather than using solely the boundary of a watershed to source funding for a water quality project, a wider boundary could be drawn to include local governments holding drinking water allocations for the specified water body.