Data API for the SolarSurfer project.
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Type Name Latest commit message Commit time
Failed to load latest commit information.

Build Status


Data API for the SolarSurfer project.


This is the data API for the BlueRobotic's SolarSurfer project. It offers SolarSurfer command and telemetry history over a RESTful HTTP interface. This service is nominally located at and


The API is capable of storing telemetry for multiple simultaneous vehicles. All incoming data is assigned a vehicle and a mission by the imei located in the incoming telemetry message. The imei (or International Mobile Station Equipment Identity) is a unique number assigned to each modem. When a new piece of data arrives, the API first tries to determine is there is a vehicle in the database with a matching imei. If there is a not, a new vehicle is created. Next, the API looks for an active mission assigned to that vehicle. If one does not exist, a new mission is created. That piece of data is then saved in the database against that mission.


This API is built on MongoDB and exposes json documents via REST-like endpoints. There are a four available endpoints:

Endpoint Actions /:id Actions
/vehicle GET, POST GET, PUT
/mission GET, POST GET, PUT
/telemetry GET, POST
/command GET, POST

All POST and PUT requests require the correct ?token= to be passed in the query string.

On the collection endpoints, the following query parameters are supported:

  • ?where={"mission":1} - used to limit which documents get returned
  • ?fields={"mission":1} - used to limit which fields get returned
  • ?sort=-_date - used to sort the documents before being returned
  • ?limit=10 - used to limit the number of documents that get returned
  • ?skip=10 - used to control which group of documents are returned


To run this service locally:

git clone
npm install
npm start

The API should now be available at http://localhost:7873/.

To, run the test suite:

npm test

To deploy to Heroku, follow this guide. If you already have the Heroku Toolbox installed and have logged into Heroku through your terminal, this basically boils down to:

heroku create  # or git remote add heroku 
heroku addons:add mongolab  # requires a credit card added to your Heroku account
git push heroku master
heroku open

Once you get up and running, also try out these fun commands:

heroku ps
heroku logs
heroku run node

There is also a backup script that let's you save a local copy of the entire remote database. Backups are stored in backups/ after running the script:

./scripts/ database_name user_name password

Change History

This project uses semantic versioning.

v0.3.0 - 2014/10/12

  • Added command POSTing and forwarding
  • Added database backup script (must have mongodump installed)
  • Removed /raw/ endpoints - raw messages is simply stored alongside fully expanded messages now
  • Depend on a specific version of message format to prevent future errors

v0.2.0 - 2014/12/06

  • Added GET parameter test cases for where, fields, sort, limit, and skip
  • Refactored auth to token secret string via an environment variable
  • Add PUT for /vehicle and /mission

v0.1.0 - 2014/08/08

  • Initial release
  • Used for Santa Monica Canyon testing