Feature Request: Marimekko

Open
#1,308 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
kotlin

Research direction

Start by locating the Bistro Plots module and reviewing how existing chart types define their inputs and rendering behavior. Use the requested X and Y labels and metrics, including count alternatives, as the acceptance criteria; confirm the result matches the Marimekko examples described in the issue.

Written by the indexing model from the issue text.

Description

*

Marimekko charts

Marimekko charts are able to consolidate two 100% stacked bar charts into one. Consolidating two related metrics helps in presenting the information concisely to viewers and results in eye-catching visuals.

Rationale

Although LetsPlot certainly has the tools to create them, the number of data transformations needed might make Marimekko Bars a good addition to the Bistro Plots module.

Expected inputs

Marimekko charts take four inputs:

  • Labels to use for the X axis.
  • An X axis metric which needs to be accumulated up to the plot size / Alternatively the number of entries of the label is counted.
  • Labels to use for the Y axis.
  • An Y axis metric which needs to be accumulated up to the plot size / Alternatively the number of entries of the label is counted.

Examples

Asset manager regions vs Asset managers per region

Image

Exported product distribution vs Main exporters per product

Image

Renewable energy jobs vs region distribution for each energy type

Image

Chart source

Dominant language
Kotlin
Stars
1.8k
Forks
63
PR merge metrics
No merged PRs in 30d

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from JetBrains/lets-plot

All issues in JetBrains/lets-plot

Similar issues

More Kotlin issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.