1 / 12

STC for VOEvent

STC for VOEvent. Arnold Rots CfA/SAO. STCLite …. STCLite …. … is dead. STC Basics. Comprehensive metadata specification of the volume in coordinate space taken up by a particular data product (including telescopes) Intertwined coordinates: Time Space Spectral Redshift/Doppler.

lori
Download Presentation

STC for VOEvent

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. STC for VOEvent Arnold RotsCfA/SAO

  2. STCLite … VOEvent II - Tucson: STC

  3. STCLite … … is dead VOEvent II - Tucson: STC

  4. STC Basics • Comprehensive metadata specification of the volume in coordinate space taken up by a particular data product (including telescopes) • Intertwined coordinates: • Time • Space • Spectral • Redshift/Doppler VOEvent II - Tucson: STC

  5. STC Basics (requirements) • Complete • Internally consistent • Cover a multitude of coordinate systems: • Celestial (equatorial, galactic, …) • Cartesian • Geographic • Solar/planetary • Detector coordinates • Unit sphere • … VOEvent II - Tucson: STC

  6. STC Basics (components) • Coordinate system • Coordinate frames • Reference frame • Reference position (origin) • Coordinates • Values • Errors • … • Coordinate volume • Regions allow any shape to be specified VOEvent II - Tucson: STC

  7. STC for Observations • Where were you looking? • Time, space (direction), (ν, λ, E), (z) • Coordinate system – reference frames • Position, errors, (FOV) • Where were you when you were looking? • Geographic position • Spacecraft ephemeris VOEvent II - Tucson: STC

  8. STC-X Referencing • Promote standardization • XInclude • Point to a file • Formally requires the link to be substituted by the entire file contents • XLink • Point to anything; e.g., an element in a document • Client decides what to do with it (if anything) VOEvent II - Tucson: STC

  9. STC Base Type • Optional Xlink attributes: type, href • type=simple href=<URI> • Optional attribute idref • reference to another element in the same document • Optional attribute id • Allowing the element to be referenced • Optional contents VOEvent II - Tucson: STC

  10. WhereWhen Example <WhereWhen> <ObservatoryLocation id="MyObservatory" xlink:type="simple" xlink:href=“ivo://STClib/Observatories.xml#MyObservatory"/> <ObservationLocation> <AstroCoordSystem id="UTC-FK5-TOPO" xlink:type="simple" xlink:href=“ivo://STClib/AstroCoordSystems.xml#UTC-FK5-TOPO"/> <crd:AstroCoords coord_system_id="UTC-FK5-TOPO"> <crd:Time unit="s"> <crd:TimeInstant> <crd:ISOTime>2005-04-15T23:59:59</crd:ISOTime> </crd:TimeInstant> <crd:Error>2</crd:Error> </crd:Time> <crd:Position2D unit="deg"> <crd:Value2>141.102469.3064</crd:Value2> <crd:Error2Radius>0.05</crd:Error2Radius> </crd:Position2D> </crd:AstroCoords> </ObservationLocation> </WhereWhen> VOEvent II - Tucson: STC

  11. Add Diamond-shaped Region <AstroCoordArea coord_system_id="UTC-FK5-TOPO"> <Region> <reg:Polygon unit="deg"> <reg:Vertex> <reg:Position>141.1 69.2</reg:Position> </reg:Vertex> <reg:Vertex> <reg:Position>140.9 69.3</reg:Position> </reg:Vertex> <reg:Vertex> <reg:Position>141.1 69.4</reg:Position> </reg:Vertex> <reg:Vertex> <reg:Position>141.3 69.3</reg:Position> </reg:Vertex> </reg:Polygon> </Region> </AstroCoordArea> VOEvent II - Tucson: STC

  12. Empty Elements • What if an element is empty (now allowed) or absent (may be allowed)? • It is UNKNOWN • What does that mean? • It is up to the client to either reject or assume a sensible default • i.e., sensible is in the eye of the beholder • If you don’t want your clients guessing, be specific VOEvent II - Tucson: STC

More Related