MyNixOS website logo
Description

Use Standardized Statistical Codelists.

The goal of statcodelists is to promote the reuse and exchange of statistical information and related metadata with making the internationally standardized SDMX code lists available for the R user. SDMX has been published as an ISO International Standard (ISO 17369). The metadata definitions, including the codelists are updated regularly according to the standard. The authoritative version of the code lists made available in this package is <https://sdmx.org/?page_id=3215/>.

statcodelists

devel-version License:CC0 dataobservatory DOI

The goal of statcodelists is to promote the reuse and exchange of statistical information and related metadata with making the internationally standardized SDMX code lists available for the R user. SDMX has been published as an ISO International Standard (ISO 17369). The metadata definitions, including the codelists are updated regularly according to the standard. The authoritative version of the code lists made available in this package is https://sdmx.org/?page_id=3215/.

Installation

You can install the development version of statcodelists like so:

devtools::install_github("antaldaniel/statcodelists")

Cross-domain concepts in the SDMX framework describe concepts relevant to many, if not all, statistical domains. SDMX recommends using these concepts whenever feasible in SDMX structures and messages to promote the reuse and exchange of statistical information and related metadata between organisations.

Code lists are predefined sets of terms from which some statistical coded concepts take their values. SDMX cross-domain code lists are used to support cross-domain concepts. The use of common code lists will help users to work even more efficiently, easing the maintenance of and reducing the need for mapping systems and interfaces delivering data and metadata to them. Therefore, a choice over code lists has a great impact on the efficiency of data sharing.

statcodelists helps the use of the latest codelist in your R workflow.

library(statcodelists)
data("codebooks")
conceptcodebookauthority
ActivityCL_ACTIVITYSDMX
AgeCL_AGESDMX
Civil or marital statusCL_CIVIL_STATUSSDMX
Classification of Individual Consumption According to Purpose (COICOP)CL_COICOPSDMX
Classification of the Functions of Government (COFOG)CL_COFOGSDMX
Classification of the Outlays of Producers According to Purpose (COPP)CL_COPPSDMX
Classification of the Purposes of Non-Profit Institutions Serving Households COPNICL_COPNISDMX
Confidentiality statusCL_CONF_STATUSSDMX
CurrencyCL_CURRENCYSDMX
DecimalsCL_DECIMALSSDMX
Degree of UrbanisationCL_DEG_URBSDMX
FrequencyCL_FREQSDMX
Geographical areasCL_AREASDMX
Observation statusCL_OBS_STATUSSDMX
OccupationCL_OCCUPATIONSDMX
Organisation conceptsCL_ORGANISATIONSDMX
Seasonal adjustmentCL_SEASONAL_ADJUSTSDMX
SexCL_SEXSDMX
Time formatCL_TIME_FORMATSDMX
Time period – collectionCL_TIME_PER_COLLECTSDMX
Unit multiplierCL_UNIT_MULTSDMX

Example: Codelist Frequency

data("CL_FREQ")
idnamedescriptionname_localedescription_locale
AAnnualTo be used for data collected or disseminated every yearenen
A2BiennialTo be used for data collected or disseminated every two yearsenen
A3TriennialTo be used for data collected or disseminated every three yearsenen
A4QuadrennialTo be used for data collected or disseminated every four yearsenen
A5QuinquennialTo be used for data collected or disseminated every five yearsenen
A10DecennialTo be used for data collected or disseminated every ten yearsenen
A20BidecennialTo be used for data collected or disseminated every twenty yearsenen
A30TridecennialTo be used for data collected or disseminated every thirty yearsenen
A_3Three times a yearTo be used for data collected or disseminated three times a yearenen
SHalf-yearly, semesterTo be used for data collected or disseminated every semesterenen
QQuarterlyTo be used for data collected or disseminated every quarterenen
MMonthlyTo be used for data collected or disseminated every monthenen
M2BimonthlyTo be used for data collected or disseminated every two monthsenen
M_2SemimonthlyTo be used for data collected or disseminated twice a monthenen
M_3Three times a monthTo be used for data collected or disseminated three times a monthenen
WWeeklyTo be used for data collected or disseminated every weekenen
W2BiweeklyTo be used for data collected or disseminated every two weeksenen
W3TriweeklyTo be used for data collected or disseminated every three weeksenen
W4Four-weeklyTo be used for data collected or disseminated every four weeksenen
W_2SemiweeklyTo be used for data collected or disseminated twice a weekenen
W_3Three times a weekTo be used for data collected or disseminated three times a weekenen
DDailyTo be used for data collected or disseminated every dayenen
D_2Twice a dayTo be used for data collected or disseminated twice a dayenen
HHourlyTo be used for data collected or disseminated every hourenen
H2BihourlyTo be used for data collected or disseminated every two hoursenen
H3TrihourlyTo be used for data collected or disseminated every three hoursenen
BDaily – business weekSimilar to “daily”, however there are no observations for Saturdays and Sundays (so, neither “missing values” nor “numeric values” should be provided for Saturday and Sunday)enen
NMinutelyWhile N denotes “minutely”, usually, there may be no observations every minute (for several series the frequency is usually “irregular” within a day/days). And though observations may be sparse (not collected or disseminated every minute), missing values do not need to be given for the minutes when no observations exist: in any case the time stamp determines when an observation is observedenen
IIrregularTo be used with irregular time series that stores data for a sequence of arbitrary timepoints. Irregular time series are appropriate when the data arrives unpredictably, such as when the application records every stock trade or when random events are recorded (the interval between each element can be a different length)enen
OAOccasional annualThe event occurs occasionally with an infrequent update that could span from 1 year to several years between events. It implies a survey that experiences a gap for several years prior to the next survey update (this is commonly linked to funding available to run a specific survey (i.e. health surveys), whereas a regular annual survey refers typically to ‘programs’ that are funded regularly and fall under the Statistics Act, and therefore never experience a gap)enen
OMOccasional monthlyThe event occurs occasionally with an infrequent update that could span from 1 month to several months between events. It implies a survey that experiences a gap for several months prior to the next survey updateenen
_OOtherTo be used when the qualitative or quantitative values that a variable takes in a data set is associated to multiple occurrences with frequency other than the already defined ones (for example every 5 hours and 32 minutes etc.)enen
_UUnspecifiedTo be used when a set of values are reported within a time range but not associated to sub ranges. Often this could happen in case of missing or sparse information. (Let’s say we have two observations for 2020 but we do not know if they are part of a monthly reporting or quarterly reporting)enen
_ZNot applicableTo be used when the qualitative or quantitative values that a variable takes in a data set is not associated to multiple occurrences (only single occurrence exists) one can use the _Z as frequencyenen

Further recommended code values for expressing general statistical concepts like not applicable, etc., can be found in section Generic codes of the Guidelines for the creation and management of SDMX Cross-Domain Code Lists.

For further codelists used by reliable statistical agency but not harmonized on SDMX level please consult the SDMX Global RegistryCodelists page.

The creator of this package is not affiliated with SDMX, and this package was has not been endorsed by SDMX.

Code of Conduct

Please note that the statcodelists project is released with a Contributor Code of Conduct. By contributing to this project, you agree to abide by its terms.

Metadata

Version

0.9.2

License

Unknown

Platforms (77)

    Darwin
    FreeBSD
    Genode
    GHCJS
    Linux
    MMIXware
    NetBSD
    none
    OpenBSD
    Redox
    Solaris
    WASI
    Windows
Show all
  • aarch64-darwin
  • aarch64-freebsd
  • aarch64-genode
  • aarch64-linux
  • aarch64-netbsd
  • aarch64-none
  • aarch64-windows
  • aarch64_be-none
  • arm-none
  • armv5tel-linux
  • armv6l-linux
  • armv6l-netbsd
  • armv6l-none
  • armv7a-darwin
  • armv7a-linux
  • armv7a-netbsd
  • armv7l-linux
  • armv7l-netbsd
  • avr-none
  • i686-cygwin
  • i686-darwin
  • i686-freebsd
  • i686-genode
  • i686-linux
  • i686-netbsd
  • i686-none
  • i686-openbsd
  • i686-windows
  • javascript-ghcjs
  • loongarch64-linux
  • m68k-linux
  • m68k-netbsd
  • m68k-none
  • microblaze-linux
  • microblaze-none
  • microblazeel-linux
  • microblazeel-none
  • mips-linux
  • mips-none
  • mips64-linux
  • mips64-none
  • mips64el-linux
  • mipsel-linux
  • mipsel-netbsd
  • mmix-mmixware
  • msp430-none
  • or1k-none
  • powerpc-netbsd
  • powerpc-none
  • powerpc64-linux
  • powerpc64le-linux
  • powerpcle-none
  • riscv32-linux
  • riscv32-netbsd
  • riscv32-none
  • riscv64-linux
  • riscv64-netbsd
  • riscv64-none
  • rx-none
  • s390-linux
  • s390-none
  • s390x-linux
  • s390x-none
  • vc4-none
  • wasm32-wasi
  • wasm64-wasi
  • x86_64-cygwin
  • x86_64-darwin
  • x86_64-freebsd
  • x86_64-genode
  • x86_64-linux
  • x86_64-netbsd
  • x86_64-none
  • x86_64-openbsd
  • x86_64-redox
  • x86_64-solaris
  • x86_64-windows