-
Notifications
You must be signed in to change notification settings - Fork 0
/
m101-wsim-gldas-python.qmd
790 lines (600 loc) · 51.2 KB
/
m101-wsim-gldas-python.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
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
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
---
title: "WSIM-GLDAS: Acquisition, Exploration, and Integration (Python)"
author:
- "Josh Brinks"
- "Elaine Famutimi"
date: "June 3, 2024"
bibliography: "references/wsim-gldas-references.bib"
---
## Overview
In this lesson, you will acquire the dataset called **Water Security Indicator Model - Global Land Data Assimilation System (WSIM-GLDAS)** from the [NASA Socioeconomic Data and Applications Center (SEDAC)](https://sedac.ciesin.columbia.edu/) website, perform various pre-processing tasks, and explore the dataset with advanced visualizations. We will also integrate WSIM-GLDAS with a global administrative boundary dataset called [geoBoundaries](https://www.geoboundaries.org/api.html) and a population dataset called the [Gridded Population of the World](https://sedac.ciesin.columbia.edu/data/collection/gpw-v4). You will learn how to perform numerous data manipulations and visualizations throughout this lesson.
## Learning Objectives
After completing this lesson, you should be able to:
- Retrieve WSIM-GLDAS data from SEDAC.
- Retrieve Administrative Boundary using the geoBoundaries API.
- Subset WSIM-GLDAS data for a region and time period of interest.
- Visualize geospatial data to highlight precipitation deficit patterns.
- Write a pre-processed NetCDF-formatted file to disk.
- Perform visual exploration with histograms, choropleths, and time series maps.
- Integrate gridded population data with WSIM-GLDAS data to perform analyses and construct visualizations to understand how people are impacted.
- Summarize WSIM-GLDAS and population raster data using zonal statistics.
::: {.callout-tip style="color: #5a7a2b;"}
## Programming Review
This is the Python version of this lesson. If you would like to work through the R version please visit [WSIM-GLDAS: Acquisition, Exploration, and Integration](https://ciesin-geospatial.github.io/TOPSTSCHOOL-water/m101-wsim-gldas.html)
:::
## Introduction
The water cycle is the process of circulation of water on, above, and under the Earth's surface [@NOAA2019]. Human activities produce greenhouse gas emissions, land use changes, dam and reservoir development, and groundwater extraction have affected the natural water cycle in recent decades [@intergovernmentalpanelonclimatechange2023]. The influence of these human activities on the water cycle has consequential impacts on oceanic, groundwater, and land processes, influencing phenomena such as droughts and floods [@Zhou2016].
Precipitation deficits, or periods of below-average rainfall, can lead to drought, characterized by prolonged periods of little to no rainfall and resulting water shortages. Droughts often trigger environmental stresses and can create cycles of reinforcement impacting ecosystems and people [@Rodgers2023]. For example, California frequently experiences drought but the combination of prolonged dry spells and sustained high temperatures prevented the replenishment of cool fresh water to the Klamath River, which led to severe water shortages in 2003 and again from 2012 to 2014. These shortages affect agricultural areas like the Central Valley, which grows almonds, one of California's most important crops, with the state producing 80% of the world's almonds. These severe droughts, coupled with competition for limited freshwater resources, resulted in declining populations of [Chinook salmon](https://www.fisheries.noaa.gov/species/chinook-salmon) due to heat stress and gill rot disease disrupting the food supply for Klamath basin tribal groups [@guillen2002; @Bland2014].
![](docs\images\watercycle_rc.jpg)[^1]
[^1]: Photo Credit, NASA/JPL.
::: column-margin
::: {.callout-tip style="color: #5a7a2b;"}
## Data Science Review
A [raster](https://docs.qgis.org/2.18/en/docs/gentle_gis_introduction/raster_data.html) dataset is a type of geographic data in digital image format with numerical information stored in each pixel. (Rasters are often called grids because of their regularly-shaped matrix data structure.) Rasters can store many types of information and can have dimensions that include latitude, longitude, and time. NetCDF is one format for raster data; others include Geotiff, ASCII, and many more. Several raster formats like NetCDF can store multiple raster layers, or a "raster stack," which can be useful for storing and analyzing a series of rasters.
:::
:::
The **Water Security (WSIM-GLDAS) Monthly Grids, v1 (1948 - 2014)** The Water Security (WSIM-GLDAS) Monthly Grids, v1 (1948 - 2014) dataset "identifies and characterizes surpluses and deficits of freshwater, and the parameters determining these anomalies, at monthly intervals over the period January 1948 to December 2014" [@isciences2022]. The dataset can be downloaded from the [NASA SEDAC](https://sedac.ciesin.columbia.edu/data/set/water-wsim-gldas-v1) website. Downloads of the WSIM-GLDAS data are organized by a combination of thematic variables (composite surplus/deficit, temperature, PETmE, runoff, soil moisture, precipitation) and integration periods (a temporal aggregation) (1, 3, 6, 12 months). Each variable-integration combination consists of a NetCDF raster (.nc) file ( with a time dimension that contains a raster layer for each of the 804 months between January, 1948 and December, 2014. Some variables also contain multiple attributes each with their own time series. Hence, this is a large file that can take a lot of time to download and may cause computer memory issues on certain systems. This is considered BIG data.
::: callout-note
## Knowledge Check
1. How would you best describe the water cycle?
a. A prolonged period of little to no rainfall.
b. Low precipitation combined with record temperatures.
c. The circulation of water on and above Earth's surface.
d. A cycle that happens due to drought.
2. What human interventions affect the water cycle? (select all that apply)
a. Greenhouse gas emissions
b. Land use changes
c. Dam and reservoir development
d. Groundwater overexploitation
3. What is a precipitation deficit?
a. A period of rainfall below the average.
b. A prolonged period of little to no rainfall.
c. A period of chain reactions.
d. A period of rainfall above the average.
:::
::: {.callout-tip style="color: #5a7a2b;"}
## Data Science Review
The **Water Security (WSIM-GLDAS) Monthly Grids dataset** used in this lesson is hosted by [NASA's Socioeconomic Data and Applications Center (SEDAC](https://sedac.ciesin.columbia.edu/)), one of several [Distributed Active Archive Centers (DAACs)](https://www.earthdata.nasa.gov/eosdis/daacs). SEDAC hosts a variety of data products including geospatial population data, human settlements and infrastructure, exposure and vulnerability to climate change, and satellite-based land use, air, and water quality data. In order to download data hosted by SEDAC, you are required to have a free NASA EarthData account. You can create an account here: [NASA EarthData](https://urs.earthdata.nasa.gov/users/new).
:::
## Acquiring the Data
For this lesson, we will work with the **WSIM-GLDAS dataset Composite Anomaly Twelve-Month Return Period NetCDF** file. This contains water deficit, surplus, and combined "Composite Anomaly" variables with an integration period of 12 months. Integration period represents the time period at which the anomaly values are averaged over. The 12-month integration averages water deficits (droughts), surpluses (floods), and combined (presence of droughts and floods) over a 12-month period ending with the month specified. We begin with the 12-month aggregation because this is a snapshot of anomalies for the entire year making it useful to get an understanding of a whole year; once we identify time periods of interest in the data, we can take a closer look using the 3-month or 1-month integration periods.
We'll start by downloading the file directly from the SEDAC website. The [dataset documentation](https://sedac.ciesin.columbia.edu/downloads/docs/water/water-wsim-gldas-v1-documentation.pdf) describes the composite variables as key features of WSIM-GLDAS that combine "the return periods of multiple water parameters into composite indices of overall water surpluses and deficits [@isciences2022a]". The composite anomaly files present the data in terms of how often they occur; or a "return period." For example, a deficit return period of 25 signifies a drought so severe that we would only expect it to happen once every 25 years. Please go ahead and download the file.
- First, go to the SEDAC website at <https://sedac.ciesin.columbia.edu/>. You can explore the website by themes, datasets, or collections. We will use the search bar at the top to search for "water security wsim". Find and click on the Water Security (WSIM-GLDAS) Monthly Grids, v1 (1948--2014) dataset. Take a moment to review the dataset's overview and documentation pages.
- When you're ready, click on the Data Download tab. You will be asked to sign in using your NASA EarthData account.
- Find the Composite Class, and click on the Variable **Composite Anomaly Twelve-Month Return Period**.
## Reading the Data
::: {.callout-tip style="color: #5a7a2b;"}
## Data Science Review
This lesson uses the [**xarray**](https://docs.xarray.dev/en/stable/), [**rioxarray**](https://corteva.github.io/rioxarray/html/index.html), [**rasterio**](https://rasterio.readthedocs.io/en/stable/), [**pandas**](https://pandas.pydata.org/), [**geopandas**](https://geopandas.org/en/stable/),[**exactextractr**](https://isciences.gitlab.io/exactextractr/), [**numpy**](https://numpy.org/), [**calendar**](https://docs.python.org/3/library/calendar.html), [**requests**](https://pypi.org/project/requests/), and [**plotnine**](https://plotnine.org/) packages. If you'd like to learn more about the functions used in this lesson you can use the help guides on their package websites.\n
The **xarray**, **rioxarray**, and **rasterio** packages are designed to work with large and complex raster spatial data while the **geopandas** package lets you handle and analyze vector spatial data (more on that later). **requests** provides methods for users to interact with online databases and websites to directly download data. **exactextractr** performs fast and efficient zonal statistics that summarizes raster and vector data. **calendar** assists with manipulating dates. **pandas** and **numpy** makes standard data processing much easier, and lastly, **plotnine** is used for creating standard plots and figures.\n
Make sure they are installed before you begin working with the code in this document. If you'd like to learn more about the functions used in this lesson you can use the help guides on their package websites.
:::
Once you have downloaded the WSIM-GLDAS file to your local computer, install and load the Python packages required for this exercise.
Once you've completed the download and placed the `composite_12mo.nc` file into your working directory and read the file with the `xr.open_dataset()` function.
```{python}
import xarray as xr
file_path = "data/composite_12mo.nc"
wsim_gldas = xr.open_dataset(file_path, engine = 'h5netcdf')
wsim_gldas
```
Running the `wsim_gldas` object name we created at the end of the code chunk provides us with basic information about our WSIM raster layer. The coordinates section lists the 3 dimensions. The first 2 dimensions are the spatial extents (x/y--longitude/latitude) and time is the 3rd dimension. The output lists the 5 attributes (deficit, deficit_cause, surplus, surplus_cause, both) along with the layer's CRS and the integration period in the Data variables section.
This means that the total number of individual raster layers in this NetCDF is 4020 (5 attributes x 804 time steps/months). Again, BIG data.
## Attribute Selection
We can manage this large file by selecting a single variable; in this case "deficit" (drought). We'll also take the CRS variable that contains our spatial reference information, but we can leave the integration, because we already know it's 12 months.
```{python}
# subset data variables with double brackets
wsim_gldas = wsim_gldas[["deficit", "crs"]]
# check info
wsim_gldas
```
Checking again we see that we're down to 2 data variables (deficit and crs).
## Time Selection
Specifying a temporal range of interest will make the file size smaller and even more manageable. We'll select every year for the range 2000-2014. This can be accomplished by generating a sequence for every year between December 2000 and December 2014 with **pandas**, and then passing that list of dates using the function `.sel()`. Remember, we're using the 12-month integration of WSIM-GLDAS. This means that each time step listed averages the deficit over the 12 prior months. Therefore, if we only select a sequence of December months spanning 2000-2014, each resulting layer will represent the average deficit for that year.
```{python}
# generate a list of dates for subsetting
import pandas as pd
# create the list of dates
keeps = pd.date_range(start="2000-12-01", end="2014-12-01", freq = "YS-DEC")
keeps
# subset the wsim_gldas object w/ keeps
wsim_gldas = wsim_gldas.sel(time= keeps)
# check the time dimension
wsim_gldas.time
```
Now we're down to a single attribute ("deficit") with 15 time steps. We can take a look with a quick plot.
```{python warning=FALSE}
# plot it
p = wsim_gldas.deficit.plot(x="lon", y="lat", col="time", col_wrap = 3, cmap = "Reds_r", aspect = 1.5, size = 1.5, cbar_kwargs = {'orientation':'vertical', 'shrink':0.5, 'label':'Deficit Anomaly'})
```
Although we have now reduced the data to a single attribute with a restricted time of interest, we can take it a step further and limit the spatial extent to a country or state of interest.
::: callout-note
## Knowledge Check
4. Which of these best describe a raster dataset?
a. A type of geographic data made up of square cells.
b. A table or list of geographic numbers.
c. A geographic region of interest.
d. A type of geographic data made up of lines and points.
5. Which of the following is true about the information that rasters can store? (select all that apply)
a. Attributes (thematic content)
b. Dimensions (information expressing spatial or temporal extent information)
c. Geographic coordinates
d. A list of numbers
:::
## Spatial Selection
::: column-margin
::: {.callout-tip style="color: #5a7a2b;"}
## Data Science Review
[GeoJSON](https://geojson.org/) is a format for encoding, storing and sharing geographic data as vector data, i.e., points, lines and polygons. It's commonly used in web mapping applications to represent geographic features and their associated attributes. GeoJSON files are easily readable by both humans and computers, making them a popular choice for sharing geographic data over the internet.
:::
:::
We can spatially crop the raster stack with a few different methods. Options include using a bounding box in which the outer geographic coordinates are specified (xmin, ymin, xmax, ymax), using another raster object, or using a vector boundary like a shapefile or GeoJSON to crop the extent of the original raster data.
In this example we use a vector boundary to accomplish the geoprocessing task of cropping the data to an administrative or political unit. First, we acquire the data in GeoJSON format for the United States from the geoBoundaries API. (Note it is also possible to download the vectorized boundaries directly from <https://www.geoboundaries.org/> in lieu of using the API).
To use the geoBoundaries' API, the root URL below is modified to include a 3 letter code from the International Standards Organization used to identify countries (ISO3), and an administrative level for the data request. Administrative levels correspond to geographic units such as the Country (administrative level 0), the State/Province (administrative level 1), the County/District (administrative level 2), and so on:
*https://www.geoboundaries.org/api/current/gbOpen/**ISO3**/**LEVEL**/*
::: column-margin
::: {.callout-tip style="color: #5a7a2b;"}
## Data Science Review
Built by the community and [William & Mary geoLab](https://github.com/wmgeolab), the geoBoundaries Global Database of Political Administrative Boundaries is an online, open license (CC BY 4.0 / ODbL) resource for administrative boundaries (i.e., state, county, province) for every country in the world. Since 2016, this project has tracked approximately 1 million spatial units within more than 200 entities; including all UN member states.
:::
:::
For this example we adjust the bolded components of the sample URL address below to specify the country we want using the ISO3 Character Country Code for the United States (**USA**) and the desired Administrative Level of State (**ADM1**).
```{python}
import requests
import geopandas as gp
# make the request to geoboundarie's website for the USA boundaries
usa = requests.get("https://www.geoboundaries.org/api/current/gbOpen/USA/ADM1/")
```
In the line of code above, we used `requests.get` to obtain metadata from the URL. We assign the result to a new variable called "usa". Next we will examine the content.
```{python}
# parse the content into a readable format
usa = usa.json()
# look at the labels for available information
usa
```
The parsed content contains 32 components. Item 29 is a direct link to the GeoJSON file (gjDownloadURL) where the vector boundary data is located. Next we will obtain the GeoJSon and check the results.
```{python}
# directly read in the geojson with sf from the geoboundaries server
usa = gp.read_file(usa['gjDownloadURL'])
# check the visuals
usa.boundary.plot()
```
Upon examination, we see that this GeoJSon includes all US states and overseas territories. For this demonstration, we can simplify it to the contiguous United States. (Of course, it could also be simplified to other areas of interest simply by adapting the code below.)
We first create a list of the geographies we wish to remove and assign them to a variable called "drops". Next, we reassign our "usa" variable to include only the entries in the continental US and finally we plot the results.
```{python}
# create a list of territories we don't want in our CONUSA boundary
drops = ["Alaska", "Hawaii", "American Samoa", "Puerto Rico", "Commonwealth of the Northern Mariana Islands", "Guam", "United States Virgin Islands"]
# select all the states and territories not in the above list
usa = usa[~usa.shapeName.isin(drops)]
# check the visuals
usa.boundary.plot()
```
We can take this a step further and select a single state for analysis. Here we use a slightly different method by creating a new object called "texas" by subsetting the state out by name.
```{python}
# extract just texas from the CONUSA boundary
texas = usa[usa["shapeName"].str.contains("Texas")]
# check the visuals
texas.boundary.plot()
```
From here we can clip the WSIM-GLDAS raster stack by using the stored boundary of Texas. You can call the `sf::st_crop()` function to crop the WSIM-GLDAS layer, but as you see below, more simply, you can just use bracket indexing to crop a **stars** object with a **sf** object.
::: {.callout-tip style="color: #5a7a2b;"}
## Drought in the News
Texas experienced a severe drought in 2011 that caused rivers to dry up and lakes to reach historic low levels [@StateImpact]. The drought was further exacerbated by high temperatures related to climate change in February of 2013. Climate experts discovered that the drought was produced by "La Niña", a weather pattern that causes the surface temperature of the Pacific Ocean to be cooler than normal. This, in turn, creates drier and warmer weather in the southern United States. La Niña can occur for a year or more, and returns once every few years [@NOAA2023].
It is estimated that the drought cost farmers and ranchers about \$8 billion in losses.[@Roeseler2011] Furthermore, the dry conditions fueled a series of wildfires across the state in early September of 2011, the most devastating of which occurred in Bastrop County, where 34,000 acres and 1,300 homes were destroyed [@Roeseler2011].
:::
```{python}
import rioxarray as rio
# specify the CRS for rasterio
wsim_gldas = wsim_gldas.rio.write_crs("epsg: 4326")
# clip the wsim object to the extent of texas border
wsim_gldas_texas = wsim_gldas.rio.clip(texas.geometry.values)
```
Finally, we visualize the last time-step in the WSIM-GLDAS dataset (15/December, 2014) and render it with an overlay of the Texas boundary to perform a visual check of our processing.
```{python warning = FALSE}
# check the visuals
wsim_gldas_texas.deficit.plot(x="lon", y="lat", col="time", col_wrap = 3, cmap = "Reds_r", aspect = 0.8, size =2.25, cbar_kwargs = {'orientation':'horizontal', 'shrink':0.6, 'label':'Deficit Anomaly'})
```
Voila! We successfully cropped the WSIM-GLDAS to the extent of Texas and created an overlay map with both dat sets to check the results. If you were carrying out further analysis or wanted to share your work with colleagues, you may want to save the processed WSIM-GLDAS to disk.
Multidimensional (deficit, time, latitude, longitude) raster files can be saved with **xarray**'s `to_netcdf()` function and vector data can be saved using **geopanda's** `to_file()`.
```{python eval = FALSE}
# the grid_mapping attribute will kick an error when we try to write to disk so we have to delete it first
del wsim_gldas_texas['deficit'].attrs['grid_mapping']
# write the processed wsim-gldas file to disk as a netcdf
wsim_gldas_texas.to_netcdf("wsim_gldas_tex.nc")
# write the Texas boundary to disk
texas.to_file('texas.geojson')
```
The size of the pre-processed dataset is 1.6 MB compared to the original dataset of 1.7 GB. This is much more manageable in cloud environments, workshops, and git platforms. T
## Advanced Visualizations and Data Integrations
Now that we've introduced the basics of manipulating and visualizing WSIM-GLDAS, we can explore more advanced visualizations and data integrations. Let's clear the workspace and start over again with the same **WSIM-GLDAS Composite Anomaly Twelve-Month Return Period** we used earlier. We will spatially subset the data to cover only the Continental United States (CONUSA) which will help to minimize our memory footprint. We can further reduce our memory overhead by reading in just the variable we want to analyze. In this instance we can read in just the `deficit` attribute from the WSIM-GLDAS Composite Anomaly Twelve-Month Return Period file, rather than reading the entire NetCDF with all of its attributes.
::: column-margin
::: {.callout-tip style="color: #5a7a2b;"}
## Coding Review
Random Access Memory (RAM) is where data and programs that are currently in use are stored temporarily. It allows the computer to quickly access data, making everything you do on the computer faster and more efficient. Unlike the hard drive, which stores data permanently, RAM loses all its data when the computer is turned off. RAM is like a computer's short-term memory, helping it to handle multiple tasks at once.
:::
:::
For this exercise, we can quickly walk through similar pre-processing steps we performed earlier in this lesson and then move on to more advanced visualizations and integrations. Read the original 12-month integration data back in, filter with a list of dates for each December spanning 2000-2014, and then crop the raster data with the boundary of the contiguous United States using our geoBoundaries object.
```{python}
# read it back in
file_path = "data/composite_12mo.nc"
wsim_gldas = xr.open_dataset(file_path, engine = 'h5netcdf')
# list of dates we want to keep
keeps = pd.date_range(start="2000-12-01", end="2014-12-01", freq = "YS-DEC")
# subset for the dates
wsim_gldas = wsim_gldas.sel(time= keeps)
# subset for the variable of interest and the crs info
wsim_gldas = wsim_gldas[["deficit", "crs"]]
# give the time variable pretty names
wsim_gldas = wsim_gldas.assign_coords(time=list(range(2000,2015)))
# clip wsim_gldas
wsim_gldas = wsim_gldas.rio.write_crs("epsg: 4326")
wsim_gldas = wsim_gldas.rio.clip(usa.geometry.values)
```
Double check the object information.
```{python}
# check the basic information again
wsim_gldas
```
You will want to review the printout to make sure it looks okay.
- Does it contain the variables you were expecting?
- Do the values for the variables seem plausible?
Other basic descriptive analyses are useful to verify and understand your data. One of these is to produce a frequency distribution (also known as a histogram), which is reviewed below.
::: callout-note
## Knowledge Check
6. What are the two ways we reduced our memory footprint when we loaded the WSIM-GLDAS dataset for this lesson? (select all that apply)
a. Spatially subsetting the data to the CONUSA
b. Reading in only one year of data
c. Reading in only the attribute of interest (i.e., 'deficit')
d. All of the above.
:::
## Annual CONUSA Time Series
The basic data properties reviewed in the previous step are useful for exploratory data analysis, but we should perform further inspection. We can start our visual exploration of annual drought in the CONUSA by creating a map illustrating the deficit return period for each of the years in the WSIM-GLDAS object.
```{python warning = FALSE, message = FALSE}
# check visuals
wsim_gldas.deficit.plot(x="lon", y="lat", col="time", col_wrap = 3, cmap = "Reds_r", aspect = 1, size =2, vmin = -60, vmax = 0, cbar_kwargs = {'orientation':'horizontal', 'shrink':0.6, 'label':'Deficit Anomaly'})
```
This visualization shows that there were several significant drought events (as indicated by dark red deficit return-period values) throughout 2000-2014. Significant drought events included the southeast in 2000, the southwest in 2002, the majority of the western 3rd in 2007, Texas-Oklahoma in 2011, Montana-Wyoming-Colorado in 2012, and the entirety of the California coast in 2014. The droughts of 2012 and 2011 are particularly severe and widespread with return periods greater than 50 years covering multiple states. Based on historical norms, we should only expect droughts this strong every 50-60 years!
::: callout-note
## Knowledge Check
7. The output maps of Annual Mean Deficit Anomalies for the CONUSA indicate that...
a. The most significant deficit in 2004 is located in the western United States.
b. The least significant deficit 2003 is located in the Midwest.
c. The most significant deficit in 2011 is located around Texas and neighboring states.
d. The least significant deficit in 2000 is located in the southeast.
:::
## Monthly Time Series
We can get a more detailed look at these drought events by using the 1-month composite WSIM-GLDAS dataset and cropping the data to a smaller spatial extent matching one of the events we've noted in the previous plot. Let's take a closer look at the 2014 California drought.
::: {.callout-tip style="color: #5a7a2b;"}
## Drought in the News
The California drought of 2012-2014 was the worst in 1,200 years [@WHOI2014]. This drought caused problems for homeowners, and even conflicts between farmers and wild salmon! Governor Jerry Brown declared a drought emergency and called on residents to reduce water intake by 20%. Water use went up by 8% in May of 2014 compared to 2013, in places like coastal California and Los Angeles. Due to the water shortages, the state voted to fine water-wasters up to \$500 dollars. The drought also affected residents differently based on economic status. For example, in El Dorado County, located in a rural area east of Sacramento, residents were taking bucket showers and rural residents reported wells, which they rely on for fresh water, were drying up. The federal government eventually announced a \$9.7 million emergency drought aid for those areas [@Sanders2014].
Additionally, there were thousands of adult salmon struggling to survive in the Klamath River in Northern California, where water was running low and warm due to the diversion of river flow into the Central Valley, an agricultural area that grows almond trees. Almonds are one of California's most important crops, with the state producing 80% of the world's almonds. However, salmon, which migrate upstream, could get a disease called gill rot, which flourishes in warm water and already killed tens of thousands of Chinook in 2002. This disease was spreading through the salmon population again due to this water allocation, affecting local Native American tribes that rely on the fish [@Bland2014].
:::
In order to limit the amount of computing memory required for the operation, we will first clear items from the in-memory workspace and then reload a smaller composite file, we'll start by removing the 12-month composite object.
```{python}
# remove the large wsim object from the environment
del wsim_gldas
```
Now let's load the composite 1-month file from SEDAC into the workspace. The attributes and dimensions will be the same as the 12-month integration so we'll skip ahead to directly loading in the deficit variable without performing a check on the structure using `proxy = TRUE`.
```{python}
# read in the 1 month wsim-gldas data
file_path = "data/composite_1mo.nc"
wsim_gldas_1mo = xr.open_dataset(file_path, engine = 'h5netcdf')
# check the basic info
wsim_gldas_1mo
```
Once again, we'll subset the time dimension for our period of interest. However, this time we want every month for 2014 so we can take a closer look at the California drought.
```{python}
# list of dates to keep
keeps = pd.date_range(start="2014-01-01", end="2014-12-01", freq = "MS")
# select just the dates
wsim_gldas_1mo = wsim_gldas_1mo.sel(time= keeps)
# keep just the deficit and crs info
wsim_gldas_1mo = wsim_gldas_1mo[["deficit", "crs"]]
# check the info
wsim_gldas_1mo
```
Now we have 12 rasters with monthly data for 2014. Let's zoom in on California and see how this drought progressed over the course of the year.
```{python warning = FALSE, message = FALSE}
# isolate only the california border
california = usa[usa["shapeName"].str.contains("California")]
# set the crs for rasterio; it doesn't pick it up from xarray on its own
wsim_gldas_1mo = wsim_gldas_1mo.rio.write_crs("epsg: 4326")
# clip/crop the wsim raster
wsim_gldas_california = wsim_gldas_1mo.rio.clip(california.geometry.values)
import calendar
# give the time dimension pretty labels
wsim_gldas_california = wsim_gldas_california.assign_coords(time=list(calendar.month_name[1:]))
# plot it
wsim_gldas_california.deficit.plot(x="lon", y="lat", col="time", col_wrap = 3, cmap = "Reds_r", aspect = 0.9, size =2.5, vmin = -60, vmax = 0, cbar_kwargs = {'orientation':'vertical', 'shrink':0.6, 'label':'Deficit Anomaly'})
```
This series of maps shows a startling picture. California faced massive water deficits throughout the state in January and February. This was followed by water deficits in the western half of the state in May-August. Although northern and eastern California saw some relief by September, southwest California continued to see deficits through December.
## Zonal Summaries
To this point we've described the 2014 California drought by examining the state as a whole. Although we have a sense of what's happening in different cities or counties by looking at the maps, they do not provide quantitative summaries of local areas.
Zonal statistics are one way to summarize the cells of a raster layer that lie within the boundary of another data layer (which may be in either raster or vector format). For example, aggregating deficit return periods with another raster depicting land cover type or a vector boundary (shapefile) of countries, states, or counties, will produce descriptive statistics by that new layer. These statistics could include the sum, mean, median, standard deviation, and range.
For this section, we begin by calculating the mean deficit return period within California counties. First, we retrieve a vector dataset of California counties from the geoBoundaries API. Since geoBoundaries does not attribute which counties belong to which states, we utilize a spatial operation called intersect to select only those counties in California.
```{python}
# get the usa county boundaries
usa_counties = requests.get("https://www.geoboundaries.org/api/current/gbOpen/USA/ADM2/")
# parse the request for the data
usa_counties = usa_counties.json()
# download with the provided link
usa_counties = gp.read_file(usa_counties['gjDownloadURL'])
# intersect california state level with usa counties
california_counties = usa_counties.overlay(california, how='intersection')
# check the intersection
california_counties.plot()
```
The output of that intersection looks as expected. As noted above, in general a visual and/or tabular check on your data layers is always a good idea. If you expect 50 counties in a given state, you should see 50 counties resulting from your intersection of your two layers, etc. You may want to be on the look out for too few (such as an island area that may be in one layer but not the other) or too many counties (such as those that intersect with a neighboring state).
::: column-margin
::: {.callout-tip style="color: #5a7a2b;"}
## Coding Review
The [exactextractr](https://github.com/isciences/exactextractr) [@Baston2023] R package summarizes raster values over groupings, or zones, also known as zonal statistics. Zonal statistics help in assessing the statistical characteristics of a certain region.
:::
:::
We will perform our zonal statistics using the **exactextractr** package [@Baston2023]. It is the fastest, most accurate, and most flexible zonal statistics tool for the R programming language.
Now let's carry out the extraction and check the January output.
```{python warning=FALSE, message=FALSE}
from exactextract import exact_extract
# run the extraction
cc_summaries = exact_extract(wsim_gldas_california.deficit, california_counties, "mean", output = 'pandas', include_cols = "shapeName_1", include_geom = True)
# make the column names pretty
col_names = [["county"], calendar.month_name[1:], ["geometry"]]
col_names = sum(col_names, [])
cc_summaries.columns = col_names
```
**exactextractr** returns summary statistics in the same order of the input boundary file, therefore we can join the California county names to the **exactextract** summary statistics output for visualization. We can take a quick look at the first 10 counties to see their mean deficit return period for January-June.
```{python}
# check first 10 rows
cc_summaries[0:10]
```
As we expected after seeing the raw WSIM-GLDAS raster, there are significant widespread deficits. We can get a better visual by constructing a choropleth using the county vector boundaries.
::: callout-note
## Knowledge Check
8. What can zonal statistics be used for?
a. Subsetting data to a time period of interest.
b. Creating a time series.
c. Summarizing the values of cells that lie within a boundary.
d. All of the above.
:::
## County Choropleths
Now that we've inspected the raw data we can make a choropleth out of the mean deficit return period data. **geopandas** makes this
```{python warning=FALSE, message=FALSE}
import matplotlib.pyplot as plt
# setup the panels for the figures
fig, axs = plt.subplots(4,3,
figsize=(8,8),
facecolor='w',
sharex=True,
sharey=True)
# convert list of 2D axis positions into a 1d list of number 1-12
axs = axs.ravel()
# make the layout pretty/tight
fig.tight_layout()
# title and size
fig.suptitle('Monthly California Deficits for 2014', fontsize=14, y=1.05)
# loop through columns to make the plot for each month
for i, month in enumerate(cc_summaries.columns[1:13]):
axs[i].set_title(month, fontsize= 11)
cc_summaries.plot(column=month, ax=axs[i], cmap = "Reds_r")
california_counties.plot(ax=axs[i], edgecolor='black', color='none', linewidth=0.25)
# loop through again and turn off the axes for a cleaner map
for ax in axs:
ax.axis('off')
# assume it's the first (and only) mappable
patch_col = axs[0].collections[0]
# setup the colorbar/legend
cb = fig.colorbar(patch_col, ax=axs, shrink=0.5, label = "Deficit Anomaly")
```
Due to the widespread water deficits in the raw data, the mean values do not appear much different from the raw deficit raster layer, however, choropleth maps, also called thematic maps, can make it easier for users to survey the landscape by visualizing familiar places (like counties) that place themselves and their lived experiences alongside the data.
While this paints a striking picture of widespread water deficits, how many people are affected by this drought? Although the land area appears rather large, if one is not familiar with the distribution of population and urban centers in California it can be difficult to get a sense of the direct human impact. (This is partly because more populous locations are usually represented by smaller land areas and the less populous locations are usually represented by large administrative boundaries containing much more land area). Normalizing a given theme by land area may be something an analyst wants to do but we cover another approach below.
::: callout-note
## Knowledge Check
9. Choropleth maps, aka thematic maps, are useful for
a. Visualizing data in familiar geographies like counties or states
b. Finding directions from one place to another
c. Visualizing data in uniform geographic units like raster grid cells.
d. Calculating return periods.
:::
## Integrating Population Data
**Gridded Population of the World (GPW)** is a data collection from SEDAC that models the distribution of the global human population as counts and densities in a raster format [@CIESIN2018].We will take full advantage of **exactextractr** to integrate across WSIM-GLDAS, geoBoundaries, and GPW. To begin, we need to download the 15-minute resolution (roughly 30 square kilometer at the equator) population density data for the year 2015 from GPW. This version of GPW most closely matches our time period (2014) and the resolution of WSIM-GLDAS (0.25 degrees). Although in many applications one might choose to use GPW's population count data layers, because we are using **exactextractr** we can achieve more accurate results (especially along coastlines) by using population density in conjunction with land area estimates from the **exactextractr** package.
::: {.callout-tip style="color: #5a7a2b;"}
## Data Review
The Gridded Population of the World Version 4 is available in multiple target metrics (e.g. counts, density), periods (2000, 2005, 2010, 2015, 2020), and spatial resolutions (30 sec, 2.5 min, 15 min, 30 min, 60 min). Read more about GPW at the [collection home page on SEDAC](https://sedac.ciesin.columbia.edu/data/collection/gpw-v4). GPW is one of four global gridded population datasets available in raster format. These datasets vary in the degree to which they use additional information as ancillary variables to model the spatial distribution of the population from the administrative units (vector polygons) in which they originate. A review of these datasets and their underlying models is found in a paper by Leyk and colleagues [@leyk2019]. You can learn more about gridded population datasets at POPGRID.org. Fitness-for-use is an important principle in determining the best dataset to use for a specific analysis. The question we ask here is --- what is the population exposure to different levels of water deficit in California? --- uses spatially coarse inputs and is for a place with high-quality data inputs, GPW is a good choice for this analysis. Users with vector-format census data (at the county or sub-county level) could also adopt this approach for those data. In the case of California, the US Census data and GPW will produce nearly identical estimates because GPW is based on the census inputs.
:::
Load in the population count layer.
```{python}
# read in GPW with rioxarray
file_path = "data/gpw_v4_population_count_rev11_2015_15_min.tif"
# Open with rioxarray
gpw = rio.open_rasterio(file_path)
```
For this example we'll classify the WSIM-GLDAS deficit return period raster layer into eight categories. Binning the data will make it easier to manage the output and interpret the results.
```{python}
import numpy
# list the class breaks
wsim_bins = [numpy.inf, 0, -3, -5, -10, -20, -40, -60, numpy.NINF]
# classify the wsim layer with the established breaks
wsim_class = xr.apply_ufunc(
numpy.digitize,
wsim_gldas_1mo,
wsim_bins)
```
In our previous example, we used **exactextractr**'s built-in `'mean'` function, but we can also pass custom functions to **exactextractr** that will carry out several operations at once as well. The following code could be combined into a single function passed to **exactextractr**, but it is presented here as multiple functions in order to follow along more easily. You can read more about **exactextractr** arguments on the package [help guide](https://github.com/isciences/exactextract/blob/master/python/README.md). The key arguments to be aware of are the calls to:
1. `['coverage', 'values', 'weights']`: These are the 3 operations we're requesting be calculated. `coverage` calculates the corresponding area of the WSIM-GLDAS raster cell that is covered by the California boundary, `values` returns the value of the WSIM cell covered by the border, and `weights` returns the population count weight we supplied in the next argument.
2. `weights = gpw`: summarizes each WSIM-GLDAS cell's deficit return period with the corresponding population count value.
```{python}
# run the extraction
cal_wsim_gpw = exact_extract(
wsim_class.deficit,
california_counties,
['coverage', 'values', 'weights'],
output = 'pandas',
include_geom = False,
weights = gpw)
```
This returns a `DataFrame` with a row for every county in the `california_counties` layer we passed to `exact_extract`.
```{python}
# check the first few rows
cal_wsim_gpw[:6]
```
In addition to a row for each WSIM-GLDAS raster cell covered by the california boundary, there are 36 columns we need to decipher. Each column is prefixed by `band_<number>_`. The 12 bands represent the 12 months of WSIM-GLDAS data we passed. The 12 bands are replicated 3 times; resulting in 36 columns. Each set of 12 bands represent the 3 operations we requested summaries for (`['coverage', 'values', 'weights']`). To complicate things further, each cell contains a list with multiple values. This is because most counties overlap multiple WSIM-GLDAS cells. We need to disaggregate the nested lists of values before proceeding further.
```{python}
# create list of columns to unnest
explode_cols = list(cal_wsim_gpw.columns)
# unnest the column value lists
cal_wsim_gpw = cal_wsim_gpw.explode(explode_cols)
# check the results
cal_wsim_gpw[:10]
```
Now we have a single row for each unique WSIM-GLDAS/California County combination. The original row indices corresponding to the order of the counties in the `california_county` layer are replicated for the number of cells the county overlapped. In the first 10 rows we see that the first county (`0`) overlapped 9 WSIM-GLDAS cells (there are 9 rows with a 0 index).
We will need to perform a few more processing steps to prepare this `DataFrame` for a time series visualization integrating all of the data. First we'll replace the band prefixes with calendar months names. Then, we will use the `pd.melt` function to transform the data from wide format to long format in order to produce a visualization in **plotnine**.
There's not a simple way to perform pattern based melts in **pandas** so we'll perform these operations on each of the 3 operations (`['coverage', 'values', 'weights']`) separately and then bind them back together.
First the `coverage`.
```{python}
# select just columns with word "coverage" in them
cal_wsim_cov = cal_wsim_gpw.filter(like = 'coverage', axis = 1)
# rename them for months
cal_wsim_cov.columns = calendar.month_name[1:]
# melt them and create new columns; month and coverage
cal_wsim_cov= pd.melt(cal_wsim_cov, var_name='month', value_name= 'coverage')
```
Now `values`.
```{python}
# select just columns with word "coverage" in them
cal_wsim_val = cal_wsim_gpw.filter(like = 'values', axis = 1)
# rename them for months
cal_wsim_val.columns = calendar.month_name[1:]
# melt them and create new columns; month and wsim class
cal_wsim_val= pd.melt(cal_wsim_val, var_name='month', value_name = 'wsim_class')
```
Lastly `density`.
```{python}
# select just columns with word "coverage" in them
cal_wsim_weight = cal_wsim_gpw.filter(like = 'weight', axis = 1)
# rename them for months
cal_wsim_weight.columns = calendar.month_name[1:]
# melt them and create new columns; month and population count
cal_wsim_weight= pd.melt(cal_wsim_weight, var_name='month', value_name = 'cell_pop_count')
```
Put them back together. The rows are all in the same order as the counties and months so we don't have to perform a proper merge; just bind them back together.
```{python}
# concactenate them back together
cal_summaries = pd.concat(
[cal_wsim_cov, #the coverages with the county and month names
cal_wsim_val["wsim_class"], # just the class values
cal_wsim_weight["cell_pop_count"]], # just the pop count values
axis=1)
cal_summaries
```
Now we have a simplified `DataFrame` in long format where each row represents a unique county/month/WSIM cell combination. The first row details the the first county passed from `california_counties` (index 0), in the January WSIM-GLDAS layer, covering 0.000052 of a WSIM cell that was class 5 (defict between -20 and -40), which overlayed a GPW population count cell with 1,1717.64 people.
::: column-margin
::: {.callout-tip style="color: #5a7a2b;"}
## Coding Review
Converting data from wide to long or long to wide formats is a key component to data processing, however, it can be confusing. To read more about melting/pivoting longer (wide to long) and casting/pivoting wider (long to wide) check out the **pandas** vignette [How to Shape the Layout of Tables](https://pandas.pydata.org/docs/getting_started/intro_tutorials/07_reshape_table_layout.html).
:::
:::
We can estimate the number of people represented by each county/month/WSIM cell combination by multiplying the coverage fraction by the population count.
```{python}
# multiply
cal_summaries["wsim_class_pop"] = cal_summaries["coverage"]*cal_summaries["cell_pop_count"]
# round so we don't have fractions of people
cal_summaries.wsim_class_pop = cal_summaries['wsim_class_pop'].astype('float').round(0)
# check the values
cal_summaries[:5]
```
To estimate the number of people in each unique month/WSIM class combination we'll summarize by group with the `pd.groupby()` function.
```{python}
# group by month and class and reset the index
cal_summaries = cal_summaries.groupby(['month', 'wsim_class'])['wsim_class_pop'].sum().reset_index()
```
Ultimately we want to calculate the fraction of the population in each WSIM-GLDAS class so we need to get the total population to divide into the WSIM class population.
```{python}
# sum the population by month (will be the same for every month in a given year)
cal_summaries['month_pop'] = cal_summaries.groupby(['month'])['wsim_class_pop'].transform('sum')
# divide the class total by month sum to get the fraction
cal_summaries['wsim_class_frac'] = cal_summaries['wsim_class_pop'] / cal_summaries['month_pop']
# check the values
cal_summaries
```
Before plotting we'll make the month labels more legible for plotting, convert the WSIM-GLDAS return period classes into a categorical class, convert the month into an ordered categorical class, and set the WSIM-GLDAS class palette.
```{python}
# wsim class as category
cal_summaries['wsim_class'] = cal_summaries['wsim_class'].astype('category')
# give ordinal pretty labels
cal_summaries['wsim_class'] = cal_summaries['wsim_class'].cat.rename_categories(
{0: "0", 1: "-3", 2: "-5", 3: "-10", 4: "-20", 5: "-40", 6: "-50", 7: "-60"})
# same for the months
cal_summaries["month"] = pd.Categorical(cal_summaries["month"],
categories=["January", "February", "March", "April", "May", "June", "July",
"August", "September", "October", "November", "December"],
ordered=True)
# set our desired palette
leg_colors=['#9B0039',
# -50 to -40
'#D44135',
# -40 to -20
'#FF8D43',
# -20 to -10
'#FFC754',
# -10 to -5
'#FFEDA3',
# -5 to -3
'#fffdc7',
# -3 to 0
'#FFF4C7',
# 0-3
"#FFFFFF"]
```
Although **matplotlib** is the more "python" way to plot, we are going to use the python version of R's popular **ggplot2** package. It's a simpler code structure, and will keep synergy between the R and Python versions of this lesson.
```{python warning=FALSE}
from plotnine import *
# plot it
(ggplot(cal_summaries, aes('month', 'wsim_class_frac', fill = 'wsim_class', group='wsim_class'))+
scale_fill_manual(values = leg_colors[::-1])+
geom_bar(stat='identity', position='stack')+
labs(title = "Population Under Water Deficits in 2014 California Drought",
subtitle = "Categorized by Intensity of Deficit Return Period",
x = "",
y = "Fraction of Population*",
caption = "*Population derived from Gridded Population of the World (2015)",
fill = "Deficit Class")+
theme_minimal()+
theme(axis_text_x=element_text(rotation=25, hjust=1))
)
```
This figure really illustrates the human impact of the 2014 drought. Nearly 100% of the population was under a 60+ year deficit in January followed by 66% in May and approximately 40% for the remainder of the summer. That is a devastating drought!
::: callout-note
## Knowledge Review
1. There are several options for spatially subsetting (or clipping) a raster object to a region of interest. What method was used in this lesson?
a. Using a list of dates.
b. Using another raster object.
c. Specifying a bounding box.
d. Using a vector boundary dataset.
2. When running into memory issues, what is something you can do to reduce the computational load?
a. Work with one time frame or region at a time.
b. Save it as a new file.
c. Subset the data to a region of interest/time frame.
d. Find other data to work with.
3. What is the importance of subsetting data?
a. Freeing up space.
b. Analyzing a certain time or area of interest.
c. Making code run faster.
d. All of the above.
4. Gridded population datasets…(select all that apply)
a. Show where river tributaries are.
b. Model the distribution of the global human population in raster grid cells.
c. Allow analyses of the number of persons impacted by a hazard such as drought.
d. Vary in the extent to which ancillary data are used in their production.
:::
## In this Lesson, You Learned...
Congratulations! Now you should be able to:
- Navigate the SEDAC website to find and download datasets.\
- Access administrative boundaries from geoBoundaries data using API.
- Temporally subset a NetCDF raster stack using R packages such as dplyr and lubridate.
- Crop a NetCDF raster stack with a spatial boundary.
- Write a subsetted dataset to disk and create an image to share results.
- Identify areas of severe drought and select these areas for further analysis.
- Summarize data by county using the exactextractr tool.
- Integrate WSIM-GLDAS deficit, GPW population, and geoBoundaries administrative boundary data to create complex time series visualizations.
## Lesson 2
In this lesson we explored the California drought of 2014. In our next lesson, we will examine near real-time flood data in California using the MODIS data product.
[Lesson 2: Moderate Resolution Imaging Spectroradiometer (MODIS) Near-Real Time (NRT) flood data](https://ciesin-geospatial.github.io/TOPSTSCHOOL-water/m102-lance-modis-nrt-global-flood.html){.btn .btn-primary .btn role="button"}