R Studio 2022.02.1 Build 461 crashes when using read_osm
Nobody has claimed this yet.
- Dominant language
- R
- Stars
- 43
- Forks
- 9
- PR merge metrics
- No merged PRs in 30d
Description
I recently updated both R (4.2.0) and RStudio (2022.02.01 Build 461) on my Windows 10. Code I had used for using tmap and tmaptools is now crashing when I try to use read_osm.
R version 4.2.0 (2022-04-22 ucrt) -- "Vigorous Calisthenics"
Copyright (C) 2022 The R Foundation for Statistical Computing
Platform: x86_64-w64-mingw32/x64 (64-bit)
R is free software and comes with ABSOLUTELY NO WARRANTY.
You are welcome to redistribute it under certain conditions.
Type 'license()' or 'licence()' for distribution details.
R is a collaborative project with many contributors.
Type 'contributors()' for more information and
'citation()' on how to cite R or R packages in publications.
Type 'demo()' for some demos, 'help()' for on-line help, or
'help.start()' for an HTML browser interface to help.
Type 'q()' to quit R.
packageVersion("tmap")
[1] ‘3.3.3’
packageVersion("tmaptools")
[1] ‘3.1.1’
library(tmap)
library(tmaptools)
load Netherlands shape
data(NLD_muni)
read OSM raster data
osm_NLD <- read_osm(NLD_muni, ext=1.1)
R Session Aborted R encountered a fatal error. The session was terminated.
Contributor guide
No contributing guide indexed for this repository
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 reproducing the supplied read_osm example with NLD_muni, ext=1.1, R 4.2.0, tmap 3.3.3, and tmaptools 3.1.1 on Windows 10. Trace the read_osm entry point and relevant package behavior; done means the example no longer causes a fatal R session termination.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- r
- Domain
- data-visualization
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100