 |
 |
> > > Sorry, for the confused that should be: > > > > > > (*12h34m56s~1m19s,12d34m56s:12d35m01s) Yep that makes more sense. This looks human readable for sky co-ordinates. For that reason it gets my vote. There is an ambiguity if one want to express an longitude distance in seconds of time instead of arcseconds. Since "s" and "m" are used for both measures of angle and time, that's not a problem and one could put in the preceding "0h[0m]" to resolve the overloading in the rare cases where this was required. I hope that there is flexibility in the formatting, say to be able to use 188.733d for the right ascension if you want to use decimal degrees rather than sexagesimal (degrees is the norm in meteor astronomy). Are there are lists of unit abbreviations for the various Frames like SpecFrame and TimeFrame? We can add plenty of examples to SUN/95 in "NDF Sections" and in individual tasks. Malcolm