[Kstars-devel] Fwd: [kde-edu]: GSoC ideas

[Akarsh Simha]

> > KStars currently knows about deep-sky objects from the NGC and IC catalogs
> > and stars from the Henry-Draper catalog. Popular objects from many other
> > catalogs are not listed [eg: Collinder] and multiple designations for the
> > same object are not supported. The aim of this project is to implement
> > support for objects from SAO, UGC, PGC, MCG, PK and Saguaro Astronomy Club
> > catalogs. The student could also consider revamping the way data is stored
> > and accessed in KStars :-). 
> 
> This is a great project. Although I'm not sure it could be implemented by one 
> studen in reasonable time frame. IMHO change of data model is not an option 
> but prerequisite. Currently it is simply list of objects. There is no simple 
> way to combine data from multiple catalogs. It doesn't support fast searches 
> either. Only option is full traversal. 
> 
> It should be something more database-like I believe. But I don't have any 
> ideas about implementation.

I agree that it might be a great idea to change the data model
itself. (Again, I have no clue here, so I need to do a lot of homework
in case this project gets selected.) I'll alter the description to
make this a requisite.

I think at least backends for Deep-Sky objects should be doable
without much ado. IMO, optimization at the first go, although
preferable, would not be so critical as to kill the usability of the
application, since DSOs are few (unless we add PGC) in number.

We could talk to people and find out the best way to do it. Jan from
Open Coeli has, in the archives, explained how his application stores
data, which might be worth looking into at this stage...

Regards
Akarsh