Closed mjwestgate closed 1 year ago
With changes to the ALA APIs, we are now limited to 400 rows, even for large datasets. For example, the GRIIS list stored by ALA here has 2984 rows, but:
search_all(lists, "dr17242") |> show_values() |> nrow() • Showing values for 'dr17242'. [1] 400
To solve this, we can either add a higher max value to the API call, or paginate.
max
Sub-issue: should the df arg in show_values be labelled .data for consistency with other functions?
df
show_values
.data
Note: atlas_GET contains pagination code that may duplicate atlas_paginate; check for efficiencies
atlas_GET
atlas_paginate
As of v 1.5.1 this appears fixed, albeit with optional limitation of number of rows via limit argument
limit
With changes to the ALA APIs, we are now limited to 400 rows, even for large datasets. For example, the GRIIS list stored by ALA here has 2984 rows, but:
To solve this, we can either add a higher
max
value to the API call, or paginate.Sub-issue: should the
df
arg inshow_values
be labelled.data
for consistency with other functions?