render the data accessible in another format (CSV/JSON etc)
The two are linked because reformatting the data (e.g. using dictionaries and not arrays; combining data to reduce lookups; saving calculations per-commune) will make the site faster but also make the data more easily available.
Questions:
how to break up the work?
how will this fit with how data is already manipulated?
NB:
all calculations can now be applied per-commune, these should then be aggregated for a grouping (whether by EPCI or custom)
Aims:
The two are linked because reformatting the data (e.g. using dictionaries and not arrays; combining data to reduce lookups; saving calculations per-commune) will make the site faster but also make the data more easily available.
Questions:
NB: