|Action||from||to||purpose||status / answer|
Check here for recent discussions (mostly the first one which addresses these questions):
|SE||Also required to introduce projection parameters using various standards (Proj4…)|
|• 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 RFM 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.
In any case, this is not necessarily similar to albedo (which is typically integrated spectrally/in angular domain, and is then related to thermal equilibrium). I would keep albedo for more general purpose.
• Correct/clarify brdf in 2018 sheet:
addQ | phys.reflectance.bidirectional.df| Bidirectional reflectance distribution function
The UCD is very weird, would better be phys.reflectance.brdf (this is not a subset of .bidirectional)
• Suggestion for reflectance in 2018 RFM sheet, to be corrected:
for normalized reflectance concept: proposal arith.ratio;phys.reflectance
=> Should be arith.factor;phys.reflectance
|How do we handle hemispherically integrated quantities?||SE||reflectance / emission|
|posAng is commonly mistaken for a generic UCD for angles (which does not exist). Make definition more explicit (e.g., Free dictionary: thedirectioninwhichoneobjectliesrelativetoanotheronthecelestialsphere,measuredindegrees fromnorthinaneasterlydirection)|
|Section 8, 2 (about pos): |
"the angular size of an object is in this section, its linear size is in the phys section)"
But we have phys.angSize (with an unclear definition) )- should be in pos?
On the same token,
phys.angVeloc would look more consistent than phys.veloc.ang
Additional set of UCDs for spectroscopy. In particular, a category phys.scattering seems required, see here
+ arithm.ang could do for angular distributions
|How do we handle asymmetric error bars? Some services need to have stat.error.min/max||SE||use stat.error;stat.min|
|How do we specify an additive constant or offset? The only close match is arith.zp, which is context specific (for magnitude scales)||SE||At least enlarge the definition to any type of offset / additive constant|
|Add JSON output to TAP standard?||SE||must be faster than VOtable (critical in the VESPA portal)|
|SAMP only pass the first table resource of a VOtable, seems to be in the standard - although TOPCAT can actually open all tables when provided directly. Why that?||SE||Mark Taylor||This is a problem to send VizieR catalogues from VESPA portal (but also from TAPhandle).||askedDone on purpose. The solution is to send table resources one by one from the interface.|