http://vo.imcce.fr/webservices/miriade/ephemcc_query.php?[parameters]

1. See the HOWTO section for a full description about how to name targets.
2. The observer location can be defined by its IAU code (e.g. 007), a particular code (e.g. @rosetta), or by its geographic coordinates (longitude, latitude in decimal degrees, and altitude in meters). See the HOWTO section for more information.
3. See Output parameters section.
4. The default value 0 means to use the default precision (13 decimals).
5. See Optional parameters section.

The output parameters are described in the following table and are available in VOTable (default), HTML, comma-separated values (CSV), and plain text format (cf. examples). Some parameters are optionnal, and their values can be omitted (just left blank the value, e.g. &-mime=&-output=). The other input parameters are mandatory.

• - the list of orbital solutions available for the computation of the ephemerides of the satellites of binary asteroids
• - the orbital parameters used to compute the ephemerides of a given asteroid or comet

http://vo.imcce.fr/webservices/miriade/ephemcc_query.php?-get=<keyword>[&-name=<target>]

The response to the request is a text/csv document which contains the following information:

genoide_solutions, genoide_best_solutions  

Source: Genoide database (Vachier et al., 2012)
Parameters:

Id	Official asteroid number (primary, blank if unnumbered).
Rank	Orbital solution ID.
System	Name or designation of the primary.
Satellite	Name or designation of the satellite.
Diameter	Equivalent diameter of the satellite in km.

This information can be used to query the ephemeris of a given binary asteroid with Miriade.ephemcc: the name argument of the HTTP request must be formatted as -name=a:<Id>/<Rank> or -name=a:<System>/<Rank>. Example: to query the ephemeris of Linus satellite: -name=a:22/1 or -name=a:Kalliope/1

 Examples: click on the following links to get:

all satellite orbital solutions

the best satellite orbital solutions

all orbital solutions of Sylvia's satellites

the best orbital solutions of Sylvia's satellites

 

orbital_params  

- Asteroids

Source: ASTORB database
Parameters:

Num	Asteroid number (blank if unnumbered).
Name	Name or preliminary designation.
OrbitComputer	Orbit computer.
H_Bowell	Absolute magnitude H, mag.
G_Bowell	Slope parameter G.
BmV	Color index B-V, mag (blank if unknown).
IRAS_Diam	IRAS diameter, km (blank if unknown).
IRAS_Taxo	IRAS Taxonomic classification (blank if unknown).
SixIntCodes	Six integer codes (see table of explanation in ASTORB).
OrbitalArc	Orbital arc, days, spanned by observations used in orbit computation.
NbObs	Number of observations used in orbit computation.
OscEpoch	Epoch of osculation, yyyymmdd (TDT).
MeanAnomaly	Mean anomaly, deg.
ArgOfPerihelion	Argument of perihelion, deg (J2000.0).
AscNodeLongitude	Longitude of ascending node, deg (J2000.0).
Inc	Inclination, deg (J2000.0).
Ecc	Eccentricity.
a	Semimajor axis, AU.
OrbitCompEpoch	Date of orbit computation, yymmdd (MST, = UTC - 7 hr).
CEU	Absolute value of the current 1-sigma ephemeris uncertainty (CEU), arcsec.
CEU_rate	Rate of change of CEU, arcsec/day.
CEU_epoch	Date of CEU, yyyymmdd (0 hr UT).
PEU	Next peak ephemeris uncertainty (PEU) from date of CEU, arcsec.
PEU_epoch	Date of occurrence of next peak ephemeris uncertainty (PEU), from date of CEU, yyyymmdd.
GPEUfromCEU	Greatest PEU in 10 years from date of CEU, arcsec.
GPEUfromCEU_epoch	Date of occurrence of greatest PEU in 10 years from date of CEU, yyyymmdd.
GPEUnextPEU	Greatest PEU in 10 years from date of next PEU, arcsec.
GPEUnextPEU_epoch	Date of occurrence of greatest PEU in 10 years from date of next PEU, yyyymmdd.

 Examples: orbital parameters of asteroid (22) Kalliope

 

- Comets:

Source: COMETPRO database
Parameters:

Note	Note number associated with the comet.
Note_epoch	Date of update (DD/MM/YYYY).
Num	IAU code of the comet.
Name	IAU name of the comet.
OrbitComputer	Name of the author elements.
RefEpoch	Reference epoch of the osculating elements (julian day).
RelativityFlag	Flag relativity: 1: effect of the sun taken into account, 0: none.
NbObs	Number of observations used in solution.
RMS (arcsec)	RMS residual (arcsec).
FirstObsEpoch	Date of first observation (DD/MM/YYYY).
LastObsEpoch	Date of last observation (DD/MM/YYYY).
px	Position vector x coordinate (AU).
py	Position vector y coordinate (AU).
pz	Position vector z coordinate (AU).
px	Velocity vector x coordinate (AU/day).
vy	Velocity vector y coordinate (AU/day).
vz	Velocity vector z coordinate (AU/day).
A1	Parameter A1 of non-gravitational forces.
A2	Parameter A2 of non-gravitational forces.
A3	Parameter A3 of non-gravitational forces.
tau	Date of perihelion passage (julian days).
q	Perihelion distance (AU).
Ecc	Eccentricity of the orbit.
ArgOfPerihelion	Argument of perihelion J2000.0 (degrees).
AscNodeLongitude	Longitude of the ascending node J2000.0 (degrees).
Inc	Inclination to ecliptic J2000.0 (degrees).
H1	Constant term of magnitude.
R1	Coefficient of log(r).
D1	Coefficient of log(Delta).
H2	Constant term of magnitude.
R2	Coefficient of log(r).
D2	Coefficient of log(Delta).

 Examples: orbital parameters of comet (1P) P/Halley

Web Service URI:

http://vo.imcce.fr/webservices/miriade/miriade.php

Namespace:

http://vo.imcce.fr/webservices/miriade

WSDL:

http://vo.imcce.fr/webservices/miriade/miriade.php?wsdl

SOAP header:

name of the SOAP header element: 'clientID'

SOAP header's content: array('from' => 'YourName', 'hostip'=>'', 'lang'=>'en|fr')

Method:

ephemcc  (inputArray)

1. see the HOWTO or FAQ section of the Miriade documentation for a more complete description.
2. see Output parameters section.
3. see Optional parameters section.
4. see HTTP Request special interface section.

 The output parameters of the method is an object containing the following attributes:

'flag'

the status of the response: flag=1 means ok; flag=0 or flag=-1 mean that an error occured

'status'

the HTTP status-code of the response (e.g. 400: bad request, 404: not found, 500: internal error)

'ticket'

the Unix timestamp of the response which can be useful to stamp the request

'result'

a string containing the ephemeris of the requested solar system body with parameters depending on user's options (cf. Output parameters section).

votable

the data are written in the IVOA standard VOTable format

html

the data are transformed from VOTable to HTML by XSLT processing (Miriade XSL style sheet)

text

the data are returned in plain text where each block of data is separated by the semi-colon character ';', and fields are separated by one or more blank character. The first block is the keyword '#! ephem' which marks the beginning of the data.

text/csv

the data are returned in plain text where each block of data is separated by the semi-colon character ';', and fields are separated by a comma. The first line provides the ticket (Unix timestamp of the response) and the flag of the response, and the second line provides the field headers.

JSON

the data are written in the JSON data-interchange format (see Howto in SsODNet documentation)

mime=text, output=--jd

mime=text/csv, output=--iso

mime=json, output=--iso

mime=html, output=--iso,--rv

mime=votable, output=--jd,--rv

1 - Spherical coordinates  

Col.	Definition	Units	Format	Option
1	Object name	-	String	(1)
2	Gregorian Date or Julian Day	datetime or day	ISO-8601 or decimal	(2)
3, 4	Spherical coordinates at the date	h:m:s and °:′:″	sexagesimal
5	Range to observer	AU	decimal
6	Visual magnitude	-	decimal
7	Phase angle	degree	decimal
8	Solar elongation	degree	decimal
9, 10	Motion on the celestial sphere (Δαcos(δ), Δδ)	arcsec/s	decimal
11	Rate of change of target distance from the observer	km/s	decimal
The next columns replace columns 9 to 11 if the option --rv is specified
9	Radial velocity (RV) of target center w.r.t. observer (3)	km/s	decimal	--rv
10	Radial velocity (RVc) of target center corrected for the radial velocity of the observer (BERV) and increased by its velocity toward the Sun (RVs): RVc = RV-BERV+RVs	km/s	decimal	--rv
11	Projection of the barycentric velocity vector of the observer along the observer-target direction (BERV)	km/s	decimal	--rv
12	Projection of the heliocentric velocity vector of the target along the heliocentric direction of the target (RVs)	km/s	decimal	--rv
The next columns supplement the previous columns if the /x option is specified on target's name (4)
13	X coordinate of the differential position of the satellite w.r.t. the primary	arcsec	decimal	<name>/x
14	Y coordinate of the differential position of the satellite w.r.t. the primary	arcsec	decimal	<name>/x
15	Projection of the satellite position along the direction observer - primary (5)	km	decimal	<name>/x
The next columns displays the thermal flux for each requested wavelengths if the option --thermalFlux() is specified
n+1 .. n+10	Thermal flux of the object for each wavelengths (≤ 10)	Jy	decimal	--thermalFlux()

2 - Rectangular coordinates  

Col.	Definition	Units	Format	Option
1	Object name	-	String	(1)
2	Gregorian Date or Julian Day	datetime or day	ISO-8601 or decimal	(2)
3..5	Position rectangular coordinates at the date	AU	decimal
6	Range to observer	AU	decimal
7	Heliocentric distance	AU	decimal
8	Visual magnitude	-	decimal
9	Phase angle	degree	decimal
10	Solar elongation	degree	decimal
11..13	Velocity rectangular coordinates at the date	AU/d	decimal
14	Rate of change of target distance from the observer	km/s	decimal
The next columns supplement the previous columns if the /x option is specified on target's name (4)
15	X coordinate of the vector position of the satellite w.r.t. the primary	km	decimal	<name>/x
16	Y coordinate of the vector position of the satellite w.r.t. the primary	km	decimal	<name>/x
17	Z coordinate of the vector position of the satellite w.r.t. the primary	km	decimal	<name>/x

3 - Local coordinates  

Col.	Definition	Units	Format	Note
1	Object name	-	String	(1)
2	Gregorian Date or Julian Day	datetime or day	ISO-8601 or decimal	(2)
3	Azimut	°:′:″	sexagesimal	0..360° from north
4	Elevation	°:′:″	sexagesimal	0..90° from horizon
5	Distance to observer	AU	decimal
6	Visual magnitude	-	decimal
7	Phase angle	degree	decimal
8	Solar elongation	degree	decimal

4 - Hour angle coordinates  

Col.	Definition	Units	Format	Note
1	Object name	-	String	(1)
2	Gregorian Date or Julian Day	datetime or day	ISO-8601 or decimal	(2)
3	Hour angle	h:m:s	sexagesimal
4	Declination	°:′:″	sexagesimal
5	Distance to observer	AU	decimal
6	Visual magnitude	-	decimal
7	Phase angle	degree	decimal
8	Solar elongation	degree	decimal

5 - Dedicated to observation  

Col.	Definition	Units	Format	Option
1	Object name	-	String	(1)
2	Gregorian Date or or Julian Day	datetime or day	ISO-8601 or decimal	(2)
3	Local Sideral Time	h:m:s	sexagesimal
4, 5	J2000 Right Ascension and Declination	h:m:s and °:′:″	sexagesimal	-
6	Hour angle	h:m:s	sexagesimal
7	Declination	°:′:″	sexagesimal
8	Azimut	°:′:″	sexagesimal
9	Elevation	°:′:″	sexagesimal
10	Airmass	-	decimal
11	Distance to observer	AU	decimal
12	Heliocentric distance	AU	decimal
13	Visual magnitude	-	decimal
14	Phase angle	degree	decimal
15	Solar elongation	degree	decimal
The next columns provide the thermal flux if the option --thermalFlux() is specified
16 .. 26	Thermal flux of the object for each wavelengths (≤ 10)	Jy	decimal	--thermalFlux()

6 - Dedicated to AO observation  

Col.	Definition	Units	Format	Note
1	Object name	-	String	(1)
2	Gregorian Date or or Julian Day	datetime or day	ISO-8601 or decimal	(2)
3	Local Sideral Time	h:m:s	sexagesimal
4, 5	J2000 Right Ascension and Declination	h:m:s and °:′:″	sexagesimal	-
6	Airmass	-	decimal
7	Distance to observer	AU	decimal
8	Heliocentric distance	AU	decimal
9	Visual magnitude	-	decimal
10	Phase angle	degree	decimal
11	Solar elongation	degree	decimal

1. This column does not exist for the 'text' mime type.
2. By default the date is expressed in the ISO-8601 format. It can be changed to julian day or calendar date with the -output argument. See Optional parameters section.
3. A positive value of RV means that the target center is moving away from the observer; while a negative value means that the target center is moving toward the observer.
4. See the HOWTO section for a full description about how to name targets.
5. If this value is positive then the satellite is in front of the primary, else it is behind it.

--greg  

to format the epoch as a calendar date.

--iso  

to format the epoch as an ISO-8601 date (default)

--jul  

to format the epoch as a julian day.

--colors(<filter>[,<filter>,...])  

to compute the magnitude of the target for listed filters (only for asteroids).
The recognized filters are: U B V R I Z Y J H Ks u g r i z
Example of request for U, V, B, R, I filters

--thermalFlux(λ,p_v,η,ε)  

to compute the thermal flux of the target (only for asteroids) using the Near-Earth Asteroid Thermal Model (NEATM) implemented by the Lagrange laboratory (OCA) and IMCCE.
The computation of the thermal flux depends on the following parameters:

• - λ: wavelength in micron in the range 4-20 µm (e.g. 10.0) or vector (size≤10) of wavelengths separated by comma and surrounded with square bracket (e.g. [5.0,10.0,20.0])
• - p_v: visible geometric albedo (e.g. 0.26)
• - η: beaming parameter, equal to one in the case that each point of the surface is in instantaneous thermal equilibrium with solar radiation (e.g. 1.0)
• - ε: infrared emissivity (e.g. 0.9)

Example of request for λ = [5.0,10.0,20.0]; p_v = 0.26; η = 1.0; ε = 0.9

--pafParams(am,h_☉)  

to produce an ephemeris file compatible with the VLT parameter file (PAF) format, to be used for the ESO Phase 2 procedures for Moving Target programmes.
The following cutoff parameters are accepted:

• - am: airmass limit, lower or equal to 2.6 (default)
• - h_☉: Sun elevation cutoff, lower or equal to 0° (default)

Example of request for am = 2.2 and h_☉ = -10.0°

In order to help you to invoke the Miriade web service, we provide some clients written in differents languages. Here are some detailed explanations to see how to write a client with PHP and SOAP which invokes the ephemcc method:

1/ Provide the input parameters which are mandatory for the service:

2/ Define the SOAP options, the namespace and the WSDL URI of Miriade web service:

3/ Create a SoapClient object in WSDL mode, set the SOAP header, then call the method and catch exceptions: