Introducing MetaSat

The MetaSat team is working to create metadata and example schemas that can be used to describe small satellite (SmallSat) missions. This work will help facilitate the ease of sharing information between missions and lower the barrier of entry into the field.

Why metadata?

Metadata is most simply defined as data about data. For example, a book contains data: the words on the page. The metadata is information about the book, such as the title, author, page count, publisher, and more. Space missions also have data—for example, the information a satellite collects and sends back to earth. The metadata about a space mission might include information about the satellite components, people and organizations involved with the mission, the launch date, or information about any ground stations receiving information from the spacecraft.

Right now, space mission metadata is not standardized, which makes it hard for different teams to talk to each other, collaborate, or share advice about what works or doesn’t work in SmallSat missions. Our goal with MetaSat is to create a metadata schema that can be shared and expanded upon, and which will eventually facilitate information sharing between satellite missions.

Why linked data?

MetaSat is being designed to take advantage of linked. Linked data is used by the web to link together related information. This facilitates both the sharing of information and the synthesis of new ideas. For more information on linked data, visit

Our work so far

The Wolbach library is working closely with the Libre Space Foundation (LSF) to create MetaSat. LSF has direct experience working on SmallSat missions and runs SatNOGS, a global network of ground stations that collects satellite observations and stores them in a database. The SatNOGS Network stores information about both the ground stations in the network and their observations, and the SatNOGS database (SatNOGS DB) stores information about active satellites. SatNOGS will be one of the earliest adopters of the MetaSat schema.

We are currently basing our schema off of four use cases: Missions, Spacecraft, Observations, and Ground Stations. Users will be able to mix and match the use cases as they see fit. For example, a user scheduling an observation on their ground station can link the Observation metadata to Ground Station metadata and Spacecraft metadata in a single JSON-LD file. A ground station owner can link their Ground Station metadata to several instances of Observation metadata to reflect the observations taken by their ground station. Our hope is that the modular nature of the project will allow a high degree of flexibility for our users.