A release scores some spatial units and merely carries others: v1 has the
composite on Planning Areas and ecoregions, v6 on Program Areas only. Read the
fld values whose zones have metric_key, so a comparison can pick the unit
each side actually scored instead of assuming Program Areas.
Usage
zone_scored_flds(con, metric_key = METRIC_SCORE_DEFAULT)
Arguments
- con
a DBI connection to a release's sdm.duckdb
- metric_key
metric to look for (default METRIC_SCORE_DEFAULT)
Value
character vector of fld values (e.g. "programarea_key"), with the
number of zones as names; empty if no unit carries the metric