
- Key Takeaways
- NASA Earth Action Begins With a Decision, Not a Dataset
- How the Earth Science to Action Strategy Reorganizes NASA’s Value Chain
- User-Centered Science Changes Who Defines Success
- Earth Observation Becomes Useful Through Translation and Trust
- Strong Proposals Join People, Science, and Management
- Application Readiness Levels Turn Adoption Into a Measurable Path
- Project Management Determines Whether Tools Survive Funding
- What NASA Earth Action Means for the Space Economy
- Summary
- Appendix: Useful Books Available on Amazon
- Appendix: Top Questions Answered in This Article
- Appendix: Glossary of Key Terms
Key Takeaways
- NASA Earth Action starts with user decisions, then develops products around operational needs.
- Strong proposals combine proven science, committed partners, measurable impact, and transition planning.
- Open data gains public value when teams translate it into trusted tools that fit established workflows.
NASA Earth Action Begins With a Decision, Not a Dataset
In June 2026, NASA published its 84-page Earth Science Applications Guidebook around a direct premise: Earth science creates public value when people can use it to make decisions. The guidebook divides that work into understanding NASA Earth science, developing an Earth Action proposal, and managing a funded project. Its emphasis is less on producing another map or model than on creating an application that a named organization can adopt, operate, and sustain after NASA funding ends.
That framing places NASA Earth Action at the end of a long information chain. Sensors measure the planet from satellites, aircraft, and ground systems. Researchers convert those measurements into calibrated records, models, and scientific findings. Data systems store and distribute the results. Earth Action connects those assets to decisions involving disasters, agriculture, water, health, public safety, infrastructure, environmental management, and commerce.
The distinction between research and application is important. Research may establish that a measurement or model works. An application must show that the output answers a defined need, arrives at a useful time, fits an established workflow, and earns enough confidence to influence action. A technically impressive product can fail if a county emergency office cannot interpret it during a fire, a water authority cannot integrate it into an existing system, or a farm agency receives information too late for planting decisions.
NASA’s approach reflects a broader change in Earth observation. The field has moved from delivering images toward providing decision services, automated alerts, repeat measurements, and analysis-ready products. New Space Economy’s examination of Earth observation and public safety describes satellites as part of the operating systems used by emergency agencies, weather services, insurers, utilities, and city planners.
That shift does not reduce the need for scientific quality. It raises the standard because an operational user needs clearly stated uncertainty, documented limitations, reliable access, and a known response process. Data must be accurate enough for the intended decision, but accuracy alone does not make a product operationally useful.
How the Earth Science to Action Strategy Reorganizes NASA’s Value Chain
NASA’s Earth Science to Action Strategy for 2024-2034 establishes a decade-long direction for joining observation, research, public exchange, and applied solutions. The strategy presents Earth science as a cycle rather than a one-way pipeline.
Technology and missions generate observations. Research builds understanding. Applications deliver services and tools. Experience from users then informs later research, mission design, data systems, and program choices. NASA describes the strategy’s goal as advancing and integrating Earth science knowledge within a decade so that people can create a more resilient world.
The guidebook’s pyramid diagram presents the same relationship visually. Technology, missions, and data form the base. Earth system science and applied research sit above them. Solutions and societal value follow, with public understanding and exchange at the top. A feedback cycle returns information from users to scientists, developers, and mission planners.
The model means NASA does not regard application as a communications activity added after the science is complete. User needs can shape data formats, delivery speed, model design, validation plans, interface choices, and later observing priorities.
NASA Earth Action organizes much of this work around three principles:
- Scaling successful applications to additional users or regions
- Connecting scientific research with organizations that can apply it
- Designing science around the needs and decisions of identified users
Scaling does not mean copying the same tool into every environment. A product that works for one state, watershed, or agency may require new validation, training, data integration, and governance before another organization can adopt it.
The approach addresses a persistent problem within the space sector. Earth observation programs can produce enormous archives without generating an equivalent increase in practical adoption. Data volume is not the same as decision value.
New Space Economy’s review of the Earth observation market describes the sector as an integrated system of satellites, aircraft, ground sensors, analytics, software, and service delivery. Much of the commercial and public value appears downstream, where observations are combined with computing, local records, domain expertise, and customer operations.
The National Academies’ 2024 midterm assessment continued to examine research, applications, data systems, technology, and observing missions as interconnected parts of the United States’ Earth information capability. That approach recognizes that scientific discovery and societal application depend on many of the same instruments, archives, technical standards, and institutions.
User-Centered Science Changes Who Defines Success
A user-centered project starts with the decision environment. The project team identifies who makes the decision, what action is possible, what evidence the organization accepts, how quickly information must arrive, and which institutional or legal restrictions affect adoption.
Only after defining those conditions does the team determine how NASA observations can contribute. This order reverses a common research pattern in which scientists create a product and later search for an organization that might use it.
The guidebook distinguishes among funded investigators, users, co-developers, decision-makers, stakeholders, and formal partners. Those roles can overlap, but they are not interchangeable.
A user may help design and test a tool. A decision-maker may have the authority to issue an alert, alter a resource plan, or approve an operational change. A stakeholder may receive the benefits without operating the application. A formal partner may have legal responsibilities under an agreement with NASA.
Clear roles prevent a proposal from treating general public interest as evidence of operational demand. A statement that farmers, emergency managers, or communities might benefit is less persuasive than evidence that a named organization has defined a problem and committed staff to the project.
The guidebook recommends a five-task engagement process:
- Understand the institutional and operational setting
- Contact potential users and listen to their needs
- Define the challenge together
- Co-design the proposed solution
- Formalize responsibilities in the proposal
Listening must uncover the real workflow rather than the workflow imagined by researchers. A flood manager may need a threshold and map layer instead of a high-resolution research product. A public health office may need a recurring risk classification connected to notification procedures. A utility may value consistency and continuity more than a new experimental algorithm.
Co-development changes how success is evaluated. Publications, presentations, and model accuracy remain useful measures, but Earth Action asks whether the application was used, whether its use affected an action, and whether the action produced a measurable benefit.
These categories represent different stages:
- Use concerns whether an organization accesses and employs the application.
- Action concerns whether the information changes a decision or activity.
- Benefit concerns the resulting effect on people, institutions, property, health, economic activity, or the environment.
A project may record thousands of downloads without proving operational use. An agency may use a dashboard without changing a decision. A changed decision may still fail to produce the intended result. Separating these stages gives project teams a more accurate picture of impact.
The Group on Earth Observations supports related work on assessing the effects and economic value of Earth observations. Its work examines how geospatial information contributes to public, business, and personal decisions. The underlying principle is similar: observations create value through access, interpretation, use, and resulting action.
Earth Observation Becomes Useful Through Translation and Trust
Satellite data provide broad geographic coverage, repeat observations, access to remote locations, and records extending across decades. They also carry limitations involving cloud cover, revisit timing, instrument failure, atmospheric interference, spatial resolution, and interpretation.
The guidebook advises combining remote sensing with in situ measurements, local records, and other spatial information for calibration, validation, and context. An application should communicate those limitations directly rather than presenting satellite information as complete or certain.
The Landsat program illustrates how continuity and access create value. NASA and the U.S. Geological Survey have collected compatible land observations since 1972, producing the longest continuous space-based record of Earth’s land surface. The archive supports analysis of urban expansion, coastline movement, forest change, crop cycles, water resources, fires, and sudden disturbances.
Landsat data became free and open in 2008. Open access increased the number of researchers, agencies, companies, and nonprofit organizations able to develop services from the archive. Products such as OpenET depend heavily on Landsat’s calibrated record and field-scale resolution.
Open access does not remove adoption costs. Users can still face unfamiliar file formats, large datasets, computing demands, uncertainty, incomplete documentation, and missing local context. New Space Economy’s guide to open Earth observation imagery and its explanation of satellite data analytics show why portals, cloud processing, software, training, and interpretation services sit between raw observations and practical decisions.
NASA’s examples demonstrate what successful translation can look like. OpenET converts satellite observations and several scientific models into daily, monthly, and annual estimates of evapotranspiration at a field-scale resolution of 30 meters by 30 meters.
Evapotranspiration is the movement of water from soil and vegetation into the atmosphere. Measuring it helps growers and water managers estimate how much water crops and other vegetation consume. OpenET information can support irrigation planning, water conservation, groundwater management, and watershed accounting.
The Environmental Protection Agency’s Cyanobacteria Assessment Network converts satellite observations into early warning information for harmful freshwater blooms. The multi-agency program supports federal, state, tribal, and local water monitoring and public health work. It provides accessible interfaces that allow water managers to examine bloom conditions without processing the original satellite records themselves.
Disaster response presents the same translation requirement under severe time pressure. NASA activated its Disasters Response Coordination System on June 23, 2025, in response to the Trout Fire and Seven Springs Fire in New Mexico.
At the request of the Federal Emergency Management Agency and the New Mexico Emergency Operations Center, NASA supplied satellite imagery and data for search and rescue, evacuation planning, and early recovery. Products included fire imagery, burn information, and landslide risk modeling for areas that faced additional flood and debris-flow hazards.
The value came from prepared products, interagency coordination, and delivery to responders. The existence of satellite imagery alone would not have produced the same operational benefit.
Strong Proposals Join People, Science, and Management
NASA Earth Action proposals must present a credible relationship among people, science, and management.
The people track defines users, decisions, collaboration, and adoption. The science track explains the observations, models, algorithms, uncertainty, validation, and technical feasibility. The management track covers staffing, schedule, budget, communications, risk, evaluation, and transition.
Weakness in any track can prevent a technically capable idea from becoming an operational application.
The proposal should begin with a precise problem and a named user. The guidebook presents three useful tests:
- Why does the problem need attention now?
- Why is the proposed scientific approach appropriate?
- Who will use the resulting application?
A team that cannot answer those questions clearly may be too early in development, too broad in scope, or still centered on research rather than application.
User letters and partner participation should describe specific commitments. General statements of support do little to prove that an application fits an organization’s workflow. Stronger evidence can include staff participation, access to operational information, involvement in design reviews, plans for testing, authority to approve deployment, and a path toward long-term ownership.
The proposal also needs a realistic account of constraints. Procurement rules, information security, staffing, training, accessibility, software maintenance, and legal responsibilities can determine whether adoption occurs.
Technical sections should explain why NASA observations suit the decision. Spatial resolution must match the scale of action. Revisit frequency must meet timing needs. Processing and delivery speed must fit the operational response. Accuracy and uncertainty must be described in terms the user can apply.
Ground validation should reflect the places and conditions in which the tool will operate. A proposal should also explain what happens when observations are unavailable, when cloud cover interferes with an optical sensor, or when a model operates outside its validated conditions.
Management deserves equal attention. Earth Action teams may require scientific, technical, communications, engagement, accessibility, and project leadership skills. Budgets should account for user meetings, training, evaluation, documentation, software support, travel where necessary, and transition activities.
A low estimate that funds data analysis but excludes adoption work may create a research product rather than an Earth Action application.
NASA’s 2025 opportunity for user-centered applications with Earth foundation models applied these principles to decision-support tools based on models developed by NASA and IBM.
Projects were required to address a specific end user and decision-making need, include the end user as a project team member, and incorporate feedback throughout development. Projects also had to begin at Application Readiness Level 3 or above and were expected to advance by at least one readiness level for each year of funding.
Application Readiness Levels Turn Adoption Into a Measurable Path
Application Readiness Levels provide a nine-step framework for tracking an application from scientific research through sustained operational use. NASA adapted the idea from Technology Readiness Levels but shifted the focus from the maturity of equipment toward the maturity of an application within a user’s decision process.
A model can be technically mature and still have a low Application Readiness Level if no user has defined the need, tested the output, integrated the product, or approved its operational use.
The framework moves through three broad periods:
- Discovery and feasibility
- Development and validation
- Deployment and adoption
Early work establishes the application concept and demonstrates that the science can address the user’s need. Middle stages involve prototype development, integration, and testing in relevant conditions. Later stages demonstrate the application within the user’s decision process, complete qualification work, and establish sustained use.
Application Readiness Levels require teams to describe evidence. A claim that a tool is ready should be connected to user participation, technical performance, testing conditions, workflow integration, and operational approval.
Progress may be demonstrated through events such as:
- Testing a prototype against historical cases
- Conducting a live operational pilot
- Completing user training
- Integrating the application with an agency system
- Receiving organizational approval for routine use
- Transferring maintenance to a long-term operator
The framework also exposes the transition gap. Research teams may fund scientific development through a grant but lack money or authority for hosting, maintenance, user support, security reviews, licensing, accessibility testing, documentation, and staff handover.
Those activities often determine whether a successful demonstration reaches operational use. Transition planning should begin during proposal preparation, with potential owners, costs, responsibilities, and approval requirements identified early.
Satellite missions benefit from the same advance preparation. The Surface Water and Ocean Topography mission established a SWOT applications program and an early-adopter community to prepare organizations to use measurements of rivers, lakes, reservoirs, oceans, and coastal waters.
Those activities allowed users to explore data requirements, test simulated products, identify limitations, and consider how mission information could fit operational systems before routine mission data became available.
The NASA-Indian Space Research Organisation Synthetic Aperture Radar mission, known as NISAR, launched on July 30, 2025. As of July 24, 2026, NASA identified NISAR as an active mission in its science phase, with data being archived and made openly available through the Alaska Satellite Facility Distributed Active Archive Center.
NISAR uses L-band and S-band synthetic aperture radar to measure changes in land, vegetation, water, and ice. Radar can observe through clouds and during darkness, making it useful for hazards, agriculture, infrastructure monitoring, ecosystem analysis, and land deformation studies.
New Space Economy’s discussion of NISAR and agricultural monitoring illustrates the adoption challenge. Frequent radar observations can reveal changes in crops and soils, but practical use requires converting those measurements into information that agricultural agencies, farmers, insurers, or supply-chain companies can interpret at the required scale and time.
Project Management Determines Whether Tools Survive Funding
Earth Action projects require active management because the work crosses institutions, disciplines, and operational environments. Plans need milestones for scientific development, user engagement, testing, communications, evaluation, training, and transition.
A schedule centered only on algorithm delivery can overlook the time required for approvals, data agreements, software integration, documentation, staff training, and changes in partner leadership.
Sustainability begins near project launch. Teams should identify who will host the application, pay recurring expenses, maintain the code, update data connections, answer user questions, and revise documentation.
The long-term owner may be a government agency, university, nonprofit organization, company, or partnership. NASA funding can develop and demonstrate a service, but sustained use requires an institution with authority, staff, and resources.
Communications support operational work rather than publicity alone. Internal communications keep scientists, developers, managers, and users aligned on requirements and changes. External communications explain the application to leaders, affected communities, funders, and potential adopters.
Good project documentation records assumptions, uncertainty, changes in scope, testing results, responsibilities, and lessons. Those records matter when staff members leave or an application transfers to another organization.
Evaluation should continue throughout the project. Teams need baseline conditions, defined measures, evidence collection, and regular review. The use-action-benefit framework prevents interest or visibility from being mistaken for impact.
A download count may indicate awareness. It does not prove that an emergency manager changed a warning, a water agency altered an allocation, or a health department reduced exposure.
Implementation problems should be expected. Budget pressure, staff departures, new leadership, delayed data, underperforming models, and changing user priorities can affect a project. Transparent communication and adaptive planning allow teams to respond without hiding scientific or organizational problems.
Applications can also fail when users do not trust the information, when developers misunderstand how decisions are made, or when the organization lacks resources to operate the product.
Closing a project should produce more than a presentation. Teams need to document performance, unresolved limitations, training, governance, maintenance, data stewardship, and ownership.
When transition remains incomplete, closeout documentation should identify the remaining work, responsible organizations, and missing resources. Evidence of use and benefit also helps NASA determine which applications may warrant wider deployment.
What NASA Earth Action Means for the Space Economy
NASA Earth Action operates where publicly funded science meets service delivery. Government missions create calibrated, long-term, open records that companies, public agencies, researchers, and nonprofit organizations can use.
Commercial firms can add software, domain analysis, customer support, cloud processing, higher-frequency observations, and tailored products. Public institutions can preserve open access, scientific standards, continuity, and services that may not generate enough revenue for a private operator.
This mixed model appears throughout the Earth observation sector. New Space Economy’s review of Earth observation satellites in 2026 describes open government programs and commercial operators differentiating their services through resolution, revisit frequency, sensor type, analytics, and delivery models.
Its examination of the global Earth observation industry describes a data business serving agriculture, infrastructure, finance, insurance, maritime operations, resource management, environmental monitoring, and public safety.
Earth Action can strengthen demand by helping users define problems and test applications before a mature market exists. A publicly funded project may demonstrate that satellite-based water estimates can support allocation decisions, that radar monitoring can improve infrastructure assessment, or that automated bloom detection can support public health warnings.
After the value and workflow have been demonstrated, an agency may operate the service, purchase it from a company, or combine public and commercial information.
As of July 24, 2026, NASA’s private-sector engagement program stated that applications for its INNOVATE funding opportunity remained open through August 31, 2026. INNOVATE provides selected teams with NASA funding, data, and expertise to develop Earth science solutions addressing commercial and societal problems.
NASA also released the Accelerating Earth Solutions opportunity in July 2026. Proposals are due October 15, 2026. The opportunity supports needs and opportunity discovery, solution development, and the scaling of existing applications.
Projects eligible for more than one year of funding are subject to progress and impact reviews. NASA identified NISAR, the Plankton, Aerosol, Cloud, ocean Ecosystem mission, and SWOT among the missions of particular interest.
Open data remains part of the economic foundation. New Space Economy’s history of Earth observation as Earth’s memory describes the sector as a layered information system built from sensors, archives, computing, standards, analytical methods, and institutional trust.
NASA Earth Action’s most significant contribution may be its definition of value. A mission is not judged only by instrument performance or data volume. An application is not judged only by technical completion.
Value appears when an organization trusts the information, changes a decision, and sustains the resulting service. That standard creates a demanding test for public programs and commercial providers, but it also explains how Earth science moves from orbit into routine choices affecting safety, resources, health, infrastructure, and economic activity.
Summary
NASA’s 2026 guidebook presents Earth Action as a complete operating method for applied Earth science. It starts with a defined decision and a committed user, connects that need to suitable observations and models, measures maturity through Application Readiness Levels, and treats transition as part of the project rather than an activity deferred until funding ends.
The method asks scientists to work with users throughout design, testing, evaluation, and adoption. It also recognizes that satellite observations require validation, translation, delivery, training, governance, maintenance, and trust before they can support routine decisions.
This approach has consequences beyond NASA. It offers public agencies a method for developing and evaluating geospatial services. It gives companies a clearer picture of how customers adopt Earth observation products. It gives researchers a path for moving proven methods into operational settings without weakening scientific standards.
The approach also gives funding organizations a stronger basis for evaluating impact because use, action, and benefit are considered separately.
A successful Earth Action project must do more than produce a capable tool. It must fit a real decision process, survive operational constraints, explain uncertainty, and reach an institution prepared to maintain it. When those conditions are met, Earth science becomes part of how organizations govern water, prepare for hazards, manage land, protect health, and plan investment.
Appendix: Useful Books Available on Amazon
- Remote Sensing and Image Interpretation
- Introduction to Remote Sensing
- Remote Sensing of the Environment
- Physical Principles of Remote Sensing
- Introduction to the Physics and Techniques of Remote Sensing
Appendix: Top Questions Answered in This Article
What Is NASA Earth Action?
NASA Earth Action is the applied science element of NASA’s Earth Science Division. It supports projects that connect Earth observations, models, and research with decisions made by government agencies, companies, nonprofit organizations, communities, and other users. The work centers on applications that can be tested, adopted, and sustained in operational environments.
How Is an Earth Action Project Different From Basic Research?
Basic research may investigate how Earth systems work or whether a scientific method can produce reliable results. An Earth Action project begins after enough science exists to address a defined user need. It must show how the output fits a decision, how users will participate, how performance will be tested, and how the application could continue after NASA funding.
What Does User-Centered Science Mean?
User-centered science means that a named user’s needs, decisions, timing, constraints, and working practices shape the application. Users help define the problem, test prototypes, interpret results, and determine whether the tool is suitable for adoption. The approach reduces the risk of delivering a technically capable product that does not fit operational practice.
What Are Application Readiness Levels?
Application Readiness Levels form a nine-step NASA framework for measuring the maturity of an application. The framework progresses from research and concept work through prototype development, testing in a relevant environment, operational qualification, deployment, and sustained use. Evidence of user participation and workflow integration matters alongside technical performance.
Why Does NASA Emphasize Co-Development?
Co-development gives users an active role in creating an application rather than asking them to evaluate a completed product. Their participation can reveal timing requirements, data limitations, legal restrictions, training needs, and system requirements early enough to influence the design. It can also build confidence because users understand how the product was created and tested.
How Does NASA Measure the Impact of an Application?
NASA separates impact into use, action, and benefit. Use asks whether people or institutions employ the application. Action asks whether the information changes a decision or activity. Benefit asks whether that action produces a positive result for users, communities, property, health, economic activity, or the environment.
Why Is Open Earth Observation Data Not Enough by Itself?
Open data lowers access barriers, but users may still face complex formats, large files, computing requirements, uncertainty, and missing local context. Operational value often requires processing, software, documentation, validation, training, and support. An application succeeds when those elements convert observations into information that fits a real decision process.
What Makes an Earth Action Proposal Strong?
A strong proposal names a specific user, defines a specific decision, explains why NASA data are suitable, and describes how the application will be tested and transitioned. It presents realistic staffing, budget, schedule, risk, evaluation, and sustainability plans. Partner commitments should demonstrate active participation rather than general interest.
Why Does Transition Planning Start Early?
Transition can require hosting, security review, software maintenance, training, documentation, data agreements, procurement, accessibility testing, and long-term funding. These activities can take longer than scientific development and may involve people outside the research team. Early planning identifies the future owner, recurring costs, approval process, and remaining work.
What Does Earth Action Contribute to the Space Economy?
Earth Action helps turn public science and open mission data into tested services for government, business, and community decisions. It can demonstrate demand, define user requirements, and reduce adoption risk for later operational programs. Commercial firms may supply analytics, software, support, or additional observations, with public missions providing continuity and science-grade records.
Appendix: Glossary of Key Terms
Earth Observation
Earth observation is the collection of information about Earth’s land, water, atmosphere, ice, and living systems through satellites, aircraft, ground instruments, ocean platforms, and other sensors. It becomes an application when measurements are processed and connected to an operational decision or defined need.
Remote Sensing
Remote sensing is the measurement of an object or area without direct physical contact. Satellite instruments detect reflected or emitted electromagnetic energy and convert it into information about surface conditions, temperature, vegetation, water, atmospheric properties, land movement, and other characteristics.
Earth Action
Earth Action is NASA’s applied Earth science program area. It supports work that connects NASA observations and research with practical decisions, develops applications with users, evaluates adoption and impact, and prepares successful tools or services for sustained operation.
User-Centered Science
User-centered science is an approach in which user needs, decisions, constraints, and working practices guide application design. Users participate in defining the problem, shaping requirements, testing outputs, interpreting results, and determining whether the application can be adopted.
Co-Development
Co-development is a working relationship in which researchers, developers, and users create an application together. It shares knowledge and decision-making throughout design and testing rather than limiting users to providing feedback after a product has been completed.
Application Readiness Level
An Application Readiness Level is a stage within NASA’s nine-step framework for tracking application maturity. The framework measures progress from research and concept work through prototype development, testing, operational qualification, deployment, and sustained use in decision-making.
Decision-Support Tool
A decision-support tool is a dataset, model, map, dashboard, alert, forecast, or software service designed to inform a defined decision. Its value depends on scientific quality, timing, usability, uncertainty communication, accessibility, and compatibility with an organization’s procedures.
In Situ Data
In situ data are measurements collected at the location of the observed condition. Examples include readings from weather stations, stream gauges, soil sensors, field surveys, and ocean buoys. These measurements often help calibrate and validate products derived from satellites.
Theory of Change
A theory of change is a structured explanation of how project activities are expected to produce outputs, changes in user behavior, and longer-term benefits. Teams can use it to select measurements, test assumptions, and connect project activities with intended outcomes.
Transition
Transition is the process of moving an application from development or demonstration into an operational environment. It can include approval, hosting, training, maintenance, documentation, funding, governance, accessibility, data stewardship, and the transfer of responsibility to a long-term owner.

