Simple HTTP PUT examples for GrapheneDB

100%

Simple HTTP PUT examples for GrapheneDB

✓ Published0🌍 Public

Last edited Sep 7, 2014

Created on Sep 7, 2014

This example demonstrates how to query and return named nodes from a Neo4j graph database via HTTP, using simple `POST` requests to GrapheneDB’s Cypher endpoint. It shows both a basic match-all query and a parameterized query that filters by a specific name value. The code relies on the command-line HTTP client `http` with authentication flags, sending queries as form-encoded data to the `/db/data/cypher` endpoint, with parameters passed as a JSON string. The visualization highlights the raw request-response interaction rather than rendering graphical output, focusing on the API’s syntax for executing Cypher queries remotely.

AI-generated description

Similar vizzes

Loading thumbnail…

Neo4j REST example

This example demonstrates a graph visualization of a Neo4j query result, showing how a single person node (e.g., “Stanley Kubrick”) is returned and rendered as a node in a force-directed layout. The code issues a Cypher POST request to the Neo4j REST endpoint, then uses d3.forceSimulation to position the node and draw it with SVG circles and labels. The visualization focuses on the raw response data, displaying only the returned `a` object without additional graph traversal or styling beyond basic node rendering.

CCliffordAnderson

62% match

Loading thumbnail…

Graph Gist

This example renders a small Cypher query result as an interactive force-directed graph. It uses d3.forceSimulation to position nodes and links, displaying person and database entities with their LIKE relationships from the Neo4j sample data. The graph draws SVG circles and connecting lines, with labels for each node, and updates positions through the simulation's tick events.

CCliffordAnderson

60% match

Loading thumbnail…

Graph Gist

This example shows a small graph of people and their database preferences, capturing two `Person` nodes connected by `LIKE` relationships to database nodes labeled `Database`, `NoSql`, and `Graph`. The visualization renders this graph data using D3.js, likely with a force-directed layout (`d3.forceSimulation`) to position nodes and links, and possibly `d3.geoPath` or standard SVG/CSS for shapes and labels. The source code, authored by CliffordAnderson and stored as a Gist, explicitly creates the nodes and relationships with Cypher, returning them for immediate display. The result emphasizes how graph structures and their labels can be directly mapped from query output to interactive visual elements.

CCliffordAnderson

59% match

Loading thumbnail…

Graph Gist

This example demonstrates a simple graph visualization of two people and their database preferences. It shows nodes for "You" and "They," each linked via a `LIKE` relationship to database nodes representing Neo4j and eXistDB. The data comes from a Cypher query that creates the graph structure, and the visualization renders it using the D3.js library with a force-directed layout. Specifically, `d3.forceSimulation` drives node positioning, while SVG elements for circles and lines represent entities and relationships. The graph is rendered as an interactive network, highlighting the connections between the person nodes and their chosen database technologies.

CCliffordAnderson

58% match

Loading thumbnail…

Graph Analysis for the Humanities

This workshop introduces humanities scholars to graph-based data modeling and analysis, presenting a series of hands-on exercises that build from introductory Neo4j concepts to practical applications. It demonstrates how to create graph data models, write Cypher queries, and render interactive visualizations in the browser. The material shows loading Berlin metro data from Wikidata via XQuery and BaseX, then visualizing those connections with Neovis.js, a JavaScript library built on Neo4j's Bolt protocol. The exercise set culminates in web development, using a Python SimpleHTTPServer to deploy graph-based websites.

CCliffordAnderson

58% match

Loading thumbnail…

A Cypher examples to unwind and collect

This example demonstrates two Cypher queries that find the shortest path between two named nodes, “Daniel” and “Jerry,” in a Neo4j graph and then process the resulting path’s nodes. The first query, `unwind.cypher`, uses `nodes(s)` to extract the path’s vertices, `unwind` to iterate over them, and returns each node’s `name` property as a column. The second query, `collect.cypher`, chains `unwind` into `collect` to aggregate all names into a single list, then `head(m)` retrieves the first element. Both queries rely on Neo4j’s `shortestPath` function to compute the route.

CCliffordAnderson

56% match

Loading thumbnail…

Data wrangling for ArcGIS to Cypher

This example shows how raw tabular GIS data is wrangled into a node-and-edge format suitable for importing into a graph database like Neo4j via Cypher. It extracts distinct pairs of connected points from an ArcGIS feature table by computing start and stop coordinates from X/Y fields and their offsets, then filters out self-loops where start equals stop. The code uses the XQuery language with the `fn:distinct-values`, `fn:data`, and `string-join` functions to build a comma-separated list of connected node IDs and edge lengths. It explicitly demonstrates the data-cleaning step—removing duplicate or invalid connections—before the result is ready for Cypher’s `LOAD CSV` or `MERGE` commands.

CCliffordAnderson

54% match

Loading thumbnail…

Cypher for determining distance between points using shortest path

This example demonstrates how to calculate the distance between two points in a graph using Cypher's shortest path algorithm. The query first matches two nodes by their IDs, then applies `shortestpath` to find the minimal path between them. Using the `reduce` function, it iterates over the relationships in that path, summing the `distance` property of each relationship to return the total distance in meters. The visualization relies on the Neo4j graph database and its Cypher query language, with the underlying graph structure and relationship properties providing the data for the calculation.

CCliffordAnderson

54% match