Google Earth AI Puts Geospatial Agents to Their First Serious Test
Google has released the most substantial public evaluation yet of its experimental Geospatial Reasoning Agent. The headline is not simply that Gemini can operate geospatial tools. It is that Google has started to measure what happens when a language model is given domain-specific data, specialist models, explicit planning and a workspace for processing planetary-scale information.
The results support a growing belief across GeoAI: access to the right tools matters more than fluent conversation. They also reveal why geospatial agents are not ready to replace expert judgment.
From chatbot to analytical system
The agent links Gemini with 23 skills and 62 tools, according to Google’s technical report. These include Google Earth Engine, Maps Platform and Data Commons, alongside Earth AI capabilities for weather, floods, population dynamics and satellite embeddings.
Before execution, the full system creates a plan. It then processes large datasets in a separate spatial workspace instead of forcing coordinates, rasters and intermediate results into the model’s context window. Google says users can inspect the plan and sources, and can add private CSV, GeoJSON or cloud-table data.
That architecture is more consequential than the chat interface. It treats the language model as an orchestrator of spatial methods, rather than pretending the model already contains a GIS.
What the benchmarks show
Google compared four configurations: a standalone Gemini model, Gemini with basic search and maps tools, Gemini with Earth AI tools but no initial plan, and the complete agent.
On GeoExpertQueries, which contains open-ended tasks created by geospatial specialists, the full agent using Gemini 3.8 Flash scored 62.7. The tools-only configuration scored 52, while the basic baseline was close to 3. On GeoKTools, a more deterministic test requiring one to four tools, the full agent reached 85.9, versus 41 for the strongest baseline. Google also reports scores above 80 on the community-developed CBGB coding benchmark, where the baselines remained below 20.
Those are large gains. They suggest specialist capabilities are doing most of the work, with explicit planning adding value on longer, less structured analyses. Interestingly, the less expensive Gemini 3.8 Flash configuration outperformed Gemini 3.1 Pro across all four reported benchmarks. Google estimates token inference costs at about $0.20 per GeoExpertQueries task for Flash, excluding external data and computation.
The evaluation also deserves credit for exposing a saturated benchmark. A standalone model scored 93.6 on UnivEARTH, probably because source material and answers were already available online. That makes the benchmark a weak discriminator of real spatial reasoning.
The most important limitation
The 62.7 score is easy to overread. GeoExpertQueries contains 101 tasks, with 76 held out for testing. Its automatic evaluator compares the agent’s trace with expert-authored workflows. It explicitly does not establish whether the final numbers, arithmetic or conclusions are correct, and it does not penalize missing maps or charts.
In other words, the benchmark asks whether the agent followed a credible analytical route, not whether it arrived safely. Google itself describes the outputs as strong first drafts for expert review, not authoritative answers.
That distinction is critical in public health, disaster response and infrastructure planning. A plausible workflow can still use the wrong boundary, date, denominator or spatial resolution. Releasing only the development splits of the two new benchmarks also limits independent reproduction of the headline results.
A stronger competitive signal
The broader market is moving in the same direction. Esri is developing agents built around authoritative ArcGIS data and controlled workflows. CARTO has exposed platform capabilities through the Model Context Protocol. Academic projects such as GeoNatureAgent are testing open, fixed-tool environments with strict pass-or-fail checks.
Google’s advantage is the breadth of its proprietary planetary data and models. Its disadvantage is that many organizations will not want a single vendor to mediate their data, reasoning and infrastructure. Governance, reproducibility and portability may matter as much as benchmark performance.
Public discussion has so far focused more on access to the experimental Ask Google Earth experience and agent-to-agent API than on validation. That imbalance is telling. The most urgent question is not whether an agent can produce an impressive map quickly. It is whether another analyst can reproduce the result, inspect every assumption and know when the system is wrong.
Google has not solved that problem. But by publishing a comparative evaluation and stating the limits clearly, it has given the geospatial industry a more useful starting point than another polished demo.
Disclosure of claims: Benchmark values, partner examples and cost estimates are reported by Google and have not been independently reproduced for this article. Benchmark design details are confirmed in Google’s published technical report. Experimental access remains limited.
How do you like this article? Read more and subscribe to our monthly newsletter!