跳到主要内容
aiomniuaiomniu
only10

V26.W46 · 10 · Show HN: Every satellite that passed over any place this week, and its photos

V26.W46 · 10 · Show HN: Every satellite that passed over any place this week, and its photos

A browser-based tool that visualizes every satellite pass over a user-chosen location in the past seven days, linking SGP4 orbital calculations to real Sentinel-2 and Landsat imagery. It offers a compelling novelty for space enthusiasts but faces the challenge of translating a one-time viral moment into sustained utility without stated monetization or retention mechanisms.

The short version

  • What it is: A client-side application that calculates satellite positions for 17,000+ objects and displays archived images from specific passes over a user’s geographic coordinates.
  • Why it matters: It democratizes access to orbital tracking and recent satellite imagery by removing the need for complex backend infrastructure, running entirely in the user's browser.
  • Main risk: The utility is highly niche and novelty-driven, with no stated business model, user retention strategy, or clarity on how image quality and storage costs are managed at scale.

What it actually does

The project allows users to input a geographic location to view every satellite that passed over that spot in the last seven days. It uses the SGP4 propagation model on the CelesTrak catalog to track over 17,000 orbital objects, performing these calculations in the user’s browser with a GPU-accelerated rendering loop. It specifically fetches imagery from Sentinel-2, Landsat, and NASA sources corresponding to those exact satellite passes. The developer notes that Sentinel-2 timestamps can be 5-10 minutes off from actual ground crossings, requiring specific mathematical adjustments for accuracy. The system does not store user location data, and the source code is available on GitHub.

Why it could matter

The tool bridges the gap between passive satellite imagery consumption and active local orbital history. By framing space-based observation as a recurring, localized event, it creates a unique engagement hook for educators, hobbyists, and space enthusiasts. The client-side architecture is significant because it offloads the computational heavy lifting of orbital propagation to the user's device, potentially reducing server costs and enabling low-latency interaction. If the imagery quality is sufficient, the tool provides a simple interface for users to understand how orbital mechanics relate to their physical coordinates, transforming abstract data into a tangible, personal sky view.

The case against it

The primary risk is the "so what" factor: viewing low-resolution images of one’s own town is likely underwhelming compared to commercial high-resolution services, and the novelty will fade quickly after the initial viral moment. Second, while the calculation runs in the browser, the source does not state how the image archive is managed, stored, or indexed globally, leaving infrastructure costs and scalability unclear. Third, there is no stated retention mechanism beyond the weekly update cadence. Without a subscription model, community layer, or advanced utility features like spectral analysis or change detection, the project risks remaining a static novelty toy with low user engagement over time.

Business and cost

The source description does not state any pricing, funding, or revenue model. The author mentions the project was built over a weekend out of boredom, suggesting a low initial cost of entry. However, operational costs for storing and serving imagery from Sentinel-2, Landsat, and NASA for any location on Earth are not detailed. The client-side calculation approach reduces compute needs for orbital tracking, but the backend infrastructure for hosting the image archive and data feeds is unspecified. Without stated monetization, the project relies on open-source contributions and community support, making long-term sustainability dependent on finding a value-capture mechanism, such as a lead generation funnel for a deeper commercial product.

Historical pattern

Historically, public-facing tools that aggregate raw astronomical or satellite data often fail to sustain engagement once the initial surprise fades. Comparable projects, such as personalized astronomy logs or geotagged photo archives, struggle to convert casual visitors into loyal users without a community layer or a distinct utility feature. Most existing satellite viewers are either complex government-grade tools or expensive commercial services. This project occupies a middle ground: accessible to casual users but lacking the actionable insights of professional tools. The pattern suggests that viewing-only data products without deeper analytical capabilities rarely build durable communities or revenue streams.

The call

The verdict is positive on technical novelty but cautious on long-term viability. The timeline for success is short, likely measured in weeks following the initial Show HN launch. The verdict would change if the project demonstrates consistent week-over-week user retention, releases an API for change-detection analysis, or secures funding for scalable infrastructure. Without these markers, it remains a high-impact but low-durability hobby project. The next step should be to validate demand for specific coordinates and explore a paid tier for higher-resolution or historical data before committing to global indexing costs.

Scorecard

RoleScore
Advisor7.0
Devil-6.0
Historian-2.0
Budget Steward0.0
Founder4.0
Overall1.3 / 10

CRP review record

Advisor

The core value proposition lies in transforming ephemeral satellite passes into a persistent, geographically indexed visual archive. For users, this provides a novel "time-lapse" of their specific location using space-based observation, which is a unique engagement hook compared to static maps. The project addresses a curiosity gap: most people see "satellite imagery" as a static product, but this frames it as a live, recurring event tied to their physical coordinates. If the data pipeline is automated and the UI allows for easy discovery of "what was over me last Tuesday," it has high viral potential via social media sharing of unique local sky events. The opportunity is strong for niche hobbyists, educators, and space enthusiasts who want deeper interaction with orbital data without needing to track satellites manually. It moves from passive data consumption to active local history.

Devil

The primary risk is the "so what" factor. Seeing a low-resolution photo of one’s house or a nearby town is likely underwhelming compared to existing high-resolution commercial satellite services. The novelty wears off quickly after a single week of viewing. Second, the technical burden of correlating global satellite passes with every geographic point on Earth is computationally heavy; the source does not state how they handle this index or data storage costs, which could scale exponentially. Third, there is no stated user retention mechanism beyond the weekly cadence. Without a subscription model or deeper data layer (like spectral analysis), the product is a novelty toy. The source description is empty ("N/A"), making it impossible to verify if the photos are actually clear or useful, risking that the core value proposition is built on a false assumption of image quality.

Historian

Historically, projects that aggregate "raw" astronomical or satellite data for the general public often fail to sustain engagement once the initial surprise of "seeing the earth from space" fades. Categories like "personalized astronomy logs" or "geotagged photo archives" typically struggle to convert casual visitors into loyal users without a community layer or a utility feature (e.g., detecting land-use changes over time). Most public-facing satellite viewers in the past have been either government-grade tools (complex) or commercial services requiring precise coordinates (expensive). This project sits in the middle: accessible enough for a casual user but lacking the utility of professional tools. Comparable historical patterns suggest that "viewing-only" data products without actionable insights rarely build durable communities or revenue streams.

Budget Steward

The source does not provide specific costs, team size, or infrastructure details, so a precise itemized breakdown is not possible. However, estimating a solo developer or small team: building the satellite tracking pipeline and UI is feasible within the $15,000 budget if leveraging free or open-source orbital data (like TLEs) and open-source image APIs. The main cost drivers would be backend compute for processing and indexing passes globally, plus storage for the photo archive. If the project stores every photo pass for every location weekly, storage and CDN costs could exceed the budget rapidly without careful optimization. Assuming a lean approach using standard cloud providers for a small traffic base, it is likely within budget initially. However, scaling to "any place" implies massive data ingestion. Without stated revenue or funding, the risk of exceeding $15,000 in operational costs after a few months of high-scale indexing is high. The margin is thin.

Founder

Build this only if it serves as a lead generator for a deeper product, such as a commercial change-detection API or a subscription-based high-res imagery service. As a standalone public website, the value capture is low and the operational costs for global indexing are high. The "Show HN" angle suggests a launch strategy for community traction, which is positive for initial user acquisition. I would build the Minimum Viable Product (MVP) focusing on a limited number of high-population cities to manage compute costs and test user engagement with "local sky history." Do not build the global index until user retention metrics prove that people return week-over-week. The timeline should be 4-6 weeks for an MVP that supports manual tracking of specific locations, not automated global scanning. Do not commit to the full global promise without validating demand for specific coordinates.