...
Database | Resource |
---|---|
Data Archive | Observation (e.g. FITS-Files) |
Staging Table | Event, ... (e.g. Event lists) |
Feature Property Database | Feature (such as Active Regions), FeatureProperty (e.g. Area, Contour, Zurich-Class, ...) |
Predictions Config DB | Scalars, Vectors, Matrices (e.g. Algo-Configurations) |
Prediction DB | ? |
Infrastructure Configuration DB | Algorithm, Person, |
Standards
- Dates should be in ISO 8601
- Date/Time formats should follow http://www.w3.org/TR/NOTE-datetime
This is a test to see if we can create inline comments And follow up
- URI Templates: https://tools.ietf.org/html/rfc6570
- Collection+JSON: http://amundsen.com/media-types/collection/
The API is self-documenting such that there a single entry point to all databases. This would be access to the resources.
Resources
Anything accessible through the API is a "resource". All available resources can be listed.
Get list of observation types | ||||||
---|---|---|---|---|---|---|
Query | https://api.flarecast.eu/
| |||||
Result |
|
...
The file archive is basically a directory structure from where the files can be loaded through the http:// protocol.
Get list of available observationsobservation types | ||||||
---|---|---|---|---|---|---|
Query | https://api.flarecast.eu/observations/list | |||||
Result |
|
Search for files | ||||||
---|---|---|---|---|---|---|
Query | https://api.flarecast.eu/
| |||||
Result |
|
...
Get list of features | ||||||
---|---|---|---|---|---|---|
Query | https://api.flarecast.eu/
| |||||
Result |
|
Template | ||||||
---|---|---|---|---|---|---|
Query | https:
| |||||
Result |
|
...