The hardware and bandwidth for this mirror is donated by dogado GmbH, the Webhosting and Full Service-Cloud Provider. Check out our Wordpress Tutorial.
If you wish to report a bug, or if you are interested in having us mirror your free-software or open-source project, please feel free to contact us at mirror[@]dogado.de.
sidrar_limit_error when the SIDRA
API rejects a request for exceeding its per-request value limit. The
condition remains a sidrar_http_error and records the
requested count, limit, minimum number of batches, response body, and
request URL (#28).sidra_catalog(),
sidra_metadata(), sidra_periods(), and
sidra_locations() using official IBGE JSON endpoints.
Identifiers remain character vectors and returned schemas are stable
when upstream responses are empty or gain fields.sidra_query() and sidra_plan() to
inspect URLs, explicit dimension cardinalities, and optional limit risk
before retrieving values. No service limit is hard-coded.sidra_split()
and sidra_collect(). Batches must be disjoint, retain their
original order, and have identical names and column types before rows
are combined.sidra_provenance() and opt-in disk caching for normalized
catalog and metadata responses. Value responses are never cached by the
package.G) queries, optional extinct
units (/u/y), case-insensitive geographic aliases, and
supported nNN level codes.sidrar_http_error conditions.value_type still
applies when api is used.search_sidra() after changes to the SIDRA
website. Searches are now case- and accent-insensitive, support multiple
non-adjacent terms, and return table codes as names (#24).info_sidra() while preserving its historical
list components: table, period,
variable, classific_category, and
geo.get_sidra(api = ...) for complete official HTTPS
URLs and preserved percent-encoded paths. Thanks to @viniciusoike for
reporting the problem and proposing a solution in #25 and #26./h/n now preserve the first
observation instead of treating it as a header.value_type to preserve SIDRA special symbols in a
character column or alongside the historical numeric value column
(#18).httr,
jsonlite, and utils.These binaries (installable software) and packages are in development.
They may not be fully stable and should be used with caution. We make no claims about them.
Health stats visible at Monitor.