Evaluation of the Near Earth Object Surveillance Satellite (NEOSSat) Project

The Near Earth Object Surveillance Satellite (NEOSSat) project began in February 2005 with the signing of a Memorandum of Understanding (MOU) between the Canadian Space Agency (CSA) and the Department of National Defence (DND), establishing NEOSSat as a collaboration combining two projects: DND's space surveillance mission HEOSS (High Earth Orbit Space Surveillance) and the CSA's asteroid finding project NESS (Near Earth Space Surveillance). The two missions share the same passive optical sensor payload integrated into a multi-mission microsatellite bus. Each mission, however, is directed and managed by a different science team.

Following a competitive process, the NEOSSat development contract, encompassing Phases B, C and D, was awarded to Dynacon in July 2007. In 2008 Dynacon sold its satellite business to Microsat Systems Canada Inc. (MSCI), and MSCI continued the project as a subcontractor to Dynacon. After lengthy delays, NEOSSat was launched in February 2013 by Antrix Corporation, an India-based launch provider.

The scope of the NEOSSat mission includes:

  • -Development of an affordable multi-mission bus for future CSA and/or DND missions, i.e., the design of the satellite platform allows the same bus to be used for several future microsatellite missions;
  • -Discovery of new asteroids and comets and monitoring their trajectories; and
  • -Development of technology and expertise for monitoring satellites and space debris in medium Earth orbits (MEO) and geosynchronous Earth orbits (GEO). .
  • The focus of this evaluation was on the CSA components of NEOSSat, i.e., the development of a multi-mission bus and the discovery and monitoring of new asteroids and comets and monitoring their trajectories. The evaluation covers the entire history of NEOSSat, from the CSA's signing of its two contracts in 2005 to the end of December 2013.

    Datasets available for download

    Additional Info

    Field Value
    Last Updated October 20, 2025, 02:57 (UTC)
    Created October 20, 2025, 02:57 (UTC)
    Domain / Topic
    Domain or topic of the dataset being cataloged.
    Title
    Title for the Dataset.
    Evaluation of the Near Earth Object Surveillance Satellite (NEOSSat) Project
    Description
    A description of the dataset.

    The Near Earth Object Surveillance Satellite (NEOSSat) project began in February 2005 with the signing of a Memorandum of Understanding (MOU) between the Canadian Space Agency (CSA) and the Department of National Defence (DND), establishing NEOSSat as a collaboration combining two projects: DND's space surveillance mission HEOSS (High Earth Orbit Space Surveillance) and the CSA's asteroid finding project NESS (Near Earth Space Surveillance). The two missions share the same passive optical sensor payload integrated into a multi-mission microsatellite bus. Each mission, however, is directed and managed by a different science team.

    Following a competitive process, the NEOSSat development contract, encompassing Phases B, C and D, was awarded to Dynacon in July 2007. In 2008 Dynacon sold its satellite business to Microsat Systems Canada Inc. (MSCI), and MSCI continued the project as a subcontractor to Dynacon. After lengthy delays, NEOSSat was launched in February 2013 by Antrix Corporation, an India-based launch provider.

    The scope of the NEOSSat mission includes:

    • -Development of an affordable multi-mission bus for future CSA and/or DND missions, i.e., the design of the satellite platform allows the same bus to be used for several future microsatellite missions;
  • -Discovery of new asteroids and comets and monitoring their trajectories; and
  • -Development of technology and expertise for monitoring satellites and space debris in medium Earth orbits (MEO) and geosynchronous Earth orbits (GEO). .
  • The focus of this evaluation was on the CSA components of NEOSSat, i.e., the development of a multi-mission bus and the discovery and monitoring of new asteroids and comets and monitoring their trajectories. The evaluation covers the entire history of NEOSSat, from the CSA's signing of its two contracts in 2005 to the end of December 2013.

    Tags / Keywords
    Keywords/tags categorizing the dataset.
    Format (CSV, XLS, TXT, PDF, etc)
    File format of the dataset.
    Dataset Size
    Dataset size in megabytes.
    Metadata Identifier
    Metadata identifier – can be used as the unique identifier for catalogue entry
    Published Date
    Published date of the dataset.
    2014-02-01
    Time Period Data Span (start date)
    Start date of the data in the dataset.
    Time Period Data Span (end date)
    End date of time data in the dataset.
    GeoSpatial Area Data Span
    A spatial region or named place the dataset covers.
    Field Value
    Access category
    Type of access granted for the dataset (open, closed, service, etc).
    License
    License used to access the dataset.
    Open Government Licence - Canada
    Limits on use
    Limits on use of data.
    Location
    Location of the dataset.
    https://open.canada.ca/data/en/dataset/dd76f7c5-42e7-4b8e-846b-0a227150ad7b
    Data Service
    Data service for accessing a dataset.
    Owner
    Owner of the dataset.
    Canadian Space Agency | Agence spatiale canadienne
    Contact Point
    Who to contact regarding access?
    Contact Point Email
    The email to contact regarding access?
    Publisher
    Publisher of the dataset.
    Publisher Email
    Email of the publisher.
    [email protected]
    Author
    Author of the dataset.
    Author Email
    Email of the author.
    Accessed At
    Date the data and metadata was accessed.
    Field Value
    Identifier
    Unique identifier for the dataset.
    Language
    Language(s) of the dataset
    Link to dataset description
    A URL to an external document describing the dataset.
    Persistent Identifier
    Data is identified by a persistent identifier.
    Globally Unique Identifier
    Data is identified by a persistent and globally unique identifier.
    Contains data about individuals
    Does the data hold data about individuals?
    Contains data about identifiable individuals
    Does the data hold identifiable data about individual?
    Contains Indigenous Data
    Does the data hold data about Indigenous communities?
    Portal Type
    Platform type of the source portal.
    Field Value
    Version
    Version of the datatset
    None
    Source
    Source of the dataset.
    None
    Version notes
    Version notes about the dataset.
    Is version of another dataset
    Link to dataset that it is a version of.
    Other versions
    Link to datasets that are versions of it.
    Provenance Text
    Provenance Text of the data.
    Provenance URL
    Provenance URL of the data.
    Temporal resolution
    Describes how granular the date/time data in the dataset is.
    GeoSpatial resolution in meters
    Describes how granular (in meters) geospatial data is in the dataset.
    GeoSpatial resolution (in regions)
    Describes how granular (in regions) geospatial data is in the dataset.
    Field Value
    Indigenous Community Permission
    Who holds the Indigenous Community Permission. Who to contact regarding access to a dataset that has data about Indigenous communities.
    Community Permission
    Community permission (who gave permission).
    The Indigenous communities the dataset is about
    Indigenous communities from which data is derived.
    Field Value
    Number of data rows
    If tabular dataset, total number of rows.
    Number of data columns
    If tabular dataset, total number of unique columns.
    Number of data cells
    If tabular dataset, total number of cells with data.
    Number of data relations
    If RDF dataset, total number of triples.
    Number of entities
    If RDF dataset, total number of entities.
    Number of data properties
    If RDF dataset, total number of unique properties used by the triples.
    Data quality
    Describes the quality of the data in the dataset.
    Metric for data quality
    A metric used to measure the quality of the data, such as missing values or invalid formats.

    0 Comments

    Please login or register to comment.