<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=iso-8859-1">
<META content="MSHTML 6.00.2800.1597" name=GENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=#ffffff>
<DIV><FONT face=Arial size=2>Dear KStars Development Team,</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>If this Email has been directed to an inappropriate
destination please let me know (<A
href="mailto:iankathy@idnet.com">iankathy@idnet.com</A>), together with detail
of the correct team to contact.</FONT></DIV>
<DIV>
<P><FONT face=Arial size=2>These notes invite comment on enhancements relating
to the star database (Hipparcos) used by KStars (version 1.2.5, using KDE
3.5.6).</FONT></P>
<P><FONT face=Arial size=2>In the past, in a Windows environment, I have used
extensively the Meade Astronomical software to interface to my Meade telescope
via the Autostar handbox. I was pleased to find the interface to the Autostar
handbox by KStars via the INDI environment and a USB/serial converter
trouble-free. The built-in drivers for the Meade Autostar handbox, and also for
the PL2303 based USB to Serial converter was a welcome find.</FONT></P>
<P><FONT face=Arial size=2>The issue I wish to raise relate to the different
star databases in use by the two planetarium environments. In the Meade case it
is the Smithsonian catalogue (SAO). As might be expected for the Meade Autostar
handbox attached to the telescope, one convenient method of inputting a target
star is by means of the SAO catalogue index number. In the case of KStars,
the more modern Hipparcos catalogue has been adopted. However, in KStars, when a
particular star is selected on-screen, and the details requested, there are, to
my mind, several omissions. In particular, the Hipparcos (HIP) index number is
not given, so there is no convenient method of cross-referencing to the SAO
index value for subsequent input to a "guided tour" file for subsequent
downloading to the Meade handbox.</FONT></P>
<P><FONT face=Arial size=2>In trawling through the KStars "bugs" database, I
have found references to the SAO catalogue in the 2003/4 time frame, but I have
gained the impression in that context that this database had been phased out. It
does prompt me to ask whether a cross-reference list of corresponding HIP and
SAO index values could be incorporated into the KStars environment, and that
<U>both values are shown </U>when the object detail of a selected star is
brought forward on the screen?</FONT></P>
<P><FONT face=Arial size=2>Secondly, I was interested in the contribution number
147744, where another user was expressing interest in the export of a Meade
compatible guided tour from KStars. In referring to the Meade specification for
a "guided tour" file, it is certainly possible to indicate a target by means of
its RA and Dec. However, I would suggest that it is far more preferable to use
star catalogue numbers for the brighter stars, and in the case of Meade, it has
to be the SAO index number.</FONT></P>
<P><FONT face=Arial size=2>The situation for deep sky objects is much more
unified, in that Meade can make use of NGC, IC and Messier index numbers, which
are also recognised in the KStars environment. Also, the "detail" panel for deep
sky objects, does show the catalogue information, and common name, e.g. for the
Pinwheel Galaxy, in addition to the popular name, the detail panel also
lists: M 101, NGC 5457 and PGC 50063. I feel sure this type of information could
also be presented on the star detail panel, hopefully to include both the HIP
and SAO index numbers.</FONT></P>
<P><FONT face=Arial size=2>I would be pleased to have your comments on the above
contribution, especially if it is believed an enhancement to KStars could be
made which implements these suggestions.</FONT></P>
<P><FONT face=Arial size=2>Yours sincerely,</FONT></P>
<P><FONT face=Arial size=2>Dr Ian Whiteley. (UK).</FONT></P></DIV></BODY></HTML>