Observatories and sites
An observatory is the organizational unit that manages one or more telescopes at a single physical site. It carries the institutional metadata, the operational constraints that apply to everything on the site, and the things that aren’t telescope-specific (site devices such as weather sensors and site IP cameras, and observatory-wide operational constraints).
If you’re an owner: this is the record your organization owns. Every telescope you bring online lives under one observatory.
Site vs. Observatory
Section titled “Site vs. Observatory”The two records are deliberately separate:
- A Site is the geographic location — latitude, longitude, elevation, country, optional IAU code. Sites can host multiple observatories (e.g., a mountain with several independent facilities).
- An Observatory is the institutional facility on that site — ownership, public visibility, weather sensors, the telescopes you operate. Its site link is optional, and it carries its own representative latitude, longitude and elevation.
Both records are provisioned by Skynet staff today; editing existing records uses PATCH /v1/sites/{uid} (Skynet staff, or a member with observatory management rights in the site’s owning organization) and PATCH /v1/observatories/{uid} (owners and device managers). See Onboarding for how to request a new one.
What lives on an observatory record
Section titled “What lives on an observatory record”| Field group | What it controls |
|---|---|
| Name, slug, IAU code | Display and lookup |
| Ownership | Which user or organization owns the observatory |
| Site association | Which site the observatory sits on (optional) |
| Public / private visibility | Whether the observatory appears on public surfaces such as the public Live page; its management pages stay limited to the owner’s members either way |
| Photo | The image shown on the observatory page, uploaded on its Overview; live video comes from its IP cameras |
| Weather sensors | Site-wide environmental telemetry (feeds into observing constraints) |
| Operational constraints | Constraints that gate observing for every telescope on the observatory |
| Telescopes | One or more telescopes — each modeled in its own record |
Operational constraints that live on the observatory apply to every telescope at the site (typical example: a single weather-sensor reading controlling go/no-go for all telescopes under the dome). Telescope-level constraints layer on top — see Telescope.
In the web app
Section titled “In the web app”For organization-owned observatories, the web app lists them under the organization’s Observatories page, and each observatory has three tabs: Overview (its photo and telescopes), Live and IP Cameras. There is no observatory settings page in the web app; other fields are edited through PATCH /v1/observatories/{uid} or by Skynet staff, and weather sensors and operational constraints are configured from SkyNode.