openmct/example/msl
Henry 4674918b4b [Examples] #359 Updated to attempt connection to remote data source and fallback to local if unavailable
Minor change to readme

Fixed JSLint errors

More JSLint errors

[Example] Rems data integration - disabled bundle by default.

[Examples] REMS data integration - added newlines at end of files

[Example] Added time conductor support to REMS data integration

Added caching of results

[Examples] Added domain format to REMS data #359

[Example] #637 Added local proxy to app.js to allow cross-origin requests

Updated readme
2016-02-26 14:03:10 -08:00
..
data [Examples] #359 Updated to attempt connection to remote data source and fallback to local if unavailable 2016-02-26 14:03:10 -08:00
src [Examples] #359 Updated to attempt connection to remote data source and fallback to local if unavailable 2016-02-26 14:03:10 -08:00
bundle.js [Examples] #359 Updated to attempt connection to remote data source and fallback to local if unavailable 2016-02-26 14:03:10 -08:00
README.md [Examples] #359 Updated to attempt connection to remote data source and fallback to local if unavailable 2016-02-26 14:03:10 -08:00

To use this bundle, add the following paths to /main.js - './platform/features/conductor/bundle', './example/msl/bundle',

An example plugin that integrates with public data from the Curiosity rover. The data shown used by this plugin is published by the Centro de Astrobiología (CSIC-INTA) at http://cab.inta-csic.es/rems/

Fetching data from this source requires a cross-origin request which will fail on most modern browsers due to restrictions on such requests. As such, it is proxied through a local proxy defined in app.js. In order to use this example you will need to run app.js locally.

This example shows integration with an historical telemetry source, as opposed to a real-time data source that is streaming back current information about the state of a system. This example is atypical of a historical data source in that it fetches all data in one request. The server infrastructure of an historical telemetry source should ideally allow queries bounded by time and other data attributes.