some comment on SSA

[Doug Tody]

On Wed, 25 Feb 2009, lesidaner-obs wrote:

> I have trouble in Maxrec parameter
> from the standard :
>
> -------------------
> "8.10.2  Overflow
>
> The operation produced results that exceeded the limits of the service in 
> some way. For instance, a data query matched too many candidate datasets. In 
> this case, the service should include an error message indicating the nature 
> of the overflow condition (see also section 8.10.2).
>
>
>
> Example:
>
> <INFO name="QUERY_STATUS" value="ERROR">DEC out of range: DEC=91</INFO>
>
> <INFO name="QUERY_STATUS" value="OVERFLOW">Number of matching spectra exceeds 
> default limit of 500</INFO>
>
>
>
> If overflow occurs the query may be repeated, requesting a higher MAXREC 
> value than the default for the maximum number of output records, up to the 
> hard limit defined by the service capabilities. Alternatively the query 
> parameters may be adjusted to more carefully constrain the query. Currently 
> these are the only ways to avoid overflow when performing a query
> -------------------------------
>
> It appear that in quite all client this parameter is not supported as i 
> imagine it should be.
> Would it be possible to change the output telling
> <INFO name="QUERY_STATUS" value="OVERFLOW">Number of matching spectra exceeds 
> default limit of 500 only Only 500 of X will be return</INFO>
> And ask the service to return the first Maxrec result
>
> This should be useful for the user and easily manage by client without 
> multiple queries.
>
> as an example you can check
> http://basebe.obspm.fr/cgi-bin/ssapBE_1.0.pl?POS=84.41116666666667%2C21.142527777777776&SIZE=0.5&BAND=&TIME=2453384.92154&FORMAT=votable
>
> Best regards
> Pierre Le Sidaner
>
>