-
Notifications
You must be signed in to change notification settings - Fork 3
Expand file tree
/
Copy pathoverview.Rmd
More file actions
68 lines (47 loc) · 4.21 KB
/
Copy pathoverview.Rmd
File metadata and controls
68 lines (47 loc) · 4.21 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
---
title: "The spatial analysis of accuracy using geographically weighted frameworks"
author: "Lex Comber & Paul Harris"
date: "June 2016"
output: pdf_document
---
# Overview
This workshop is structured as follows:
- 09h15-10h45 Introduction & GW framework and Computer practical
- 10h45-11h00 Coffee break
- 11h00-12h30 Mapping spatial accuracy and computer practical
- 12h30-14h00 Lunch break
- 14h00-15h30 Putting it all together (loops, functions) and computer practical
- 15h30-15h45 Coffee break
- 15h45-17h15 Additional materials and computer practical support
Each session will include a short introduction (some slides by Lex or Harry), followed by some participant coding.
The workshop main aim is get you thinking a bit more like a geographer. It draws from the plethora of methods for analysing point data many of which were developed within the domain of *quantitative social geography* and explores their application to observations about land cover. The fundamental theme that it promotes is that *Space is Special*. Through a series of illustrative analyses it argues that location, *latitude* and *longitude* or *easting* and *northing*, cannot be treated as just another variable. Specifically, the workshop encourages those interested in remote sensing and land cover scientists to wear 'geography goggles' through which to view the world. These promote a view of the world in which the wearer:
- does not expect relationships to be same everywhere
- does not consider the world to be not normally distributed esp. in space
- expects processes, relationships, trends etc to vary spatially
- and therefore expects to find clusters, hotspots, coldspots, etc
In the context of remote sensing accuracy assessments it seeks to move away from the a-spatial nature of the measures generated by the confusion matrix. The background to this work is clearly outlined in three papers:
FOODY, G.M., 2005, Local characterization of thematic classification accuracy through spatially constrained confusion matrices. *International Journal of Remote Sensing*, 26, pp. 1217–1228.
COMBER, A., FISHER, P.F., BRUNSDON, C. and KHMAG, A., 2012, Spatial analysis of remote sensing image classification accuracy. *Remote Sensing of Environment*, 127, pp. 237–246.
COMBER A.J., 2013. Geographically weighted methods for estimating local surfaces of overall, user and producer accuracies. *Remote Sensing Letters*, 4(4): 373-380
The last of this is available at this location `from XYZ-GITHUB` and provides an thorough introduction to the materials covered in this practical.
# Practicalities
Before we start you should do the following :
- install R on your computer R which an be downloaded from CRAN at `https://cran.r-project.org`
- you may prefer use R through RStudio `https://www.rstudio.com/products/rstudio/download/`
- you should use the code below to install a number of `packages` or `libraries`
```{r eval=FALSE}
install.packages("spgwr", dep = T)
install.packages("GISTools", dep = T)
install.packages("repmis", dep = T)
```
Code and data are provided and can be downloaded from Lex Comber's github site [https://github.com/lexcomber/LexTrainingR/](https://github.com/lexcomber/LexTrainingR/). You will a summary of the materials of the course.
# Tips
For efficient R coding and learning it helps if you:
1. Keep your code in scripts, typically saved with a `.R` extension and a file name that has some meaning (eg `WorkshpPt1.R')
2. Annotate your scripts with comments to help you remember what you have done when you come back to a piece of code that you wrote a few years ago. Annotations starts with `#` and you should use them freely. Every after the `#` is not read by R
3. Use the shortcuts in RStudio and R for running code - highlight cmd / ctrl `Return` in R for example
4. Use the massive amounts of online help that is available via RBloggers [http://www.r-bloggers.com](http://www.r-bloggers.com) and StackOverFlow [http://stackoverflow.com/questions/tagged/r](http://stackoverflow.com/questions/tagged/r)
5. Copy and modify code where you can - the standard rules of plagiarism do not apply, although acknowledgements and licensing are important
# Finally....
We hope that you enjoy this day and that you find that you find it useful.
Lex and Harry