Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Below are two sets of metadata which will be stored in the new archive in regard to Images and the Image Sets to which they belong.  Included where relevant are the equivalent fields in the Virtual Observatory ObsCore Data Model,  a potential source from which to obtain the data, and a comment.  The images table was written specifically with the idea of spacial spatial images in mind.  Other data products (spectra, time series, etc) would have different amounts of granularity in the header information available.

...

  • Split center_position and observing_band fields
  • Retaining image size data (the VO _xel fields)
  • Add fields for spectral resolution, physical data description, and spacial spatial region information
  • Determination and acquisition of time-domain information.

...

Column NameVO EquivalentSourceComments
sourcenametarget_nameOBJECT Keyword
ra (center_position)s_raCenter of Ra Axis
dec (center_position)s_decCenter of Dec Axis
field_of_views_fovAverage of NAXISn*CRDELn of the Spacial spatial Axes
spacialspatial_regions_regionDerived from Spacial spatial DataSTC-S String Defined in the TAP (Dowler, et al 2010)
ra_element_counts_xel1Relevent NAXISn Keyword
dec_element_counts_xel2Relevent NAXISn Keyword
spacialspatial_resolutions_resolutionAverage of CRDELn of the Spacial spatial Axes
starttimet_max

Temporal domain information for an image is dependent upon the observation(s) used in its generation.  Some controlling process (Like Vlass Manager, whatever imaging pipeline we create, and any image manipulation software we use) will need to supply it. 


endtimet_min
exposure_timet_exptime
min_frequency observing_band)em_minMinimum of Spectral Axis


The spectral information is recoverable from the FITS header, and will identify the spectral coverage, and total bandwidth processed for the image. 

max_frequency (observing_band)em_maxMaximum of Spectral Axis
spectral_resolutionem_res_powerSpectral CRDELn Keyword
polarization_codepol_states

Currently, there is insufficient information provided about the polarization information of the image in the quicklook FITS headers.  There is a STOKES axis, but no further information is provided. 

Since Single Epoch images will be created in Stokes I, Q, and U, that information must be provided to distinguish the files.  Adding the stokes parameter name to the CTYPEn or CUNITn header keywords would solve this issue. 

telescopeinstrument_nameTELESCOP KeywordThis must accommodate images for multiple instruments (i.e. VLA + Single Dish)
file_id
automatically generatedlink to information about the physical file
image_idobs_idautomatically generatedUnique Identifier for the Image
image_units

o_ucd

BTYPE & BUNIT KeywordsDescription of the physical quantity measured in the image
max_intensity


These values are can be determined from the data portion of the image file in conjunction with the BSCALE & BZERO keywords.  The library which is used for FITS interaction for ingestion can perform these calculations, but no information about the speed of results is yet available.

min_intensity

rms_noise

thumbnail
weblog, a PNG with identical name

...