InterOpNov2023Apps < IVOA

<br />
<!--
      * Set ALLOWTOPICRENAME = IVOA.TWikiAdminGroup
-->

---+ Applications Working Group : November 2023, Online

* [[InterOpNov2023][back to main programme page]]]*
---++ Schedule
| *Applications Session 1: Saturday Nov 11 2023 @ 14:00-15:30 (Session #1)* ||||
| *Speaker* | *Title* | *Materials* | *Time* |
| Jonathan Normand | <p> *Solar system Open Database Network (SsODNet)* </p> <p>The sample of Solar system objects (asteroids, comets) has dramatically increased over the last decade. The number of measured properties (e.g. diameter, mass, etc.) has expanded even more quickly. We aim at offering a practical solution to the identification of Solar system objects from any of their multiple designation. We also aim at compiling and rationalizing the properties to provide an easy access to them. During Victoria 2018 Interop I presented the identification of Solar system objects and now I would like to focus on how to access to all these properties.</p> | | 10+3 |
| Chiara Marmo | <p> *Planetary World Coordinate System in Astropy* </p> <p>Different research communities are involved in planetary coordinate standardization: astronomers, geologists, plasma physics researchers,. In the framework of the EuroplanetH2024 European grant [1] some work has been done to define planetary standards for FITS World Coordinate System [2], in connection with Geographical Information System standards. To improve interoperability between those worlds we implemented the planetary WCS description in Astropy.<br />This presentation describes the related new features available in Astropy 6.0:</p> <ul> <li>the possibility to define a Geodetic Coordinate Representation on a custom spheroid using its equatorial radius and flattening</li> <li>the definition of a new Bodycentric coordinate representation for custom spheroids.</li> <li>the possibility to read and write planetary WCS keywords to define a body-fixed planetary reference frame.</li> </ul> | [[xxx][pdf]] | 8+3 mins  |
| Pierre Fernique | <p> *The IVOA HiPS network: status and evolutions* </p> <p>We will present the state of the art of the IVOA HiPS network at the end of 2023: the evolution of content, servers and tools. We will also address the weak points identified and we will suggest some solutions.</p> | | 12+3 |
| Laurent Michel | <p> *Mivot approach for the Epoch propagation* </p> <p>We will show how the [MIVOT + model] pattern can resolve the Epoch propagation case in a convenient way.<br />We will first give a brief reminder on both MIVOT standard and MANGO draft.<br />After that, we will present our AstroPy /PyVO implementation.</p> | | 16+13 |
| Tom Donaldson | <p> *VOTable 1.5 Status* </p> <p>Status of VOTable 1.5 before moving to RFC.</p> | | 12+10 |

---++ Schedule
| *Applications Session 2: Sunday Nov 12 2023 @ 9:00-10:30 (Session #2)* ||||
| *Speaker* | *Title* | *Materials* | *Time* |
| François Bonnarel | <p> *Access from visualisation tools to SKA science images and cubes stored in a rucio DataLake through IVOA discovery and access services* </p> <p>TBD</p> | [[xxx][pdf]] | 12+3 mins  |
| Markus Demleitner | <p> *Global image discovery in PyVO* </p> <p>Global dataset discovery is one of the promises of the VO that is still very hard to do for normal users. I am currently writing code to provide a pyVO-based API for the particularly hairy case of image discovery (https://github.com/astropy/pyvo/pull/470). Problems to be solved include: (a) dealing with the three available protocols (SIA1, SIA2, Obscore); (b) keeping the number of services to be queried low while accomodating services still not declaring STC coverage; (c) providing a sensible API to keep track of unresponsive or broken services without confusing casual usage; (d) keeping the number of dupicates low. This talk will discuss the state of affairs – and of course invite participation.</p> | | 12+3 |
| Mark Taylor | <p> *Authentication in TOPCAT* </p> <p>The most recent release of TOPCAT/STILTS can work with services that implement the "SSO_next" draft authentication proposal. That means TOPCAT users can log in within the application to access TAP and other (e.g. DataLink) services that declare their authentication arrangements as described by SSO_next. Currently known services that this covers include DaCHS, CADC, and soon ESDC. The library that enables this is suitable for use by third-party java applications.</p> | | 12+3 |
| Adrian Damian | Feedback on implementing S_region in Obscore | | 12+3 |
| Pierre Le Sidaner | <p> *Geospatial VESPA portal, alternative search tool in EPN-TAP services using HIPS and MOC* </p> <p>an approach based on harvesting metadata in a NoSQL database, allowing natural language interogation and simplified selections. We have added a spatial selection function</p> | | 12+3 |
| Kai Polsterer | <p> *HiPSter: Using HiPS tiling to allow for explorative access to simulations* </p> <p>TBD</p> | | 12+3 |
This topic: IVOA > WebHome > WebPreferences > InterOpNov2023Apps
Topic revision: r10 - 2023-10-30 - PierreLeSidaner