Databases
AuraScore 85/100

Spatial Engine Evaluation Matrix for Real Estate Portfolios

Compare spatial database engines to optimize parcel boundary lookups, GIS integrations, and multi-tenant PropTech performance.

Use this template when evaluating geospatial databases or extensions for real estate asset mapping and zoning queries. It helps database leads select the best spatial indexing engine based on throughput and cost constraints.

Template

Role: Lead Spatial Database Architect specializing in geospatial property registries and multi-tenant proptech platforms.

Context

  • Target PropTech Environment: {{proptech_platform}}
  • Core Spatial Dataset: {{spatial_dataset_type}}
  • Expected Query Load: {{query_throughput_target}}
  • Capital and Operational Tier: {{storage_budget_tier}}
  • GIS Interoperability Standard: {{gis_integration_standard}}
  • Cloud Host: {{cloud_infrastructure_provider}}

Task

Synthesize geospatial database engine options into a structured comparison matrix to determine the optimal spatial index and storage topology for parcel boundary tracking.

Method

  1. Parse the {{spatial_dataset_type}} polygon and multipolygon complexity parameters.
  2. Benchmark bounding box search index efficiency across prospective spatial engines.
  3. Assess geo-partitioning capabilities against {{query_throughput_target}}.
  4. Evaluate alignment with {{gis_integration_standard}} for CAD and BIM spatial layer exports.
  5. Model operational overhead and managed service pricing within {{storage_budget_tier}}.
  6. Map latency characteristics under peak concurrent tenant lookups on {{cloud_infrastructure_provider}}.
  7. Score candidates across functional criteria to produce the evaluation matrix.

Constraints

  • MUST evaluate at least 3 distinct spatial database candidates.
  • MUST NOT recommend unmanaged bare-metal solutions exceeding {{storage_budget_tier}}.
  • Scoring must use a strict 1-5 integer scale with defined criteria.
  • Recommendations must reference native indexing support for {{spatial_dataset_type}}.

Output format

  • Section 1: Executive Spatial Landscape Summary (max 100 words).
  • Section 2: Spatial Engine Comparison Matrix (Markdown table with columns: Engine, Spatial Index Type, Ingestion Speed, Query Latency, {{gis_integration_standard}} Compatibility, Cost Score 1-5, Weighted Rank).
  • Section 3: Final Engine Selection and Tradeoff Rationale (max 150 words).

Self-review

  1. Confirm all 6 variables are represented in matrix evaluation criteria.
  2. Verify the matrix contains exact comparative columns with integer scores.
  3. Ensure the word counts and structural constraints are strictly met.
AuraScore breakdown
85/100Provisional
Instruction clarity15/15 · Strong

Explicit role, a named task, and discrete steps the model can follow.

Context architecture12/12 · Strong

Background, inputs and variables the model needs before it starts.

Constraint engineering12/12 · Strong

Hard boundaries — what the model must and must not do.

Output specification6/14 · Thin

A named, field-level shape for the response.

Reasoning structure10/10 · Strong

Ordered work items that force analysis before an answer.

Model compatibility10/10 · Strong

Length and structure that travel across frontier models.

Token efficiency9/10 · Strong

Signal density — instruction weight without padding.

Reusability7/7 · Strong

Documented variables so the scaffold adapts to new inputs.

Robustness3/5 · Adequate

Quality bar, assumptions and behaviour when inputs are thin.

Observed performance1/5 · Thin

How much real usage the template has behind it.

developers
developers-databases
real-estate-construction
proptech
geospatial
gis