Nexma GeoEngine
Jax is your GIS analyst. Ask in plain language — query, join, and analyze every layer of the physical world, from a file you just uploaded to years of live history — and get answers as maps, not spreadsheets.
Legacy Challenges
Traditional GIS makes a human drive every step — wrangle projections, write the joins, stitch tools together. The data sits in silos, and by the time the map is ready, the question has already moved on.
Buffers, joins, projections, exports — each a manual step in a desktop GIS, repeated by hand for every new question.
Core Capabilities
Nexma GeoEngine lets Jax query and analyze every source — uploaded, live, and historical — in natural language, and render the answer straight onto the map.
Describe the question; Jax composes the SQL and spatial operations, runs them, and explains the result. There's no query language to learn.
Product Benefits
Replace days of manual GIS with an agent that analyzes every layer of your world on demand.
Anyone can ask a spatial question in plain language and get a rigorous, sourced answer — no GIS specialist required.
Join a dataset you just dropped in to live telemetry and years of history in a single question, without moving data between tools.
Every result is a live, styled map layer in your project — provenance intact — ready for the next decision.
Feature Details
Jax composes SQL, spatial operations, and optimization over every source, then renders the result.
Jax writes the SQL; an embedded engine runs it — so you never touch a query language unless you want to.
Uploads, the world model, live telemetry, and the lakehouse join in a single statement.
When a project has an ontology, queries are typed and semantic — by entity, property, and unit.
Related Products
One platform for all spatial data and workloads, from design to field operations.
FAQ
It is AI-native spatial analysis. Jax — the platform's agent — answers spatial questions in natural language by composing SQL, spatial operations, and optimization over your data, and renders the result as a map.
No. SQL is one of the things it runs underneath. GeoEngine is the analyst: it interprets the question, chooses the right spatial methods, queries across every source, and returns a styled, sourced map — you never write SQL unless you want to.
Yes. Upload CSV, Parquet, GeoJSON, or shapefiles and analyze them immediately — on their own, or joined to the world model, live telemetry, and historical data.
No. GeoEngine works on raw uploads with no setup. When a project does have an ontology, analysis becomes typed and semantic — but it is never required.