-
Notifications
You must be signed in to change notification settings - Fork 2
/
01_introduction.Rmd
80 lines (41 loc) · 6.53 KB
/
01_introduction.Rmd
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
67
68
69
70
71
72
73
74
75
76
77
78
79
80
# Coordinate Reference System (CRS)
A coordinate reference system (CRS) is the way we translate locations measured on a spherical surface (the earth or other planet) onto a flat surface (a map printed on paper or displayed on a screen).
**CRS = Datum + Projection + Additional Parameters**
*A common analogy employed to teach projections is the [orange peel analogy](https://ceiengineers.com/about/news-media?id=34025/how-is-a-map-projection-like-an-orange-peel). If you imagine that the earth is an orange, how you peel it and then flatten the peel is similar to how projections get made. We will also use it here.*
## Datum
A **Datum** is a model of the shape of the earth.
It has angular units (i.e. degrees) and defines the starting point (i.e. where is (0,0)?) so the angles reference a meaningful spot on the earth.
Common global datums are WGS84 and NAD83. Datums can also be local, fit to a particular area of the globe, but ill-fitting outside the area of intended use.
When datums are used by themselves it's called a *Geographic Coordinate System*.
*Orange Peel Analogy: a datum is your choice of fruit to use in the orange peel analogy. Is the earth an orange, a lemon, a lime, a grapefruit?*
Comments from the pros: Datums matter! California Albers with NAD27 is **NOT** the same as California Albers with NAD83. See all of the advice [here](https://twitter.com/MicheleTobias/status/955861280174174208)
## Projection
A **Projection** is a mathematical transformation of the angular measurements on a round earth to a flat surface (i.e. paper or a computer screen).
The units associated with a given projection are usually linear (feet, meters, etc.).
Many people use the term "projection" when they actually mean "coordinate reference system". (With good reason, right? Coordinate References System is long and might make you sound pretentious.) One example is the title of this workshop... but you wouldn't know what it was about if I said it was a workshop on "Coordinate Reference Systems in R", would you?
*Orange Peel Analogy: a projection is how you peel your orange and then flatten the peel.*
Image source: https://kaiserscience.wordpress.com/earth-science/maps/map-projections/
## Additional Parameters
Additional parameters are often necessary to create the full coordinate reference system. For example, one common additional parameter is a definition of the center of the map. The number of required additional parameters depends on what is needed by each specific projection.
*Orange Peel Analogy: an additional parameter could include a definition of the location or orientation of the stem of the fruit.*
## Which CRS/projection should I use?
To decide if a projection is right for your data, answer these questions:
1. What is the area of minimal distortion?
2. What aspect of the data does it preserve?
[The Geographer's Craft Map Projection Overview](https://foote.geography.uconn.edu/gcraft/notes/mapproj/mapproj_f.html), [CUNY Hunter College](http://www.geo.hunter.cuny.edu/~jochen/gtech201/lectures/lec6concepts/map%20coordinate%20systems/how%20to%20choose%20a%20projection.htm), and [Kaiser Science](https://kaiserscience.wordpress.com/earth-science/maps/map-projections/) have good discussions of these aspects of projections. Online tools like [Projection Wizard](http://projectionwizard.org/) can also help you discover projections that might be a good fit for your data.
Advice from the pros: Take the time to figure identify a projection that is suited for your project. You don't have to stick to the ones that are popular.
## Notation for Coordinate Reference Systems
You typically have two options for identifying a CRS in most tools for working with geospatial data. The documentation for a command or function that requires projection information will tell you which is required. Often you can choose between the two options.
### EPSG Code
*A note on linguistics:* EPSG stands for "European Petroleum Survey Group"... but everyone just says EPSG.
An EPSG Code is an ID that has been assigned to most common projections to make reference to a particular projection easy. It is a method for standardizing references to map projections. An EPSG Code is also called an SRID (Spatial Reference Identifier). Technically, EPSG is the authority that assigns SRIDs, but you will hear these terms used interchangeably.
The main advantages to using this method of specifying a projection are that it is standardized and ensures you have the same parameters every time. The disadvantage is that if you need to know the parameters used by the projection or it's name, you have to look them up, but that's fairly easy to to at [spatialreference.org](http://spatialreference.org/ref/epsg/). Also, you can't customize the parameters if you use an EPSG code. For example: `EPSG:27561`
### PROJ String
[PROJ](https://www.osgeo.org/projects/proj/) is an open source library for defining and converting between coordinate reference systems. It defines a standard way to write projection parameters. For example: `+proj=lcc +lat_1=49.5 +lat_0=49.5 +lon_0=0 +k_0=0.999877341 +x_0=6 +y_0=2 +a=6378249.2 +b=6356515 +towgs84=-168,-60,320,0,0,0,0 +pm=paris +units=m +no_defs`
Two important advantages to using this option are (1) the parameters are human-readable and immediately transparent and (2) the strings are easily customized. The main disadvantage to this option is that it's easy to make a mistake when you reproduce the string, accidentally changing parameters.
*A note on linguistics:* PROJ is commonly pronounced "prodge" ("PROJ" rhymes with "dodge"); PROJ is short for "projection". Sometimes people will add a number to the end of PROJ to indicate which version of the library they are referring to.
## Avoid a Common Mistake
A very common mistake in any GIS (ArcGIS, QGIS, R, GRASS, Python, etc.) is defining a projection for a dataset when the person should have re-projected the data. It is very common that you'll need to tell your GIS what the projection/CRS of your data should be. In these cases, the GIS needs to know what the projection/CRS **currently** is, not what you would like it to be. If you need to change a projection, you need to go through a different process, often called Re-project or Transform.