Skip to content

Query

Query builds a graph search from visible controls. You do not need to write a query language.

On the Write tab, begin with FIND:

  1. Choose a node type, or leave it as any node.
  2. Add anchor filters when needed.
  3. For each filter, choose a field or property, an available operator, and a value.
  4. Use AND or OR to control how multiple filters combine.

Operators depend on the value type and may include equality, inequality, comparisons, membership, existence, contains, and starts-with.

Enable CONNECTED to find nodes reachable from each anchor. Configure:

  • direction: any, outgoing, or incoming;
  • target node type and edge type;
  • a hop range from 1 to 5;
  • optional filters on target nodes and traversed edge properties;
  • whether every traversed edge or any traversed edge must match edge filters.

A one-hop query checks direct neighbors. Higher ranges can traverse intermediate nodes before reaching the result.

In SHOW, choose a limit from 1 to 200. Global is the default and searches the whole graph. You can instead choose a focused Scope, a spatial layout, or the visible content layers sent from Atlas. A focused Scope contains all its selected nodes, including nodes that are not currently placed on any Canvas. A spatial layout contains nodes targeted by effective linked geometry; unlinked, relationship-linked, and layout-linked features do not add nodes. An Atlas scope is the deduplicated union of those existing per-layout memberships. Then choose an optional sort field—name, type, created, or updated—and its direction.

Scoped connected queries stay entirely inside the selected member-node set, including anchors, intermediate nodes, and targets. For an Atlas selection, that set is the union of all selected layouts. Relationships are eligible when both endpoints are members; overlapping content, touching layout outlines, and geometry contact do not create graph connections.

Choose Run query. Validation stays in the builder when required pieces are missing or incompatible.

The Results tab groups output into Anchors, Connected, and Edges as applicable. Select a row to open that node or relationship. Use More to load another result page when available.

Choose Add to Scope to apply the complete query, not only the currently loaded page. Add once pins every anchor and connected match at the current query scope and viewed time. Keep updated saves the query as a dynamic Scope rule; it is available for Global queries and follows the all-time graph. Edges remain query results rather than Scope members. See Scopes for update and removal behavior.

The History panel stores prior project queries. Select one to load its configuration back into the builder; history has no rename, manual save, or delete action.

Queries run at the current project time. If you switch project or viewed time, results from the previous context are hidden until the query runs again.