Skip to content

Commit f1748da

Browse files
author
Jon Jablonski
committed
clarifying language about vertical vs horizontal resolution and the metadata.
1 parent 70fa947 commit f1748da

File tree

1 file changed

+10
-4
lines changed

1 file changed

+10
-4
lines changed

episodes/01-raster-structure.Rmd

Lines changed: 10 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -210,9 +210,15 @@ plot(DSM_HARV)
210210

211211
This map shows the elevation of our study site in Harvard Forest. From the
212212
legend, we can see that the maximum elevation is ~400, but we can't tell whether
213-
this is 400 feet or 400 meters because the legend doesn't show us the units. We
214-
can look at the metadata of our object to see what the units are. Much of the
215-
metadata that we're interested in is part of the CRS. We introduced the
213+
this is 400 feet or 400 meters because the legend doesn't show us the units.
214+
215+
Unfortunately, nothing in the technical metadata (that which is built into
216+
the file format) tells us what the _vertical_ resolution is. For now you will
217+
have to trust us that it is meters.
218+
219+
However, we can look at the metadata of our object to see what the horizontal
220+
units are: in other words how many meters from the origin are the
221+
x and y points. That metadata, is part of the CRS. We introduced the
216222
concept of a CRS in [an earlier
217223
lesson](https://datacarpentry.org/organization-geospatial/03-crs).
218224

@@ -232,7 +238,7 @@ crs(DSM_HARV, proj = TRUE)
232238

233239
## Challenge
234240

235-
What units are our data in?
241+
What units are our horizontal data in?
236242

237243
::::::::::::::: solution
238244

0 commit comments

Comments
 (0)