Methodology

How Globelume works, and where it falls short

Everything here comes from open sources. We collect it, combine it and put it on one map. We don't verify it independently.

How often data updates

  • FlightsEvery minute or two. A position older than three minutes is not shown.
  • ShipsA live stream, saved every minute. A ship not heard for an hour is removed.
  • EarthquakesEvery minute.
  • Other natural eventsEvery 10 minutes.
  • Weather stationsEvery 10 minutes.
  • Ocean buoysEvery 30 minutes.
  • Travel advisoriesEvery 6 hours.
  • SatellitesOrbital data about every 8 hours. Positions are calculated from it.
  • Sanctions listOnce a day.
  • Fire hotspotsEvery 30 minutes, from a NASA satellite that passes over each place about twice a day.
  • Clouds on the globeYesterday's NASA satellite images, not live weather. Gaps between satellite passes show as clear sky.

If a source fails, we keep its last good data and the map says when data is out of date.

What moves on the map is partly estimated

Between reports, aircraft and ships are moved forward from their last known speed and heading, so the globe stays smooth. The position you see can differ from the real one, most of all just before a new report arrives.

What the counts mean

A count is what our sources heard, not what is there. Flights and ships rely on networks of volunteer receivers, so coverage is good near busy coasts and cities and thin over oceans and in some countries. A rise or fall in a chart can reflect receivers going on or offline as well as real traffic.

A fire hotspot is heat seen from space. It can be a wildfire, but also farm burning, a gas flare or an industrial site, and smoke or cloud can hide a real fire. We leave out low-confidence detections. Hotspots come from NASA FIRMS, provided as is, with NASA's disclaimer.

Ships report their own name, type, destination and IMO number, and those can be wrong or deliberately false. Aircraft and ships can also choose not to transmit.

Automated signals

Possible GPS interference and sanctions matches are worked out by fixed rules. Each one is a reason to look closer, never a finding about a ship, company or country. The rules and their limits are on the insights page.

An aircraft emergency code appears only after several separate reports over at least 90 seconds, because a single garbled message can read as one. Even then it only means the aircraft kept sending the code. Pilots sometimes set these by mistake, and we can't confirm what is happening on board.

We don't flag ships for going quiet. On our free feed, moving ships drop out for 30 minutes or more thousands of times a day and then come back, some after many hours, so a silence tells you nothing about the ship.

Open flight data

Our flights contain information from adsb.lol, made available under the Open Database License 1.0. The original data is open to everyone, and adsb.lol publishes a daily archive of it.

We change it in these ways: we sample a set of regions rather than the whole sky, merge them so each aircraft appears once with its newest position, drop anything older than 180 seconds, and remove the accuracy fields once we have used them to look for GPS interference.

What not to use it for

Don't use Globelume for navigation, flight planning, emergencies, sanctions screening or any decision about safety. Use the official source for each of those.

Sources

Something wrong, or something of yours that should come down? Tell us.