The support for SODA v1.1 has been deployed at lsst-lstp-int.
ImgServ Class Diagrams
The following two diagrams describe the main classes and their interactions with each other in the ImgServ SODA design.
SODA Usage Examples
The coordinate system has to be ICRS with coordinates in degrees, per SODA v1.1 specification.
Note: for now ID is used as the image dataset identifier, but really with it should be the unique image ID, or the data_id per LSST parlance.
Example 1-3 for the standard SODA shapes:
Example 1: CIRCLE <longitude> <latitude> <radius>
Example 2: RANGE <longitude1> <longitude2> <latitude1> <latitude2>
Example 3: POLYGON <longitude1> <latitude1> ... (at least 3 pairs)
The following example is defined by LSST DAX only:
Example 4: BRECT <longitude> <latitude> <width> <height> <size_unit>, size_unit = pixel | arcsec
Generic Implementation of SODA
Historically VO services have been implemented in Java, in conjunction with XML as the linga franca, from the beginning for almost 20 years since.
Given the popularity of astropy and affiliated packages in the astronomy community, there is strong value proposition for Python based service implementation,
which can take advantage of popular and proven Python packages, such as pyvo, astroquery, astrocut, etc.
Hence ImgServ can implement this generic layer with the changes to the following modules:
a. ImageGet
b. MetaServGet
b. Image