An project

Data Products Definition Document

  • M. Jurić
  • T. Axelrod
  • A.C. Becker
  • J. Becla
  • E. Bellm
  • J.F. Bosch
  • D. Ciardi
  • A.J. Connolly
  • G.P. Dubois-Felsmann
  • F. Economou
  • M. Freemon
  • M. Gelman
  • R. Gill
  • M. Graham
  • L.P. Guy
  • Ž. Ivezić
  • T. Jenness
  • J. Kantor
  • K.S. Krughoff
  • K-T Lim
  • R.H. Lupton
  • F. Mueller
  • D. Nidever
  • W. O’Mullane
  • M. Patterson
  • D. Petravick
  • D. Shaw
  • C. Slater
  • M. Strauss
  • J. Swinbank
  • J.A. Tyson
  • M. Wood-Vasey
  • X. Wu


This document describes the data products and processing services to be delivered by the Large Synoptic Survey Telescope (LSST).

LSST will deliver three levels of data products and services. Prompt (Level 1) data products will include images, difference images, catalogs of sources and objects detected in difference images, and catalogs of Solar System objects. Their primary purpose is to enable rapid follow-up of time-domain events. Data Release (Level 2) data products will include well calibrated single-epoch images, deep coadds, and catalogs of objects, sources, and forced sources, enabling static sky and precision time-domain science. The Science Platform will allow for the creation of User Generated (Level 3) data products and will enable science cases that greatly benefit from co-location of user processing and/or data within the LSST Archive Center. LSST will also devote 10% of observing time to programs with special cadence. Their data products will be created using the same software and hardware as Prompt (Level 1) and Data Release (Level 2) products. All data products will be made available using user-friendly databases and web services.
Note, prior to 2018 Data products were referred to as Level 1, Level 2, and Level 3; this nomenclature was updated in 2018 to Prompt Products, Data Release Products and User Generated Products respectively [LPM-231]. In the abstract of this document both nomenclatures are used but throughout the remainder of this document only the new terminology is used. In other project and requirements documentation, the old terminology will likely persist.