Logical Next Areas For Improvement

Issue	Explanation	Action Needed
Administrative Units	The Reporting Tool code is currently based on the Kenyan Administrative Unit Structure. The Flux Output Database that served as reference for developing the Reporting Tool was Kenyan Based	A picture of what a generic Flux output database could look like is needed. Work then needs to be done against this to make the administrative unit and hence reporting system Generic.
Data Copying Weaknesses	The Reporting Tool currently has its own PostgreSQL Database instance. FLINT output is copied from FLINT’s PostgreSQL database instance and imported to the Reporting Tool’s database for processing. This is a huge problem for a full country spatial run since the database is usually massive	The Reporting Tool should be improved to share the same PostgreSQL database with the FLINT to avoid re-importation issues. If the above is not possible, the Reporting Tool needs to be redesigned to have its PostgreSQL database in its own optimized server to allow successful importation of dumped data which is memory intensive
Data Loading Weaknesses	The FLINT output data is currently loaded into the Reporting Tool’s PostgreSQL database via a script which also kick starts the aggregation exercise	An interface for onboarding data needs to be provided to make it easier for non technical users to operate the system
Missing Configuration Screens	The Reporting Tool Report Parameters were fixed based on Kenyan policies. E.g. The Periods that it takes to have a land conversion were fixed to Kenya’s land use policies	The system’s configurations need to be exposed to allow future users to tweak them to their country requirements