Skip to content

Commit f142e86

Browse files
author
Jon Jablonski
committed
adding some concept explanations around line 170 to start to address issue #24.
1 parent e7e21a0 commit f142e86

File tree

1 file changed

+5
-4
lines changed

1 file changed

+5
-4
lines changed

01_make_map.qmd

Lines changed: 5 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -134,7 +134,7 @@ infrastructure on campus (bike lanes and line, bike racks as points,
134134
buildings as polygons) and to then annotate on top of that some of your
135135
personal experience as a bicyclist or pedestrian on campus.
136136

137-
### Import lines layer (bike paths)
137+
### Import lines Feature layer (bike paths)
138138

139139
From the **Layers** panel, click on the add layer button. Search
140140
`My organization` for 'UCSB OSM Paths'. There should be only one result.
@@ -168,9 +168,10 @@ layer](images/Workshop1/Step1/select-feature-polygon-layer.png){width="70%"}
168168

169169
## Accessing the underlying data
170170

171-
One advantage of those \* feature layers \* (are we consistent with our
172-
nomenclature?) is that there is often data associated with it. For
173-
example, if you click on the three dots on the right of a feature layer
171+
\* Feature layers \* are driven by data.
172+
Each point, line, or polygon has associated with it a row in an attribute table.
173+
174+
For example, if you click on the three dots on the right of a feature layer
174175
you can access their *attribute table* using "Show table".
175176

176177
![attibute table of UCSB buildings

0 commit comments

Comments
 (0)