-
Notifications
You must be signed in to change notification settings - Fork 13
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
Feature Requests #30
Comments
So a big usability thing I've noticed when actually using SkyCoords recently is that humans don't work well with radians. Most of the errors as well as the time spent scratching my head recently has been simply formatting the SkyCoords into proper hour angle or degree formats for calculating offsets and for display. This was really frustrating, because I know all of the hard spherical geometry is coded up really nicely, but the coords don't really feel usable. This has shown me that working on the string representations (and corresponding parsing methods) will benefit this package the most, currently. For some ideas, I'm curious how
This way, we don't run into questions with "how do we store the coordinate"- we can always store the numerical value in radians, and use the formatter for the display. This also gives a struct that could be used for bulk parsing of coordinates. |
Long time Julia user, just getting into astro for my PhD work. I'd love to help on this as it would be super useful for my research as well as for a few of my colleagues. Specifically, I would love to see the Unitful integration as well as the |
That would be great! 🙂 |
Here are some features I'd love to see here:
c1 = ICRSCoord(0, 0); c2 = offset(c1, sep, theta)
I'm happy to crack open some of these but some of these implementations would make good first issues for possible contributors.
The text was updated successfully, but these errors were encountered: