Closed lekoenig closed 1 year ago
I'm guessing some folks will want the site information, but perhaps we could add a target that retrieves that info on its own (so users could join the site info with the data if desired).
I've been asked about this, so I'm going to go ahead and pull out the siteInfo
attribute from each of the individual branches in p2_wqp_data_aoi
and bind the site metadata into a single table that will be represented by a new target, p2_wqp_site_info
.
This issue follows up on one @padilla410 introduced in #87. Although it doesn't appear to have caused the behavior Julie documented originally, I have wondered whether the attributes are likely to trigger unnecessary or unexpected rebuilds, and if we should do anything with either the site or query (
url
,queryTime
) attributes that get appended in the call todataRetrieval
.Perhaps
targets
drops attributes when combining the mapped data frames, because I don't see any attributes on the full data frame.However, site/query attributes are there when I load any given branch:
We could omit the site attributes by setting
ignore_attributes
toTRUE
indataRetrieval::readWQPdata()
. I'm guessing some folks will want the site information, but perhaps we could add a target that retrieves that info on its own (so users could join the site info with the data if desired).