Object Explorer
The typed instance browser. Query, filter, and inspect every object in your world by type — the structured, tabular view onto the DataStore, driven entirely by the active ontology.
Legacy Challenges
A map shows where things are, but not the structured answers operators need. Finding every asset of a type, filtering by attribute, or auditing a class of objects falls back to exports and spreadsheets.
The map can't answer 'show me every overdue inspection' as a sortable list — so teams export to a spreadsheet that's stale on arrival.
Core Capabilities
Object Explorer reads the DataStore through the active ontology, giving every entity type a typed, queryable, tabular surface.
Tabs are generated from the ontology — closures, valves, transformers, waypoints — each with the columns that matter for that type.
Product Benefits
Give operators a typed, live, structured view of every object — no exports, no stale spreadsheets, no guessing.
The explorer reads the same DataStore as the map, so the table is always current — no copy that drifts the moment you export it.
Because every object is typed by the ontology, filtering, sorting, and validation are built in rather than hand-rolled per dataset.
Select an object in the table to locate it on the map, or pick it on the map to open its full record — one world, two views.
Feature Details
Object Explorer turns the DataStore into a structured, queryable surface driven by the active ontology.
Tabs and columns are generated from the ontology, so the browser matches your domain automatically.
Open any object to see its full typed record, geometry, and connected entities in one place.
Jump between a table row and its location on the map in either direction, keeping context.
Related Products
One platform for all spatial data and workloads, from design to field operations.
FAQ
It is the typed instance browser for your world — a structured, tabular view onto the DataStore. You query, filter, and inspect every object by type, with tabs and columns generated from the active ontology.
The map answers where; the explorer answers which and what. It gives operators sortable, filterable lists of typed objects — every overdue inspection, every asset of a class — alongside the map, reading the same live data.
Yes. The explorer reads the same DataStore as every other surface, so the table is always current. There's no export that goes stale the moment it's created.
It runs queries against typed indexes rather than raw geometry, and pages and gates high-cardinality types, so it stays responsive across hundreds of thousands of objects.