The Satellite Dashboard is a joint project between the CSIS Aerospace Security Program, Secure World Foundation, and University of Texas Austin. It tracks the locations of objects in orbit in GEO and provides analysis on key events.

• Quick-Start Instructions
• Usage
  • Local Development
  • Build for Production
  • Generate Static Project
  • See More Commands
  • Nuxt
• Data & API
  • Analysis
  • Satellites
• Contributing
  • Branching
  • Commit Messages
  • Naming Conventions
  • Recommended Extensions

# Clone repository
$ git clone [email protected]:CSIS-iLab/satellite-dashboard.git

# Navigate to project
$ cd satellite-dashboard

# install dependencies
$ npm install

# serve with hot reload at localhost:3000
$ npm dev

This will give you file watching, browser synchronization, auto-rebuild, CSS injecting, etc.

$ npm dev

log

$ npm build

# Optionally start server to view built site.
$ npm start

$ npm generate

This will display all available commands, such as running eslint or stylelint independently.

$ npm run

This project is built using Nuxt.js. For detailed explanation on how things work, check out Nuxt.js docs.

Data for this project is provided by UT Austin's AstriaGraph API.

A cron script pulls in data to the WordPress site database daily and are pulled into the Nuxt site's store via the WordPress REST API.

Returns Analysis post content and associated metadata (tags, categories, authors, etc.).

• Endpoint: /wp-json/wp/v2/posts
• Accessible via store/analysis.js

Returns satellite objects orbital data and metadata, including any meta values overridden by the program via the WordPress dashboard.

• Endpoint: /wp-json/satdash/v1/satellites: Returns most recent database record for each satellite (ie. Most updated data we have for that satellite) in GEO.
• Params:
  • date: ?date=YYYY-MM-DD will return all records added to the Satellite Dashboard database on the given date. Note that the actual propogation date might differ.
  • orbit: ?orbit=???? will return all records classified in the specified orbit. By default, returns all objects in GEO.
• Accessible via store/satellites.js

Each responses contains an array of objects with the properties listed below.

  {
    "id":"10000_2020-11-03T09:05:16.000000Z",
    "catalog_id":"10000",
    "source1":{
        "CatalogId":"10002",
        "Name":"TITAN 3C TRANSTAGE R\/B",
        "NoradId":"10002",
        "OrbitType":"GEO",
        "countryOfLaunch":"US",
        "source1LastCatalogUpdate":"2020-11-14T09:05:16.000000Z",
        "Source1Name":null
    },
    "source2":{
        "Type":"",
        "Status":"",
        "Purpose":"",
        "Lifetime":"",
        "Operator":"",
        "Contractor":"",
        "LaunchSite":"",
        "source2Name":"UCS",
        "LaunchVehicle":"",
        "source2UniqueId":7,
        "countryOfJurisdiction":"",
        "source2LastCatalogUpdate":"2020-05-20T15:44:00.000000Z"
    },
    "orbital":{
        "ArgP":0.87797688487499825,
        "Ecc":0.029299349237009727,
        "Epoch":"2020-11-13T22:17:34.000000Z",
        "Inc":0.23444950870574993,
        "MeanAnom":5.2347829487779922,
        "RAAN":5.5017097220786413,
        "SMA":43542224.427652501
    }
  },

When modifying the code base, always make a new branch. Unless it's necessary to do otherwise, all branches should be created off of main.

Branches should use the following naming conventions:

When ready to merge, submit a Pull Request into main. All code will be reviewed by the lead developer on the project before being merged into main.

Write clear and concise commit messages describing the changes you are making and why. If there are any issues associated with the commit, include the issue # in the commit title.

• This project uses the BEM naming convention.
• This project uses Stylelint to maintain a consistent code style. Errors are flagged in the console during development and can be automatically fixed by running yarn run lint:styles-fix.

It is recommended to use the following extensions when working on this project to assist with code formatting:

• Veuter
• ESLint
• Prettier

This work is licensed under a Creative Commons Attribution-ShareAlike 4.0 International License.