Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Coordinate system conversions #17

Open
robertbutora opened this issue Mar 22, 2024 · 1 comment
Open

Coordinate system conversions #17

robertbutora opened this issue Mar 22, 2024 · 1 comment

Comments

@robertbutora
Copy link

We faced a project studying the Galaxy, where the clients were required to operate in GALACTIC coordinates.
The SODA interface mandates ICRS, [WAVE,Barycentric,m]. However we needed GALACTIC, [VELO,LSRK,km/s].
Conversion is needed.
In general, astronomers pointed out that some projects might benefit if data could be accessed via 'few' (2..3)
coordinate systems rather then one fixed.

Would it be possible to standardize coordinate system for (SODA) parameters ?
It would avoid each implementation in need, to come up with its own keywords and coord system encodings.

Sketched example:
Coordinate system could be conveyed by new parameters like POSSYS, BANDSYS, TIMESYS.
Or alternatively be appended as last element of the current parameters (POS, BAND, TIME). For instance

POS=RANGE 10.0 12.0 -1.0 1.0 GALACTIC

Coordinate system names supported by given service-instance could follow conventions (FITS standard or AST lib or other?)
and be enumerated in service descriptor.

Note: include also non-WCS systems like PIXEL-GRID ?

@msdemlei
Copy link

msdemlei commented Mar 22, 2024 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants