DAAF-Contribution-Community/daaf / .claude/skills/sf-terra
sf-terra
VerifiedR spatial data: sf vectors, terra rasters, spdep/spatialreg spatial stats, leaflet interactive maps, ggplot2+geom_sf() choropleths. CRS, spatial joins, geometry ops. Use when execution language is R. Python equivalent: geopandas.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 16.4 KB |
| references/crs.md | markdown | 7.5 KB |
| references/gotchas.md | markdown | 9.1 KB |
| references/interactive.md | markdown | 6.7 KB |
| references/mapping.md | markdown | 8.3 KB |
| references/quickstart.md | markdown | 7.8 KB |
| references/raster.md | markdown | 7.2 KB |
| references/spatial-ops.md | markdown | 8.4 KB |
| references/spatial-stats.md | markdown | 10.1 KB |
references/interactive.md
View on GitHub# Interactive Maps with leaflet
Creating interactive web maps using the leaflet package -- tile layers, choropleth polygons, markers, popups, legends, and saving to HTML. leaflet is the R counterpart to Python's folium.
---
## Basic Leaflet Map
```r
library(leaflet)
library(sf)
# Minimal map centered on data
m <- leaflet(counties) |>
addTiles() |> # OpenStreetMap base tiles
addPolygons() # Add sf polygons
m # Display (in viewer) or save (see below)
```
---
## Tile Providers
```r
# OpenStreetMap (default)
addTiles()
# CartoDB Positron (light, clean -- best for choropleth overlays)
addProviderTiles(providers$CartoDB.Positron)
# CartoDB DarkMatter (dark background)
addProviderTiles(providers$CartoDB.DarkMatter)
# Esri World Imagery (satellite)
addProviderTiles(providers$Esri.WorldImagery)
# Stamen Terrain
addProviderTiles(providers$Stadia.StamenTerrain)
# Stamen Toner Lite (grayscale)
addProviderTiles(providers$Stadia.StamenTonerLite)
# Multiple tile layers with layer control
leaflet() |>
addProviderTiles(providers$CartoDB.Positron, group = "Light") |>
addProviderTiles(providers$Esri.WorldImagery, group = "Satellite") |>
addLayersControl(baseGroups = c("Light", "Satellite"))
```
---
## Choropleth Polygons
```r
library(leaflet)
library(sf)
# Color palette function
pal <- colorBin(
palette = "YlOrRd",
domain = counties$poverty_rate,
bins = 5
)
# Build choropleth
m <- leaflet(counties) |>
addProviderTiles(providers$CartoDB.Positron) |>
addPolygons(
fillColor = ~pal(poverty_rate),
fillOpacity = 0.7,
color = "white", # Border color
weight = 1, # Border width
opacity = 1, # Border opacity
highlight = highlightOptions(
weight = 3,
color = "#666",
fillOpacity = 0.8,
bringToFront = TRUE
),
popup = ~paste0(
"<b>", name, "</b><br/>",
"Poverty Rate: ", round(poverty_rate, 1), "%<br/>",
"Population: ", format(population, big.mark = ",")
),
label = ~name
) |>
addLegend(
pal = pal,
values = ~poverty_rate,
title = "Poverty Rate (%)",
position = "bottomright"
)
```
---
## Color Palette Functions
leaflet provides three palette constructors:
| Function | Use For | Example |
|----------|---------|---------|
| `colorBin()` | Binned continuous (equal-interval or custom breaks) | `colorBin("YlOrRd", domain, bins = 5)` |
| `colorQuantile()` | Quantile-based bins (equal count per bin) | `colorQuantile("YlOrRd", domain, n = 5)` |
| `colorNumeric()` | Continuous gradient (no binning) | `colorNumeric("viridis", domain)` |
| `colorFactor()` | Categorical / factor variables | `colorFactor("Set2", domain)` |
### Custom Breaks with classInt
```r
library(classInt)
brks <- classIntervals(counties$poverty_rate, n = 5, style = "fisher")
pal <- colorBin(
palette = "YlOrRd",
domain = counties$poverty_rate,
bins = brks$brks
)
```
---
## Points and Markers
### Circle Markers
```r
leaflet(schools) |>
addProviderTiles(providers$CartoDB.Positron) |>
addCircleMarkers(
radius = ~sqrt(enrollment) / 5, # Size by enrollment
color = "steelblue",
fillColor = "steelblue",
fillOpacity = 0.6,
stroke = TRUE,
weight = 1,
popup = ~paste0("<b>", school_name, "</b><br/>Enrollment: ", enrollment),
label = ~school_name
)
```
### Default Markers (Pin Icons)
```r
leaflet(schools) |>
addTiles() |>
addMarkers(
popup = ~school_name,
label = ~school_name,
clusterOptions = markerClusterOptions() # Cluster nearby markers
)
```
---
## Popups and Labels
### Popup (Click to Show)
```r
addPolygons(
popup = ~paste0(
"<b>", name, "</b><br/>",
"<table>",
"<tr><td>Population:</td><td>", format(pop, big.mark = ","), "</td></tr>",
"<tr><td>Poverty:</td><td>", round(pov_rate, 1), "%</td></tr>",
"</table>"
)
)
```
### Label (Hover to Show)
```r
addPolygons(
label = ~paste0(name, ": ", round(poverty_rate, 1), "%"),
labelOptions = labelOptions(
style = list("font-size" = "12px"),
direction = "auto"
)
)
```
---
## Legends
```r
# Continuous legend
addLegend(
pal = pal,
values = ~poverty_rate,
title = "Poverty Rate (%)",
position = "bottomright", # "topright", "bottomright", "bottomleft", "topleft"
opacity = 1
)
# Custom labels
addLegend(
pal = pal,
values = ~poverty_rate,
title = "Poverty Rate",
labFormat = labelFormat(suffix = "%", digits = 1),
position = "bottomright"
)
```
---
## Layered Maps
```r
m <- leaflet() |>
addProviderTiles(providers$CartoDB.Positron) |>
# Layer 1: Counties
addPolygons(
data = counties,
fillColor = ~pal(poverty_rate),
fillOpacity = 0.5,
color = "gray",
weight = 0.5,
group = "Counties"
) |>
# Layer 2: Schools
addCircleMarkers(
data = schools,
radius = 3,
color = "red",
fillOpacity = 0.8,
group = "Schools",
popup = ~school_name
) |>
# Layer control (toggle layers)
addLayersControl(
overlayGroups = c("Counties", "Schools"),
options = layersControlOptions(collapsed = FALSE)
)
```
---
## Setting View and Bounds
```r
# Set initial view
leaflet() |>
setView(lng = -96, lat = 37.5, zoom = 4) |> # Center of US
addTiles()
# Fit to data bounds
leaflet(counties) |>
addTiles() |>
addPolygons() |>
fitBounds(
lng1 = st_bbox(counties)["xmin"],
lat1 = st_bbox(counties)["ymin"],
lng2 = st_bbox(counties)["xmax"],
lat2 = st_bbox(counties)["ymax"]
)
```
---
## Saving Leaflet Maps
```r
library(htmlwidgets)
# Save to HTML file
saveWidget(m, file = "interactive_map.html", selfcontained = TRUE)
# selfcontained = TRUE bundles all resources into one file (larger but portable)
# selfcontained = FALSE creates a folder of dependencies (smaller HTML)
```
In DAAF research pipelines, interactive maps are saved to the project output directory for inspection but are not the primary deliverable (static maps from ggplot2 are preferred for reports).
---
## CRS Considerations
leaflet expects data in **WGS84 (EPSG:4326)** -- longitude/latitude coordinates. leaflet does **not** reproject other CRS for you: passing a projected sf object produces the warning "sf layer is not long-lat data" (verified with EPSG:3857 input) and the layer will not render at the correct location. Always transform explicitly:
```r
# Ensure WGS84 for leaflet
counties_wgs <- st_transform(counties, 4326)
leaflet(counties_wgs) |> addTiles() |> addPolygons()
```
---
## References and Further Reading
Cheng, J. et al. (2024). *leaflet: Create Interactive Web Maps with the JavaScript 'Leaflet' Library*. https://rstudio.github.io/leaflet/
Lovelace, R., Nowosad, J., and Muenchow, J. (2024). *Geocomputation with R* (2nd ed.), Ch. 9: "Making maps with R." https://r.geocompx.org/
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirements | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |