search

expersso / BIS

Programmatic access to BIS data
19 stars 10 forks source link

get_bis doesn't work #7

Open JulianVeit opened 1 year ago

JulianVeit commented 1 year ago

Hey!

I am trying to run the code as was presented in the example usage. Somehow I have problems with the get_bis function and following warning message occurs:

library(BIS) datasets <- get_datasets() head(datasets, 20) rates <- get_bis(datasets$url[datasets$name == "Policy rates (monthly)"], quiet = TRUE) Rows: 39 Columns: 933
── Column specification ─────────────────────────────────────────────────────────────── Delimiter: "," chr (933): X1, X2, X3, X4, X5, X6, X7, X8, X9, X10, X11, X12, X13, X14, X15, X16, X...

ℹ Use spec() to retrieve the full column specification for this data. ℹ Specify the column types or set show_col_types = FALSE to quiet this message. Rows: 38 Columns: 933
── Column specification ─────────────────────────────────────────────────────────────── Delimiter: "," chr (10): FREQ, Frequency, REF_AREA, Reference area, COMPILATION, Decimals, SOURCE... dbl (921): DECIMALS, 1946-01, 1946-02, 1946-03, 1946-04, 1946-05, 1946-06, 1946-07,... lgl (2): TIME_FORMAT, Time Format

ℹ Use spec() to retrieve the full column specification for this data. ℹ Specify the column types or set show_col_types = FALSE to quiet this message. Warning messages: 1: as_data_frame() was deprecated in tibble 2.0.0. ℹ Please use as_tibble() instead. ℹ The signature and semantics have changed, see ?as_tibble. ℹ The deprecated feature was likely used in the BIS package. Please report the issue at https://github.com/expersso/BIS/issues. This warning is displayed once every 8 hours. Call lifecycle::last_lifecycle_warnings() to see where this warning was generated. 2: The x argument of as_tibble.matrix() must have unique column names if .name_repair is omitted as of tibble 2.0.0. ℹ Using compatibility .name_repair. ℹ The deprecated feature was likely used in the tibble package. Please report the issue at https://github.com/tidyverse/tibble/issues. This warning is displayed once every 8 hours. Call lifecycle::last_lifecycle_warnings() to see where this warning was generated.

Any help is very much appreciated!

Best reagrds, Veit