Open mmontesanonyc opened 1 year ago
NB, consolidated with other "Ideas" card. FYI, Mike had some thoughts (added here) about adding some type of "Data Explorer Drill-down" functionality that gets into ways to explain what a user is seeing. Touches on a lot of ideas we had - and definitely an interesting area for growth.
@cgettings related to WM's point about legend labels not wrapping. I've been interested for a while in applying direct labels to trend charts, instead of legends. Here's an initial - there's a layer that takes the max date, the value at the max date, and then encodes a text mark there. The major drawback is interference, but I'm going to look into the label transform and avoidMarks
to see what can be accomplished with that.
Adding an idea in here: hiding a menu sidebar control when there is only one option within it.
We'll add a list of data explorer enhancements in this issue. When one gets traction, we'll spin off a new, focused and dedicated issue for it.
Priorities:
hotfix-measure-metadata
): on all but Table, show only single measure. Problem: when map is initial load,renderMeasures
runs and shows multiple measures in HC/S boxes. Otherwise, sorted.hotfix-DE-tooltip
)vizOptions
inindicators.json
, and could be paired with importing it into the page in a variety of places (as a y-value in the trend chart; as a stick-to-top value in the table; in the tooltip on the map?) to add explanation/comparison/context in a strong way. See gist here.Map:
Table:
Links
Trend
end_period
for x-axis field, butTimePeriod
for label won't work, becauselabelExpr
doesn't have access to anything but the name and value of thefield
. One alternative: finding missing sequence values inrenderComparisonsChart
and adding them to the data. Another alternative: usingend_period
, but conditionally modifying thetimeUnit
orformat
inrenderComparisonsChart
to recreateTimePeriod
. This is probably the better option.Disparities
General
Data Explorer Drill-down Add some type of interpretation - something that helps answer The Why.
Console logs: Revise console logs to be descriptive. Log the relevant objects, specific selections. Partly, this can be useful for us (easier to find the names of objects), and partly, useful to any techie poking around.