Reflections on SIA V2 and generic cutout services
François Bonnarel
francois.bonnarel at astro.unistra.fr
Wed Mar 9 11:29:26 CET 2016
Hi Walter,
In complement to what I answered Tom
Le 03/03/2016 21:39, Walter Landry a écrit :
> "Tom McGlynn (NASA/GSFC Code 660.1)" <tom.mcglynn at nasa.gov> wrote:
>> 1. SkyView is a cutout and mosaicking service. So in terms of
>> retrieving an image SkyView needs two kinds of inputs: those that
>> select the survey or surveys we are interested in (e.g., bandpass and
>> resolution) and the WCS parameters that define the region to be
>> generated.
> I had the same problem with our Planck image generation service. SIA2
> is really not set up for this. SIA2 is much better for retrieving
> links to existing images.
Yes. It is totally true for 2.0
> For example, your mosaicing service might
> have a multitude of options on how exactly to stitch images together.
Apart from simple cutouts, which only semect values, (SODA 1.0 scope)
There are two major distinct functionalities we can imagine. Refactoring
a subset of a given dataset.
Providing a real mosaic or merge of the datasets.
Of course in case of Cubes the emrge may be really complex.
Another main difference will be that the ID SODA parameter will now more
allow us to ACEES to a given datataset, but actualy would have to do it
for a COLLECTION of mergeable datasets.
This will be a major difference to tackle ..... in the future.
Cheers
François
> The best conceptual match I could find was something like SimDAL,
> which allows for this sort of extensive computation in order to
> generate an artifact for the end-user. With that said, I have not
> actually implemented anything like SimDAL for our service.
>
> Cheers,
> Walter Landry
More information about the dal
mailing list