generated from allisonhorst/meds-distill-template
-
Notifications
You must be signed in to change notification settings - Fork 9
/
day_3.qmd
54 lines (28 loc) · 1.41 KB
/
day_3.qmd
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
---
title: "Getting data in a programmatic way"
---
```{r setup, include=FALSE}
knitr::opts_chunk$set(echo = TRUE)
```
## Day 3
| **Time (PST)** | **Activity** |
|-------------------|--------------------------------------|
| 10:00am - 11:00am | *Introduction to APIs (50min)* |
| 11:00am - 11:10am | *Break (10 min)* |
| 11:10am - 12:30am | *APIs hands-on (80 min)* |
| 12:30pm - 1:30pm | *Lunch (60 min)* |
| 1:30pm - 2:00pm | *Introduction to the group project (30 min)* |
| 2:00pm - 4:00pm | *Group Projects (120min)* |
## Getting Data
## The manual way
Using website to retrieve data is great interactive way to search and explore data of interest. Let's start our day by searching some data on the data repository DateONE: <https://search.dataone.org/data>
In case you need some inspiration, look at this dataset about historic precipitation in Alaska: <https://doi.org/10.5063/N29VCQ>
<br>
## The programmatic way
Although discovering data through a web interface is convenient and offers a great experience, it is often hard to scale this approach or to integrate it into a reproducible workflow.
**[Slides](https://brunj7.github.io/eds214-slides/api.html)**
### Hands-on -- APIs
[**Repository**](https://github.com/brunj7/eds214-handson-api)
---
## Group project
[**Group project**](group_project.html)