This page describes the telescope-net astrocoding service, and how to use it. It provides an introduction to using this API, and describes the parameters which can be included in requests.

This system has two primary purposes. First, to provide positions of astronomical objects suitable for pointing a telescope equipped with a wide-field camera (i.e., with a field of view of several arcminutes or more). Second, to help identify objects appearing on images taken with this sort of equipment.

This astrocoder incorporates some features that, in some sense, might be considered a "reverse astrocoder", such as being able to limit results to within a particular region of interest. This system will also output data in VOTable 1.2 format and accept "Simple Cone Search" query parameters. Additionally, the system can produce topocentric coordinates, appropriate for any observing site known to the telescope-net geocoding service.

Again, just as with the geocoder, you are free to use this service so long as the results are used for some astronomical or astronomy-related purpose. Because this service produces astronomical coordinates, that is probably a given.

http://www.telescope-net.com/apta/ASTROCODER?parameters

You must include either a name or a bounds variable in your search, or else you must include all of the "simple cone search" parameters (RA, DEC and SR). You can include the name parameter in conjunction with either bounds or the simple cone search parameters if you wish - please see below for examples of this.

• name=object name (optional)
  The name parameter in the request specifies the name (or a part of the name) of the object for which you require coordinates. By default, a partial match will be performed on the name value. For example, searching for "NGC 157" produces eleven objects, namely NGC1570 through NGC 1579 in addition to NGC 157. Please specify "searchtype=exact" to limit a search to the exact string.

• searchtype=exact|partial (optional)
  This specifies how the name match is to be performed. The default match type is partial, which means that the supplied name value can match anywhere within the name of the object. Setting searchtype=exact will limit the search such that the object name must exactly match the supplied name. Either zero or one responses will be returned in this latter case.

• objecttype=asteroid|comet|planet|galaxy|nebula|star|cluster|globular cluster|galactic cluster|open cluster (optional)
  If specified, the results returned by the astrocoder will be limited to objects of the specified type.

• bounds=Dec,RA|Dec,RA (optional)
  If specified, the returned results will be limited to those objects with positions that lie within the specified range, or "bounding box". The bounds value consists of two (J2000.0) Declination and Right Ascension pairs. These coordinates correspond to the southwest and northeast corners of the bounding box, and are separated by a pipe ("|") character. Both the Right Ascension and Declination values are specified in degrees (for Right Ascension, this is equal to a value in Hours times 15). An example of a bounds specification which includes the galaxy NGC 4945 (which has approximate coordinates of RA 13.1 hr, Dec -49.5° is

  bounds=-50.0,196.0|-49.0,197

  Note that results outside of the bounds specification are not returned. This behaviour is different to our geocoder, which will still return matches which lie outside of a bounding box specification. For solar system bodies, the edges of a bounding box are a little "fuzzy", in that some objects which lie just inside the bounding box may be omitted and some which lie just outside may be included. In all cases, however, the returned positions and rates will be accurate.

• magbounds=faintest,brightest (optional)
  If specified, results will be limited to those objects with an approximate integrated magnitude which lies between the specified values.

• epoch=2010-06-15T11:53:17Z (optional)
  If specified, the positions of solar system bodies will be calculated for the given epoch. The value should be in the particular ISO 8601 time format shown above. It is envisaged that this will be mainly used for identifying the positions of solar system bodies on images taken at a particular time. If no epoch is given, calculations will be made for the time at which the request is received by the service.

• siteid=siteid (optional)
  If siteid corresponds to the siteid of a known, publicly accessible observing site, the astrocoder results will also include topocentric coordinates appropriate for this observing location. As described more fully on our geocoder info page, sites may include cities (typically those with populations of 100000 people or more), observatories defined by the Minor Planet Center, telescope-net observing sites and other, user-defined observing sites. The coordinates of observing sites used to calculate topocentric data will be appropriately "fuzzed" if required (please see the geocoder information page for more details on this).

• votable=true (optional)
  This will output data in VOTable 1.2 format. The VOTable-format data differ in several ways. First, only J2000.0 positions are returned. Second, no constellation or angular size information is currently provided. Third, instead of providing RA and Dec rate data for solar system bodies, two entries appear in the VOTable output for each solar system body. The timestamps on these position estimates differ by one hour, so that the positions of these objects can be interpolated between these points. Requesting output in VOTable format means that you have to supply the RA, DEC and SR search parameters (detailed below), or else an error will result. You can use other parameters as well (e.g., name=ngc or objecttype=asteroids or epoch=2010-06-15T11:53:17Z).

• RA, DEC and SR (optional)
  As an alternative to providing a bounds specification, you may supply the variable names RA, DEC and SR. This specification is basically a "Simple Cone Specification", with the RA and DEC variables specifying the centre of the cone and SR specifying the radius of the cone. These should all be specified in decimal degrees. It is envisaged that the use of these parameters will typically be accompanied by votable=true, but that is not a requirement. Some objects which lie outside (but near to) the boundary of the specified cone may also be returned.

The set of catalogues currently searched can be seen here. Although we may add or update catalogues from time to time, we will not remove any.

http://www.telescope-net.com/apta/ASTROCODER?name=M33&searchtype=exact

The response is as follows:

<AstrocodeResponse>
  <engine>APTA SAROS astrocoder rev 85</engine>
  <status>OK</status>
  <timestamp>2010-06-27T04:59:09Z</timestamp>
  <result>
    <name>M 33</name>
    <type>Galaxy</type>
    <magnitude>5.7</magnitude>
    <geometry>
      <location referent="geocentric" equinox="J2000.0">
        <right_ascension>23.4750</right_ascension>
        <declination>+30.6500</declination>
        <constellation>Tri</constellation>
        <constellation_fullname>Triangulum</constellation_fullname>
      </location>
      <location referent="geocentric" equinox="date">
        <right_ascension>23.6257</right_ascension>
        <declination>+30.7028</declination>
        <constellation>Tri</constellation>
        <constellation_fullname>Triangulum</constellation_fullname>
      </location>
    </geometry>
  </result>
</AstrocodeResponse>

Note that any of the following forms can be used, as they are all regarded as valid name values:

name=M33
name=m33
name=M 33
name=M%2033
name=M+33

An an example of using the bounds variable, let's make a request which selects objects within a one (square) degree area of sky around M 33. We'll also place a magnitude limit of between 5 and 7. This request looks like this:

http://www.telescope-net.com/apta/ASTROCODER?bounds=30,23|31,24&magbounds=5,7

The response returns three results, and is as follows:

<AstrocodeResponse>
  <engine>APTA SAROS astrocoder rev 85</engine>
  <status>OK</status>
  <timestamp>2010-06-27T05:02:07Z</timestamp>
  <result>
    <name>M 33</name>
    <type>Galaxy</type>
    <magnitude>5.7</magnitude>
    <geometry>
      <location referent="geocentric" equinox="J2000.0">
        <right_ascension>23.4750</right_ascension>
        <declination>+30.6500</declination>
        <constellation>Tri</constellation>
        <constellation_full>Triangulum</constellation_full>
      </location>
      <location referent="geocentric" equinox="date">
        <right_ascension>23.6257</right_ascension>
        <declination>+30.7028</declination>
        <constellation>Tri</constellation>
        <constellation_full>Triangulum</constellation_full>
      </location>
    </geometry>
  </result>
  <result>
    <name>NGC 598</name>
    <type>Galaxy</type>
    <magnitude>5.7</magnitude>
    <geometry>
      <location referent="geocentric" equinox="J2000.0">
        <right_ascension>23.4750</right_ascension>
        <declination>+30.6500</declination>
        <constellation>Tri</constellation>
        <constellation_full>Triangulum</constellation_full>
      </location>
      <location referent="geocentric" equinox="date">
        <right_ascension>23.6257</right_ascension>
        <declination>+30.7028</declination>
        <constellation>Tri</constellation>
        <constellation_full>Triangulum</constellation_full>
      </location>
    </geometry>
  </result>
  <result>
    <name>PGC 5818</name>
    <type>Galaxy</type>
    <magnitude>6.2</magnitude>
    <geometry>
      <location referent="geocentric" equinox="J2000.0">
        <right_ascension>23.4621</right_ascension>
        <declination>+30.6603</declination>
        <constellation>Tri</constellation>
        <constellation_full>Triangulum</constellation_full>
      </location>
      <location referent="geocentric" equinox="date">
        <right_ascension>23.6128</right_ascension>
        <declination>+30.7131</declination>
        <constellation>Tri</constellation>
        <constellation_full>Triangulum</constellation_full>
      </location>
    </geometry>
  </result>
</AstrocodeResponse>

The objects returned are M 33, NGC 598 and PGC 5818. These are in fact the same physical object, appearing in three different catalogues. A convenient way to limit this to a particular catalogue is to also include a name value in the request, e.g.,

http://www.telescope-net.com/apta/ASTROCODER?name=pgc&bounds=30,23|31,24&magbounds=5,7

So this time we only get back the entry from the Principal Galaxy Catalogue.

<AstrocodeResponse>
  <engine>APTA SAROS astrocoder rev 85</engine>
  <status>OK</status>
  <timestamp>2010-06-27T05:03:25Z</timestamp>
  <result>
    <name>PGC 5818</name>
    <type>Galaxy</type>
    <magnitude>6.2</magnitude>
    <geometry>
      <location referent="geocentric" equinox="J2000.0">
        <right_ascension>23.4621</right_ascension>
        <declination>+30.6603</declination>
        <constellation>Tri</constellation>
        <constellation_full>Triangulum</constellation_full>
      </location>
      <location referent="geocentric" equinox="date">
        <right_ascension>23.6128</right_ascension>
        <declination>+30.7131</declination>
        <constellation>Tri</constellation>
        <constellation_full>Triangulum</constellation_full>
      </location>
    </geometry>
  </result>
</AstrocodeResponse>

Below is an example of a request for an object with the string marples in the name. Only one result is returned, for asteroid 7527 Marples. Here is the request:

http://www.telescope-net.com/apta/ASTROCODER?name=marples

The response is below. Note the presence of both instantaneous Right Ascension and Declination values (appropriate for the instant specified in <timestamp>), but also the Right Ascension and Declination rates. These rates are calculated from positions calculated for the object at times of <timestamp> and <timestamp> + one hour. (In the case that the object's apparent motion is very swift indeed, a smaller time period will be used.)

<AstrocodeResponse>
  <engine>APTA SAROS astrocoder rev 85</engine>
  <status>OK</status>
  <timestamp>2010-06-27T05:10:35Z</timestamp>
  <result>
    <name>7527 Marples</name>
    <type>Asteroid</type>
    <magnitude>18.9</magnitude>
    <geometry>
      <location referent="geocentric" equinox="J2000.0">
        <right_ascension>121.7964</right_ascension>
        <declination>+21.4879</declination>
        <right_ascension_rate>+0.438</right_ascension_rate>
        <declination_rate>-0.105</declination_rate>
        <constellation>Cnc</constellation>
        <constellation_fullname>Cancer</constellation_fullname>
      </location>
      <location referent="geocentric" equinox="date">
        <right_ascension>121.9499</right_ascension>
        <declination>+21.4575</declination>
        <right_ascension_rate>+0.438</right_ascension_rate>
        <declination_rate>-0.105</declination_rate>
        <constellation>Cnc</constellation>
        <constellation_fullname>Cancer</constellation_fullname>
      </location>
    </geometry>
  </result>
<information>Asteroid and dwarf planet data last updated 2010-06-27T03:09:50Z.</information>
</AstrocodeResponse>

An example of limiting the returned objects based upon object type appears below. Here we again request name=marples, but limit the returned object type to stars. This is a fairly silly request and, as you might expect, returns no results. Here is the request:

http://www.telescope-net.com/apta/ASTROCODER?name=marples&objecttype=stars

The response is:

<AstrocodeResponse>
  <engine>APTA SAROS astrocoder rev 85</engine>
  <status>ZERO_RESULTS</status>
  <timestamp>2010-06-27T05:10:55Z</timestamp>
</AstrocodeResponse>

A further example of an asteroid query is below. Here we request name=Brisbane, and also ask for topocentric coordinates appropriate for the city of Brisbane, Australia. The request is:

http://www.telescope-net.com/apta/ASTROCODER?name=Brisbane&objecttype=asteroids&siteid=AU_Brisbane

The response is:

<AstrocodeResponse>
  <engine>APTA SAROS astrocoder rev 85</engine>
  <status>OK</status>
  <timestamp>2010-06-22T12:52:27Z</timestamp>
  <result>
    <name>5277 Brisbane</name>
    <type>Asteroid</type>
    <magnitude>18.2</magnitude>
    <geometry>
      <location referent="geocentric" equinox="J2000.0">
        <right_ascension>304.8881</right_ascension>
        <declination>-21.5779</declination>
        <right_ascension_rate>-0.186</right_ascension_rate>
        <declination_rate>+0.002</declination_rate>
        <constellation>Cap</constellation>
        <constellation_fullname>Capricornus</constellation_fullname>
      </location>
      <location referent="geocentric" equinox="date">
        <right_ascension>305.0511</right_ascension>
        <declination>-21.5426</declination>
        <right_ascension_rate>-0.186</right_ascension_rate>
        <declination_rate>+0.002</declination_rate>
        <constellation>Cap</constellation>
        <constellation_fullname>Capricornus</constellation_fullname>
      </location>
      <location referent="topocentric" siteid="AU_Brisbane" equinox="date">
        <right_ascension>305.0522</right_ascension>
        <declination>-21.5423</declination>
        <right_ascension_rate>-0.192</right_ascension_rate>
        <declination_rate>+0.001</declination_rate>
        <constellation>Cap</constellation>
        <constellation_fullname>Capricornus</constellation_fullname>
      </location>
    </geometry>
  </result>
<information>Asteroid and dwarf planet data last updated 2010-06-22T03:10:07Z.</information>
</AstrocodeResponse>

http://www.telescope-net.com/apta/GEOCODER?address=AU_Brisbane

As a final example, below is a request for the location of the Moon, asking for topocentric coordinates appropriate for Berlin, Germany. Note in this case that the topocentric coordinates lie in a different constellation to the geocentric ones. This is of course a result of the moon's significant equatorial horizontal parallax, an effect which also gives rise to the different apparent Right Ascension and Declination rates. The request is:

http://www.telescope-net.com/apta/ASTROCODER?name=moon&searchtype=exact&siteid=DE_Berlin

The response is:

<AstrocodeResponse>
  <engine>APTA SAROS astrocoder rev 85</engine>
  <status>OK</status>
  <timestamp>2010-06-20T12:10:06Z</timestamp>
  <result>
    <name>Moon</name>
    <type>The Moon</type>
    <magnitude>-12.7</magnitude>
    <angsize>1910</angsize>
    <geometry>
      <location referent="geocentric" equinox="J2000.0">
        <right_ascension>192.7617</right_ascension>
        <declination>-11.1743</declination>
        <right_ascension_rate>+12.971</right_ascension_rate>
        <declination_rate>-5.265</declination_rate>
        <constellation>Vir</constellation>
        <constellation_full>Virgo</constellation_full>
      </location>
      <location referent="geocentric" equinox="date">
        <right_ascension>192.9040</right_ascension>
        <declination>-11.2342</declination>
        <right_ascension_rate>+12.971</right_ascension_rate>
        <declination_rate>-5.265</declination_rate>
        <constellation>Vir</constellation>
        <constellation_full>Virgo</constellation_full>
      </location>
      <location referent="topocentric" siteid="DE_Berlin" equinox="date">
        <right_ascension>193.5094</right_ascension>
        <declination>-11.9895</declination>
        <right_ascension_rate>+12.453</right_ascension_rate>
        <declination_rate>-5.995</declination_rate>
        <constellation>Crv</constellation>
        <constellation_full>Corvus</constellation_full>
      </location>
    </geometry>
  </result>
</AstrocodeResponse>

http://www.telescope-net.com/apta/ASTROCODER?votable=true&RA=23.5&DEC=30.5&SR=0.5&objecttype=galaxies

The VOTable response is as follows:

<?xml version="1.0" encoding="UTF-8"?>
<VOTABLE version="1.2" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
  xmlns:stc="http://www.ivoa.net/xml/STC/stc-v1.30.xsd"
  xmlns="http://www.ivoa.net/xml/VOTable/v1.2">
  <DESCRIPTION>APTA SAROS Simple Cone Search service</DESCRIPTION>
  <RESOURCE name="APTA SAROS astrocoder response">
    <TABLE name="query response">
      <INFO name="QUERY_STATUS" value="OK" />
      <PARAM datatype="char" arraysize="*" ucd="meta.bib.author" name="Author" value="telescope-net.com"/>
      <PARAM name="Software" datatype="char" arraysize="*" ucd="meta.title;meta.software" value="APTA SAROS astrocoder"/>
      <PARAM name="Revision" datatype="char" arraysize="*" ucd="meta.version;meta.software" value="90"/>
      <PARAM name="Soft_URL" datatype="char" arraysize="*" ucd="meta.ref.url;meta.software" value="http://www.telescope-net.com/apta/ASTROCODERINFO"/>
      <GROUP utype="stc:CatalogEntryLocation">
        <PARAM name="CoordFlavor" datatype="char" arraysize="*"
          utype="stc:AstroCoordSystem.SpaceFrame.CoordFlavor" value="SPHERICAL"/>
        <PARAM name="coord_naxes" datatype="char" arraysize="*"
          utype="stc:AstroCoordSystem.SpaceFrame.CoordFlavor.coord_naxes" value="2"/>
        <PARAM name="CoordRefFrame" datatype="char" arraysize="*"
          utype="stc:AstroCoordSystem.SpaceFrame.CoordRefFrame" value="ICRS"/>
        <PARAM name="ReferencePosition" datatype="char" arraysize="*"
          utype="stc:AstroCoordSystem.SpaceFrame.ReferencePosition" value="GEOCENTER"/>
        <PARAM name="TimeScale" datatype="char" arraysize="*"
          utype="stc:AstroCoordSystem.TimeFrame.TimeScale" value="UTC"/>
        <PARAM name="URI" datatype="char" arraysize="*"
	  utype="stc:DataModel.URI" value="http://www.ivoa.net/xml/STC/stc-v1.30.xsd"/>
	<FIELDref ref="ID_MAIN" ucd="ID_MAIN"/>
	<FIELDref ref="ObjectName" ucd="meta.id;meta.main"/>
	<FIELDref ref="ObjectType" ucd="meta.code.class"/>
	<FIELDref ref="DateObs" utype="stc:AstroCoords.Time.TimeInstant.ISOTime"/>
	<FIELDref ref="RA" ucd="POS_EQ_RA_MAIN"/>
	<FIELDref ref="Dec" ucd="POS_EQ_DEC_MAIN"/>
	<FIELDref ref="Vmag" ucd="phot.mag;em.opt.V"/>
      </GROUP>
      <FIELD ID="ID_MAIN" name="unique_id" datatype="char" arraysize="*">
        <DESCRIPTION>Unique integer key for each table row</DESCRIPTION>
      </FIELD>
      <FIELD ID="ObjectName" name="object_name" datatype="char" arraysize="*">
        <DESCRIPTION>Identifying name for the object</DESCRIPTION>
      </FIELD>
      <FIELD ID="ObjectType" name="object_type" datatype="char" arraysize="*">
        <DESCRIPTION>Type of object (e.g., galaxy, nebula, asteroid, comet, star)</DESCRIPTION>
      </FIELD>
      <FIELD ID="DateObs" name="DateObs" datatype="char" xtype="adql:TIMESTAMP" arraysize="*"/>
      <FIELD ID="RA" name="right_ascension" datatype="double" unit="degree">
        <DESCRIPTION>Right Ascension</DESCRIPTION>
      </FIELD>
      <FIELD ID="Dec" name="declination" datatype="double" unit="degree">
        <DESCRIPTION>Declination</DESCRIPTION>
      </FIELD>
      <FIELD ID="Vmag" name="Vmag" datatype="float" unit="mag"/>
      <DATA>
        <TABLEDATA>
          <TR>
            <TD>0</TD><TD>M 33</TD><TD>Galaxy</TD><TD>2010-06-30T01:46:09Z</TD><TD>23.4750</TD><TD>+30.6500</TD><TD>5.7</TD>
          </TR>
          <TR>
            <TD>1</TD><TD>NGC 598</TD><TD>Galaxy</TD><TD>2010-06-30T01:46:09Z</TD><TD>23.4750</TD><TD>+30.6500</TD><TD>5.7</TD>
          </TR>
          <TR>
            <TD>2</TD><TD>PGC 5818</TD><TD>Galaxy</TD><TD>2010-06-30T01:46:09Z</TD><TD>23.4621</TD><TD>+30.6603</TD><TD>6.2</TD>
          </TR>
        </TABLEDATA>
      </DATA>
    </TABLE>
  </RESOURCE>
</VOTABLE>

Last, here is an example of a (slightly) sneaky way of performing a name-based search and returning the data as a VOTable. Here we search for objects named marples. We basically select an SR value of 180 degrees, and limit the results by specifying a name parameter. The request is:

http://www.telescope-net.com/apta/ASTROCODER?votable=true&RA=0&DEC=0&SR=180&name=marples

The response is:

<?xml version="1.0" encoding="UTF-8"?>
<VOTABLE version="1.2" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
  xmlns:stc="http://www.ivoa.net/xml/STC/stc-v1.30.xsd"
  xmlns="http://www.ivoa.net/xml/VOTable/v1.2">
  <DESCRIPTION>APTA SAROS Simple Cone Search service</DESCRIPTION>
  <RESOURCE name="APTA SAROS astrocoder response">
    <TABLE name="query response">
      <INFO name="QUERY_STATUS" value="OK" />
      <PARAM datatype="char" arraysize="*" ucd="meta.bib.author" name="Author" value="telescope-net.com"/>
      <PARAM name="Software" datatype="char" arraysize="*" ucd="meta.title;meta.software" value="APTA SAROS astrocoder"/>
      <PARAM name="Revision" datatype="char" arraysize="*" ucd="meta.version;meta.software" value="90"/>
      <PARAM name="Soft_URL" datatype="char" arraysize="*" ucd="meta.ref.url;meta.software" value="http://www.telescope-net.com/apta/ASTROCODERINFO"/>
      <GROUP utype="stc:CatalogEntryLocation">
        <PARAM name="CoordFlavor" datatype="char" arraysize="*"
          utype="stc:AstroCoordSystem.SpaceFrame.CoordFlavor" value="SPHERICAL"/>
        <PARAM name="coord_naxes" datatype="char" arraysize="*"
          utype="stc:AstroCoordSystem.SpaceFrame.CoordFlavor.coord_naxes" value="2"/>
        <PARAM name="CoordRefFrame" datatype="char" arraysize="*"
          utype="stc:AstroCoordSystem.SpaceFrame.CoordRefFrame" value="ICRS"/>
        <PARAM name="ReferencePosition" datatype="char" arraysize="*"
          utype="stc:AstroCoordSystem.SpaceFrame.ReferencePosition" value="GEOCENTER"/>
        <PARAM name="PlanetaryEphem" datatype="char" arraysize="*"
          utype="stc:AstroCoordSystem.SpaceFrame.ReferencePosition.PlanetaryEphem" value="JPL-DE405"/>
        <PARAM name="TimeScale" datatype="char" arraysize="*"
          utype="stc:AstroCoordSystem.TimeFrame.TimeScale" value="UTC"/>
        <PARAM name="URI" datatype="char" arraysize="*"
	  utype="stc:DataModel.URI" value="http://www.ivoa.net/xml/STC/stc-v1.30.xsd"/>
	<FIELDref ref="ID_MAIN" ucd="ID_MAIN"/>
	<FIELDref ref="ObjectName" ucd="meta.id;meta.main"/>
	<FIELDref ref="ObjectType" ucd="meta.code.class"/>
	<FIELDref ref="DateObs" utype="stc:AstroCoords.Time.TimeInstant.ISOTime"/>
	<FIELDref ref="RA" ucd="POS_EQ_RA_MAIN"/>
	<FIELDref ref="Dec" ucd="POS_EQ_DEC_MAIN"/>
	<FIELDref ref="Vmag" ucd="phot.mag;em.opt.V"/>
      </GROUP>
      <FIELD ID="ID_MAIN" name="unique_id" datatype="char" arraysize="*">
        <DESCRIPTION>Unique integer key for each table row</DESCRIPTION>
      </FIELD>
      <FIELD ID="ObjectName" name="object_name" datatype="char" arraysize="*">
        <DESCRIPTION>Identifying name for the object</DESCRIPTION>
      </FIELD>
      <FIELD ID="ObjectType" name="object_type" datatype="char" arraysize="*">
        <DESCRIPTION>Type of object (e.g., galaxy, nebula, asteroid, comet, star)</DESCRIPTION>
      </FIELD>
      <FIELD ID="DateObs" name="DateObs" datatype="char" xtype="adql:TIMESTAMP" arraysize="*"/>
      <FIELD ID="RA" name="right_ascension" datatype="double" unit="degree">
        <DESCRIPTION>Right Ascension</DESCRIPTION>
      </FIELD>
      <FIELD ID="Dec" name="declination" datatype="double" unit="degree">
        <DESCRIPTION>Declination</DESCRIPTION>
      </FIELD>
      <FIELD ID="Vmag" name="Vmag" datatype="float" unit="mag"/>
      <DATA>
        <TABLEDATA>
          <TR>
            <TD>0</TD><TD>7527 Marples</TD><TD>Asteroid</TD><TD>2010-06-30T02:32:12Z</TD><TD>123.0609</TD><TD>+21.1814</TD><TD>18.9</TD>
          </TR>
          <TR>
            <TD>1</TD><TD>7527 Marples</TD><TD>Asteroid</TD><TD>2010-06-30T03:32:12Z</TD><TD>123.0791</TD><TD>+21.1769</TD><TD>18.9</TD>
          </TR>
        </TABLEDATA>
      </DATA>
    </TABLE>
  </RESOURCE>
</VOTABLE>