7. ODS Adoption

7.1. Current ODS RAS Community

The ODS system is currently being adopted, developed, and tested independently by the following non-NRAO radio astronomy facilities. Some have already had the Telescope Boresight Avoidance (TBA) engaged by SpaceX:

  • Hat Creek Radio Observatory - TBA operational

  • CSIRO Australia Telescope National Facility (CSIRO-ODS) - TBA operational

  • MIT Haystack Observatory (Haystack-ODS) - TBA operational

  • Owens Valley Radio Observatory (OVRO-ODS/DSA-2000) - under development

7.2. Steps to create your own ODS system

Although the current ODS JSON format is available for any radio observatory to use without any warranty by NRAO, please contact the NRAO ODS Helpdesk to inform us of your adoption plan as well as review and acknowledge all the disclaimer terms on ODS Data JSON Fields. This will help us keep you informed of any future releases and changes to the ODS JSON Schema.

Additionally, you will need to set up and maintain your own ODS API server to report your ODS Mitigations Requests (MRs), as summarized in the Developer Notes.

To have satellite operators utilize your ODS data, you will first need to contact each of the satellite operators individually (if your facility is based outside the US) or coordinate with the satellite operators through NSF (for US-based radio telescopes only). You will then need to grant access to the satellite operators for querying your ODS data with your own preferred authentication mechanisms, such as one in Authentication.