Dominik Moritz

@drgould Is there anything we can help with to get this pull request over the finish line?

Thanks for the update and good luck with the new direction @drgould. @wmarques do you have time to take it from here?

Since it's not merged, no. Please help us push it over the finish line if you need it.

I think it would be great to support additional transforms in lookup. I remember that there were similar requests in the past.

I also consider this a bug. We should map the range to [0..max] but 0 should map to a circle that doesn't have an empty area inside.

Instead of setting the domain, we should set the range. ``` { "$schema": "https://vega.github.io/schema/vega-lite/v2.json", "width": 500, "height": 300, "data": { "url": "data/seattle-weather.csv" }, "encoding": { "color": { "field": "weather", "type":...

I wonder whether this is actually a Vega bug. With size 1, points are visible and even have a hole, while with size 0, they completely disappear. The documentation says...

Hmm, if we set the size of points to less than 1, we get thinner strokes. I wonder whether there is a way to get filled circles of radius 1...

Can you show an example in Vega? I can implement it in Vega-Lite afterwards.

Something like ```json { "$schema": "https://vega.github.io/schema/vega/v3.0.json", "autosize": "pad", "padding": 5, "width": 500, "height": 500, "style": "cell", "data": [ { "name": "source_0", "url": "https://vega.github.io/vega-datasets/data/seattle-weather.csv", "format": { "type": "csv", "parse": { "precipitation":...