Overview

What this is

GIS Tenancy & Spatial (spatial) models a multi-tenant geospatial platform: each organisation's tenant holds its own GIS layers and spatial features, shares them selectively with other tenants, and relies on a spatial engine to detect how features interact across tenant boundaries — surfacing rule breaches as events, disclosing them to the right party under controlled profiles, and reconciling the shared picture.

The domain, in one paragraph

An organisation owns one or more tenants (each with domains); users hold roles with permissions scoped to tenant/layer/feature. A tenant's GIS layers contain spatial features (geometry + properties), and layer shares grant another tenant a level of access (metadata / geometry / read / export). Feature responsibility records who owns or regulates each feature. A spatial evaluation run compares features and records spatial relationships (intersects, within, overlaps, near…); a spatial rule defines which relationships matter and at what severity. A matching relationship, via a trigger definition, raises a spatial event, which is delivered (event delivery) and — where a disclosure profile allows — disclosed to another tenant through a data transfer. Every material action is an audit event, and cross-tenant state is verified by reconciliation checks.

The 21 models by area

🏢 Organisation & tenancy

Organisation · Tenant · TenantDomain — the ownership and tenant-isolation backbone.

🔑 Access & sharing

User · Role · UserRole · Permission · LayerShare — who can do what, and which layers cross tenant boundaries.

🗺️ Spatial data

GISLayer · SpatialFeature · FeatureResponsibility — the layers, the geometry, and who's responsible for each feature.

📐 Spatial evaluation

SpatialEvaluationRun · SpatialRelationship · SpatialRule — the engine runs, the detected relationships, and the rules that judge them.

⚡ Events & triggers

TriggerDefinition · SpatialEvent · EventDelivery — what to watch, the events raised, and their delivery to consumers.

🔒 Disclosure & integration

DisclosureProfile · DataTransfer · AuditEvent — what may be disclosed, the transfers that carry it, and the audit trail.

🔁 Reconciliation

ReconciliationCheck — verifying that shared/disclosed state stays consistent across tenants.

The demo scenario

Northgate Minerals (a mining-company tenant) holds mining lease ML-4471 on its TENEMENTS layer; the State Resources Regulator (a regulator tenant) holds the Koala Conservation Area PA-KOALA on its PROTECTED layer. Northgate shares its tenements layer (geometry access) with the regulator.

A spatial evaluation run (EVAL-2026-0007) detects that ML-4471 overlaps PA-KOALA (≈1.85 M m²) — a critical breach of rule RULE-LEASE-PARK ("a mining lease must not overlap a protected area"). A trigger raises spatial event EVT-2026-000042, delivered to the regulator's endpoint; under disclosure profile DP-REGULATOR the geometry is disclosed via an outbound data transfer (GeoJSON), audited, and later reconciled (RECON-2026-0003, passed). Users, roles, permissions and feature responsibilities complete the tenancy picture — 32 rows across all 21 models.