## Performance evidence update / 18 September 2026 MODALITY PERFORMANCE / EVIDENCE REVIEWED 18 SEPTEMBER 2026 Six million locations. A 14.7 ms filtering core. Different measurement boundaries May 7, 2026 campaign milliseconds · radius filter Lower is better · linear scale from zero 8DB kernel 14.7 Preloaded coordinates · count only DuckDB query 140 Reading and materializing results SedonaDB query 470 Reading and materializing results Historical SF1 report; all shown paths reported 94 matches. Kernel and query timers cover different work, so these are not matched full-query speedups. GeoPandas is also in the source comparison at 13,140 ms; omitted from these bars to keep the other values readable. Read the results, comparison and methods → What happens when models work together? See the separate graphs + time series + spatial benchmark against SurrealDB → 01 Exact geometry / neighbor results 02 Cold & warm latency 03 Index build & footprint Include memory, storage, energy and hardware writes [Read the results, comparison and methods →](/journal/8db-spatial-search-market-context) [See the separate graphs + time series + spatial benchmark against SurrealDB →](/modalities#multimodal-performance) # Spatial data | 8DB Product reference. Reviewed 18 September 2026. Implementation and evaluation scope are stated below. Explore the models (https://8braid.com/modalities) / 8DB Spatial data Put the question in its place. Relate locations, regions and movement to the records and events your application needs to understand. Explore the capabilities See a complete workload Locate · measure · query Model / Spatial data Conceptual diagram [Diagram: spatial representation: conceptual diagram] A path passes through a search region. Nearby observations can be connected to their time and source context. Capabilities What changes Input to value Alternatives Performance Adoption Related articles Reference Start with the operations your question needs. n-dimensional linear/grid indexes Euclidean, Manhattan and Chebyshev metric choices Distinct geographic and point-cloud query paths Documented product scope, reviewed 17 September 2026. The underlying build and deployment must be qualified for your application. Units, coordinate system and metric determine meaning. Historical 2-D radius timings do not measure every dimension, geographic operator or full spatial application. Trajectory support needs its own operator qualification. Connected native models Keep the next question within reach. 8DB documents n-dimensional linear/grid indexes with declared distance metrics. The application opportunity is to combine the spatial candidate set with source-backed records and other models in the same data environment. [Diagram: time series representation: conceptual diagram] Time series Keep the meaning in every observation. Observe · window · analyze Explore model ↗ (https://8braid.com/modalities/time-series) [Diagram: media representation: conceptual diagram] Media Make content part of the answer. Represent · relate · retrieve Explore model ↗ (https://8braid.com/modalities/media) [Diagram: graphs representation: conceptual diagram] Graphs Follow the relationship to a better answer. Connect · traverse · follow Explore model ↗ (https://8braid.com/modalities/graphs) These connections show the models involved in the application design. Compare the supported combination and full workflow with a realistic alternative. Input → usable value / interactive design example Review the evidence around a field inspection 0 1 Receive a location → 0 2 Check coordinates → 0 3 Find nearby assets → 0 4 Connect the evidence → 0 5 Review in context → [Diagram: spatial representation: conceptual diagram] Step 1 / Spatial data Receive coordinates, time and a capture record A path passes through a search region. Nearby observations can be connected to their time and source context. Next: Check coordinates Conceptual application workflow. Qualify the supported operations, external tools, protection and persistence for the complete path. These diagrams are explanatory, not measured results. Read the complete workflow and comparison scope Receive coordinates, time and a capture record Validate units and the coordinate representation Find the relevant asset or spatial neighbourhood Retrieve recent readings, photos and inspection relations Return a localized evidence view for the reviewer The useful response includes input validation, index availability, temporal selection, evidence joins and delivery. Geometry-library kernel timings describe only one part of that path. Compare a realistic alternative. PostGIS offers an extensive spatial function reference. Evaluate the exact geometry/geography functions, index paths and coordinate handling you need alongside 8DB’s mixed-model workflow. PostGIS function reference (https://8braid.com/modalities/https://postgis.net/docs/manual-3.6/reference) Compare equivalent outputs and required guarantees, including the simplest single-product alternative where one exists. A specialist may remain the better fit when its operators, ecosystem or operational maturity are decisive. Combining native models becomes valuable when your actual question crosses them. Performance & resources Measure the work that delivers the answer. Exact result identities or declared spatial error; p95 query/full-response latency; dimensionality; load/index time; update freshness; memory/disk and device footprint. The published comparison below covers selected historical paths and configurations. Keep those conditions attached to the result; it does not measure the complete design example on this page. 8DB spatial | 14.7 ms vs. 140–13,140 ms for GIS tools (https://8braid.com/journal/8db-spatial-search-market-context) What belongs inside the timer and resource budget? For input-to-value testing, declare the input state and the consumer-ready output first. Include parsing, derivation, storage/protection, index readiness, querying, result assembly and delivery as applicable. Identify amortized setup and any work deferred past the finish line. Report database-stage and full-job results separately. Do not add unrelated medians or p95 values, or multiply component speedups into a claimed workflow result. Energy needs measured joules; reduced handoffs alone do not establish a saving. Choose the path that fits your deployment. Verify the supported API/SDK, data format, persistence and indexing behaviour for the release you plan to use. Match the operation-by-modality protection profile and device qualification to the workload. Post-quantum protection (https://8braid.com/pqc) · Plan a workload evaluation (https://8braid.com/build) Related articles Take the next step into the thinking. Benchmark & methods 8DB spatial | 14.7 ms vs. 140–13,140 ms for GIS tools (https://8braid.com/journal/8db-spatial-search-market-context) Explore the measured path, comparison and conditions. Mechanism & application A City of Thirteen Million Entities on a Phone, With No JSON in the Hot Path (https://8braid.com/journal/we-put-a-citys-map-on-a-phone-here-is-what-stopped-us-at-the-planet) Explore the ideas and implementation context behind this capability. Mechanism & application One Sealed Store for Every Shape of Data, and It Works With the Network Gone (https://8braid.com/journal/one-store-for-many-shapes-disconnected) Explore the ideas and implementation context behind this capability. Reference / Reviewed 17 September 2026 Readable, shareable and traceable. This reference explains 8DB’s public modality description (https://8braid.com/modalities#explore) with an explicit workload and selection criteria. It is a documentary review, not fresh execution of every operator or platform. Public sources: 8DB modality scope (https://8braid.com/modalities) ; PostGIS function reference (https://8braid.com/modalities/https://postgis.net/docs/manual-3.6/reference) ; the related articles above. Internal source leads and outstanding release checks remain in the editorial record. Download this reference (https://8braid.com/modality-reference/spatial.md) Evaluate the question your application needs to answer. Bring the data shapes, input state, expected output and the systems you use today. Define a comparison around that complete job. Discuss your workload (https://8braid.com/build)