This page lists requests sent / to be sent to IVOA discussion groups to accommodate VESPA needs.
Roadmap described here: Planetary Science requirements in the VO
Interop May 2017 (Shanghai)
All this to be discussed in advance on mailing lists.
Ask to include VESPA related tools in IVOA Application lists:
|SE||helpdesk for this page (email@example.com) & Pierre Fernique for this page||Advertise VESPA |
|PLS||Mark Taylor and Thomas Bochs|
UCDs and Utypes for Solar System
|SE||Mireille Louys||Discussed in May 2018 (Victoria interop) for inclusion.|
|SE||this is addressed in SDM2, TBC|
|SE||Support of UCDs in |
in particular, but also
instrument names, etc
|PLS||François Bonnarel, Dave Morris, Markus Demleitner|
RegTAP functions have been reviewed by TCG, included “ivo_” functions. We can refer to that in EPN-TAP service specification. It is a function to implement on server-side, by data provider. It exist already in DaCHS, it seems to be easy to implement with Gregory Mantelet’s library.
Tools / standards:
OK with dedicated script in CASSIS, to be made more generic
|M. Taylor (passed, TBC for him)||Mark not very excited…|
|All those fixed in v10. However open issues are shown on Aladin pages in Confluence|
SE / Chiara Marmo
|? - IAU fits commission?||Support planetary mapping & surface feature catalogues|
|SE||Markus Demleitner, Dave Morris||Support body fixed |
frames, consistency with
|new version of TAP (v1.1) removes reference frame in box, circle, polygon. Client must do the query correctly, interpreting the TAP service coordinate frame (default is ICRS)|
It would be very important to be able to specify if one wants to search for model outputs, experimental data or observations. Right now it is not possible to specify it, and if used blindly it can be very confusing!
|Check here for recent discussions (mostly the first one which addresses these questions): |
|• UCD needed for VOevents||SE|
|• Clarify usage of inf / -inf / Nan in ADQL (should apparently exist, as per DALI - but do not)||SE|
• Correct/clarify definition of reflectance in 2018 sheet:
Radiance factor is the same as I/F; in this case, this is divided by input irradiance (not radiance), i.e. by solar flux.
We can keep phys.reflectance for the reflectance factor (standard quantity for lab measurements, currently listed as phys.reflectance.factor) = ratio of radiance to that of a Lambertian disk at the same distance and illuminated under the same incidence (also called radiance coefficient)
In any case, this is not necessarily similar to albedo (which is typically integrated spectrally, and is then related to thermal equilibrium). I would keep albedo for more general purpose.
|How do we handle asymmetric error bars? Some services need to have stat.error.min/max||SE|
|How do we specify an additive constant / offset? The only close match is arith.zp, specific||SE|