MocServer / Form & Documentation v5.06 - May 2022
MOC Server tool for retrieving as fast as possible the list of astronomical data sets (32794 catalogs, surveys, ... harvested from CDS and VO servers) having at least one observation in a specifical sky region/and or time range. The default result is an ID list. MOC Server is based on Multi-Order Coverage maps (MOC) described in the IVOA REC standard.
This form allows one to discover, test and check the various HTTP parameters supported by the MocServer remote API (inline spec).
RA,DEC must be expressed in degrees (ICRS), SR in degrees, TIME as 2 MJD values space separated
This version only supports Circle & Polygon in ICRS
MOC must be a string following the ASCII or JSON syntax
MOC must be a HTTP stream (FITS, ASCII or JSON syntax)
MOC must be a local file (FITS, ASCII or JSON syntax)
'intersect' param determines if the query coverage must overlap (default), enclosed, or cover the matching collection coverages,
'spacesys' and 'timesys' params determine the space and the time reference system concerned by the query coverage (if not specified, reference system will be ignored).
The ID selection must be an identifier or a template(**) of identifier or a comma separated template list. The field names are used for filtering the properties (***). The associated value must be a template(**) or a comma separated template list. The boolean logic is OR inside comma lists and AND between fields.
In "record" get mode, the list of output fields can be explicitely specified in "fields" as a comma separated template(**) list.
Previous basic query modes can also accept any of these additional parameters in order to filter and/or control the result.
Each operand is a filter rule expression as described above. The operators are the union (→ ||), the intersection (→ &&) and the subtraction (→ &!).Parenthesis must be used to change the default operator priority. Expression values containing control characters (,),|,& must be quoted (" or '), and the possible internal quotes must be backslashed.Output control fields described above may be added for controlling the output content and format.
Previous query modes can also accept the MOC retrieval mode. In case of Cone Search or other query by region, the resulting MOC will be the intersection with the union (or intersection) of all matching MOCs
(*) ID is built from "creator_did" (alternatively "publisher_did", or or "creator_id/obs_id" or "publisher_id/obs_id") without "ivo://" prefix and only with slash (/) separator (canonical form)
(**) A template is a mask with basic wildcards (*, ?), possibly starting with (!) for negation mode or (<,>,<=,>=) for numerical, ISO8601 date or alphanumerical inequality test, ormin..max for range test.
(***) The field name must be prefixed by "filter." in case of parameter name synonym. It can incorporate wildcards.List of field name templates, comma (,) separated, are authorized. Templates without any explicit field name are relative to ID.
(****) An OR logic algorithm is used in case of list of fields/values/masks, except for the case where the operator is != (ex: obs_title,ID=!*CDS*,!*ESAVO*)
The query must be an identifier or a mask of identifier (with wildcards), or a list of, comma separated.
The resulting MOC will be the union (resp. intersection) of the matching MOCs, projected on the spatial dimension (smoc), or explicitly on the temporal dimension (tmoc), or on both dimensions (stmoc) or according to the matching MOCs (anymoc). (If a physical dimension is required but missing, it is assumed to be present on the whole coverage.)
The resolution of the resulting MOC can be reduced, either explicitly by setting the maximum order (1 value in the case of a SMOC or TMOC, or 2 values preceded by an 's' and a 't' in the case of a STMOC), and/or by indicating the maximum allowed size suffixed by 'KB' or 'MB'.
In case of empty list, all records are provided. If the list only contains one TIMESTAMP value, all records updated after the specified date will be provided. If the IDs are provided without =TIMESTAMP suffix, only these records will be provided. If the IDs are provided with a =TIMESTAMP suffix, only the records, amongs this list, updated after each specified date + the new records will be provided. The returned fields may be controlled with the "fields" parameter as described above. The IDs removed or unknown by the MOC server will be returned with the dedicated field: MOCSERVER_REMOVE = true.
List of ID[=TIMESTAMP] must be coded in ASCII format, one per line and sent via POST method (multipartID: maj).