...
- site - GBT or VLA
- effective datetime UTC - used to determine effective schedule when previous schedule has been updated.
- obs start datetime UTC
- obs end datetime UTC
- center RA of the sources
- center Dec of the sources
- radius over which the sources are distributed (for GBT map observations)
- tracking rate of instrument (for non-sidereal observations)
- frequency range of observation (in Hz or MHz)
- text field (for notes)
The JSON keys - these are the JSON keys with an example API response:
- freq_lower_hz":26000000000.0,
- "freq_upper_hz":40000000000.0,
- "notes":"inAdv:True",
- "obs_id":"20B-062.sb38816982",
- "site_alt_meters" :2124.0,
- "site_id":"vla",
- "site_lat_deg":34.07874917,
- "site_lon_deg":-107.6177275,
- "src_dec_j2000_deg":38.02661111111111,
- "src_end_utc":"2023-08-02T16:43:14.000772",
- "src_id":"J0418+3801_BU",
- "src_is_pulsar_bool":false,
- "src_ra_j2000_deg":64.58865416666667,
- "src_start_utc":"2023-08-02T16:42:44.000936",
- "trk_rate_dec_deg_per_sec":0.0,
- "trk_rate_ra_deg_per_sec":0.0
Although radians is the default unit for angles in the international system, ISO 6709 sets degrees for point location by coordinates. Also, major astronomical tools (Simbad, AstroPy) use degree instead of radiansare described in each Observatory data sender.
API process - will expose REST interface to SpaceX. API process will receive request from SpaceX, query Obs Status DB for GBT and VLA observation status data and format and send response to SpaceX. API format to be finalized. Interface security needs to be finalized. API process will be deployed on a VLA web server.
...