Get people appearing with a list of people from NewsReader

100%

Get people appearing with a list of people from NewsReader

✓ Published0🌍 Public

Last edited Jun 6, 2014

Created on Jun 6, 2014

This visualization maps the co-occurrence of people mentioned in news articles, showing which individuals appear alongside a list of queried names from NewsReader. The code retrieves data by iterating through paginated JSON requests to the NewsReader API, using the `requests` library to fetch actor pairs and their associated event counts. It filters results for names like David Beckham and Sepp Blatter, saving each co-occurrence record via `scraperwiki.sqlite` into an "actors" table. The example demonstrates a network-style data pipeline where connections between people are extracted from structured news metadata, though it does not include any client-side rendering or charting library.

AI-generated description

Similar vizzes

Loading thumbnail…

Get a timeline from the NewsReader API

This visualization builds a chronological timeline of events involving the actor Mohammed bin Hammam by querying the NewsReader API, which returns event summaries linked to a specific DBpedia URI. It shows how each event’s size and timestamp are recorded, with the timeline displaying event occurrences over time. The code uses the `requests` library to fetch paginated JSON data, parsing the response to extract event details, and saves the results to an SQLite database via `scraperwiki.sqlite.save`. The timeline itself is not rendered here; the script only collects and stores the temporal data.

IIanHopkinson

66% match

Loading thumbnail…

For Jim Duran & co.

This example shows a list of reporter names extracted from a single XML data column, tokenized by pipe delimiters into an array of individual contributors. The code uses the XQuery function `fn:tokenize` on the text of a `<column>` element named "Reporters" and returns the resulting sequence of names. The visualization itself is minimal, relying on the query language’s string-handling API rather than a graphical library, making it a data-cleaning step rather than a rendered chart. The source is a gist by CliffordAnderson, and the output simply displays the parsed names.

CCliffordAnderson

57% match

Loading thumbnail…

Actor Graph

This interactive visualization displays a force-directed graph of actors and the movies they appear in, where each actor is represented as a node and connections between actors who share a film are shown as links. The graph is built using D3.js v7, with the `d3.forceSimulation` API handling node positioning and link physics. Data comes from a CSV file listing movies and their cast, parsed using `d3.csvParse`, and rendered as SVG elements (circles, text labels, and lines). The visualization explores collaborative networks among actors across the included film dataset.

KKyle?

56% match

Loading thumbnail…

NO a priori knowledge needed to detect anything about a web page

This example visualizes the distribution of JavaScript event listeners attached to DOM nodes on the BBC and CNN homepages using data from JSON dumps supplied in the gist. It shows which event types occur most frequently and how many listeners are registered per element, with node IDs and tag names labeled directly in the visualization. The React-based interface renders the listener counts using D3’s hierarchical layout and color-coded circles, while node-specific data is processed from the `listenerCount` and `listenersPerNode` objects. The code relies on `d3.hierarchy` and `d3.pack` to generate the bubble chart from the provided JSON files.

NN0taN3rd

55% match

Loading thumbnail…

Gist ea92be31b5382266079042e50d4f7de6

This example visualizes a dataset of comedians stored in a CSV file, plotting each person as a node in a force-directed graph. It shows the relationship between name, city, and email by positioning nodes using `d3.forceSimulation`, with the city serving as a categorical grouping. The rendering relies on D3’s selection and data-binding methods to draw circles and text labels, while the CSV is loaded via `d3.csv`. The code does not include interactive features or additional layout constraints; it simply maps the three fields into a basic spatial arrangement, emphasizing the distribution of comedians across cities.

WWill Carter

54% match

Loading thumbnail…

Gist b541552eb18726aea9a989003304b013

This visualization shows a network of Premier League players as connected nodes, with each player’s node size and position determined by a custom weight calculation. The code, written in Python, uses a pandas DataFrame to compute an `in_weight` for each player by combining fixture difficulty, current form, and the chance of playing this round, with negative weights clamped to zero. The rendering approach is not shown in the code, but the visible structure suggests a force-directed or scatter-plot layout, likely built with a library like D3.js or Plotly. The data source is a player statistics table, with the weight influencing node prominence.

CConorAspell

53% match

Loading thumbnail…

Gist 98aa71734dd0d7e9e89fd00440c278c4

This example demonstrates a database-driven player lookup interface, showing how stored player records are retrieved and displayed based on email queries. The code uses the `sqlite3` Node.js library to execute SQL queries, with `getPlayers` fetching all records and `getPlayerByEmail` filtering by a specific email address. The visualization likely renders the resulting name, city, and email data in a table or list format, though the exact visual output is not shown. The implementation relies on promise-based asynchronous database access, where each function returns a promise that resolves with the queried rows, making it suitable for integration with a frontend framework or a simple server response.

WWill Carter

53% match

Loading thumbnail…

Gist 752e79ef7b1d634b16a9e7020da164ff

This visualization presents a narrative chart that maps character appearances and introductions across scenes in a story. Using D3.js’s narrative layout, it positions scenes horizontally and characters vertically, encoding each character’s presence as small black ellipses within scene clusters. The code employs mxGraph to render the final graph, with curved edges connecting characters across scenes. Appearance vertices are placed at precise scene coordinates, while introduction labels sit beside the timeline, with links drawn between these points. The underlying data wrangling occurs in a dedicated function that groups scene characters by ID, and the graph is exported as XML via mxCodec.

HHugoberry

53% match