Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Planning questions: spatial scale and excluding goals #30

Open
jules32 opened this issue Jul 23, 2018 · 2 comments
Open

Planning questions: spatial scale and excluding goals #30

jules32 opened this issue Jul 23, 2018 · 2 comments

Comments

@jules32
Copy link
Contributor

jules32 commented Jul 23, 2018

Here are a few great planning questions from the Cornwall team that many people ask, so I thought we'd answer them here as a Question&Answer and answered a bit more generalized:

Spatial scale and thinking ahead

Q: We are currently doing an assessment in the Southwest United Kingdom (UK). But in the future, we may do a full-UK study. How should we set up the assessment repository to be best set up now and in the future?

A: Create a Southwest repository now, and create a second UK repository when the time comes. This will be easier to communicate and will allow the two spatial scales to be separate, since there are different stakeholder and audiences for these spatial scales.

I thought this through a bit more, and wrote out good ("pros") and bad ("cons") attributes of two options:

Option 1: Create one repository for the Southwest now, and one for the entire UK later

  • Pros:
    • Simpler to set up now
    • UK-scale data preparation can be scripted and re-used later
  • Cons:
    • Requires a second repository later, and the shuffling that involves

Option 2: Create only one repository at the UK scale, but now only assess the Southwest

  • Pros:
    • Just one repo
  • Cons:
    • More complicated to set up now (more decisions to be made now)
    • More difficult to communicate scale of the region now
    • Means you have to know full UK regions now, which may change in the future

Region size differences

Q: Is it OK to have high variation in size between possible regions?

A: Yes, it's OK to have regions of different sizes. Each region is calculated separately and then combined by a weighted average. The default is area-weighted average, but if there was a compelling reason to do something different, it is possible.

Excluding goals

Q: Excluding goals – what has been the justification/level deemed suitable for excluding a goal?

A: Goals should be excluded because they are deemed not relevant to a region – not because there aren't good data available. But there is no perfect formula to determine relevance. Talk with experts/stakeholders and consult reports/studies to see if a goal is relevant, and discuss if there are ways to modify definitions to better suit a location. It is possible to add/remove/re-add/re-remove goals throughout the OHI process, with all progress saved even if you ultimately do not want the goal included. And remember to document why or why not a goal was excluded (especially if it changed) because it will be important for communication and reporting, as well as for future efforts.

Website

Q: How do we develop our repos's website on Github in preparation for SH engagement?

A: Soon, the place to look will be in the Toolbox-Training chapter Updating your website. Until then, this resource is more general but will give you some familiarity with how websites work: Making free websites with RStudio’s R Markdown

@jamiecmontgomery
Copy link
Contributor

Options 1 & 2 are the same as written right now.

@jules32
Copy link
Contributor Author

jules32 commented Jul 24, 2018 via email

@jules32 jules32 changed the title Some planning questions Planning questions about spatial scale and excluding goals Aug 14, 2018
@jules32 jules32 changed the title Planning questions about spatial scale and excluding goals Planning questions: spatial scale and excluding goals Aug 14, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants