[Kstars-devel] USNO is sending me 100 million stars

[Jason Harris]

They get only 6 bytes per star because they only provide RA, Dec, and
2 magnitudes.  Our catalog will additionall have proper motions, so
our positions will be more accurate for remote dates.

Still, if we want to give users the option of foregoing proper motion,
then this would be an exciting option...

On Mon, Jun 30, 2008 at 3:29 PM, Akarsh Simha <akarshsimha at gmail.com> wrote:
>
>> Any chance of supporting USNO A 2.0 binary format?
>>
>> It have quite simple format 6byte record per star, is also indexed.
>> There are some C libraries for reading it. Many amateurs already have
>> downloaded it since CdC and other programs can read it.
>
> Could you link me to it's specification? I wonder how they manage with
> 6 bytes per star.
>
> It might be easy to write a program to convert this format into
> KStars' format. We should probably stick to KStars' present format at
> the end, because the KStars format is designed keeping speed in mind,
> so that all fields lie on appropriate byte boundaries.
>
> Regards
> Akarsh
> _______________________________________________
> Kstars-devel mailing list
> Kstars-devel at kde.org
> https://mail.kde.org/mailman/listinfo/kstars-devel
>