Asteroids
Unavailable- Component score
- —
- Freshness state
- Unavailable
- Observed
- No approved current observation
Source completeness0%
Seven-day approach window
Asteroids this week: a seven-day planning view
A weekly view trades immediacy for orientation: it can group expected approach times across seven UTC days and make units easier to compare. It still cannot answer whether an object is dangerous without a separate authoritative risk assessment. Counts also depend on detection, catalog updates, and the source's inclusion rules, so a week is context rather than a forecast of catastrophe.
- Page reviewed
- Current evidence
- Unavailable
Current evidence
Verified approaches for the next seven days
The production panel would state its window boundaries, preserve revisions, and show distance and velocity with consistent units. It would keep Sentry risk classifications outside the close-approach table.
The seven-day production list is withheld while CNEOS and Sentry remain behind the source-rights gate. A missing list is not a claim that the official catalogs contain no upcoming approaches or monitored objects.
Seven-day approach window
What a wider window adds—and what it cannot add
Seven days can make comparison easier, but it increases the chance that values will be revised before the approach. A useful weekly page therefore records when each prediction was observed and when the page calculated its view. Sorting is a presentation choice and never changes the underlying source classification.
The close-approach table and an impact-monitoring table answer different questions. Combining them would make routine flybys look alarming or strip uncertainty from risk assessments. The provider-neutral domain model prevents that merge, while the unresolved permission request prevents controlled fixtures from leaking into production content.
Methodology
How to compare a seven-day list
Explicit boundaries
The start and end of the UTC window make the weekly count reproducible.
Consistent units
Distances and velocities need labeled units before objects can be compared responsibly.
Separate risk record
Only a dedicated provider assessment can add impact probability or a recognized risk scale.
Freshness state
Weekly predictions need revision awareness
The page treats later provider calculations as revisions of the same approach identity. If the calculation ages beyond policy, the entry becomes delayed or unavailable instead of remaining silently current.
Current view calculated:
Provenance
Sources and usage boundaries
The public source registry is unavailable. Source decisions remain fail-closed.
| Source | Rights decision | Production state | Attribution and limits |
|---|---|---|---|
| NASA/JPL CNEOS | Conditional | Not enabled for production | Potential close-approach context would be attributed to NASA/JPL CNEOS with the applicable provider timestamp and object identity. Conditional. Production ingestion, persistent storage, and normalized redistribution remain blocked pending sufficiently explicit usage confirmation. |
| NASA Sentry | Conditional | Not enabled for production | Any future impact-risk assessment would retain the NASA Sentry record, observation date, and source-supported risk classification. Conditional. A close approach is never converted into impact risk, and no production Sentry data is stored while the rights gate is unresolved. |
Keep exploring