2. Restructure code to allow easy integration of customised inputs

[shellstanton]

Restructure code so it contains an initial section for user inputs relating to:

• area of interest
• road travel speeds
• NDVI parameters i.e. period of time over which to summarise NDVI plus walking speeds assigned to NDVI intervals

[joshlongbottom]

I think the majority of these would be simple to add. I envisage that most users won't know the coordinates for the bounding box of their area of interest, but may have a shapefile, or know the name of a district. Would it be useful to allow the option of a data-upload at the start of the script? We can grab the extent from a spatial object. Something to discuss.

[johnrobertarcher]

Now mostly completed but not quite as straightforward for a potential user to setup as hoped; can discuss in future.

The initial 'setup' section currently consists of these stages, allowing potential users to input custom parameters:

• loading required packages
• defining area of interest (using coordinate data or uploading a shapefile)
• importing landsat 8 parameters (currently just importing an existing file)
• defining travel speeds (walking and road), which can be changed according to expected travel speeds e.g., slower during rainy weather etc
• population data parameters (this was a little tricky as a dataframe needs to be downloaded and checked to select a specific covariate. I have generated a function to do this but does hinder the setup process slightly)
• health facility data (again, currently just importing an existing file with potential to update in future by incorporating AfriMapR)