Equator¶

Plane: Spatial Plane

Purpose¶

Spatial data management. Equator is the source of truth for maps, floor plans, zones, coordinates, racks, charging stations, landmarks, and geofencing boundaries. It is the write-side of the Spatial Plane — all spatial data is authored and maintained here.

Responsibilities¶

Store and version maps and floor plans
Define zones, geofences, and region boundaries
Manage landmarks (charging stations, docks, pick locations, drop-off points)
Maintain coordinate systems and transformations
Expose spatial data to Marie for querying

Key Entities¶

Entity	Description
Map	A floor plan or site map (raster or vector) with coordinate metadata
Zone	A named region with a boundary polygon (e.g., “Zone A”, “Loading Dock”)
Geofence	A boundary with associated rules (entry/exit triggers)
Landmark	A point of interest (charging station, rack, shelf, elevator)
Coordinate System	Mapping between physical and logical coordinates

API Surface¶

Operation	Description
`POST /maps`	Upload a new map
`GET /maps/{id}`	Retrieve map with metadata
`POST /maps/{id}/zones`	Define a zone on a map
`GET /maps/{id}/zones`	List zones
`POST /maps/{id}/landmarks`	Add a landmark
`GET /maps/{id}/landmarks?type=`	List landmarks by type

Dependencies¶

Service	Relationship
DotID	Authentication and tenant scoping
Org Service	Maps and zones are scoped to accounts

Consumed By¶

Consumer	Usage
Marie	Reads all spatial data for query processing
Execution Manager	Includes map data in execution contracts pushed to devices
Applications	Upload maps, define zones and landmarks