Bill,

I placed the file into \Guide9. The format of the Spacetrack tle format
was, by all appearances, the same as the bright.tle the dvd supplied,
but when I searched for a particular satellite name with GOTO, Guide did
not find it by name.

Typical Spacetrack format is:

0 INTELSAT 1-F1
1 1317U 65028A 15337.21796532 -.00000289 +00000-0 +00000-0 0 9997
2 1317 001.6810 299.7740 0005735 221.6391 288.2075 01.00325188088581
0 ATS 1
1 02608U 66110A 15340.15720613 -.00000255 00000-0 00000+0 0 9990
2 02608 3.9217 301.0965 0008193 247.5154 261.6569 1.00342698 96208
0 INTELSAT 2-F2
1 02639U 67001A 15340.13706689 -.00000119 00000-0 00000+0 0 9998
2 02639 5.6949 303.4688 0015079 268.1550 258.4703 1.00231083 80696

Thought the zero in front of the names may have been the format issue,
but when I changed a few at the start of the tle file, Guide still
didn't find them.

Tom

On 12/6/2015 11:51 AM, Bill Gray pluto@... [guide-user] wrote:
> Hi Tom,
>
> The files ought to match... perhaps you aren't looking at the
> actual TLE files from the disk? They're 'classfd.tle', 'iridium.tle',
> 'alldat.tle', in the 'text' directory. The TLEs in them look like
>
> YAHSAT 1A
> 1 37393U 11016B 11176.79389188 .00000110 00000-0 10000-3 0 686
> 2 37393 0.0104 339.5778 0002398 140.9562 131.3411 1.00273642 721
>
> Spacetrack TLEs ought to look identical for lines 1 and 2. They
> may have the name given with a zero in front of it; Guide will figure
> it out if that happens.
>
> -- Bill
>
> On 12/06/2015 10:58 AM, tom loeblt@... [guide-user] wrote:
>> I notice the satellite txt file supplied on the dvd does not have the
>> standard columnar tle file that I download from Spacetrack. Is there a
>> conversion utility used to generate the Guide txt file or can I just
>> load the standard tle file in the satellite folder in the Guide
>> directory as I do in other satellite tracking programs??
>>
>> Tom
>>
>>
>> On 12/5/2015 10:42 PM, 'Tom Kunsitis' kunsitis@... [guide-user]
>> wrote:
>>>
>>>
>>> I noticed a strange phenomenon regarding Comet Panstarrs (C/2013 X1) in
>>> Guide 9.0. When I right click and ask for more information, it will
>>> give the estimated magnitude as 10.1 for zoom levels 4 and 5 and then
>>> show it as 13.3 for levels 6 and higher. The go to comets function
>>> always shows it as magnitude 13.3. I have data shown for comets set to
>>> auto at magnitude 11 for level 4 and magnitude 12.3 for level 5 so
>>> Panstarrs should not be showing at these levels. I am running the 27
>>> July 2015 version of Guide 9.0. Has anyone else had this happen?
>>>
>>> ---------------------------------------------------------
>>>
>>> Tom Kunsitis - Richmond, Virginia USA
>>>
>>>
>>>
>>>
>>
>
>
> ------------------------------------
>
> ------------------------------------
>
> To unsubscribe from this group, send an empty email to:
> guide-user-unsubscribe@egroups.com
> ------------------------------------
>
> Yahoo Groups Links
>
>
>
>

--
Tom