In Part I of the book, we learned that our GeoTable representation of geospatial data provides the data access pattern of the DataFrame, a feature that is very convenient for data science. To recap, let’s consider the following geotable with four random variables:
N =10000a = [2randn(N÷2) .+6; randn(N÷2)]b = [3randn(N÷2); 2randn(N÷2)]c =randn(N)d = c .+0.6randn(N)table = (; a, b, c, d)gt =georef(table, CartesianGrid(100, 100))
10000×5 GeoTable over 100×100 CartesianGrid
a
b
c
d
geometry
Continuous
Continuous
Continuous
Continuous
Quadrangle
[NoUnits]
[NoUnits]
[NoUnits]
[NoUnits]
🖈 Cartesian{NoDatum}
5.34644
-4.56489
0.651825
1.00182
Quadrangle((x: 0.0 m, y: 0.0 m), ..., (x: 0.0 m, y: 1.0 m))
8.4421
-3.18679
-0.607636
-0.377739
Quadrangle((x: 1.0 m, y: 0.0 m), ..., (x: 1.0 m, y: 1.0 m))
6.28023
4.34089
-1.08599
-2.18776
Quadrangle((x: 2.0 m, y: 0.0 m), ..., (x: 2.0 m, y: 1.0 m))
4.93703
-2.37637
-1.51221
-2.1182
Quadrangle((x: 3.0 m, y: 0.0 m), ..., (x: 3.0 m, y: 1.0 m))
2.70852
-2.37348
-1.07627
-1.08518
Quadrangle((x: 4.0 m, y: 0.0 m), ..., (x: 4.0 m, y: 1.0 m))
6.80429
-1.94561
0.432787
0.254107
Quadrangle((x: 5.0 m, y: 0.0 m), ..., (x: 5.0 m, y: 1.0 m))
2.6952
-6.75328
0.122659
0.469774
Quadrangle((x: 6.0 m, y: 0.0 m), ..., (x: 6.0 m, y: 1.0 m))
4.91135
0.195679
-0.700238
-1.11035
Quadrangle((x: 7.0 m, y: 0.0 m), ..., (x: 7.0 m, y: 1.0 m))
9.01226
0.384668
-0.959113
-0.154578
Quadrangle((x: 8.0 m, y: 0.0 m), ..., (x: 8.0 m, y: 1.0 m))
7.16825
0.812532
0.856561
1.94897
Quadrangle((x: 9.0 m, y: 0.0 m), ..., (x: 9.0 m, y: 1.0 m))
⋮
⋮
⋮
⋮
⋮
We can easily retrieve the “a” column of the geotable as a vector, and plot its histogram:
Mke.hist(gt.a, color ="gray80")
┌ Warning: Found `resolution` in the theme when creating a `Scene`. The `resolution` keyword for `Scene`s and `Figure`s has been deprecated. Use `Figure(; size = ...` or `Scene(; size = ...)` instead, which better reflects that this is a unitless size and not a pixel resolution. The key could also come from `set_theme!` calls or related theming functions.
└ @ Makie ~/.julia/packages/Makie/We6MY/src/scenes.jl:227
We can compute the cross-correlation between columns “a” and “b”:
cor(gt.a, gt.b)
-0.003634614647021587
And inspect bivariate distributions of the values of the geotable with PairPlots.jl by Thompson (2023):
usingPairPlotspairplot(values(gt))
┌ Warning: Found `resolution` in the theme when creating a `Scene`. The `resolution` keyword for `Scene`s and `Figure`s has been deprecated. Use `Figure(; size = ...` or `Scene(; size = ...)` instead, which better reflects that this is a unitless size and not a pixel resolution. The key could also come from `set_theme!` calls or related theming functions.
└ @ Makie ~/.julia/packages/Makie/We6MY/src/scenes.jl:227
This pattern is useful to answer geoscientific questions via marginal analysis (i.e. entire columns treated as measurements of a single random variable). However, the answers to many questions in geosciences depend on where the measurements were made.
Attempting to answer geoscientific questions with basic access to rows and columns can be very frustrating. In particular, this approach is prone to unintentional removal of geospatial information:
Any script that is written in terms of direct column access has the potential to discard the special geometry column, and become unreadable very quickly with the use of auxiliary indices for rows.
We propose a new approach to geospatial data science with the concept of transforms, which we introduce in three classes with practical examples:
Feature transforms
Geometric transforms
Geospatial transforms
5.2 Feature transforms
A feature transform is a function that takes the values of the geotable and produces a new set of values over the same geospatial domain. The framework provides over 30 such transforms, ranging from basic selection of columns, to data cleaning, to advanced multivariate statistical transforms.
5.2.1 Basic
Let’s start with two basic and important transforms, Select and Reject. The Select transform can be used to select columns of interest from a geotable:
gt |>Select("a", "b") # select columns "a" and "b"
10000×3 GeoTable over 100×100 CartesianGrid
a
b
geometry
Continuous
Continuous
Quadrangle
[NoUnits]
[NoUnits]
🖈 Cartesian{NoDatum}
5.34644
-4.56489
Quadrangle((x: 0.0 m, y: 0.0 m), ..., (x: 0.0 m, y: 1.0 m))
8.4421
-3.18679
Quadrangle((x: 1.0 m, y: 0.0 m), ..., (x: 1.0 m, y: 1.0 m))
6.28023
4.34089
Quadrangle((x: 2.0 m, y: 0.0 m), ..., (x: 2.0 m, y: 1.0 m))
4.93703
-2.37637
Quadrangle((x: 3.0 m, y: 0.0 m), ..., (x: 3.0 m, y: 1.0 m))
2.70852
-2.37348
Quadrangle((x: 4.0 m, y: 0.0 m), ..., (x: 4.0 m, y: 1.0 m))
6.80429
-1.94561
Quadrangle((x: 5.0 m, y: 0.0 m), ..., (x: 5.0 m, y: 1.0 m))
2.6952
-6.75328
Quadrangle((x: 6.0 m, y: 0.0 m), ..., (x: 6.0 m, y: 1.0 m))
4.91135
0.195679
Quadrangle((x: 7.0 m, y: 0.0 m), ..., (x: 7.0 m, y: 1.0 m))
9.01226
0.384668
Quadrangle((x: 8.0 m, y: 0.0 m), ..., (x: 8.0 m, y: 1.0 m))
7.16825
0.812532
Quadrangle((x: 9.0 m, y: 0.0 m), ..., (x: 9.0 m, y: 1.0 m))
⋮
⋮
⋮
In the example above, we selected the columns “a” and “b” explicitly, but Select has various methods for more flexible column selection:
gt |>Select(1:3) # select columns 1 to 3
10000×4 GeoTable over 100×100 CartesianGrid
a
b
c
geometry
Continuous
Continuous
Continuous
Quadrangle
[NoUnits]
[NoUnits]
[NoUnits]
🖈 Cartesian{NoDatum}
5.34644
-4.56489
0.651825
Quadrangle((x: 0.0 m, y: 0.0 m), ..., (x: 0.0 m, y: 1.0 m))
8.4421
-3.18679
-0.607636
Quadrangle((x: 1.0 m, y: 0.0 m), ..., (x: 1.0 m, y: 1.0 m))
6.28023
4.34089
-1.08599
Quadrangle((x: 2.0 m, y: 0.0 m), ..., (x: 2.0 m, y: 1.0 m))
4.93703
-2.37637
-1.51221
Quadrangle((x: 3.0 m, y: 0.0 m), ..., (x: 3.0 m, y: 1.0 m))
2.70852
-2.37348
-1.07627
Quadrangle((x: 4.0 m, y: 0.0 m), ..., (x: 4.0 m, y: 1.0 m))
6.80429
-1.94561
0.432787
Quadrangle((x: 5.0 m, y: 0.0 m), ..., (x: 5.0 m, y: 1.0 m))
2.6952
-6.75328
0.122659
Quadrangle((x: 6.0 m, y: 0.0 m), ..., (x: 6.0 m, y: 1.0 m))
4.91135
0.195679
-0.700238
Quadrangle((x: 7.0 m, y: 0.0 m), ..., (x: 7.0 m, y: 1.0 m))
9.01226
0.384668
-0.959113
Quadrangle((x: 8.0 m, y: 0.0 m), ..., (x: 8.0 m, y: 1.0 m))
7.16825
0.812532
0.856561
Quadrangle((x: 9.0 m, y: 0.0 m), ..., (x: 9.0 m, y: 1.0 m))
Quadrangle((x: 0.0 m, y: 0.0 m), ..., (x: 0.0 m, y: 1.0 m))
-3.18679
-0.607636
-0.377739
Quadrangle((x: 1.0 m, y: 0.0 m), ..., (x: 1.0 m, y: 1.0 m))
4.34089
-1.08599
-2.18776
Quadrangle((x: 2.0 m, y: 0.0 m), ..., (x: 2.0 m, y: 1.0 m))
-2.37637
-1.51221
-2.1182
Quadrangle((x: 3.0 m, y: 0.0 m), ..., (x: 3.0 m, y: 1.0 m))
-2.37348
-1.07627
-1.08518
Quadrangle((x: 4.0 m, y: 0.0 m), ..., (x: 4.0 m, y: 1.0 m))
-1.94561
0.432787
0.254107
Quadrangle((x: 5.0 m, y: 0.0 m), ..., (x: 5.0 m, y: 1.0 m))
-6.75328
0.122659
0.469774
Quadrangle((x: 6.0 m, y: 0.0 m), ..., (x: 6.0 m, y: 1.0 m))
0.195679
-0.700238
-1.11035
Quadrangle((x: 7.0 m, y: 0.0 m), ..., (x: 7.0 m, y: 1.0 m))
0.384668
-0.959113
-0.154578
Quadrangle((x: 8.0 m, y: 0.0 m), ..., (x: 8.0 m, y: 1.0 m))
0.812532
0.856561
1.94897
Quadrangle((x: 9.0 m, y: 0.0 m), ..., (x: 9.0 m, y: 1.0 m))
⋮
⋮
⋮
⋮
A convenient method is also provided to select and rename columns:
gt |>Select("a"=>"A", "b"=>"B")
10000×3 GeoTable over 100×100 CartesianGrid
A
B
geometry
Continuous
Continuous
Quadrangle
[NoUnits]
[NoUnits]
🖈 Cartesian{NoDatum}
5.34644
-4.56489
Quadrangle((x: 0.0 m, y: 0.0 m), ..., (x: 0.0 m, y: 1.0 m))
8.4421
-3.18679
Quadrangle((x: 1.0 m, y: 0.0 m), ..., (x: 1.0 m, y: 1.0 m))
6.28023
4.34089
Quadrangle((x: 2.0 m, y: 0.0 m), ..., (x: 2.0 m, y: 1.0 m))
4.93703
-2.37637
Quadrangle((x: 3.0 m, y: 0.0 m), ..., (x: 3.0 m, y: 1.0 m))
2.70852
-2.37348
Quadrangle((x: 4.0 m, y: 0.0 m), ..., (x: 4.0 m, y: 1.0 m))
6.80429
-1.94561
Quadrangle((x: 5.0 m, y: 0.0 m), ..., (x: 5.0 m, y: 1.0 m))
2.6952
-6.75328
Quadrangle((x: 6.0 m, y: 0.0 m), ..., (x: 6.0 m, y: 1.0 m))
4.91135
0.195679
Quadrangle((x: 7.0 m, y: 0.0 m), ..., (x: 7.0 m, y: 1.0 m))
9.01226
0.384668
Quadrangle((x: 8.0 m, y: 0.0 m), ..., (x: 8.0 m, y: 1.0 m))
7.16825
0.812532
Quadrangle((x: 9.0 m, y: 0.0 m), ..., (x: 9.0 m, y: 1.0 m))
⋮
⋮
⋮
The Reject transform can be used to reject columns from a geotable that are not relevant for a given analysis. It supports the same column specification of Select:
gt |>Reject("b") # reject column "b"
10000×4 GeoTable over 100×100 CartesianGrid
a
c
d
geometry
Continuous
Continuous
Continuous
Quadrangle
[NoUnits]
[NoUnits]
[NoUnits]
🖈 Cartesian{NoDatum}
5.34644
0.651825
1.00182
Quadrangle((x: 0.0 m, y: 0.0 m), ..., (x: 0.0 m, y: 1.0 m))
8.4421
-0.607636
-0.377739
Quadrangle((x: 1.0 m, y: 0.0 m), ..., (x: 1.0 m, y: 1.0 m))
6.28023
-1.08599
-2.18776
Quadrangle((x: 2.0 m, y: 0.0 m), ..., (x: 2.0 m, y: 1.0 m))
4.93703
-1.51221
-2.1182
Quadrangle((x: 3.0 m, y: 0.0 m), ..., (x: 3.0 m, y: 1.0 m))
2.70852
-1.07627
-1.08518
Quadrangle((x: 4.0 m, y: 0.0 m), ..., (x: 4.0 m, y: 1.0 m))
6.80429
0.432787
0.254107
Quadrangle((x: 5.0 m, y: 0.0 m), ..., (x: 5.0 m, y: 1.0 m))
2.6952
0.122659
0.469774
Quadrangle((x: 6.0 m, y: 0.0 m), ..., (x: 6.0 m, y: 1.0 m))
4.91135
-0.700238
-1.11035
Quadrangle((x: 7.0 m, y: 0.0 m), ..., (x: 7.0 m, y: 1.0 m))
9.01226
-0.959113
-0.154578
Quadrangle((x: 8.0 m, y: 0.0 m), ..., (x: 8.0 m, y: 1.0 m))
7.16825
0.856561
1.94897
Quadrangle((x: 9.0 m, y: 0.0 m), ..., (x: 9.0 m, y: 1.0 m))
⋮
⋮
⋮
⋮
Note
Unlike direct column access, the Select and Reject transforms preserve geospatial information.
Tip for all users
The Select transform can be used in conjunction with the viewer to quickly visualize a specific variable:
gt |>Select("a") |> viewer
┌ Warning: Found `resolution` in the theme when creating a `Scene`. The `resolution` keyword for `Scene`s and `Figure`s has been deprecated. Use `Figure(; size = ...` or `Scene(; size = ...)` instead, which better reflects that this is a unitless size and not a pixel resolution. The key could also come from `set_theme!` calls or related theming functions.
└ @ Makie ~/.julia/packages/Makie/We6MY/src/scenes.jl:227
The Rename transform can be used to rename specific columns of a geotable. It preserves all other columns that are not part of the column specification:
gt |>Rename("a"=>"A", "b"=>"B")
10000×5 GeoTable over 100×100 CartesianGrid
A
B
c
d
geometry
Continuous
Continuous
Continuous
Continuous
Quadrangle
[NoUnits]
[NoUnits]
[NoUnits]
[NoUnits]
🖈 Cartesian{NoDatum}
5.34644
-4.56489
0.651825
1.00182
Quadrangle((x: 0.0 m, y: 0.0 m), ..., (x: 0.0 m, y: 1.0 m))
8.4421
-3.18679
-0.607636
-0.377739
Quadrangle((x: 1.0 m, y: 0.0 m), ..., (x: 1.0 m, y: 1.0 m))
6.28023
4.34089
-1.08599
-2.18776
Quadrangle((x: 2.0 m, y: 0.0 m), ..., (x: 2.0 m, y: 1.0 m))
4.93703
-2.37637
-1.51221
-2.1182
Quadrangle((x: 3.0 m, y: 0.0 m), ..., (x: 3.0 m, y: 1.0 m))
2.70852
-2.37348
-1.07627
-1.08518
Quadrangle((x: 4.0 m, y: 0.0 m), ..., (x: 4.0 m, y: 1.0 m))
6.80429
-1.94561
0.432787
0.254107
Quadrangle((x: 5.0 m, y: 0.0 m), ..., (x: 5.0 m, y: 1.0 m))
2.6952
-6.75328
0.122659
0.469774
Quadrangle((x: 6.0 m, y: 0.0 m), ..., (x: 6.0 m, y: 1.0 m))
4.91135
0.195679
-0.700238
-1.11035
Quadrangle((x: 7.0 m, y: 0.0 m), ..., (x: 7.0 m, y: 1.0 m))
9.01226
0.384668
-0.959113
-0.154578
Quadrangle((x: 8.0 m, y: 0.0 m), ..., (x: 8.0 m, y: 1.0 m))
7.16825
0.812532
0.856561
1.94897
Quadrangle((x: 9.0 m, y: 0.0 m), ..., (x: 9.0 m, y: 1.0 m))
⋮
⋮
⋮
⋮
⋮
The Identity transform can be used as a placeholder to forward the geotable without modifications to the next transform:
gt |>Identity()
10000×5 GeoTable over 100×100 CartesianGrid
a
b
c
d
geometry
Continuous
Continuous
Continuous
Continuous
Quadrangle
[NoUnits]
[NoUnits]
[NoUnits]
[NoUnits]
🖈 Cartesian{NoDatum}
5.34644
-4.56489
0.651825
1.00182
Quadrangle((x: 0.0 m, y: 0.0 m), ..., (x: 0.0 m, y: 1.0 m))
8.4421
-3.18679
-0.607636
-0.377739
Quadrangle((x: 1.0 m, y: 0.0 m), ..., (x: 1.0 m, y: 1.0 m))
6.28023
4.34089
-1.08599
-2.18776
Quadrangle((x: 2.0 m, y: 0.0 m), ..., (x: 2.0 m, y: 1.0 m))
4.93703
-2.37637
-1.51221
-2.1182
Quadrangle((x: 3.0 m, y: 0.0 m), ..., (x: 3.0 m, y: 1.0 m))
2.70852
-2.37348
-1.07627
-1.08518
Quadrangle((x: 4.0 m, y: 0.0 m), ..., (x: 4.0 m, y: 1.0 m))
6.80429
-1.94561
0.432787
0.254107
Quadrangle((x: 5.0 m, y: 0.0 m), ..., (x: 5.0 m, y: 1.0 m))
2.6952
-6.75328
0.122659
0.469774
Quadrangle((x: 6.0 m, y: 0.0 m), ..., (x: 6.0 m, y: 1.0 m))
4.91135
0.195679
-0.700238
-1.11035
Quadrangle((x: 7.0 m, y: 0.0 m), ..., (x: 7.0 m, y: 1.0 m))
9.01226
0.384668
-0.959113
-0.154578
Quadrangle((x: 8.0 m, y: 0.0 m), ..., (x: 8.0 m, y: 1.0 m))
7.16825
0.812532
0.856561
1.94897
Quadrangle((x: 9.0 m, y: 0.0 m), ..., (x: 9.0 m, y: 1.0 m))
⋮
⋮
⋮
⋮
⋮
The RowTable and ColTable transforms change the underlying table representation of the values of the geotable as discussed in the first chapter of the book:
rt = gt |>RowTable()
10000×5 GeoTable over 100×100 CartesianGrid
a
b
c
d
geometry
Continuous
Continuous
Continuous
Continuous
Quadrangle
[NoUnits]
[NoUnits]
[NoUnits]
[NoUnits]
🖈 Cartesian{NoDatum}
5.34644
-4.56489
0.651825
1.00182
Quadrangle((x: 0.0 m, y: 0.0 m), ..., (x: 0.0 m, y: 1.0 m))
8.4421
-3.18679
-0.607636
-0.377739
Quadrangle((x: 1.0 m, y: 0.0 m), ..., (x: 1.0 m, y: 1.0 m))
6.28023
4.34089
-1.08599
-2.18776
Quadrangle((x: 2.0 m, y: 0.0 m), ..., (x: 2.0 m, y: 1.0 m))
4.93703
-2.37637
-1.51221
-2.1182
Quadrangle((x: 3.0 m, y: 0.0 m), ..., (x: 3.0 m, y: 1.0 m))
2.70852
-2.37348
-1.07627
-1.08518
Quadrangle((x: 4.0 m, y: 0.0 m), ..., (x: 4.0 m, y: 1.0 m))
6.80429
-1.94561
0.432787
0.254107
Quadrangle((x: 5.0 m, y: 0.0 m), ..., (x: 5.0 m, y: 1.0 m))
2.6952
-6.75328
0.122659
0.469774
Quadrangle((x: 6.0 m, y: 0.0 m), ..., (x: 6.0 m, y: 1.0 m))
4.91135
0.195679
-0.700238
-1.11035
Quadrangle((x: 7.0 m, y: 0.0 m), ..., (x: 7.0 m, y: 1.0 m))
9.01226
0.384668
-0.959113
-0.154578
Quadrangle((x: 8.0 m, y: 0.0 m), ..., (x: 8.0 m, y: 1.0 m))
7.16825
0.812532
0.856561
1.94897
Quadrangle((x: 9.0 m, y: 0.0 m), ..., (x: 9.0 m, y: 1.0 m))
The Functional transform can be used to apply a function to columns of a geotable in place:
gt |>Functional(cos) |> values |> pairplot
┌ Warning: Found `resolution` in the theme when creating a `Scene`. The `resolution` keyword for `Scene`s and `Figure`s has been deprecated. Use `Figure(; size = ...` or `Scene(; size = ...)` instead, which better reflects that this is a unitless size and not a pixel resolution. The key could also come from `set_theme!` calls or related theming functions.
└ @ Makie ~/.julia/packages/Makie/We6MY/src/scenes.jl:227
┌ Warning: Found `resolution` in the theme when creating a `Scene`. The `resolution` keyword for `Scene`s and `Figure`s has been deprecated. Use `Figure(; size = ...` or `Scene(; size = ...)` instead, which better reflects that this is a unitless size and not a pixel resolution. The key could also come from `set_theme!` calls or related theming functions.
└ @ Makie ~/.julia/packages/Makie/We6MY/src/scenes.jl:227
The Map transform can be used to create new columns from existing columns in the geotable. It takes a column specification, calls a function on the selected columns row-by-row, and returns the result as a new column:
gt |>Map("a"=> sin, "b"=> cos =>"cos(b)")
10000×7 GeoTable over 100×100 CartesianGrid
a
b
c
d
sin_a
cos(b)
geometry
Continuous
Continuous
Continuous
Continuous
Continuous
Continuous
Quadrangle
[NoUnits]
[NoUnits]
[NoUnits]
[NoUnits]
[NoUnits]
[NoUnits]
🖈 Cartesian{NoDatum}
5.34644
-4.56489
0.651825
1.00182
-0.805635
-0.146969
Quadrangle((x: 0.0 m, y: 0.0 m), ..., (x: 0.0 m, y: 1.0 m))
8.4421
-3.18679
-0.607636
-0.377739
0.831987
-0.998979
Quadrangle((x: 1.0 m, y: 0.0 m), ..., (x: 1.0 m, y: 1.0 m))
6.28023
4.34089
-1.08599
-2.18776
-0.00295416
-0.36301
Quadrangle((x: 2.0 m, y: 0.0 m), ..., (x: 2.0 m, y: 1.0 m))
4.93703
-2.37637
-1.51221
-2.1182
-0.974874
-0.721225
Quadrangle((x: 3.0 m, y: 0.0 m), ..., (x: 3.0 m, y: 1.0 m))
2.70852
-2.37348
-1.07627
-1.08518
0.419657
-0.719222
Quadrangle((x: 4.0 m, y: 0.0 m), ..., (x: 4.0 m, y: 1.0 m))
6.80429
-1.94561
0.432787
0.254107
0.497837
-0.366101
Quadrangle((x: 5.0 m, y: 0.0 m), ..., (x: 5.0 m, y: 1.0 m))
2.6952
-6.75328
0.122659
0.469774
0.431715
0.891526
Quadrangle((x: 6.0 m, y: 0.0 m), ..., (x: 6.0 m, y: 1.0 m))
4.91135
0.195679
-0.700238
-1.11035
-0.980272
0.980916
Quadrangle((x: 7.0 m, y: 0.0 m), ..., (x: 7.0 m, y: 1.0 m))
9.01226
0.384668
-0.959113
-0.154578
0.400913
0.926923
Quadrangle((x: 8.0 m, y: 0.0 m), ..., (x: 8.0 m, y: 1.0 m))
7.16825
0.812532
0.856561
1.94897
0.773957
0.687663
Quadrangle((x: 9.0 m, y: 0.0 m), ..., (x: 9.0 m, y: 1.0 m))
⋮
⋮
⋮
⋮
⋮
⋮
⋮
gt |>Map([2, 3] => ((b, c) ->2b + c) =>"f(b, c)")
10000×6 GeoTable over 100×100 CartesianGrid
a
b
c
d
f(b, c)
geometry
Continuous
Continuous
Continuous
Continuous
Continuous
Quadrangle
[NoUnits]
[NoUnits]
[NoUnits]
[NoUnits]
[NoUnits]
🖈 Cartesian{NoDatum}
5.34644
-4.56489
0.651825
1.00182
-8.47795
Quadrangle((x: 0.0 m, y: 0.0 m), ..., (x: 0.0 m, y: 1.0 m))
8.4421
-3.18679
-0.607636
-0.377739
-6.98122
Quadrangle((x: 1.0 m, y: 0.0 m), ..., (x: 1.0 m, y: 1.0 m))
6.28023
4.34089
-1.08599
-2.18776
7.5958
Quadrangle((x: 2.0 m, y: 0.0 m), ..., (x: 2.0 m, y: 1.0 m))
4.93703
-2.37637
-1.51221
-2.1182
-6.26495
Quadrangle((x: 3.0 m, y: 0.0 m), ..., (x: 3.0 m, y: 1.0 m))
2.70852
-2.37348
-1.07627
-1.08518
-5.82323
Quadrangle((x: 4.0 m, y: 0.0 m), ..., (x: 4.0 m, y: 1.0 m))
6.80429
-1.94561
0.432787
0.254107
-3.45844
Quadrangle((x: 5.0 m, y: 0.0 m), ..., (x: 5.0 m, y: 1.0 m))
2.6952
-6.75328
0.122659
0.469774
-13.3839
Quadrangle((x: 6.0 m, y: 0.0 m), ..., (x: 6.0 m, y: 1.0 m))
4.91135
0.195679
-0.700238
-1.11035
-0.30888
Quadrangle((x: 7.0 m, y: 0.0 m), ..., (x: 7.0 m, y: 1.0 m))
9.01226
0.384668
-0.959113
-0.154578
-0.189777
Quadrangle((x: 8.0 m, y: 0.0 m), ..., (x: 8.0 m, y: 1.0 m))
7.16825
0.812532
0.856561
1.94897
2.48162
Quadrangle((x: 9.0 m, y: 0.0 m), ..., (x: 9.0 m, y: 1.0 m))
⋮
⋮
⋮
⋮
⋮
⋮
The name of the resulting column can be provided or omitted. If the name is omitted like in the example above with the column “a”, it is created by concatenation of column and function names.
Note
The Map transform mimics the behavior of the transform function in DataFrames.jl, except that it always broadcasts the functions to the rows of the selected columns and always produces a single column for each function.
To filter rows in the geotable based on a given predicate (i.e., a function that returns true or false), we can use the Filter transform:
Quadrangle((x: 95.0 m, y: 40.0 m), ..., (x: 95.0 m, y: 41.0 m))
12.2622
-7.06497
1.90979
1.80014
Quadrangle((x: 99.0 m, y: 46.0 m), ..., (x: 99.0 m, y: 47.0 m))
11.7581
-0.889193
1.05054
1.12464
Quadrangle((x: 54.0 m, y: 19.0 m), ..., (x: 54.0 m, y: 20.0 m))
11.7558
3.34142
-0.880079
-0.967804
Quadrangle((x: 32.0 m, y: 11.0 m), ..., (x: 32.0 m, y: 12.0 m))
11.5805
-1.02659
0.809095
-0.641355
Quadrangle((x: 42.0 m, y: 35.0 m), ..., (x: 42.0 m, y: 36.0 m))
11.5773
-2.75985
-0.824167
-0.825913
Quadrangle((x: 23.0 m, y: 2.0 m), ..., (x: 23.0 m, y: 3.0 m))
11.568
-0.75467
-1.44538
-1.82733
Quadrangle((x: 60.0 m, y: 38.0 m), ..., (x: 60.0 m, y: 39.0 m))
11.531
4.08359
-0.158821
-0.428526
Quadrangle((x: 97.0 m, y: 25.0 m), ..., (x: 97.0 m, y: 26.0 m))
11.5118
0.239354
0.490768
0.521445
Quadrangle((x: 25.0 m, y: 9.0 m), ..., (x: 25.0 m, y: 10.0 m))
11.5032
-1.25125
-0.0528816
0.460566
Quadrangle((x: 12.0 m, y: 31.0 m), ..., (x: 12.0 m, y: 32.0 m))
⋮
⋮
⋮
⋮
⋮
5.2.2 Cleaning
Some feature transforms are used to clean the data before geostatistical analysis. For example, the StdNames transform can be used to standardize variable names that are not very readable due to file format limitations. To illustrate this transform, let’s create a geotable with unreadable variable names:
ut = gt |>Select("a"=>"aBc De-F", "b"=>"b_2 (1)")
10000×3 GeoTable over 100×100 CartesianGrid
aBc De-F
b_2 (1)
geometry
Continuous
Continuous
Quadrangle
[NoUnits]
[NoUnits]
🖈 Cartesian{NoDatum}
5.34644
-4.56489
Quadrangle((x: 0.0 m, y: 0.0 m), ..., (x: 0.0 m, y: 1.0 m))
8.4421
-3.18679
Quadrangle((x: 1.0 m, y: 0.0 m), ..., (x: 1.0 m, y: 1.0 m))
6.28023
4.34089
Quadrangle((x: 2.0 m, y: 0.0 m), ..., (x: 2.0 m, y: 1.0 m))
4.93703
-2.37637
Quadrangle((x: 3.0 m, y: 0.0 m), ..., (x: 3.0 m, y: 1.0 m))
2.70852
-2.37348
Quadrangle((x: 4.0 m, y: 0.0 m), ..., (x: 4.0 m, y: 1.0 m))
6.80429
-1.94561
Quadrangle((x: 5.0 m, y: 0.0 m), ..., (x: 5.0 m, y: 1.0 m))
2.6952
-6.75328
Quadrangle((x: 6.0 m, y: 0.0 m), ..., (x: 6.0 m, y: 1.0 m))
4.91135
0.195679
Quadrangle((x: 7.0 m, y: 0.0 m), ..., (x: 7.0 m, y: 1.0 m))
9.01226
0.384668
Quadrangle((x: 8.0 m, y: 0.0 m), ..., (x: 8.0 m, y: 1.0 m))
7.16825
0.812532
Quadrangle((x: 9.0 m, y: 0.0 m), ..., (x: 9.0 m, y: 1.0 m))
⋮
⋮
⋮
We can standardize the names with:
ut |>StdNames()
10000×3 GeoTable over 100×100 CartesianGrid
ABC_DE_F
B_2_1
geometry
Continuous
Continuous
Quadrangle
[NoUnits]
[NoUnits]
🖈 Cartesian{NoDatum}
5.34644
-4.56489
Quadrangle((x: 0.0 m, y: 0.0 m), ..., (x: 0.0 m, y: 1.0 m))
8.4421
-3.18679
Quadrangle((x: 1.0 m, y: 0.0 m), ..., (x: 1.0 m, y: 1.0 m))
6.28023
4.34089
Quadrangle((x: 2.0 m, y: 0.0 m), ..., (x: 2.0 m, y: 1.0 m))
4.93703
-2.37637
Quadrangle((x: 3.0 m, y: 0.0 m), ..., (x: 3.0 m, y: 1.0 m))
2.70852
-2.37348
Quadrangle((x: 4.0 m, y: 0.0 m), ..., (x: 4.0 m, y: 1.0 m))
6.80429
-1.94561
Quadrangle((x: 5.0 m, y: 0.0 m), ..., (x: 5.0 m, y: 1.0 m))
2.6952
-6.75328
Quadrangle((x: 6.0 m, y: 0.0 m), ..., (x: 6.0 m, y: 1.0 m))
4.91135
0.195679
Quadrangle((x: 7.0 m, y: 0.0 m), ..., (x: 7.0 m, y: 1.0 m))
9.01226
0.384668
Quadrangle((x: 8.0 m, y: 0.0 m), ..., (x: 8.0 m, y: 1.0 m))
7.16825
0.812532
Quadrangle((x: 9.0 m, y: 0.0 m), ..., (x: 9.0 m, y: 1.0 m))
⋮
⋮
⋮
By default the transform, uses the :uppersnake naming convention. Other conventions can be specified depending on personal preference:
ut |>StdNames(:uppercamel)
10000×3 GeoTable over 100×100 CartesianGrid
AbcDeF
B21
geometry
Continuous
Continuous
Quadrangle
[NoUnits]
[NoUnits]
🖈 Cartesian{NoDatum}
5.34644
-4.56489
Quadrangle((x: 0.0 m, y: 0.0 m), ..., (x: 0.0 m, y: 1.0 m))
8.4421
-3.18679
Quadrangle((x: 1.0 m, y: 0.0 m), ..., (x: 1.0 m, y: 1.0 m))
6.28023
4.34089
Quadrangle((x: 2.0 m, y: 0.0 m), ..., (x: 2.0 m, y: 1.0 m))
4.93703
-2.37637
Quadrangle((x: 3.0 m, y: 0.0 m), ..., (x: 3.0 m, y: 1.0 m))
2.70852
-2.37348
Quadrangle((x: 4.0 m, y: 0.0 m), ..., (x: 4.0 m, y: 1.0 m))
6.80429
-1.94561
Quadrangle((x: 5.0 m, y: 0.0 m), ..., (x: 5.0 m, y: 1.0 m))
2.6952
-6.75328
Quadrangle((x: 6.0 m, y: 0.0 m), ..., (x: 6.0 m, y: 1.0 m))
4.91135
0.195679
Quadrangle((x: 7.0 m, y: 0.0 m), ..., (x: 7.0 m, y: 1.0 m))
9.01226
0.384668
Quadrangle((x: 8.0 m, y: 0.0 m), ..., (x: 8.0 m, y: 1.0 m))
7.16825
0.812532
Quadrangle((x: 9.0 m, y: 0.0 m), ..., (x: 9.0 m, y: 1.0 m))
⋮
⋮
⋮
ut |>StdNames(:upperflat)
10000×3 GeoTable over 100×100 CartesianGrid
ABCDEF
B21
geometry
Continuous
Continuous
Quadrangle
[NoUnits]
[NoUnits]
🖈 Cartesian{NoDatum}
5.34644
-4.56489
Quadrangle((x: 0.0 m, y: 0.0 m), ..., (x: 0.0 m, y: 1.0 m))
8.4421
-3.18679
Quadrangle((x: 1.0 m, y: 0.0 m), ..., (x: 1.0 m, y: 1.0 m))
6.28023
4.34089
Quadrangle((x: 2.0 m, y: 0.0 m), ..., (x: 2.0 m, y: 1.0 m))
4.93703
-2.37637
Quadrangle((x: 3.0 m, y: 0.0 m), ..., (x: 3.0 m, y: 1.0 m))
2.70852
-2.37348
Quadrangle((x: 4.0 m, y: 0.0 m), ..., (x: 4.0 m, y: 1.0 m))
6.80429
-1.94561
Quadrangle((x: 5.0 m, y: 0.0 m), ..., (x: 5.0 m, y: 1.0 m))
2.6952
-6.75328
Quadrangle((x: 6.0 m, y: 0.0 m), ..., (x: 6.0 m, y: 1.0 m))
4.91135
0.195679
Quadrangle((x: 7.0 m, y: 0.0 m), ..., (x: 7.0 m, y: 1.0 m))
9.01226
0.384668
Quadrangle((x: 8.0 m, y: 0.0 m), ..., (x: 8.0 m, y: 1.0 m))
7.16825
0.812532
Quadrangle((x: 9.0 m, y: 0.0 m), ..., (x: 9.0 m, y: 1.0 m))
⋮
⋮
⋮
The Replace transform can be used to replace specific values in the geotable by new values that are meaningful to the analysis. For example, we can replace the values -999 and NaN that are used to represent missing values in some file formats:
rt =georef((a=[1,-999,3], b=[NaN,5,6]))
3×3 GeoTable over 3 CartesianGrid
a
b
geometry
Categorical
Continuous
Segment
[NoUnits]
[NoUnits]
🖈 Cartesian{NoDatum}
1
NaN
Segment((x: 0.0 m), (x: 1.0 m))
-999
5.0
Segment((x: 1.0 m), (x: 2.0 m))
3
6.0
Segment((x: 2.0 m), (x: 3.0 m))
rt |>Replace(-999=>missing, NaN=>missing)
3×3 GeoTable over 3 CartesianGrid
a
b
geometry
Categorical
Continuous
Segment
[NoUnits]
[NoUnits]
🖈 Cartesian{NoDatum}
1
missing
Segment((x: 0.0 m), (x: 1.0 m))
missing
5.0
Segment((x: 1.0 m), (x: 2.0 m))
3
6.0
Segment((x: 2.0 m), (x: 3.0 m))
or replace all negative values using a predicate function:
rt |>Replace(<(0) =>missing)
3×3 GeoTable over 3 CartesianGrid
a
b
geometry
Categorical
Continuous
Segment
[NoUnits]
[NoUnits]
🖈 Cartesian{NoDatum}
1
NaN
Segment((x: 0.0 m), (x: 1.0 m))
missing
5.0
Segment((x: 1.0 m), (x: 2.0 m))
3
6.0
Segment((x: 2.0 m), (x: 3.0 m))
Note
In Julia, the expression <(0) is equivalent to the predicate function x -> x < 0.
Although Replace could be used to replace missing values by new values, there is a specific transform for this purpose named Coalesce:
Unlike Replace, the Coalesce transform also changes the column type to make sure that no missing values can be stored in the future:
typeof(ct.a)
Vector{Int64} (alias for Array{Int64, 1})
In many applications, it is enough to simply drop all rows for which the selected column values are missing. This is the purpose of the DropMissing transform:
The DropNaN is an alternative to drop all rows for which the selected column values are NaN.
5.2.3 Statistical
The framework provides various feature transforms for statistical analysis. We will cover some of these transforms in more detail in Part V of the book with real data. In the following examples we illustrate the most basic statistical transforms with synthetic data.
The Sample transform can be used to sample rows of the geotable at random, with or without replacement depending on the replace option. Other options are available such as rng to set the random number generator and ordered to preserve the order of rows in the original geotable:
gt |>Sample(1000, replace=false) |> viewer
┌ Warning: Found `resolution` in the theme when creating a `Scene`. The `resolution` keyword for `Scene`s and `Figure`s has been deprecated. Use `Figure(; size = ...` or `Scene(; size = ...)` instead, which better reflects that this is a unitless size and not a pixel resolution. The key could also come from `set_theme!` calls or related theming functions.
└ @ Makie ~/.julia/packages/Makie/We6MY/src/scenes.jl:227
Note
Similar to Filter and Sort, the Sample transform is lazy. It simply stores the indices of sampled rows for future construction of the new geotable.
The Center and Scale transforms can be used to standardize the range of values in a geotable. Aliases are provided for specific types of Scale such as MinMax and Interquartile. We can use the describe function to visualize basic statistics before and after the transforms:
gt |> describe
Table with 6 columns and 4 rows:
variable mean minimum median maximum nmissing
┌───────────────────────────────────────────────────────────────
1 │ a 2.99029 -3.36844 2.01773 16.3513 0
2 │ b -0.0221687 -10.6788 -0.0217469 10.8266 0
3 │ c -0.00178608 -4.58574 0.00165673 4.07011 0
4 │ d -0.00684002 -4.60128 -0.0149594 4.18453 0
gt |>Center("a") |> describe
Table with 6 columns and 4 rows:
variable mean minimum median maximum nmissing
┌────────────────────────────────────────────────────────────────
1 │ a -3.63798e-16 -6.35873 -0.97256 13.361 0
2 │ b -0.0221687 -10.6788 -0.0217469 10.8266 0
3 │ c -0.00178608 -4.58574 0.00165673 4.07011 0
4 │ d -0.00684002 -4.60128 -0.0149594 4.18453 0
gt |>MinMax() |> describe
Table with 6 columns and 4 rows:
variable mean minimum median maximum nmissing
┌─────────────────────────────────────────────────────────
1 │ a 0.322455 0.0 0.273136 1.0 0
2 │ b 0.495532 0.0 0.495552 1.0 0
3 │ c 0.529579 0.0 0.529977 1.0 0
4 │ d 0.522939 0.0 0.522015 1.0 0
The ZScore transform is similar to the Scale transform, but it uses the mean and the standard deviation to standardize the range:
gt |>ZScore() |> describe
Table with 6 columns and 4 rows:
variable mean minimum median maximum nmissing
┌─────────────────────────────────────────────────────────────────
1 │ a 9.09495e-17 -1.88552 -0.288388 3.96187 0
2 │ b -5.68434e-18 -4.15672 0.000164519 4.23168 0
3 │ c -4.26326e-18 -4.59057 0.00344778 4.07777 0
4 │ d -7.28306e-18 -3.9461 -0.00697361 3.59991 0
Another important univariate transform is the Quantile transform, which can be used to convert empirical distribution in a column of the geotable to any given distribution from Distributions.jl by Lin et al. (2023). Selected columns are converted to a Normal distribution by default, but more than 60 distributions are available:
gt |>Quantile() |> values |> pairplot
┌ Warning: Found `resolution` in the theme when creating a `Scene`. The `resolution` keyword for `Scene`s and `Figure`s has been deprecated. Use `Figure(; size = ...` or `Scene(; size = ...)` instead, which better reflects that this is a unitless size and not a pixel resolution. The key could also come from `set_theme!` calls or related theming functions.
└ @ Makie ~/.julia/packages/Makie/We6MY/src/scenes.jl:227
In data science, scientific traits are used to link data types to adequate statistical algorithms. The most popular scientific traits encountered in geoscientific applications are the Continuous and the Categorical scientific traits. To convert (or coerce) the scientific traits of columns in a geotable, we can use the Coerce transform:
st =georef((a=[1,2,2,2,3,3], b=[1,2,3,4,5,6])) |>Coerce("b"=> Continuous)
6×3 GeoTable over 6 CartesianGrid
a
b
geometry
Categorical
Continuous
Segment
[NoUnits]
[NoUnits]
🖈 Cartesian{NoDatum}
1
1.0
Segment((x: 0.0 m), (x: 1.0 m))
2
2.0
Segment((x: 1.0 m), (x: 2.0 m))
2
3.0
Segment((x: 2.0 m), (x: 3.0 m))
2
4.0
Segment((x: 3.0 m), (x: 4.0 m))
3
5.0
Segment((x: 4.0 m), (x: 5.0 m))
3
6.0
Segment((x: 5.0 m), (x: 6.0 m))
eltype(st.b)
Float64
Note
All scientific traits are documented in the DataScienceTraits.jl module, and can be used to select variables:
st |>Only(Continuous)
6×2 GeoTable over 6 CartesianGrid
b
geometry
Continuous
Segment
[NoUnits]
🖈 Cartesian{NoDatum}
1.0
Segment((x: 0.0 m), (x: 1.0 m))
2.0
Segment((x: 1.0 m), (x: 2.0 m))
3.0
Segment((x: 2.0 m), (x: 3.0 m))
4.0
Segment((x: 3.0 m), (x: 4.0 m))
5.0
Segment((x: 4.0 m), (x: 5.0 m))
6.0
Segment((x: 5.0 m), (x: 6.0 m))
The Levels transform can be used to adjust the categories (or levels) of Categorical columns in case the sampling process does not include all possible values:
st = st |>Levels("a"=> [1,2,3,4])
6×3 GeoTable over 6 CartesianGrid
a
b
geometry
Categorical
Continuous
Segment
[NoUnits]
[NoUnits]
🖈 Cartesian{NoDatum}
1
1.0
Segment((x: 0.0 m), (x: 1.0 m))
2
2.0
Segment((x: 1.0 m), (x: 2.0 m))
2
3.0
Segment((x: 2.0 m), (x: 3.0 m))
2
4.0
Segment((x: 3.0 m), (x: 4.0 m))
3
5.0
Segment((x: 4.0 m), (x: 5.0 m))
3
6.0
Segment((x: 5.0 m), (x: 6.0 m))
levels(st.a)
4-element Vector{Int64}:
1
2
3
4
Another popular transform in statistical learning is the OneHot transform. It converts a Categorical column into multiple columns of true/false values, one column for each level:
st |>OneHot("a")
6×6 GeoTable over 6 CartesianGrid
a_1
a_2
a_3
a_4
b
geometry
Categorical
Categorical
Categorical
Categorical
Continuous
Segment
[NoUnits]
[NoUnits]
[NoUnits]
[NoUnits]
[NoUnits]
🖈 Cartesian{NoDatum}
true
false
false
false
1.0
Segment((x: 0.0 m), (x: 1.0 m))
false
true
false
false
2.0
Segment((x: 1.0 m), (x: 2.0 m))
false
true
false
false
3.0
Segment((x: 2.0 m), (x: 3.0 m))
false
true
false
false
4.0
Segment((x: 3.0 m), (x: 4.0 m))
false
false
true
false
5.0
Segment((x: 4.0 m), (x: 5.0 m))
false
false
true
false
6.0
Segment((x: 5.0 m), (x: 6.0 m))
A similar transform for Continuous columns is the Indicator transform. It converts the column into multiple columns based on threshold values on the support of the data. By default, the threshold values are computed on a quantile scale:
st |>Indicator("b", k=3, scale=:quantile)
6×5 GeoTable over 6 CartesianGrid
a
b_1
b_2
b_3
geometry
Categorical
Categorical
Categorical
Categorical
Segment
[NoUnits]
[NoUnits]
[NoUnits]
[NoUnits]
🖈 Cartesian{NoDatum}
1
true
true
true
Segment((x: 0.0 m), (x: 1.0 m))
2
true
true
true
Segment((x: 1.0 m), (x: 2.0 m))
2
false
true
true
Segment((x: 2.0 m), (x: 3.0 m))
2
false
true
true
Segment((x: 3.0 m), (x: 4.0 m))
3
false
false
true
Segment((x: 4.0 m), (x: 5.0 m))
3
false
false
true
Segment((x: 5.0 m), (x: 6.0 m))
More advanced statistical transforms such as EigenAnalysis, PCA, DRS, SDS, ProjectionPursuit for multivariate data analysis and Remainder, Closure, LogRatio, ALR, CLR, ILR for compositional data analysis will be covered in future chapters.
5.3 Geometric transforms
While feature transforms operate on the values of the geotable, geometric transforms operate on the geospatial domain. The framework provides various geometric transforms for 2D and 3D space.
5.3.1 Coordinate
A coordinate transform is a geometric transform that modifies the coordinates of all points in the domain without any advanced topological modification (i.e., connectivities are preserved). The most prominent examples of coordinate transforms are Translate, Rotate and Scale.
Let’s load an additional geotable to see these transforms in action:
┌ Warning: Found `resolution` in the theme when creating a `Scene`. The `resolution` keyword for `Scene`s and `Figure`s has been deprecated. Use `Figure(; size = ...` or `Scene(; size = ...)` instead, which better reflects that this is a unitless size and not a pixel resolution. The key could also come from `set_theme!` calls or related theming functions.
└ @ Makie ~/.julia/packages/Makie/We6MY/src/scenes.jl:227
The Beethoven domain has been saved in the .ply file in a position that is not ideal for visualization. We can rotate this domain with any active rotation specification from Rotations.jl by Koolen et al. (2023) to improve the visualization. For example, we can specify that we want to rotate all points in the mesh by analogy with a rotation between coordinates (0, 1, 0) and coordinates (0, 0, 1):
┌ Warning: Found `resolution` in the theme when creating a `Scene`. The `resolution` keyword for `Scene`s and `Figure`s has been deprecated. Use `Figure(; size = ...` or `Scene(; size = ...)` instead, which better reflects that this is a unitless size and not a pixel resolution. The key could also come from `set_theme!` calls or related theming functions.
└ @ Makie ~/.julia/packages/Makie/We6MY/src/scenes.jl:227
Beethoven is now standing up, but still facing the wall. Let’s rotate it once again by analogy between coordinates (1, 0, 0) and (-1, 1, 0):
┌ Warning: Found `resolution` in the theme when creating a `Scene`. The `resolution` keyword for `Scene`s and `Figure`s has been deprecated. Use `Figure(; size = ...` or `Scene(; size = ...)` instead, which better reflects that this is a unitless size and not a pixel resolution. The key could also come from `set_theme!` calls or related theming functions.
└ @ Makie ~/.julia/packages/Makie/We6MY/src/scenes.jl:227
Rotation specifications are also available in 2D space. As an example, we can rotate the 2D grid of our synthetic geotable by the counter clockwise angle π/4:
gt |>Rotate(Angle2d(π/4)) |> viewer
┌ Warning: Found `resolution` in the theme when creating a `Scene`. The `resolution` keyword for `Scene`s and `Figure`s has been deprecated. Use `Figure(; size = ...` or `Scene(; size = ...)` instead, which better reflects that this is a unitless size and not a pixel resolution. The key could also come from `set_theme!` calls or related theming functions.
└ @ Makie ~/.julia/packages/Makie/We6MY/src/scenes.jl:227
In GIS, this new geotable would be called a rotated “raster”. As another example, let’s translate the geotable to the origin of the coordinate system with the Translate transform:
c =centroid(gt.geometry)gt |>Translate(-to(c)...) |> viewer
┌ Warning: Found `resolution` in the theme when creating a `Scene`. The `resolution` keyword for `Scene`s and `Figure`s has been deprecated. Use `Figure(; size = ...` or `Scene(; size = ...)` instead, which better reflects that this is a unitless size and not a pixel resolution. The key could also come from `set_theme!` calls or related theming functions.
└ @ Makie ~/.julia/packages/Makie/We6MY/src/scenes.jl:227
and scale it with a positive factor for each dimension:
gt |>Scale(0.1, 0.2) |> viewer
┌ Warning: Found `resolution` in the theme when creating a `Scene`. The `resolution` keyword for `Scene`s and `Figure`s has been deprecated. Use `Figure(; size = ...` or `Scene(; size = ...)` instead, which better reflects that this is a unitless size and not a pixel resolution. The key could also come from `set_theme!` calls or related theming functions.
└ @ Makie ~/.julia/packages/Makie/We6MY/src/scenes.jl:227
The StdCoords transform combines Translate and Scale to standardize the coordinates of the domain to the interval [-0.5, 0.5]:
gt |>StdCoords() |> viewer
┌ Warning: Found `resolution` in the theme when creating a `Scene`. The `resolution` keyword for `Scene`s and `Figure`s has been deprecated. Use `Figure(; size = ...` or `Scene(; size = ...)` instead, which better reflects that this is a unitless size and not a pixel resolution. The key could also come from `set_theme!` calls or related theming functions.
└ @ Makie ~/.julia/packages/Makie/We6MY/src/scenes.jl:227
In GIS, another very important coordinate transform is the Proj transform. We will cover this transform in the next chapter because it depends on the concept of map projection, which deserves more attention.
Note
In our framework, the Proj transform is just another coordinate transform. It is implemented with the same code optimizations, and can be used in conjunction with many other transforms that are not available elsewhere.
5.3.2 Advanced
Advanced geometric transforms are provided that change the topology of the domain besides the coordinates of points. Some of these transforms can be useful to repair problematic geometries acquired from sensors in the real world.
The Repair transform is parameterized by an integer K that identifies the repair to be performed. For example, Repair{0}() is a transform that removes duplicated vertices and faces in a domain represented by a mesh. The Repair{9}() on the other hand fixes the orientation of rings in polygonal areas so that the external boundary is oriented counter clockwise and the inner boundaries are oriented clockwise. The list of available repairs will continue to grow with the implementation of new geometric algorithms in the framework.
To understand why geometric transforms are more general than coordinate transforms, let’s consider the following polygonal area with holes:
┌ Warning: Found `resolution` in the theme when creating a `Scene`. The `resolution` keyword for `Scene`s and `Figure`s has been deprecated. Use `Figure(; size = ...` or `Scene(; size = ...)` instead, which better reflects that this is a unitless size and not a pixel resolution. The key could also come from `set_theme!` calls or related theming functions.
└ @ Makie ~/.julia/packages/Makie/We6MY/src/scenes.jl:227
We can connect the holes with the external boundary (or ring) using the Bridge transform:
poly |>Bridge(0.01) |> viz
┌ Warning: Found `resolution` in the theme when creating a `Scene`. The `resolution` keyword for `Scene`s and `Figure`s has been deprecated. Use `Figure(; size = ...` or `Scene(; size = ...)` instead, which better reflects that this is a unitless size and not a pixel resolution. The key could also come from `set_theme!` calls or related theming functions.
└ @ Makie ~/.julia/packages/Makie/We6MY/src/scenes.jl:227
By looking at the visualization, we observe that the number of vertices changed to accommodate the so called “bridges” between the rings. The topology also changed as there are no holes in the resulting geometry.
As a final example of advanced geometric transform, we illustrate the TaubinSmoothing transform, which gradually removes sharp boundaries of a manifold mesh:
st = bt |>TaubinSmoothing(30)fig = Mke.Figure()viz(fig[1,1], bt.geometry)viz(fig[1,2], st.geometry)fig
┌ Warning: Found `resolution` in the theme when creating a `Scene`. The `resolution` keyword for `Scene`s and `Figure`s has been deprecated. Use `Figure(; size = ...` or `Scene(; size = ...)` instead, which better reflects that this is a unitless size and not a pixel resolution. The key could also come from `set_theme!` calls or related theming functions.
└ @ Makie ~/.julia/packages/Makie/We6MY/src/scenes.jl:227
For more advanced geometric transforms, please consult the official documentation.
5.4 Geospatial transforms
Geospatial transforms are those transforms that operate on both the valuesand the domain of the geotable. They are common in geostatistical workflows that need to remove geospatial “trends” or workflows that need to extract geometries from domains.
As an example, let’s consider the following geotable with a variable z that made of a trend component μ and a noise component ϵ:
# quadratic + noiser =range(-1, stop=1, length=100)μ = [x^2+ y^2 for x in r, y in r]ϵ =0.1rand(100, 100)t =georef((z=μ+ϵ,))viewer(t)
┌ Warning: Found `resolution` in the theme when creating a `Scene`. The `resolution` keyword for `Scene`s and `Figure`s has been deprecated. Use `Figure(; size = ...` or `Scene(; size = ...)` instead, which better reflects that this is a unitless size and not a pixel resolution. The key could also come from `set_theme!` calls or related theming functions.
└ @ Makie ~/.julia/packages/Makie/We6MY/src/scenes.jl:227
We can use the Detrend transform to remove a trend of polynomial degree 2:
t |>Detrend(degree=2) |> viewer
┌ Warning: Found `resolution` in the theme when creating a `Scene`. The `resolution` keyword for `Scene`s and `Figure`s has been deprecated. Use `Figure(; size = ...` or `Scene(; size = ...)` instead, which better reflects that this is a unitless size and not a pixel resolution. The key could also come from `set_theme!` calls or related theming functions.
└ @ Makie ~/.julia/packages/Makie/We6MY/src/scenes.jl:227
The remaining component can then be modeled with geostatistical models of geospatial correlation, which will be covered in Part IV of the book.
Models of geospatial correlation such as variograms (Hoffimann and Zadrozny 2019) require unique coordinates in the geotable and that is the purpose of the UniqueCoords transform. It removes duplicate points in the geotable and aggregates the values with custom aggregation functions.
Let’s consider the following geotable stored in a .png file to illustrate another geospatial transform:
letters = GeoIO.load("data/letters.png")
44255×2 GeoTable over 265×167 TransformedGrid
color
geometry
Colorful
Quadrangle
[NoUnits]
🖈 Cartesian{NoDatum}
Gray{N0f8}(1.0)
Quadrangle((x: -1.62266e-14 m, y: 265.0 m), ..., (x: 1.0 m, y: 265.0 m))
Gray{N0f8}(1.0)
Quadrangle((x: -1.61653e-14 m, y: 264.0 m), ..., (x: 1.0 m, y: 264.0 m))
Gray{N0f8}(1.0)
Quadrangle((x: -1.61041e-14 m, y: 263.0 m), ..., (x: 1.0 m, y: 263.0 m))
Gray{N0f8}(1.0)
Quadrangle((x: -1.60429e-14 m, y: 262.0 m), ..., (x: 1.0 m, y: 262.0 m))
Gray{N0f8}(1.0)
Quadrangle((x: -1.59816e-14 m, y: 261.0 m), ..., (x: 1.0 m, y: 261.0 m))
Gray{N0f8}(1.0)
Quadrangle((x: -1.59204e-14 m, y: 260.0 m), ..., (x: 1.0 m, y: 260.0 m))
Gray{N0f8}(1.0)
Quadrangle((x: -1.58592e-14 m, y: 259.0 m), ..., (x: 1.0 m, y: 259.0 m))
Gray{N0f8}(1.0)
Quadrangle((x: -1.57979e-14 m, y: 258.0 m), ..., (x: 1.0 m, y: 258.0 m))
Gray{N0f8}(1.0)
Quadrangle((x: -1.57367e-14 m, y: 257.0 m), ..., (x: 1.0 m, y: 257.0 m))
Gray{N0f8}(1.0)
Quadrangle((x: -1.56755e-14 m, y: 256.0 m), ..., (x: 1.0 m, y: 256.0 m))
⋮
⋮
The Potrace transform can be used to extract complex geometries from a geotable over a 2D Grid. It transforms the Grid domain into a GeometrySet based on any column that contains a discrete set of marker values. In this example, we use the color as the column with markers:
Ab = letters |>Potrace("color", ϵ=0.8)
2×2 GeoTable over 2 GeometrySet
color
geometry
Colorful
MultiPolygon
[NoUnits]
🖈 Cartesian{NoDatum}
Gray{N0f8}(1.0)
Multi(4×PolyArea)
Gray{N0f8}(0.0)
Multi(2×PolyArea)
The option ϵ controls the deviation tolerance used to simplify the boundaries of the geometries. The higher is the tolerance, the less is the number of segments in the boundary:
viz(Ab.geometry[2], color ="black")
┌ Warning: Found `resolution` in the theme when creating a `Scene`. The `resolution` keyword for `Scene`s and `Figure`s has been deprecated. Use `Figure(; size = ...` or `Scene(; size = ...)` instead, which better reflects that this is a unitless size and not a pixel resolution. The key could also come from `set_theme!` calls or related theming functions.
└ @ Makie ~/.julia/packages/Makie/We6MY/src/scenes.jl:227
In the reverse direction, we have the Rasterize transform, which takes a geotable over a GeometrySet and assigns the geometries to a Grid. In this transform, we can either provide an external grid for the the assignments, or request a grid size to discretize the boundingbox of all geometries:
Triangle((x: 2.0 m, y: 0.0 m), (x: 6.0 m, y: 2.0 m), (x: 2.0 m, y: 2.0 m))
2
2.2
Triangle((x: 0.0 m, y: 6.0 m), (x: 3.0 m, y: 8.0 m), (x: 0.0 m, y: 10.0 m))
3
3.3
Quadrangle((x: 3.0 m, y: 6.0 m), ..., (x: 6.0 m, y: 9.0 m))
4
4.4
Quadrangle((x: 7.0 m, y: 0.0 m), ..., (x: 7.0 m, y: 4.0 m))
5
5.5
Pentagon((x: 1.0 m, y: 3.0 m), ..., (x: 0.0 m, y: 6.0 m))
gt |> viewer
┌ Warning: Found `resolution` in the theme when creating a `Scene`. The `resolution` keyword for `Scene`s and `Figure`s has been deprecated. Use `Figure(; size = ...` or `Scene(; size = ...)` instead, which better reflects that this is a unitless size and not a pixel resolution. The key could also come from `set_theme!` calls or related theming functions.
└ @ Makie ~/.julia/packages/Makie/We6MY/src/scenes.jl:227
nt = gt |>Rasterize(20, 20)
400×3 GeoTable over 20×20 CartesianGrid
A
B
geometry
Categorical
Continuous
Quadrangle
[NoUnits]
[NoUnits]
🖈 Cartesian{NoDatum}
missing
missing
Quadrangle((x: 0.0 m, y: 0.0 m), ..., (x: 0.0 m, y: 0.5 m))
missing
missing
Quadrangle((x: 0.5 m, y: 0.0 m), ..., (x: 0.5 m, y: 0.5 m))
missing
missing
Quadrangle((x: 1.0 m, y: 0.0 m), ..., (x: 1.0 m, y: 0.5 m))
1
1.1
Quadrangle((x: 1.5 m, y: 0.0 m), ..., (x: 1.5 m, y: 0.5 m))
1
1.1
Quadrangle((x: 2.0 m, y: 0.0 m), ..., (x: 2.0 m, y: 0.5 m))
missing
missing
Quadrangle((x: 2.5 m, y: 0.0 m), ..., (x: 2.5 m, y: 0.5 m))
missing
missing
Quadrangle((x: 3.0 m, y: 0.0 m), ..., (x: 3.0 m, y: 0.5 m))
missing
missing
Quadrangle((x: 3.5 m, y: 0.0 m), ..., (x: 3.5 m, y: 0.5 m))
missing
missing
Quadrangle((x: 4.0 m, y: 0.0 m), ..., (x: 4.0 m, y: 0.5 m))
missing
missing
Quadrangle((x: 4.5 m, y: 0.0 m), ..., (x: 4.5 m, y: 0.5 m))
⋮
⋮
⋮
nt |> viewer
┌ Warning: Found `resolution` in the theme when creating a `Scene`. The `resolution` keyword for `Scene`s and `Figure`s has been deprecated. Use `Figure(; size = ...` or `Scene(; size = ...)` instead, which better reflects that this is a unitless size and not a pixel resolution. The key could also come from `set_theme!` calls or related theming functions.
└ @ Makie ~/.julia/packages/Makie/We6MY/src/scenes.jl:227
The values of the variables are aggregated at geometric intersections using a default aggregation function, which can be overwritten with an option. Once the geotable is defined over a Grid, it is possible to refine or coarsen the grid with the Downscale and Upscale transforms.
The Transfer of values to a new geospatial domain is another very useful geospatial transform. The Aggregate transform is related, but aggregates the values with given aggregation functions.
5.5 Remarks
In this chapter we learned the important concept of transforms, and saw examples of the concept in action with synthetic data. In order to leverage the large number of transforms implemented in the framework, all we need to do is load our geospatial data as a geotable using georef or GeoIO.jl.
Some additional remarks:
One of the major advantages of transforms compared to traditional row/column access in data science is that they preserve geospatial information. There is no need to keep track of indices in arrays to repeatedly reattach values to geometries.
Transforms can be organized into three classes—feature, geometric and geospatial—depending on how they operate with the values and the domain of the geotable:
Feature transforms operate on the values. They include column selection, data cleaning, statistical analysis and any transform designed for traditional Tables.jl.
Geometric transforms operate on the domain. They include coordinate transforms that simply modify the coordinates of points as well as more advanced transforms that can change the topology of the domain.
Geospatial transforms operate on both the values and domain. They include geostatistical transforms and transforms that use other columns besides the geometry column to produce new columns and geometries.
In the next chapters, we will review map projections with the Proj coordinate transform, and will introduce one of the greatest features of the framework known as transform pipelines.
Hoffimann, Júlio, and Bianca Zadrozny. 2019. “Efficient Variography with Partition Variograms.”Computers & Geosciences 131: 52–59. https://doi.org/https://doi.org/10.1016/j.cageo.2019.06.013.
Koolen, Twan, Yuto Horikawa, Andy Ferris, Claire Foster, awbsmith, ryanelandt, Jan Weidner, et al. 2023. “JuliaGeometry/Rotations.jl: V1.6.0.” Zenodo. https://doi.org/10.5281/zenodo.8366010.
Lin, Dahua, David Widmann, Simon Byrne, John Myles White, Andreas Noack, Mathieu Besançon, Douglas Bates, et al. 2023. “JuliaStats/Distributions.jl: V0.25.100.” Zenodo. https://doi.org/10.5281/zenodo.8224988.
