TE
TechEcho
Home24h TopNewestBestAskShowJobs
GitHubTwitter
Home

TechEcho

A tech news platform built with Next.js, providing global tech news and discussions.

GitHubTwitter

Home

HomeNewestBestAskShowJobs

Resources

HackerNews APIOriginal HackerNewsNext.js

© 2025 TechEcho. All rights reserved.

Show HN: The story of space debris, made with WebGL for the Royal Institution

36 pointsby stugreyover 9 years ago

4 comments

CapitalistCartrover 9 years ago
NASA have a quartery newsletter on space debris called, appropriately enough, The Orbital Debris Quarterly News.<p><a href="http:&#x2F;&#x2F;www.orbitaldebris.jsc.nasa.gov&#x2F;newsletter&#x2F;newsletter.html" rel="nofollow">http:&#x2F;&#x2F;www.orbitaldebris.jsc.nasa.gov&#x2F;newsletter&#x2F;newsletter....</a>
gus_massaover 9 years ago
(Just in case it&#x27;s not obvious: Click the yellow link to see the animated visualization.)<p>Each debris has a different color. What does it mean?<p>Do the page download all the initial data and make a simulation or it download the positions periodically?<p>There is a ring at high altitude. What is it&#x27;s origin? Geocentric satellites? (I think there is another ring at medium altitude, but I&#x27;m not sure.)<p>Does this show the satellites that are currently in use or only the unuseful debris? Can you add a button to show&#x2F;hide them?
评论 #10696114 未加载
gjem97over 9 years ago
It&#x27;s a bit surprising to me that it&#x27;s not made more clear that the individual pieces of debris are not to scale. That is, just glancing at the visualization (especially the early ones in the presentation that focus on low Earth orbit) would lead the viewer to believe that space is much more crowded than it actually is. This in turn would make the viewer believe that collisions are much more likely than they actually are.
评论 #10699315 未加载
Cogitoover 9 years ago
FYI, this was broken behind my company proxy.<p>I <i>think</i> the proxy was rewriting the &quot;Content-Range&quot; request header, which is used in the function (papaparse.js:533):<p><i>function getFileSize(xhr) { var contentRange = xhr.getResponseHeader(&quot;Content-Range&quot;); return parseInt(contentRange.substr(contentRange.lastIndexOf(&quot;&#x2F;&quot;) + 1)); }</i><p>I could work around this by using the &quot;Content-Length&quot; header instead, which was available.<p>Once it was working, I thought it worked quite well, with only a little bit of stuttering and visual glitches detracting from the presentation, but those are probably on my end :)<p>I have seen a at least one similar presentations before, so I wonder if you were involved in any other similar things, or have borrowed concepts from them?