[time-nuts] NIST

[jimlux]

On 8/31/18 11:17 AM, Hal Murray wrote:
> 
> attila at kinali.ch said:
>> I have somewhere a paper (which i cannot find currently, sorry) that used a
>> dish trained at one of the EGNOS satellites and used it as the only source
>> for timing. IIRC the results were promising, but not spectacular. The problem
>> being that all the ionospheric and tropospheric ...
> 
> There is another problem in that area.  How accurately is the location of the
> satellite known?  published?
> 
> Geo-sync satellites actually wander around their nominal positions.  How much
> does that effect timing?  I've seen figure-8 pictures of the pattern, but I
> don't remember any data on elevation changes.


Their orbital elements are published and updated periodically - download 
them off spacetrack or other sources.

Here's an example

The orbit data is extracted from the following two-line orbital elements,

1 43228U 18023A   18243.14094620 -.00000224  00000-0  00000+0 0  9995
2 43228   0.0377  58.1839 0003405  72.7364 229.1178  1.00272082  1950
Epoch (UTC):	31 August 2018 03:22:57
Eccentricity:	0.0003405
inclination:	0.0377°
perigee height:	35772 km
apogee height:	35800 km
right ascension of ascending node:	58.1839°
argument of perigee:	72.7364°
revolutions per day:	1.00272082
mean anomaly at epoch:	229.1178°
orbit number at epoch:	195





> 
> 
> 
> 
>