Re: Notice on space track site

From: JAY RESPLER via Seesat-l <>
Date: Sat, 26 Jul 2014 03:10:25 -0400
The reason I got them to publish RCS values in the first place was not 
for payloads and rockets where the size was generally known.  It was to 
get a rough idea of visibility of debris where all sizes were unknown.
And since debris usually has odd shapes, RCS can vary widely from one 
pass to another.
Still, I'd rather they kept actual values instead of "scaling".

Jay Respler
  Freehold, New Jersey

On 7/24/2014 6:56 PM, Henry Hallam via Seesat-l wrote:
> The data was of pretty poor quality anyway, wide variations between
> objects that were known to be physically identical, and no sigmas
> provided.
> But still, I'd rather have it than not :(
> Henry
> On Wed, Jul 23, 2014 at 6:57 AM, Jonathan McDowell via Seesat-l
> <> wrote:
>> This is too bad. I guess someone decided these should not be public. Even
>> worse, currently  "SMALL" will mean either small or unknown - there are a
>> lot of zeroes in the RCSVALUE field that aren't real zeroes, just 'not
>> measured' and now it won't be possible to distinguish these from
>> measured small values unless they tweak their plan.
>>     - Jonathan
>> On 23 July 2014 05:06, Kevin Fetter via Seesat-l <>
>> wrote:
>>> What has appeared.
>>> USSTRATCOM has added scaling of RCS values to the SATCAT. Until 18 Aug 14,
>>> there will be a dual-feed of both current values (RCSVALUE) & scaled values
>>> (RCS_SIZE). RCS_SIZE has 3 values: Small (< 0.1m2), Medium (0.1m2 – 1m2), &
>>> Large (>1m2). Space-Track will show only scaled values starting 18 Aug
>>> (RCSVALUE will show static value of 0 in satcat, satcat_debut, & decay
>>> classes). There is no change to CDM spaceflight safety notification info or
>>> procedures. Contact admin_at_space-track for more info.

Seesat-l mailing list
Received on Sat Jul 26 2014 - 02:11:20 UTC

This archive was generated by hypermail 2.2.0 : Sat Jul 26 2014 - 07:11:20 UTC