:Data Set Overview::The data from the Rosetta Navigation Camera (NavCam) was extracted byBernhard Geiger; the data set was constructed and submitted by MaudBarthelemy on behalf of the Planetary Science Archives (PSA).The data have been observed and measured from 5th Apr 2016 to 3rdMay 2016. The frequency of the navigation slots was of one 2x2 rasterevery five hours, with interruption by manoeuvres. One raster withfour images was acquired with CAM2 in order to check its healthstatus. 528 navigation images were taken. In addition 280 contextimages and 4 calibration ones were taken, which makes a totalof 813 images.Three planned context images were not acquired due to ground stationissue.There is one navigation image with lost rows due also to groundstation issue.The orbiter was executing far fly-by arcs starting at 200km in theterminator plane and descending to 80km at 80degrees phase angle.Then, it executed a close fly-by through zero degree phase angle adnat 30km minimum distance. The outbound trajectory arc was captured at140km. The orbiter approached the comet at 70km at terminator plane.The insertion into bound orbits was done by a night side arc with amaximum phase angle of 120 degrees that reduced the distance to 19km.The bound orbits at the end of MTP028 was at 19km distance.All images in this data set are raw and uncalibrated data taken usingthe imaging mode. The data set contains images resolved using bothNavCams onboard the Rosetta S/C and the DATA directory is organisedto reflect this with two sub directories: - CAM1 - CAM2CAM2 directory is only present if CAM2 observations are done.After hibernation exit CAM2 was only switched on to confirm its healthstatus in a check-out. During the comet escort phase CAM2 will only beused in the case of a failure of the nominal camera CAM1.For each image, the user can also find the FITS format of theobservation in the EXTRAS directory.:Filename Convention::In DATA:The filenaming convention for all data levels is given by: __. ROS CAM1 YYYYMMDDThhmmss IMG CAM2 LBLExamples: ROS_CAM1_20140223T081016.IMG ROS_CAM1_20140223T081016.LBL ROS_CAM2_20140223T094017.IMG ROS_CAM2_20140223T094017.LBLIn BROWSE:The filenaming convention for all data levels is given by: __. ROS CAM1 YYYYMMDDThhmmss JPG CAM2 LBLExamples: ROS_CAM1_20140223T081016.LBL ROS_CAM1_20140223T081016.JPG ROS_CAM2_20140223T094017F.LBL ROS_CAM2_20140223T094017.JPGIn EXTRAS:The filenaming convention for all data levels is given by: __F. ROS CAM1 YYYYMMDDThhmmss FIT CAM2 LBLExamples: ROS_CAM1_20140223T081016F.FIT ROS_CAM1_20140223T081016F.LBL ROS_CAM2_20140223T094017F.FIT ROS_CAM2_20140223T094017F.LBL:Geometry Information - Coordinate System::The label files include the following geometric variables:- SC SUN POSITION VECTOR: The vector from the spacecraft to the Sun in equatorial J2000 inertial frame.- SC TARGET POSITION VECTOR: The vector from the spacecraft to the centre of the comet nucleus in equatorial J2000 inertial frame.- SC TARGET VELOCITY VECTOR: The spacecraft to comet nucleus velocity vector in in equatorial J2000 inertial frame.- TARGET CENTER DISTANCE: The distance between the spacecraft and the comet nucleus centre. (Note that also for checkout and stellar calibration images the comet nucleus distance is given here.)- SUB SPACECRAFT LATITUDE and SUB SPACECRAFT LONGITUDE: The latitudeand longitude of the sub-spacecraft point derived from the FlightDynamics body-fixed reference frame implicitly specified by theinformation provided in the comet attitude file CATT.- RIGHT ASCENSION and DECLINATION: Right Ascension and Declination ofthe camera boresight direction in equatorial J2000 inertial frame.- CELESTIAL NORTH CLOCK ANGLE: The direction of celestial north at the center of the image - measured from the upward direction, clockwise to the direction toward celestial north.- SOLAR ELONGATION: The angle between the line of sight of observation and the direction of the Sun.All geometric values are calculated for the time t : IMAGE TIME(and not START TIME).:

All data have been validated by ESA and found as expected. Any exceptions are noted by the DATA_QUALITY field in the label files.