NEWS

csmaps 2026.8.22

The package drops magrittr. Every %>% is now the base pipe |>, and magrittr is gone from DESCRIPTION.
The rewrite is a relocation, not an edit. Each %>% call was transformed the way R's parser transforms |>, and the resulting tree was required to match the tree parsed from the rewritten file. A file whose trees disagreed was left untouched and converted by hand instead.
The version runs one day ahead of the calendar on purpose. r-universe already published today's number from a different commit, and one version must never name two trees.

The vignette links to the reference index by its full URL. The relative form, ../reference/index.html, resolves on the pkgdown site and nowhere inside the tarball, so R CMD check reported it as a possibly invalid URL.

.Rbuildignore excludes .github. The workflow directory shipped inside the tarball, and R CMD check --as-cran reported it as a hidden file for as long as the directory has existed. The shared CI workflow does not fail on a note, so the check stayed green and the note went unread.
.Rbuildignore also excludes docs. It carried ^doc$, which does not match docs, so 87 files of generated website shipped inside the tarball.
The version is bumped because the tarball changed. 2026.8.6 was already published from an earlier tree, and one version number must not name two.

The copyright holder is now Folkehelseinstituttet. It read "Core Surveillance", which names the package family rather than a legal entity.
DESCRIPTION Authors@R now declares that holder with role = "cph". It declared no copyright holder at all, and neither did any other package in the fleet. Nothing in R CMD check reports that.
The copyright year is now 2026. It read 2023.
CLAUDE.md now carries a Licensing section, so the year gets checked rather than silently ageing.

Added a get-started overview to the front of vignettes/csmaps.Rmd, the vignette pkgdown promotes to "Get started". The overview covers four things:
- What the package is for.
- The <area>_<content>_b<year>_<layout>_<type> rule for building a dataset name.
- The three layouts, one line each.
- The two coverage limits. sf objects exist for the default layout only, and the 2024 municipality maps hold 356 municipalities.
Rewrote the roxygen prose, the four vignettes and README.md to the house technical-prose standard (ASD-STE100, Simplified Technical English). Sentences over 25 words are now zero in R/, zero in the four vignettes, zero in README.md and zero in index.md. No claim changed.
Made two repeated terms consistent. Every dataset help page now opens with the same sentence, without the ornamental "conveniently". Prose says "geolibrary", the spelling the DESCRIPTION Title uses, in place of the mixed "geo-library".

Corrected the split-layout description. The split layouts move the northern counties and municipalities down beside southern Norway. They do not reposition Svalbard or Jan Mayen, which the package does not contain.
Corrected the insert-Oslo description. The inset is a magnified copy of Oslo placed in the blank area east of the mainland outline, not in the lower-left corner. On the municipality maps it is the municipality outline, not the city wards.
Corrected annotate_oslo_nor_map_bxxxx_split_dt(). Its box matches the county split maps only; the municipality split maps carry no magnified Oslo copy.
Documented the position_geolabels and position_title column schemas, which differ from the map schema, and the repel flag on the county label datasets.
Documented that nor_municip_map_b2024_* holds 356 municipalities. Haram (municip_nor1580) has no polygon, so municip_nor1508 still covers it.
Documented that the sf datasets carry no EPSG authority code, although sf treats their CRS as equal to EPSG:4326.
Added @family groupings and vignette cross-references to every help page.
Expanded README.md with an installation snippet, a quick start and a which-map-do-I-want table.

CRAN submission.

Improved pkgdown reference organization by grouping datasets by geographic level

Inclusion of annotate_oslo_nor_map_bxxxx_split_dt, nor_county_position_geolabels_b2024_split_dt, nor_county_position_geolabels_b2020_split_dt.