tm_crs and raster data
Open
Nobody has claimed this yet.
- Dominant language
- R
- Stars
- 32
- Forks
- 9
- PR merge metrics
- No merged PRs in 30d
Description
@mtennekes, have you considered moving raster.warp to the tm_crs function as one of the arguments? It seems like a good home for it, and a little bit easier to explain than tm_options.
See https://tmap.geocompx.org/map-projections#raster-data for examples.
tm_shape(worldelevation) +
tm_raster("worldelevation.tif",
col.scale = tm_scale(values = terrain.colors(8))) +
tm_crs("EPSG:8857") +
tm_options(raster.warp = FALSE)
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by inspecting the tm_crs and tm_options entry points and the raster.warp behavior described in the raster-data map-projections example. Determine whether raster.warp belongs in tm_crs, then update the API and documentation example so the chosen option is clearly explained and works for the shown raster workflow.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- r
- Domain
- data-visualization
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100