From d53d64a003342434d00af3c33c745f27c30aacc3 Mon Sep 17 00:00:00 2001 From: robinlovelace Date: Wed, 31 Jul 2024 12:08:38 +0100 Subject: [PATCH] Update URLs (#247) --- NEWS.md | 5 +++-- README.Rmd | 2 +- README.md | 2 +- vignettes/stats19.Rmd | 2 +- 4 files changed, 6 insertions(+), 5 deletions(-) diff --git a/NEWS.md b/NEWS.md index 1b38e76..770e2b6 100644 --- a/NEWS.md +++ b/NEWS.md @@ -1,5 +1,6 @@ -# stats19 3.1.0 -* stats19 now relies on the `stats19_variables` object to format the different tables columns (#245). +# stats19 3.1.0 2024-07 + +* stats19 now relies on the `stats19_variables` object to format the different tables columns (#245) (credit @layik), fixing an issue in which ages were removed from the `casualties` table, fixing (#235) # stats19 3.0.3 2024-02 diff --git a/README.Rmd b/README.Rmd index 09e36c5..e3bcc31 100644 --- a/README.Rmd +++ b/README.Rmd @@ -64,7 +64,7 @@ install.packages("stats19") ## get_stats19() `get_stats19()` requires `year` and `type` parameters, mirroring the provision of STATS19 data files, which are categorised by year (from 1979 onward) and type (with separate tables for crashes, casualties and vehicles, as outlined below). -The following command, for example, gets crash data from 2022 (**note**: we follow the "crash not accident" campaign of [RoadPeace](https://www.roadpeace.org/get-involved/crash-not-accident/) in naming crashes, although the DfT refers to the relevant tables as 'accidents' data): +The following command, for example, gets crash data from 2022 (**note**: we follow the "crash not accident" campaign of [RoadPeace](https://www.roadpeace.org/working-for-change/crash-not-accident/) in naming crashes, although the DfT refers to the relevant tables as 'accidents' data): ```{r} crashes = get_stats19(year = 2022, type = "collision") diff --git a/README.md b/README.md index 9d7cc84..cf2c473 100644 --- a/README.md +++ b/README.md @@ -77,7 +77,7 @@ provision of STATS19 data files, which are categorised by year (from vehicles, as outlined below). The following command, for example, gets crash data from 2022 (**note**: we follow the “crash not accident” campaign of -[RoadPeace](https://www.roadpeace.org/get-involved/crash-not-accident/) +[RoadPeace](https://www.roadpeace.org/working-for-change/crash-not-accident/) in naming crashes, although the DfT refers to the relevant tables as ‘accidents’ data): diff --git a/vignettes/stats19.Rmd b/vignettes/stats19.Rmd index 1d7862d..d126d27 100644 --- a/vignettes/stats19.Rmd +++ b/vignettes/stats19.Rmd @@ -27,7 +27,7 @@ A description of variables in the database can be found in a [document](https:// The datasets are collectively called STATS19 after the form used to report them, which can be found [here](https://assets.publishing.service.gov.uk/government/uploads/system/uploads/attachment_data/file/995422/stats19.pdf). This vignette focuses on how to use the **stats19** package to work with STATS19 data. -**Note**: The Department for Transport used to refer to 'accidents', but "crashes" may be a more appropriate term, as emphasised in the "crash not accident" arguments of road safety advocacy groups such as [RoadPeace](https://www.roadpeace.org/get-involved/crash-not-accident/). +**Note**: The Department for Transport used to refer to 'accidents', but "crashes" may be a more appropriate term, as emphasised in the "crash not accident" arguments of road safety advocacy groups such as [RoadPeace](https://www.roadpeace.org/working-for-change/crash-not-accident/). We use the term collision only in reference to nomenclature within the data as provided. The development version is hosted on [GitHub](https://github.com/ITSLeeds/stats19) and can be installed and loaded as follows: