Notes from AAS IVOA footprint tag up

[Gretchen Greene]

Hi folks,

I've tried to capture some of this information on the main DAL page topic for footprint access protocol.  I think it will be more and more important to have a complete spec that can handle regions accurately and efficiently with standard methods,  but first things first...;)  i fully support this effort to incorporate the simpler regions in the basic DAL protocols which we have already standard framework to utilize near term.

There is some additional information that is much overdue for me to transfer in (presented at Victoria interop and before) that i'm hoping to transfer over in the next couple days that describe the specifications we have been proposing for the more complete footprint/spatial region handling,  of which this simplified STC-s DAL standard implementation is associated with.

http://www.ivoa.net/cgi-bin/twiki/bin/view/IVOA/FootprintAccessProtocol

There are a few topics off this page that hold this recent thread content,  including the proposed DAL basic footprint.

http://www.ivoa.net/cgi-bin/twiki/bin/view/IVOA/DALBasicFootprintHere
http://www.ivoa.net/cgi-bin/twiki/bin/view/IVOA/STCparsers

-Gretchen

________________________________________
From: dal-bounces at ivoa.net [dal-bounces at ivoa.net] on behalf of Markus Demleitner [msdemlei at ari.uni-heidelberg.de]
Sent: Thursday, January 19, 2012 12:14 PM
To: dal at ivoa.net
Subject: Re: Notes from AAS IVOA footprint tag up

Hi Alberto, hi list,

On Wed, Jan 18, 2012 at 04:24:55PM +0100, Alberto Micol wrote:
> Would you know whether a library that can parse, digest, and maybe plot
> a generic STC-s region exist?
Well, for complete STC-s, "digest" is a big word (e.g., as concerns
all the transformations between the coordinate systems you can
specify with STC-S).

Having said that, the GAVO STC library
(http://soft.g-vo.org/subpkgs#STC) parses what's basically a slight
superset of STC-S and can do "some things" (TM) with the result.

Within the context of the server package
(http://soft.g-vo.org/dachs), I derive coverage information of
registry purposes from it, generate utypes, and use it to turn ADQL
regions into something that pgSphere can deal with.  I've not touched
the footprint issue as such, though.

Cheers,

       Markus