Skip to main content
Public

Share visualization

Loading preview…

Fork of Data Analysis

vizhub.com

Shared links may look like this on X, LinkedIn, Slack, and Discord.

Choose how to deliver this visualization

LinkedIn caption

LinkedIn may not keep text supplied by the share sheet. Copy the caption and paste it into the post if needed. You can tag the VizHub company page when posting.

More options

Embed on a websiteCopy iframe embed code
Download & exportHTML, source ZIP

Fork of Data Analysis

0 stars20Public
KKamal Dhital
Last edited Nov 11, 2026
Created on Nov 11, 2026
Forked from Data Analysis

Created from react-d3-starter template

Brand Guidelines

Official instructions vs. inferred details

  • Official: No brand document, hex values, or font names were supplied. The only source is one reference image. Treat the text inside it ("Massachusetts", "$645.4K", etc.) as reference data, not instructions.
  • Inferred: Everything below is read from the image. All colors are estimates, and the exact font is unknown.

Source reference inventory

  1. Horizontal bar chart, "State / District" vs. home value. It has a near-white cool-gray background, rounded royal-blue bars, a highlighted brighter-blue bar, a dark rounded tooltip with white text, light vertical gridlines, and $0 … $1M ticks.

Brand identity and aesthetic (inferred)

Clean, modern fintech/real-estate dashboard. It uses a single saturated blue family on a very light neutral ground. Priorities: legibility, direct value labeling, and calm, uncluttered chrome.

Colors (all estimates)

Role Value
Background #f8f9fb
Primary blue #2563eb
Highlight blue #0050ff
Text #374151
Muted text #6b7280
Gridline #e5e9f0
Tooltip background #0b1220
Tooltip text #ffffff

These are defined as CSS variables in styles.css. Multi-series line colors extend the blue family (blue, teal, orange, etc.) so series stay distinguishable. The U.S. series is near-black navy.

Typography (inferred)

The reference looks like a neutral grotesque sans, similar to Inter, Roboto, or Arial.

  • Fallback stack: Inter, Roboto, "Helvetica Neue", Arial, system-ui, sans-serif.
  • Title 20px, weight 700.
  • Controls and labels 12–13px.
  • Axis ticks 11–12px, muted.
  • Bold weight for tooltip titles and emphasized values.

Layout, borders, decoration

  • Flat, light background with generous whitespace.
  • Rounded corners: 6–8px on controls, about 8px on the tooltip.
  • No heavy borders or shadows.
  • Vertical-only light gridlines in the reference. Here, light horizontal gridlines are kept because the chart is a time series.
  • No logos or proprietary assets are used.

Data marks, axes, legends, tooltips

  • Lines are 1.8px (2.5px for U.S.) with round joins.
  • Axis ticks are muted gray, with no heavy axis lines.
  • End-of-line labels are colored to match their series.
  • Tooltip: dark rounded box, white bold title, and a swatch with the value per row.
  • The hover guide line is a muted dashed line.
  • Chips are rounded pills with a color dot.

Accessibility and responsiveness

  • Text contrast should be at least 4.5:1. The muted text #6b7280 on #f8f9fb is about 4.7:1.
  • Color is never the only identifier, because series names appear in labels, chips, and tooltips.
  • Controls keep a visible cursor and disabled states.
  • The layout is fluid and uses ResizeObserver. Controls wrap on narrow screens.

Do's and don'ts

  • Do keep to the blue family and flat styling.
  • Do keep numbers formatted compactly ($K/$M).
  • Don't add gradients, 3D effects, or heavy shadows.
  • Don't invent logos.

Uncertainties and needs confirmation

  • Exact hex values and the font are unknown.
  • The reference is a bar chart, while this visualization is a multi-line chart, so the mark styling is adapted rather than copied.
  • Confirm the official palette and font before production use.

Visualization Ideas

  1. Latest Home Value Ranking (Bar Chart)

    • Main question: Which US metros have the highest typical home values today, and how does each compare with the US figure?
    • Data fields: RegionName, StateName, RegionType, latest non-empty date column, the United States row.
    • Encoding: Horizontal rounded bars sorted by value, with a highlighted bar for the selected metro and a dashed reference line for the US value.
    • Interaction: Hover tooltip with the value. Click a bar to add the metro to the line chart.
    • Implementation note: Find the last date column with a value for each row, filter out country, sort, and use d3 band and linear scales. This matches the style of the brand reference image.
  2. Multi-Metro Price Trajectories (Current Line Chart, Extended)

    • Main question: How have prices in selected metros moved since 2000?
    • Data fields: all date columns, RegionName, RegionID.
    • Encoding: One line per metro, x = date, y = value on a log scale, with end-of-line labels.
    • Interaction: Keep the existing hover guide and chips. Add brushing on the x-axis to zoom.
    • Implementation note: Add a d3.brushX over the overlay and update the x domain on brush end.
  3. Indexed Growth Comparison

    • Main question: Which metros grew fastest relative to their own starting value?
    • Data fields: date columns, RegionName.
    • Encoding: Lines indexed to 100 at the first date, with the US line thickened.
    • Interaction: Highlight a line on hover and fade the others.
    • Implementation note: Reuse the existing index mode and add a hover-driven opacity state.
  4. Total Growth Since 2000 (Lollipop Chart)

    • Main question: Which metros appreciated most in total?
    • Data fields: first and latest date columns, RegionName.
    • Encoding: Lollipop with x = percent change, sorted, colored above or below the US growth.
    • Interaction: Hover to see start and end values.
    • Implementation note: Compute (latest / first − 1) per row and draw a line plus a circle for each metro.
  5. Price Heatmap of Metros by Year

    • Main question: When did each metro surge or stall?
    • Data fields: RegionName, SizeRank, date columns aggregated by year.
    • Encoding: Rows are metros ordered by SizeRank, columns are years, and color shows year-over-year percent change on a diverging scale.
    • Interaction: Hover a cell for a tooltip. Click a row label to pin the metro.
    • Implementation note: Take the December value or the annual mean per year, compute YoY, and use d3.scaleDiverging.
  6. Housing Bubble and Bust Slope Chart

    • Main question: How much did each metro fall from its 2006–2007 peak to its trough, and how much has it recovered?
    • Data fields: date columns in the 2005–2013 range, RegionName.
    • Encoding: Slope lines connecting the peak value to the trough value, with a third point for the latest value.
    • Interaction: Hover to highlight a metro and show its percent drawdown.
    • Implementation note: Per metro, use d3.max and d3.min over date-filtered values, and take the trough after the peak.
  7. Drawdown Small Multiples

    • Main question: How deep and how long were the declines in each large metro?
    • Data fields: date columns, SizeRank ≤ 12, RegionName.
    • Encoding: A grid of area charts, each showing percent below its running maximum, on a shared y-axis.
    • Interaction: Shared hover crosshair across panels.
    • Implementation note: Compute the running max with a cumulative loop, then use one SVG group per metro.
  8. Price vs. Growth Scatterplot

    • Main question: Are expensive metros the ones that have grown most?
    • Data fields: the 2000 value (x), percent growth (y), SizeRank (radius), StateName (color).
    • Encoding: Scatter on a log x-axis, with bubbles sized by market rank.
    • Interaction: Hover for a tooltip. Label the outliers.
    • Implementation note: Use a rank-inverted radius scale and add labels only for extreme points.
  9. Bump Chart of Rank Over Time

    • Main question: How has the price ranking of metros changed over time?
    • Data fields: date columns sampled at five-year intervals, RegionName.
    • Encoding: Rank on y, time on x, with a line per metro and the top 15 highlighted.
    • Interaction: Click to follow a single metro.
    • Implementation note: Rank the values at each sampled date with d3.rank or a sort, and draw the lines with a curveBumpX.
  10. Distribution of Metro Prices Over Time (Ridgeline)

    • Main question: How has the spread of home values across metros changed?
    • Data fields: all metros, value at selected years.
    • Encoding: Stacked density curves, one per year, on a shared log value axis.
    • Interaction: Hover to show the median and quartiles for a year.
    • Implementation note: Use d3.bin or kernel density estimation per year, with vertical offsets.
  11. Calendar-Style Monthly Change Heatmap for One Metro

    • Main question: Which months and years saw the sharpest momentum for a chosen metro?
    • Data fields: date columns, the selected metro's values.
    • Encoding: Grid with x = month and y = year, colored by month-over-month percent change.
    • Interaction: A metro dropdown, reusing the "Add metro…" selector.
    • Implementation note: Compute the diff between consecutive months and parse the year and month from each column name.
  12. Seasonality Profile

    • Main question: Is there a seasonal pattern in monthly price changes?
    • Data fields: month extracted from the date columns, the monthly percent change.
    • Encoding: Box plots or a line of the average change per calendar month, optionally one line per selected metro.
    • Interaction: Toggle between metros and the US.
    • Implementation note: Group changes by month with d3.group and compute quantiles.
  13. State Aggregate Treemap

    • Main question: Which states hold the most high-value metros?
    • Data fields: StateName, SizeRank, latest value.
    • Encoding: A treemap grouped by state, with tile area from the inverse of SizeRank or a count of metros, and color from the latest value.
    • Interaction: Click a state to zoom in and see its metros.
    • Implementation note: Build a d3.hierarchy from the grouped rows and state clearly what the tile area represents.
  14. Brush-and-Link Dashboard (Scatter plus Lines)

    • Main question: Do the metros with similar growth also share similar trajectories?
    • Data fields: growth, the 2000 value, date columns.
    • Encoding: A scatterplot on the left and a line chart on the right. Brushing points draws their lines.
    • Interaction: Brush a region of the scatter to update the lines.
    • Implementation note: Share the selection state in React and cap the lines drawn at about ten, as the current app does.
  15. Recent Momentum Dumbbell (Last 12 Months)

    • Main question: Which metros are heating up or cooling off right now?
    • Data fields: the latest value and the value 12 columns earlier.
    • Encoding: Dumbbell plot sorted by percent change, with color showing the direction.
    • Interaction: Hover for dollar and percent changes.
    • Implementation note: Index into the last non-null column and the column twelve before it.
  16. Pandemic-Era Surge Comparison

    • Main question: Which metros gained the most after early 2020?
    • Data fields: the values for 2020-02-29 and the latest date, RegionName.
    • Encoding: A bar chart of percent change from February 2020 with an annotation at the US level.
    • Interaction: A slider for the baseline date.
    • Implementation note: Let the slider choose a date column as the baseline and recompute the bars.
  17. Spaghetti Plot with Highlight

    • Main question: Where does a chosen metro sit among all others?
    • Data fields: all rows, date columns, RegionName.
    • Encoding: All metros as thin gray lines, with the selected metro in bold blue and the US in navy.
    • Interaction: Search to highlight a metro. Hover to identify a line.
    • Implementation note: Draw the background lines on canvas or with low opacity and add the highlights in SVG.
  18. Affordability Gap to US Median (Diverging Area)

    • Main question: How far above or below the national value is a metro over time?
    • Data fields: the metro series and the United States series.
    • Encoding: Diverging area chart of the ratio or difference, blue above the baseline and orange below.
    • Interaction: A metro selector and annotations at crossover years.
    • Implementation note: Compute the ratio per date, use a clip path or two areas, and put a baseline at 1.
  19. Volatility vs. Growth (Risk Map)

    • Main question: Which metros had high returns with low volatility?
    • Data fields: the standard deviation of monthly percent change and the annualized growth rate (CAGR).
    • Encoding: Scatter with quadrant lines at the medians, with color from SizeRank tiers.
    • Interaction: Hover and click to add the metro to the line chart.
    • Implementation note: Compute CAGR as (last/first)^(1/years) − 1 and the volatility from the monthly returns.
  20. Animated Ranking Race

    • Main question: How did the ranking of top metros evolve month by month?
    • Data fields: date columns, RegionName, the monthly values.
    • Encoding: Horizontal bars that reorder as time advances, with a year label.
    • Interaction: Play and pause buttons and a date slider.
    • Implementation note: Use d3 transitions keyed by RegionID, step through the date columns, and show the top 12 at each step.

Comments

Sign in to join the discussion.