Skip to content
I.STEM Lab

Concept · GeoAI

GeoAI in plain language

What GeoAI is, what it can and cannot do, and how to start a first project without getting lost in jargon.

Beginner8 min read

Key takeaways

  • GeoAI applies machine learning to data that has a location: imagery, maps, GPS traces and sensor readings.
  • It is strongest at repetitive mapping tasks across large areas, where people cannot cover every location by hand.
  • Results depend on image quality, good labels and local knowledge far more than on the choice of algorithm.
  • The best first project is small, specific and tied to a decision someone has to make.

Every day, satellites, drones, phones and sensors record enormous amounts of information about the places we live and work. Most of it is never looked at. No team of analysts can scroll through every image of a province, a coastline or a city. GeoAI exists to close that gap. It lets software do the first pass of looking, so that people can spend their time deciding what to do about what it finds.

This article explains GeoAI in plain language: what it is, where its data comes from, what it can do, where it goes wrong, and how an organisation can start without a large budget or a team of data scientists.

What GeoAI means

GeoAI is short for geospatial artificial intelligence. It is the use of machine learning on data that is tied to a location. That data might be a satellite photograph, a map of roads, a trail of GPS points or a reading from a sensor in a river. What makes the field distinct is that location matters. Two pixels that sit next to each other usually have something in common, and a model that understands this can make better predictions than one that treats every data point as unrelated.

Traditional geographic information systems, or GIS, are very good at storing, combining and displaying spatial data. A GIS analyst can overlay flood zones on a map of buildings and count how many fall inside. GeoAI adds a different ability: learning patterns from examples, and then applying them at a scale no analyst could match. The two are partners. GIS organises and presents the information. GeoAI helps create new information from raw data.

Where the data comes from

Most GeoAI projects start with one or more of these sources.

  • Optical satellite imagery. These are pictures taken in visible and near-infrared light, much like a camera. They show crops, buildings, water and forest, but they cannot see through clouds.
  • Radar imagery. Radar satellites send their own signal and measure what bounces back. They work at night and through cloud, which makes them valuable for flood mapping and for monitoring in rainy regions.
  • Drone and aerial photography. These give very fine detail over small areas, and you control when the images are taken.
  • Vector maps. Roads, buildings, rivers and boundaries drawn as points, lines and polygons. They are often used as labels to teach a model, or as context to check its results.
  • Sensor and GPS data. Weather stations, river gauges, vehicle traces and phone location data add information about what is happening, not only what the land looks like.

What GeoAI can do

Most real-world GeoAI work falls into a handful of task types.

  • Classification. Assign a label to every pixel or area: forest, cropland, water, built-up land. The result is a land cover map.
  • Detection. Find and count individual objects, such as buildings, vehicles, ships or solar panels.
  • Change detection. Compare two dates and flag what changed, for example new construction, a flooded field or cleared forest.
  • Prediction. Combine many layers of data to estimate something that cannot be seen directly, such as likely crop yield or landslide risk.
  • Enhancement. Improve the data itself, for instance sharpening low-resolution imagery or filling gaps caused by cloud.

A worked example: watching crops across a province

Imagine a provincial agriculture office that wants to know which districts are likely to have a poor harvest, early enough to plan support. Walking every field is impossible. Instead, the team collects free satellite images every few days through the growing season. A model, trained on examples from fields that were surveyed on the ground, learns what healthy and stressed crops look like in those images. Each week it produces a map showing where vegetation is lagging behind a normal year.

None of this replaces field officers. It tells them where to go first. The map turns a province-wide guess into a short list of districts worth visiting, and that is where GeoAI earns its keep: it narrows attention to where it matters.

How a GeoAI project actually runs

  1. 01Start with the question. Write it as a decision: which fields need irrigation support this month? A vague goal such as “use AI on our satellite data” rarely produces anything useful.
  2. 02Choose the data. Check that imagery exists at a resolution and frequency that can answer the question for your area and season.
  3. 03Prepare labels. A model learns from examples, so someone must mark what is what in a sample of the data. This is often the slowest and most valuable step.
  4. 04Train and test. Build a model, then test it on areas it has never seen, and measure honestly how often it is right.
  5. 05Check against the real world. Visit a sample of places, or ask local experts whether the map matches what they know.
  6. 06Deliver in a form people use. A map in a dashboard, a monthly report or an alert is worth more than an accurate model that nobody opens.

Where GeoAI goes wrong

The failures are rarely about the algorithm. They are almost always about the data and the setup.

  • Clouds, haze and shadows hide the ground or change how it looks.
  • Training labels are few, inconsistent or biased towards easy places, so the model is confident where it should not be.
  • A model trained in one region or season is moved to another where the land looks different, and accuracy drops quietly.
  • The image detail does not match the question. You cannot count houses in 10 metre pixels.
  • Accuracy is measured on data too similar to the training data, which makes the score look better than the real performance.

Questions worth asking any GeoAI team

  • Which decision will this improve, and who will use the result?
  • What imagery will you use, at what resolution and how often?
  • Who creates the labels, and how many do you need?
  • How will you test it on places the model has not seen?
  • What will happen when the model is wrong, and how will users know?
  • Who will maintain it after launch?

How to start

Pick one question, one area and one season. Check that suitable imagery exists. Gather a small set of labelled examples with the help of someone who knows the ground. Build a simple model, test it honestly and show the result to the people who would use it. If it helps them, grow it. If it does not, you have spent weeks, not years, to find out.

GeoAI in practice: three short examples

Agriculture. A farmers’ cooperative uses free Sentinel-2 images to track crop vigour every week. When one block of fields lags behind its neighbours, an extension officer visits that block first, instead of driving to every farm in the district.

Disaster response. After heavy rain, radar satellite images show where water has spread, even through cloud. A model separates flooded from dry land within hours, and relief teams use the map to plan routes and decide where to send supplies.

Cities. A municipality compares images from two different years to find new buildings that have no permit on record. The model flags candidates, and inspectors check the flagged sites instead of searching the whole city.

In every case, the model decides nothing by itself. It shortens the list of places where a person needs to look.

Tools you will meet along the way

  • QGIS: a free desktop GIS for viewing, editing and mapping data.
  • Python with libraries such as rasterio, geopandas and scikit-learn: for repeating analyses and training models.
  • Public data catalogues and platforms such as Google Earth Engine: for finding and processing large archives of satellite imagery.
  • Cloud notebooks: for running code without a powerful computer.
  • Web mapping libraries: for sharing results as interactive maps.

You do not need all of them at once. A sensible order is QGIS first, to build intuition for how spatial data behaves, then Python once you want to repeat a task or analyse more data than you can click through.

Frequently asked questions

Do I need to be a programmer to start with GeoAI?
No. You can learn the concepts and make useful maps with QGIS and online tools. Programming becomes important when you want to repeat an analysis on many images, or train your own models, and Python is the usual choice.
Is GeoAI the same as GIS?
No. GIS is the discipline and the software for storing, analysing and presenting spatial data. GeoAI is one set of techniques within it, using machine learning to extract information from data at scale.
How many labelled examples do I need?
It depends on how varied the land is and how many classes you map. A few hundred well-chosen examples per class can give a useful first result. More varied examples usually help more than simply more of the same kind.
How accurate can it be?
Good land cover maps often reach high overall accuracy, but the figure depends on the classes, the imagery and how the test was done. Always ask how accuracy was measured, and where the model makes its mistakes.

GeoAI is not magic, and it does not need to be. At its best it is a patient assistant that reads every image so your experts can spend their attention where it counts.

Share

Join the conversation

Reactions & comments

Comments are opening soon.

In the meantime, tell us what you think by email at info.istem.lab@gmail.com.

Start a project

Need this built for your organization?

If you would rather have a working system than a tutorial, tell us your goal and we will scope it with you.