Recursively unnest_wide all list columns in a tibble.
Source:R/odata_submission_rectangle.R
unnest_all.Rd
Usage
unnest_all(
nested_tbl,
names_repair = "universal",
names_sep = "_",
form_schema = NULL,
verbose = get_ru_verbose()
)
Arguments
- nested_tbl
A nested tibble
- names_repair
The argument
names_repair
fortidyr::unnest_wider
, default: "universal".- names_sep
The argument
names_sep
fortidyr::unnest_wider
, default: "_". Un-nested variables inside a list column will be prefixed by the list column name, separated bynames_sep
. This avoids unsightly repaired names such aslatitude...1
. Set toNULL
to disable prefixing.- form_schema
An optional form_schema, like the output of
form_schema
. If a form schema is supplied, location fields will not be unnested. While WKT location fields contain plain text and will never be unnested, GeoJSON location fields would cause errors during unnesting.- verbose
Whether to display debug messages or not.
Read
vignette("setup", package = "ruODK")
to learn howruODK
's verbosity can be set globally or per function.
Details
odata_submission_rectangle
uses this function
internally.
Interested users can use this function to break down ruODK
's automated
steps into smaller components.
The quite verbose output of tidyr::unnest_wider
is captured
and hidden from the user.
See also
Other utilities:
attachment_get()
,
attachment_link()
,
attachment_url()
,
drop_null_coords()
,
form_schema_parse()
,
get_one_attachment()
,
get_one_submission()
,
get_one_submission_att_list()
,
get_one_submission_audit()
,
handle_ru_attachments()
,
handle_ru_datetimes()
,
handle_ru_geopoints()
,
handle_ru_geoshapes()
,
handle_ru_geotraces()
,
isodt_to_local()
,
odata_submission_rectangle()
,
predict_ruodk_name()
,
prepend_uuid()
,
split_geopoint()
,
split_geoshape()
,
split_geotrace()
,
strip_uuid()
,
tidyeval