(r1) ObsLocTAP < IVOA

IVOA Web>IvoaDAL>ObsLocTAP (revision 1) (raw view)~~EditAttach~~
<span style="background-color: transparent; font-size: 22.75px;">ObsLocTAP</span><span style="background-color: transparent; color: #630000; font-size: 22.75px;"> protocol</span>

The Observation Locator Table Access Protocol (ObsLocTAP) specification describes the necessary data model elements and the access protocol to discover metadata <span style="background-color: transparent;">about observations for a given Astronomical Observatory through a uniform interface within the VO framework. The used data model makes reference to IVOA Observation </span><span style="background-color: transparent;">Data Model elements (Mireille, et al., 2017), removing the ones associated to datasets access, as these elements are not available yet for future </span><span style="background-color: transparent;">observations that are planned, scheduled, performed but not archived. In this way, present standard is focused on the access to metadata related to </span><span style="background-color: transparent;">the planning of a certain observatory, more than in the access to the scientific data products of a certain observation. Also, the data model </span><span style="background-color: transparent;">described in the present standard will be focused on metadata discovery, useful for multiwavelength coordination observations. However, and in </span><span style="background-color: transparent;">order to prevent coupling between </span><span style="background-color: transparent;">ObsCore</span><span style="background-color: transparent;"> and </span><span style="background-color: transparent;">ObsLocTAP</span><span style="background-color: transparent;"> standards, </span><span style="background-color: transparent;">ObsLocTAP</span><span style="background-color: transparent;"> defines its own data model.The access protocol will be expressed </span><span style="background-color: transparent;">by the implementation of an IVOA Table Access Protocol (TAP) (Patrick, Guy, & Doug, 2010), that, as described in the use cases, allows a powerful </span><span style="background-color: transparent;">discovery process and, also, the implementation of the use cases proposed in the present specification. ObsLocTAPservices could be registered </span><span style="background-color: transparent;">using a TAP VOResource Extension (Demleitner, Dowler, Plante, Rixon, & Taylor, 2015) providing the relevant </span><span style="background-color: transparent;">ObsLocTAP</span><span style="background-color: transparent;"> capability. Exact details of the </span><span style="background-color: transparent;">VOResource Extension will be defined in another appropriate standard definition.In the case of a simple use case, planned observations of </span><span style="background-color: transparent;">a certain target can be discovered via a TAP and ADQL (Iñaki, et al., 2008) query that searches for sky regions (or FOV) that overlap a certain </span><span style="background-color: transparent;">sky coordinate. Adding a certain radius to the sky coordinates and/or filtering by instrument identifier could expand this simple use case. As described </span><span style="background-color: transparent;">in TAP, the service will return a list of performed observations of the given target and also the future planned and/or scheduled observations in </span><span style="background-color: transparent;">VOTable format or, optionally, in other tabular serialization format, e.g. JSON. The information about the planned observation, in the near future, </span><span style="background-color: transparent;">will be subject to changes due to any operational issue (re-planning, </span><span style="background-color: transparent;">ToO</span><span style="background-color: transparent;"> alerts, etc...). Thus, an implementation of the service may </span><span style="background-color: transparent;">support additional search parameters (some of which may be custom to that particular service) to more finely control the selection of the observation </span><span style="background-color: transparent;">information.</span>

---+ <span style="background-color: transparent;">ObsLocTAP Datamodel</span>
| table_name | column_name | data type | units |
| ivoa.obsplan | t_planning | adql:DOUBLE | d |
| ivoa.obsplan | target_name | adql:VARCHAR | |
| ivoa.obsplan | obs_id | adql:VARCHAR | |
| ivoa.obsplan | obs_collection | adql:VARCHAR | |
| ivoa.obsplan | s_ra | adql:DOUBLE | deg |
| ivoa.obsplan | s_dec | adql:DOUBLE | deg |
| ivoa.obsplan | s_fov | adql:DOUBLE | deg |
| ivoa.obsplan | s_resolution | adql:DOUBLE | arcsec |
| ivoa.obsplan | t_min | adql:DOUBLE | d |
| ivoa.obsplan | t_max | adql:DOUBLE | d |
| ivoa.obsplan | t_exptime | adql:DOUBLE | s |
| ivoa.obsplan | t_resolution | adql:DOUBLE | s |
| ivoa.obsplan | em_min | adql:DOUBLE | m |
| ivoa.obsplan | em_max | adql:DOUBLE | m |
| ivoa.obsplan | em_res_power | adql:DOUBLE | |
| ivoa.obsplan | o_ucd | adql:VARCHAR | |
| ivoa.obsplan | pol_states | adql:VARCHAR | |
| ivoa.obsplan | pol_xel | adql:BIGINT | |
| ivoa.obsplan | facility_name | adql:VARCHAR | |
| ivoa.obsplan | instrument_name | adql:VARCHAR | |
| ivoa.obsplan | obs_release_date | adql:TIMESTAMP | date |
| ivoa.obsplan | t_plan_exptime | adql:DOUBLE | s |
| ivoa.obsplan | category | adql:VARCHAR | |
| ivoa.obsplan | priority | adql:INTEGER | |
| ivoa.obsplan | fov | adql:VARCHAR | |
| ivoa.obsplan | stc_s | adql:VARCHAR | |
---+ Possible prototypes

Some observatories have offered the possibility to collaborate on this standard by the creation of prototypes

   * XMM-Newton and Integral future observations publication
   * Chandra
   * nuStar
On the client side, there is a plan to modify ESASky to show the result of these server implementations

---+ Comments
Topic revision: r1 - 2019-03-01 - JesusSalgado
IVOA
Log in or Register
IVOA.net
Wiki Home
WebChanges
WebTopicList
WebStatistics
Twiki Meta & Help
IVOA
Know
Main
Sandbox
TWiki
TWiki intro
TWiki tutorial
User registration
Notify me
Working Groups
Interest Groups
Time Domain
Committees
Stds&Procs
www.ivoa.net
Documents
Events
Members
XML Schema