Each K2 Campaign has a duration of approximately 80 days and remains fixed upon a single boresight position. This page details the previous, current, and future K2 Campaign fields.
Observed and planned
Field dates and positions
|0||2014 Mar 08||2014 May 27||2014 Sep 08||06:33:11||+21:35:16||Near Galactic Anti-center, M35, NGC 2158|
|1||2014 May 30||2014 Aug 21||2014 Dec 23||11:35:46||+01:25:02||North Galactic Cap|
|2||2014 Aug 23||2014 Nov 13||2015 Mar 16||16:24:30||-22:26:50||Near Gal Center, M4, M80, M19, Upr Sco, ρ Oph|
|3||2014 Nov 14||2015 Feb 03||2015 Jul 17||22:26:40||-11:05:48||South Galactic Cap, Neptune|
|4||2015 Feb 07||2015 Apr 23||2015 Sep 04||03:56:18||+18:39:38||M45 (Pleiades), NGC1647, Hyades|
|5||2015 Apr 27||2015 Jul 10||2015 Oct 31||08:40:38||+16:49:47||M44 (Beehive), M67|
|6||2015 Jul 14||2015 Sep 30||2016 Feb 12||13:39:28||-11:17:43||North Galactic Cap|
|7||2015 Oct 04||2015 Dec 26||2016 Apr 20||19:11:19||-23:21:36||Near Galactic Center, NGC 6717, Pluto|
|8||2016 Jan 03||2016 Mar 23||2016 Jul 04||01:05:21||+05:15:44||Uranus, IC1613|
|9†||2016 Apr 21||2016 Jul 01||2016 Sep 01||18:01:25||-21:46:47||Gal Center, M21, M18, M25, M8, Earth, Mars|
|10||2016 Jul 06||2016 Sep 20||2016 Nov 28||12:27:07||-04:01:38||North Galactic Cap|
|11||2016 Sep 24||2016 Dec 08||2017 Feb 06||17:21:33||-23:58:33||Galactic Center, Saturn|
|12||2016 Dec 15||2017 Mar 04||2017 May 30||23:26:43||-05:05:44||South Galactic Cap, Chiron, Mars|
|13||2017 Mar 08||2017 May 27||2017 Jul 27||04:51:11||+20:47:11||Hyades, Taurus|
|14||2017 May 31||2017 Aug 19||2017 Oct 23||10:42:44||+06:51:06||North Galactic Cap, Wolf 359, WASP-104|
|15||2017 Aug 23||2017 Nov 08||2018 Jan 14||15:34:28||-20:04:44||Upper Sco, GW Lib, HP Lib|
|16||2017 Nov 19||2018 Jan 28||2018 Apr 01||21:21:58||-16:36:30||Comet 29P, WASP-70, WASP-89|
†Note: field 9 is a forward-facing campaign (+VV), enabling simultaneous observations to be made from the ground.
The fields below indicate fields being considered for Campaign 17 and beyond. The coordinates are not final and will change to optimize science and accommodate engineering constraints (e.g. the availability of guide stars).
We encourage the community to provide input on the placement of these fields by emailing us at email@example.com.
Proposed future fields
|Field||Start after†||End before†||RA (J2000)||Dec (J2000)||Comments|
|17††||2018 Feb 1||2018 Apr 22||12:33:24||-01:57:31||Forward-facing|
|18||2018 Apr 22||2018 Jul 12||07:31:33||+20:13:38||Approximate position|
†Note: the dates shown are the earliest possible start dates, and the latest possible end dates. The feasible date ranges of these campaigns overlap slightly to allow for some flexibility in the final choice of dates and positions.
††Note: field 17 is proposed to be a forward-facing campaign (+VV), enabling simultaneous observations to be made from the ground during the campaign.
Target selection tools
You can learn more about the installation and usage of these tools on the software page.
To enable the community to create custom field visualisations, the coordinates in the footprint plots shown above have been exported to machine-readable CSV and JSON text files. These files specify the coordinates of the corners of each CCD channel in each campaign, along with the observing dates and module numbers. The JSON files also provide galactic coordinates.
Campaigns 0 through 16:
Campaigns 17 and 18:
Usage of the JSON files
Files in the JSON format can easily be read into a Python script using the standard json module. For example:
import json footprint_dictionary = json.load(open("k2-footprint.json"))
The dictionary obtained in this way may then be used to plot the position of a CCD channel on the sky. For example, the position of channel #10 in Campaign 13 can be visualised as follows:
import matplotlib.pyplot as pl mychannel = footprint_dictionary["c13"]["channels"]["10"] pl.plot(mychannel["corners_ra"] + mychannel["corners_ra"][:1], mychannel["corners_dec"] + mychannel["corners_dec"][:1]) pl.show()
Beware however that a plot obtained in this way approximates channel edges as straight lines in the 2D-projected sky.
In addition to the JSON and CSV files described above, we also offer sky coverage information in the MOC data format. MOC is a HealPix-based VO standard which can be opened using the Aladin interactive sky atlas, where it can be used to query remote databases given a K2 footprint.
The MOC files, one for each Campaign, can be downloaded from a GitHub repository.