Databases
AuraScore 83/100

Construction Project Spatial Indexing Readiness Checklist

Prepare PostGIS and spatial index structures for high-density CAD, GIS, and job-site telemetry datasets.

Deploy this checklist when configuring geospatial queries and bounding box indices for construction site databases. It establishes query performance baselines and storage bounds.

Template

Role: Principal Spatial Data Engineer specializing in civil engineering, CAD, and geospatial database infrastructure.

Context

  • Target Database: {{spatial_database_name}}
  • Coordinate Reference System: {{target_srid}}
  • Monitored Geometry Types: {{cad_layer_types}}
  • Ingestion Rate: {{average_daily_ingest_volume}}
  • Latency SLA: {{query_latency_sla_ms}} ms
  • Target Compute Tier: {{db_instance_tier}}

Task

Produce an operational readiness checklist to configure, index, and benchmark spatial query layers in {{spatial_database_name}} for {{cad_layer_types}} under a {{query_latency_sla_ms}} ms latency ceiling.

Method

  1. Inspect coordinate reference system alignment to ensure all incoming geometries standardize to {{target_srid}} prior to insertion.
  2. Evaluate spatial indexing algorithms (e.g., GiST, BRIN, or SP-GiST) based on {{average_daily_ingest_volume}} and spatial distribution.
  3. Validate geometry simplify and topology validation triggers for uploaded CAD polygon boundaries.
  4. Design vacuum and statistics sampling frequencies suited to high-volume updates on {{db_instance_tier}}.
  5. Audit spatial partition strategies (e.g., by project site or geographic quadkey) to contain index size bloat.
  6. Formulate synthetic bounding box query benchmarks to test throughput against the {{query_latency_sla_ms}} ms SLA.
  7. Verify spatial extension configuration parameters (e.g., work_mem, maintenance_work_mem) for spatial joins.

Constraints

  • MUST mandate geometry validity checks (e.g., ST_IsValid) before index population.
  • MUST NOT recommend full-table spatial scans for any real-time site query.
  • Every checklist item MUST specify a metric-based threshold.
  • Configuration items must fit within the compute resources of {{db_instance_tier}}.

Output format

Provide a technical checklist divided into: 'Spatial Schema Configuration', 'Index Optimization & Tuning', and 'Query Performance Benchmark'. Use Markdown task lists with columns or bullet fields for Check Item, Configuration Setting, Validation Query, and Target Metric. Limit the output to 12 to 18 actionable checklist items.

Self-review

  • Check that the specified SRID ({{target_srid}}) is consistently referenced.
  • Validate that index tuning instructions match {{db_instance_tier}} constraints.
  • Confirm the benchmark section explicitly enforces the {{query_latency_sla_ms}} ms limit.
AuraScore breakdown
83/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 efficiency7/10 · Adequate

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
postgis
gis
spatial-indexing