Modular set of functions for SGP4 and SDP4 propagation of TLEs.
JavaScript HTML CSS

satellite.js v1.2.0


A library to make satellite propagation via TLEs possible in the web. Provides the functions necessary for SGP4/SDP4 calculations, as callable javascript. Also provides functions for coordinate transforms.

The internals of this library are nearly identical to Brandon Rhode's sgp4 python library. However, it is encapsulated in a standard JS library (self executing function), and exposes only the functionality needed to track satellites and propagate paths. The only changes I made to Brandon Rhode's code was to change the positional parameters of functions to key:value objects. This reduces the complexity of functions that require 50+ parameters, and doesn't require the parameters to be placed in the exact order.

Special thanks to ezze, for modernizing the code and greatly improving usability =)

Start Here:

The javascript in this library is heavily based (straight copied) from:

I've included the original PKG-INFO file from the python library.

The coordinate transforms are based off T.S. Kelso's columns:

And the coursework for UC Boulder's ASEN students

I would recommend anybody interested in satellite tracking or orbital propagation to read all of TS Kelso's columns. Without his work, this project would not be possible.

Get a free Space Track account and download your own up to date TLEs for use with this library.

Installation (Bower or NPM)

Install the library with Bower:

bower install satellite.js

Install the library with NPM:

npm install satellite.js


Include dist/satellite.min.js as a script in your html or use as Require.js module.

When you include satellite.min.js as a script, the object satellite is defined in global scope. You use this object to access all the functions in the satellite library:

var positionAndVelocity = satellite.sgp4(satrec, time);

When you use it as Require.js module satellite object is not defined in global scope, you should use it as a dependency of your module:

define(['path/to/satellite'], function(satellite) {
    var positionAndVelocity = satellite.sgp4(satrec, time);

Sample Usage

// Sample TLE
var tleLine1 = '1 25544U 98067A   13149.87225694  .00009369  00000-0  16828-3 0  9031',
    tleLine2 = '2 25544 051.6485 199.1576 0010128 012.7275 352.5669 15.50581403831869';

// Initialize a satellite record
var satrec = satellite.twoline2satrec(tleLine1, tleLine2);

//  Propagate satellite using time since epoch (in minutes).
var positionAndVelocity = satellite.sgp4(satrec, timeSinceTleEpochMinutes);

//  Or you can use a JavaScript Date
var positionAndVelocity = satellite.propagate(satrec, new Date());

// The position_velocity result is a key-value pair of ECI coordinates.
// These are the base results from which all other coordinates are derived.
var positionEci = positionAndVelocity.position,
    velocityEci = positionAndVelocity.velocity;

// Set the Observer at 122.03 West by 36.96 North, in RADIANS
var observerGd = {
    longitude: -122.0308 * deg2rad,
    latitude: 36.9613422 * deg2rad,
    height: 0.370

// You will need GMST for some of the coordinate transforms.
var gmst = satellite.gstimeFromDate(new Date()));

// You can get ECF, Geodetic, Look Angles, and Doppler Factor.
var positionEcf   = satellite.eciToEcf(positionEci, gmst),
    observerEcf   = satellite.geodeticToEcf(observerGd),
    positionGd    = satellite.eciToGeodetic(positionEci, gmst),
    lookAngles    = satellite.ecfToLookAngles(observerGd, positionEcf),
    dopplerFactor = satellite.dopplerFactor(observerCoordsEcf, positionEcf, velocityEcf);

// The coordinates are all stored in key-value pairs.
// ECI and ECF are accessed by `x`, `y`, `z` properties.
var satelliteX = positionEci.x,
    satelliteY = positionEci.y,
    satelliteZ = positionEci.z;

// Look Angles may be accessed by `azimuth`, `elevation`, `range_sat` properties.
var azimuth   = lookAngles.azimuth,
    elevation = lookAngles.elevation,
    rangeSat  = lookAngles.rangeSat;

// Geodetic coords are accessed via `longitude`, `latitude`, `height`.
var longitude = positionGd.longitude,
    latitude  = positionGd.latitude,
    height    = positionGd.height;

//  Convert the RADIANS to DEGREES for pretty printing (appends "N", "S", "E", "W", etc).
var longitudeStr = satellite.degreesLong(longitude),
    latitudeStr  = satellite.degreesLat(latitude);


The code is organized as AMD modules but it can be built into a single file to use in production.

The library uses Grunt task runner for building and testing. It also relies on Bower package of Require.js plugins needed for test scripts. In order to run Grunt tasks follow these steps:

  • install Node.js and Node Package Manager;

  • install Grunt command line interface globally:

    npm install -g grunt-cli
  • install Bower globally:

    npm install -g bower
  • install all required packages with NPM and Bower by running the following commands from repository's root directory:

    npm install
    bower install
  • run default Grunt task to build the library:

  • run the following Grunt task to run Jasmine specs located in test/*.spec.js files with Karma:

    grunt test

All configuration files for Grunt tasks are located in grunt directory.

These are main available Grunt tasks:

  • build (default) validates, optimizies and minifies source code to dist directory;
  • clean removes all built files;
  • test tests the library by running Jasmine specs.


Optional functions that utilize Worker Threads

Exposed Objects


The satrec object comes from the original code by Rhodes as well as Vallado. It is immense and complex, but the most important values it contains are the Keplerian Elements and the other values pulled from the TLEs. I do not suggest that anybody try to simplify it unless they have absolute understanding of Orbital Mechanics.

  • satnum Unique satellite number given in the TLE file.
  • epochyr Full four-digit year of this element set's epoch moment.
  • epochdays Fractional days into the year of the epoch moment.
  • jdsatepoch Julian date of the epoch (computed from epochyr and epochdays).
  • ndot First time derivative of the mean motion (ignored by SGP4).
  • nddot Second time derivative of the mean motion (ignored by SGP4).
  • bstar Ballistic drag coefficient B* in inverse earth radii.
  • inclo Inclination in radians.
  • nodeo Right ascension of ascending node in radians.
  • ecco Eccentricity.
  • argpo Argument of perigee in radians.
  • mo Mean anomaly in radians.
  • no Mean motion in radians per minute.

Exposed Functions


var satrec = satellite.twoline2satrec(longstr1, longstr2);

returns satrec object, created from the TLEs passed in. The satrec object is vastly complicated, but you don't have to do anything with it, except pass it around.

NOTE! You are responsible for providing TLEs. Get your free Space Track account here. longstr1 and longstr2 are the two lines of the TLE, properly formatted by NASA and NORAD standards. if you use Space Track, there should be no problem.


Both propagate() and sgp4() functions return position and velocity as a dictionary of the form:

  "position" : { "x" : 1, "y" : 1, "z" : 1 },
  "velocity" : { "x" : 1, "y" : 1, "z" : 1 }

position is in km, velocity is in km/s, both the ECI coordinate frame.

var positionAndVelocity = satellite.propagate(satrec, new Date());

Returns position and velocity, given a satrec and the calendar date. Is merely a wrapper for sgp4(), converts the calendar day to Julian time since satellite epoch. Sometimes it's better to ask for position and velocity given a specific date.

var positionAndVelocity = satellite.sgp4(satrec, timeSinceTleEpochMinutes);

Returns position and velocity, given a satrec and the time in minutes since epoch. Sometimes it's better to ask for position and velocity given the time elapsed since epoch.


You can get the satellites current Doppler factor, relative to your position, using the dopplerFactor() function. Use either ECI or ECF coordinates, but don't mix them.

var dopplerFactor = satellite.dopplerFactor(observer, position, velocity);

See the section on Coordinate Transforms to see how to get ECF/ECI/Geodetic coordinates.

Coordinate Transforms

Greenwich Mean Sidereal Time

You'll need to provide some of the coordinate transform functions with your current GMST aka GSTIME. You can use Julian Day:

var gmst = satellite.gstimeFromJday(julianDay);

or a JavaScript Date:

var gmst = satellite.gstimeFromDate(new Date());


Most of these are self explanatory from their names. Coords are arrays of three floats EX: [1.1, 1.2, 1.3] in kilometers. Once again, read the following first.

The coordinate transforms are based off T.S. Kelso's columns:

And the coursework for UC Boulder's ASEN students

These four are used to convert between ECI, ECF, and Geodetic, as you need them. ECI and ECF coordinates are in km or km/s. Geodetic coords are in radians.

var ecfCoords = satellite.eciToEcf(eciCoords, gmst);
var eciCoords = satellite.ecfToEci(ecfCoords, gmst);
var geodeticCoords = satellite.eciToGeodetic(eciCoords, gmst);
var ecfCoords = satellite.geodeticToEcf(geodeticCoords);

These function is used to compute the look angle, from your geodetic position to a satellite in ECF coordinates. Make sure you convert the ECI output from sgp4() and propagate() to ECF first.

var lookAngles = satellite.ecfToLookAngles(observerGeodetic, satelliteEcf);

Latitude and Longitude

These two functions will return human readable Latitude or Longitude strings (Ex: "125.35W" or "45.565N") from geodeticCoords:

var latitudeStr = satellite.degreesLat(geodeticRadians),
    longitudeStr = satellite.degreesLong(geodeticRadians);

Note about Code Conventions

Like Brandon Rhodes before me, I chose to maintain as little difference between this implementation and the prior works. This is to make adapting future changes suggested by Vallado much simpler. Thus, some of the conventions used in this library are very weird.

How this was written

I took advantage of the fact that Python and JavaScript are nearly semantically identical. Most of the code is just copied straight from Python. Brandon Rhodes did me the favor of including semi-colons on most of the lines of code. JavaScript doesn't support multiple values returned per statement, so I had to rewrite the function calls. Absolutely none of the mathematical logic had to be rewritten.


I've included a small testing app, that provides some benchmarking tools and verifies SGP4 and SDP4 using the Test Criteria provided by SpaceTrack Report #3, and is based off System Benchmarking by TS Kelso.

The testing app is a Chrome Packaged App that uses the angular.js framework.

To run the test, open up Chrome, go to the extensions page, and check "Developer Mode". Then, click "Load Unpacked App", and select the sgp4_verification folder. Then run the app from within Chrome. The test file is located within the sgp4_verification directory, as a JSON file called spacetrack-report-3.json.


Major thanks go to Brandon Rhodes, TS Kelso, and David Vallado's team. Also, I'd like to thank Professor Steve Petersen (AC6P) of UCSC for pointing me in the correct directions.


All files marked with the License header at the top are Licensed. Any files unmarked by me or others are unlicensed, and are kept only as a resource for [Shashwat Kandadai and other developers] for testing.

I chose the MIT License because this library is a derivative work off Brandon Rhodes sgp4, and that is licensed with MIT. It just seemed simpler this way, sub-licensing freedoms notwithstanding.

I worked in the Dining Hall at UCSC for a month, which means I signed a form that gives UCSC partial ownership of anything I make while under their aegis, so I included them as owners of the copyright.

Please email all complaints to