Visualizing the Donors Choose data set with Kibana and Elasticsearch

The Elasticsearch example codebase includes a Donors Choose public data set. The example uses a set of Kibana visualizations. The following image shows a subset of the visualizations used in the dashboard.  

Donors Choose Kibana Dashboard

  • The map visualization uses provided geopoint , Lat and Long, data.
  • You can see there are 
    • 6.2 million donations in the data set.
    • 2 million donations.
    • $500 million in donated
    • Contains data from 2003 through 2018

Video Talk

This talk mostly describes how to get the data set and index it in Elasticsearch and then visualize with the provided dashboard.

Importing the Dashboard

This assumes that you have already indexed the data using the scripts in the GitHub repository. See the related blog pieces for more information.

Connect to the Kibana dashboard.  If you ran Elasticsearch / Kibana locally then the URL is probably:
  • http://localhost:5601
Verify the index exists.  You can explore the fields by clicking on donorschoose
Visualizations bind to index patterns.  Create an index pattern using the new index.
First specify the pattern value you will use to bind to the index
Specify the field to be used for the time series. All Elasticsearch data is time series data.

You should be presented with the fields that make up the donorschoose index pattern fields
The index pattern donorschoose should now appear in the Saved Objects list
Now we are going to load the saved dashboard configuration.  Load donorschoose_dashboard.ndjson from the git repository
The Index Pattern Identifier will have changed so we need to tell the loaded items that they are bound to the index pattern we created above.  Make sure you do this for any/all that are pointed out in the right side panel.  Select donorschoose for any index pattern binding requests.
The dashboard consists of a Dashboard parent and 30+ visualizations. Find and click on the Dashboard parent to launch a connection to the dashboard.

Tha's all folks. You should now see a visualization similar to the one at the top of the blog. Set the date range to start in 2003.

Blogs in this set

Popular posts from this blog

Installing the RNDIS driver on Windows 11 to use USB Raspberry Pi as network attached

Image
I do a lot of my development and configuration via ssh into my Raspberry Pi Zero over the RNDIS connection. Some models of the Raspberry PIs can be configured with  gadget drivers  that let the Raspberry pi emulate different devices when plugged into computers via USB. My favorite gadget  is the network profile that makes a Raspberry Pi look like an RNDIS-attached network device.  All types of network services travel over an RNDIS device without knowing it is a USB hardware connection. A Raspberry Pi shows up as a Remote NDIS (RNDIS) device when you plug the Pi into a PC or Mac via a USB cable. The gadget  in the Windows Device Manager picture shows this RNDIS Gadget connectivity between a Windows machine and a Raspberry Pi. The Problem Windows 11 and Windows 10 no longer auto-installs the RNDIS driver that makes magic happen. Windows recognizes that the Raspberry Pi is some type of generic USB COM device. Manually running W indows Update  or  Upd...
Read more

My blog whispered 'genius'. Turning the content into a video shouted 'chaotic dreck'

Image
 Your content is only as good as it presents 💬 I've had plenty of blog articles that I thought were good enough to put out on the Internet. It was only after I tried to use them as a basis for a video that I realized how chaotic or incomplete they were. AI-Assisted Timeline 2 hours wall clock getting an LLM to create outlines for 6 blog articles 1 hour to generate a blog article from the outline 2 wall clock hours of iteration and ideation and proofreading 4 days of coffee decompression Return to project 6 wall clock hours of iteration with the AI and proofreading Published the article. Immediately found problems 2 wall clock hours of iteration and republished 1 day later LLM found problems while working on other article. 1 wall clock hour of proofreading and iteration 4 days of other stuff including coffee decompression Started video recording Unrecorded hours of swearing 1 wall clock hour of iteration and republished Unrecorded hours of moaning and banging head on table. 2 wall ...
Read more

On Ollama, memory type and runner decide whether a new conversation reuses the cached prompt - 8

Image
This article was revised with later test data. Earlier figures and tables on this page were replaced. Each Ollama runner keeps a prefix cache that can skip re-evaluating a shared system prompt. Nine of seventeen local builds reused the cached system prompt on nearly every new conversation. Four others re-evaluated a 1,024-token batch of it each time. Four more re-evaluated all of it once per system prompt, up to 37 seconds on the largest. The model's memory type and runner set the group, not the prompt. In freemansoft/Flutter-AdaptiveCards a demonstration Dart chat server asks a local Ollama model for an answer as Adaptive Card JSON. That is a strict, closed-vocabulary schema, which a Flutter app renders as interactive UI. The card system prompt that describes the element vocabulary runs to about 3,800 to 4,400 tokens, by the model's tokenizer. The chat server replays up to ten prior exchanges on every turn. Each Ollama runner keeps a prefix cache, so a request whose open...
Read more