You are viewing an old version of this page. View the current version.
Compare with Current
View Page History
« Previous
Version 20
Next »
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.
Action | from | to | purpose | status |
---|
Ask to include VESPA related tools in IVOA Application lists: - ESPA : http://vespa.obspm.fr
web application, EPN-TAP (and PDAP) client / Query databases connected to VO tools via SAMP
- APERICubes: http://voparis-apericubes.obspm.fr
web-based tool Spectral cube slicer for PDS3 formatted cubes (VIRTIS on Venus-Express and Rosetta currently) connected via SAMP (both I/O)
| SE | helpdesk & Mark Taylor | Advertise VESPA developments | |
Applications - Evolution of SAMP messages (content) we want to add:
- geojson
- pds3 + pds4 (+ datalink ?)
example to present as usecase, sending geojson to MIZAR and CESIUM
| PLS |
|
|
|
UCDs and Utypes for Solar System - See in EPN-TAP V2.0 parameters (related to parameters)
UCDs in red and italics/blue are non standard but needed by VESPA.
| SE | ? | | |
- Add "spectral matrix" UCD (use case = what to know that data can be sent to iPECMan): phys.spectralmatrix
- UCD for gravitational field "Power Spectrum of Spherical Harmonic Coefficients of Lunar Gravity Model": phys.gravitation
- Shape model (full 3D shape) or Terrain Model (or Elevation model) with respect to geoid or ellipsoid: phys.shape, phys.shape.elevation
| BC |
|
|
|
Spectroscopy - How do we pass Utypes and UCDs to VO tools? Really included in VOTables only, not in fits ?
The reason is apparently related to the length of value fields in fits. - Add fits kw for UCD (and Utypes, if space permits)?
Otherwise, data handling in tools depends on how data are transmitted.
| SE | | this is addressed in SDM2, TBC | |
ADQL additions - we need to look inside a field of list, ie to combine ivo_hashlist_has with LIKE
to look for a UCD in a list (and get time vs time;stat.min)
| SE | ? | Support of UCDs in measurement_type in particular, but also instrument names, etc | |
- Use case for "ivo_hashlist_has" : function to parse list in ADQL. We need an ADQL function to handle a multi value field that is resume in a sigle filed. Idea from markus is that we should not asked ADQL transformation but put that in endorse note. He will help in writing it, but doesnt want to be the handler of it in IVOA. What we have to say, is that we have use case for it target_name, target_class. That also exist in obscore. Moreover this function is used in relational registry interogation and will be handle by Gregory library and DaCHS. We could handle this note if TCG thing it's the right way to go.
| PLS | ? |
|
|
Tools / standards: - Spectral aggregates? Required to plot measurements from spectrometers with several channels
(very common in our field). Appears to require a formatting standard to store several spectral elements in the same file - TOPCAT:
Implement cross-matches based on s_region (in addition to cone search-like criteria)?
| SE | J-M Glorian? M. Taylor (done,TBC for him) | | |
- Aladin (to be discussed directly with PFernique?):
See fits format items- stability issue of v9 on Mac / java 1.8 (blocks on my machine at startup very often)
- issue with auto hips from files, does not work as expected, and never finishes on my side
- implement E-handed frames in s_region (see STC item)
| SE | Pierre Fernique | | |
Fits format: - Chiara's request for additional keywords
- Need to implement the planetary ref systems in Aladin, they are part of the fits std:
MALN + MALT, etc + proj types (see her ex Mars & Venus) - Define equivalent for Earth (don't seem to exist)
- Current fits keywords do not allow for image projections on ellipsoids, even less on a 67P
(one kw missing, see Chiara's docs)
| SE / Chiara Marmo | ? | | |
STC, etc: - s_region is very nice, but we need a E-handed system with longitudes [0, 360[.
Should we add another predefined system (BODY, or BODY-FIXED, or E-HANDED? ) We're currently using UnknownFrame, appears to be W-handed also (used like this in Aladin at least). Or combine UnknownFrame with something else?
| SE | Arnold Rots? | Support of body fixed frames, consistency with IAU conventions | |
- AstroCoords for VOEvent: we need to be able to tell that the event occurs at a named planet or a spacecraft (e.g., "Jupiter", "Juno") in the WHERE section.
|
|
|
|
|
TCG discussion - : We need an ADQL function to handle a multi value field that is resume in a sigle filed. Idea from markus is that we should not asked ADQL transformation but put that in endorse note. He will help in writing it, but doesn't want to be the handler of it in IVOA. What we have to say, is that we have use case for it target_name, target_class. That also exist in obscore. Moreover this function is used in relational registry interrogation and will be handle by Gregory library and DaCHS. We could handle this note if TCG thing it's the right way to go.
There is also another function to handle Hips in ADQL with first implementation in DaCHS, use case are already there, it's not our goal, but we may use it and it's another argument to build this note and circulate it. This is a question to DAL, but Baptiste must ask in TCG a way to build it as input come from different group (Planetary Science, Registry, Hips ?)
- Endorment of VOResource schema that is necessary to register EPN-TAP service in RofR registry. That yet stop for non compliance
(ivo-id containing # characters should be valid)
| PLS | | | |
VOEvent: - Using ORCiD for identification of author ?
- See STC comments also
| BC |
|
|
|