sehHeiden
I am searching for version to plot two dataframes with the same colon name into a layer each. I tried it in VegLite Json:
{
"$schema": "https://vega.github.io/schema/vega-lite/v5.json",
"data": {
"values": [
{"x": 1, "y": 10},
{"x": 2, "y": 20},
{"x": 3, "y": 15}
],
"name": "data1"
},
"layer": [
{
"data": {
"values": [
{"x": 2, "y": 30},
{"x": 3, "y": 25},
{"x": 4, "y": 35}
],
"name": "data2"
},
"mark": "line",
"encoding": {
"x": {"field": "x", "type": "quantitative"},
"y": {"field": "y", "type": "quantitative"},
"color": {"value": "blue"}
}
},
{
"data": {"name": "data1"},
"mark": "line",
"transform": [
{"filter": {"field": "x", "range": [2, 3]}}
],
"encoding": {
"x": {"field": "x", "type": "quantitative"},
"y": {"field": "y", "type": "quantitative"},
"color": {"value": "red"}
}
}
],
"resolve": {
"scale": {
"x": "shared",
"y": "independent"
}
}
}
What I came up with in Elixir draws the seconds DataFrame so that, it is WWWWAY to high over the correct place and the y range is evenly wrongly scaled:
def create_compare_graph(data_a, data_b, title, col) do
Vl.new(width: 500, height: 300, title: title)
|> Vl.data_from_values(data_a,
only: ["day", col])
|> Vl.layers([
Vl.new()
|> Vl.mark(:line, color: "blue")
|> Vl.encode_field(:x, "day",
type: :quantitative,
title: "Day of the year"
)
|> Vl.encode_field(:y, col,
type: :quantitative,
scale: [domain: [0, 1]],
title: "DF1"),
Vl.new()
|>Vl.data_from_values(data_b,
only: ["day", col])
|> Vl.mark(:line, color: "red")
|> Vl.encode_field(:x, "day",
type: :quantitative,
title: "Day of the year")
|> Vl.encode_field(:y, party,
type: :quantitative,
scale: [domain: [0, 1]],
title: "DF2")
])
|> Vl.resolve(:scale, y: :independent)
end
end
Example Data:
DF1:
day value
| 250 | 0.125
| 251 | 0.13
| 252 | 0.13
| 256 | 0.14
| 257 | 0.14
DF2:
day value
| 250 | 0.36
| 251 | 0.36
| 252 | 0.36
| 256 | 0.36
| 257 | 0.36
If possible I would prefer to do it, in Tucan as the code locks much cleaner with it. ![]()
Trending in Questions
I having some trouble figuring out if I have set myself too strict of standards for my production server. Currently I can handle 75% of r...
New
Documentation
While reading the Scoped Routes section, I noticed that the documentation currently refers to a problem without explainin...
New
Hello,
I know there is an approach for handling lists that allows for optimized traversal, but I can’t recall the specific method (somet...
New
Hi everyone,
I am toying with the idea of building a “match maker” for giving personal help to people that wants to start coding.
I sta...
New
So my question is quite simple and i have found no conclusive answer on forum, google or AI.
Should we use :erlang.float for Integer to ...
New
I recently noticed that Elixir’s Logger defaults its primary log level to :debug when no :logger, :level application configuration is pre...
New
I’m new to elixir and just tried to install the elixirLS extension for VScode(ium) and it is throwing some errors that I would like help ...
New
Other Trending Topics
Edit: 2026 May 15 - This post is archived.
Mob is alive!!
Main docs: mob v0.7.11 — Documentation
A bit of explanation for the slightly c...
New
Hey, I’m Jesse and I’m the main contributor behind Dexter, a full-featured, lightning-fast Elixir LSP optimized for large codebases. It s...
New
I am happy to introduce the very α version of the new programming language compiled to BEAM.
Welcome Cure.
It has literally three kille...
New
Hobbes is a low-level distributed database for the Elixir programming language.
Hobbes provides a simple, safe, and scalable storage lay...
New
Hi everyone!
The first release candidate for the Expert language server project is now available!
We’ve published a press release detai...
New
A little off-topic, but I feel like people here have a good head on their shoulders.
I used to be quite good at making software. Was luc...
New
Categories:
Sub Categories:
Forums
Popular Tags
- #ecto
- #liveview
- #troubleshooting
- #learning-elixir
- #library
- #deployment
- #erlang
- #testing
- #genserver
- #mix
- #absinthe
- #remote-other
- #otp
- #plug
- #how-to-question
- #macros
- #postgres
- #elixirconf
- #channels
- #exunit
- #discussion
- #code-sync
- #podcasts
- #javascript
- #onsite
- #dialyzer
- #docker
- #authentication
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ai
- #ecto-query
- #elixirconf-us
- #blog-post
- #elixir-ls
- #phoenix_html
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #elixirconf-eu
- #api
- #forms
- #metaprogramming
- #hex










Showing Posts 1 to 4- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
sehHeiden
A reply to myself.
VegaLite-datasets_from_values allows several sources.
I tried to apply it with:
Error:
Edited: the error Because chcnage Vl.Data → Vl.data
awerment
Are the domains in the real data significantly different? If so, does setting the scale resolution to
:sharedhelp? (|> Vl.resolve(:scale, y: :shared)Without a legend, independent scales can look confusing, although the chart is correct:
With
:shared:sehHeiden
Sorry,
I did have a data error. And did not change the varible. Therefore they ware out of scale.
I also applied Tucan. Which greatly reduces the amount of code.
The only thing I would like to add is a Legend.
sehHeiden
Solved it somewhat with Annotate.