# How upfront planning became a measurable part of geospatial agents

How Earth AI’s geospatial-agent evaluation makes upfront planning a testable design choice, while separating planning quality from extra computation.

Author: Retrivium editorial team
Language: en
Analysis published: 2026-11-03
Event date: 2026-10-14
Original announcement: https://research.google/blog/putting-earth-ai-to-work-geospatial-agents-for-our-planets-biggest-challenges/
Canonical URL: https://retrivium.ai/retrospectives/earth-ai-planning-before-execution/

The Earth AI announcement discusses agent configurations with different tools and planning stages. This makes a useful retrospective question concrete: when does writing a plan improve an investigation, and when does it merely add another model call?

## The dated path

- 2025-07-30: [Google Earth AI: Our state-of-the-art geospatial AI models](https://blog.google/innovation-and-ai/products/google-earth-ai/).

- 2025-07-30: [AlphaEarth Foundations helps map our planet in unprecedented detail](https://deepmind.google/blog/alphaearth-foundations-helps-map-our-planet-in-unprecedented-detail/).

- 2026-10-14: [Earth AI expands experimental geospatial agents](https://research.google/blog/putting-earth-ai-to-work-geospatial-agents-for-our-planets-biggest-challenges/).

## Why planning became a separate component

A complex question may require several operations whose order matters. Choosing data after starting a calculation can lead to avoidable rework or unsupported shortcuts. Our interpretation is that a planning stage offers an explicit place to inspect those dependencies before execution. Its value lies in the resulting choices, not in the presence of a polished plan paragraph. A plan that lists plausible steps without checking available evidence can still lead the system toward an invalid result.

## The comparison needs an appropriate control

An agent with a planning stage may also receive more reasoning time or more opportunities to inspect the task. A useful experiment distinguishes those changes from the effect of dependency-aware planning itself. Keep tools and task conditions comparable, record the execution budget and inspect what actually happened after the plan. This is an evaluation argument, not a claim that any single published comparison settles every mechanism. The point is to avoid attributing a combined system improvement to the most visible named component alone.

## A counterfactual based on an unavailable input

Give the agent a task whose preferred dataset is unavailable but a defensible alternative exists. A useful plan should identify the missing input, explain the alternative and preserve the changed assumptions through execution. A weak plan may continue as though the preferred evidence were present. This test examines planning as a commitment about dependencies. It is more informative than asking whether the generated plan sounds methodical, because the later operations reveal whether the stated constraints influenced the work.

## What a provider can learn from the trajectory

The earlier Earth AI model collection made specialized capabilities available; the later agent work asks how those capabilities are coordinated. For infrastructure, that means a plan can be a versioned job artifact linked to tool calls and outcomes. The October system remains experimental, and a benchmark score should be interpreted within its stated evaluation method. The historical lesson is to make orchestration choices measurable. A provider can then inspect whether extra computation improved the investigation rather than merely producing a longer explanation of the intended work.

## Technical background

Related engineering context: [Controlled evaluation](/journal/inference-benchmark-method/); [Execution traces](/journal/provider-request-id-trace-context/).