Satellite Tech 101: Understanding Orbits, LEO, and GEO (Part 1)

Confused by satellite jargon? In Part 1 of our series, we demystify the satellite technology stack, explaining the critical differences between LEO, MEO, and GEO orbits.

Space is hard. It’s expensive, it’s cold, and it’s full of radiation. But for modern developers and tech enthusiasts, space is also becoming the next great frontier for data.

We used to think of satellites as massive, government-funded school buses floating in the void, beaming down weather reports or spy photos once a week. Today? It’s a completely different ballgame. We have private companies launching thousands of “flying routers” to give us gigabit internet, and startups analyzing crop yields from space in real-time.

But before we can start scraping satellite imagery with Python or building apps on top of Starlink (which we will cover in Part 2), we need to understand the hardware.

Welcome to Part 1 of our Satellite Tech Series. Today, we are ignoring the code and focusing on the physics. We’re going to break down satellite technology, decode the alphabet soup of orbits, and figure out why a satellite’s “parking spot” determines how fast your internet loads

What is a Modern Satellite? (It’s Not Just a Metal Box)

If you picture a satellite as a shiny gold foil-wrapped object the size of a truck, you aren’t wrong—but you are a bit outdated. Those still exist (mostly for deep space science or massive military comms), but the industry is trending toward miniaturization.

In the “New Space” era, hardware is shrinking.

• The Old Guard: Traditional satellites often weigh thousands of kilograms and cost hundreds of millions to build. They are bespoke, hand-crafted Ferraris.
• The New Class (CubeSats): These are the Honda Civics of space. Standardized, modular, and small. A “1U” CubeSat is literally a 10cm x 10cm x 10cm box.
• The Mega-Constellations: Think Starlink or Kuiper. These are flat-packed satellites, roughly the size of a table, designed to be mass-produced and stacked inside a rocket fairing like IKEA furniture.

Why does this matter? Because smaller satellites are cheaper to launch, which means we can put more of them up there. This shift from “one big satellite” to “thousands of small ones” is changing how we handle data latency and availability.

The “Altitude” Game: Understanding Orbits

This is the most critical concept for developers to grasp. In terrestrial networking, we worry about the distance between a client and a server (e.g., US-East vs. EU-West). In space, we worry about Altitude.

Where a satellite sits relative to Earth dictates what it can see, how fast it communicates, and how long it stays in the sky.

GEO: The “Parking Spot” (Geostationary Orbit)

• Altitude: ~35,786 km (22,236 miles)
• Best For: TV Broadcasts, Weather monitoring, global comms backbone.

Imagine you are standing in a field and you fly a drone directly above your head. As you walk, the drone matches your speed exactly, so it’s always looking down at the top of your head. That is GEO.

Satellites in GEO match the Earth’s rotation exactly. From our perspective on the ground, they appear frozen in the sky. This is great for DirectTV or Dish Network—you point your satellite dish at one spot on the roof, bolt it down, and never touch it again.

The Downside? Latency. The signal has to travel 35,000 km up and 35,000 km back down. Even at the speed of light, that trip takes time (roughly 600ms round trip). This is why satellite internet used to be terrible for gaming or Zoom calls.

LEO: The “Speed Demons” (Low Earth Orbit)

• Altitude: 160 km to 2,000 km (100 – 1,200 miles)
• Best For: High-speed internet (Starlink), High-resolution spy imagery, Scientific research.

If GEO is a drone hovering calmly, LEO is a fighter jet buzzing the tower. Satellites here are very close to Earth, which means two things:

1. Low Latency: The data trip is short (20-40ms), comparable to fiber optics.
2. High Speed: To stay in orbit without falling, they have to move incredibly fast—about 17,000 mph. They orbit the entire Earth every 90 minutes.

The Developer Challenge: Because they move so fast, a LEO satellite is only visible to your ground station for about 10 minutes before it disappears over the horizon. To provide continuous service (like internet), you can’t just have one satellite; you need a “constellation” of hundreds or thousands, handing off the signal like a baton in a relay race.

Ground Stations: How the Data Gets Down

We often forget that satellite technology is useless without the ground. A satellite collecting 4K video of a rainforest is just an expensive camera until it can “downlink” that data to a server.

This happens via Ground Stations—massive antenna farms located strategically around the globe.

In the old days, you had to wait. If a spy satellite took a picture over a remote desert, it had to store that data on a hard drive and wait until it flew over a friendly ground station to download it. This is the “Store and Forward” method.

Today, we are seeing the rise of Inter-satellite Links (ISLs). This is basically lasers in space. If a satellite can’t see a ground station, it lasers the data to a neighboring satellite, which lasers it to another, until the data reaches a satellite that is over a ground station. This creates a mesh network in the vacuum of space.

Why This Matters

Okay, so why should a full-stack developer or a data engineer care about orbital mechanics?

Because the source of your data defines its limitations.

1. Latency Constraints: If you are building a high-frequency trading bot or a real-time multiplayer game, you need to know if the user is on a GEO connection (high lag) or LEO connection (low lag).
2. Data Freshness (Revisit Rate): If you are building an app that monitors deforestation or parking lot traffic using satellite imagery, you are limited by orbits. A single LEO satellite might only fly over Walmart once a day at 2:00 PM. If you need hourly updates, you need to access a constellation, not just a single sensor.
3. Bandwidth: While LEO is getting faster, space bandwidth is still a precious resource compared to a fiber line in a data center. Optimizing your data payloads is crucial when the “pipe” is floating 500km overhead.

Conclusion: The Sky is No Longer the Limit

The barrier to entry for space is crumbling. We are moving away from an era where only superpowers controlled the skies to an era where developers can rent satellite time via an API key.

Understanding the difference between LEO and GEO is the first step in leveraging this new infrastructure. But knowing the hardware is just the beginning. How do we actually get the data? How do we parse it? And how do we use it to build something cool?

Stay tuned for Part 2 of this series, where we leave the physics classroom and enter the coding bootcamp. We’ll discuss Geospatial APIs, Python libraries for space data, and the concept of “Space-as-a-Service.”

See you in orbit.

Sources
* NASA – Low Earth Orbit vs Geostationary: https://www.nasa.gov
* European Space Agency (ESA) – Types of Orbits: https://www.esa.int