Query signature
location root query returns a single location by ID. For browsing the hierarchy, use locations nested on Building or Location.
All root queries require
siteId. See multi-tenant scoping. Examples below omit siteId for brevity.Arguments
| Argument | Type | Description |
|---|---|---|
siteId | String! | Required. Scopes the query to a specific site |
locationId | String! | Required. Location identifier |
Return fields
| Field | Type | Description |
|---|---|---|
uri | String! | Full entity URI |
id | ID! | Location identifier |
name | String! | Location name |
type | String! | Brick class (Wing, Floor, Room, etc.) |
ifcId | String | IFC model element ID |
properties | [EntityProperty!]! | Static metadata (name, value, unit) |
locations | [Location!]! | Child locations. Accepts name, nameMatch, is, recursive filters |
parent | Location | Parent location |
equipment | [Equipment!]! | Equipment at this location. Accepts name, nameMatch, is, recursive filters |
points | [Point!]! | Points at this location. Accepts name, nameMatch, is, recursive filters |
zones | [Zone!]! | Zones within this location |
Spatial hierarchy
Buildings contain a nested hierarchy of locations:Examples
Browse the full spatial tree
Start from a building and drill into its location hierarchy:Get a specific location with its equipment
Filter locations by type
Find only floors (skip wings):recursive: true flattens the hierarchy, returning all floors across all wings in a single list.
All equipment on a floor
Navigate up with parent
Locations vs zones
Locations represent physical space: where things are. Zones represent conditioned space: what equipment serves.| Concept | Example | Query |
|---|---|---|
| Where is this AHU? | Tower East Level 1 | equipment { location { name } } |
| What space does this VAV cool? | Library zone | equipment { feeds { name } } on zone |
location for spatial questions, zones for HVAC questions.