Open CarmenTamayo opened 1 year ago
The upcoming development day for {cleanepi} presents an opportunity to reinvigorate this discussion. The new design of the package is flexible and can easily accommodate the integration of new features by adding new modules, without risking the integrity of its core architecture.
I had had the exact same idea to focus on this during today's dev day, so it's great that it's been highlighted :D
This is related also to issue #9
Last month we had a meeting with the HARMONIZE team, where we discussed best ways to link climate and epi data, and identified opportunities for collaboration with Epiverse. One of the issues that we identified was the lack of wrangling and cleaning tools for aggregated data, which is the most common format for climate data, often the format found for outbreak data (e.g., in situation reports), and therefore the format that would have to be used to merge both types of dataset. Given this need that overlaps in both projects, I'm raising this issue to start a conversation about incorporating functions to
cleanepi
that are suitable for aggregated data, and specifying in the documentation of the package that both individual and aggregated data can be used as inputs