Catalogs

In the Catalogs page, you can configure which object catalogs are displayed by KStars, as well as how much information you would like to be included on the Sky Map. By default, KStars includes ~300,000 named and unnamed stars up to magnitude 8. For Deep Sky Objects, the included catalog is the New General Catalog (“NGC”) including the Index Catalog (“IC”) and the Messier Catalog.

De New General Catalog of Nebulae and Clusters of Stars (afgekort als NGC), is een catalogus van 7840 deep-sky objecten.

De Index catalogus voor nevels en sterrenhopen (afgekort als IC), is een supplement voor de NGC-catalogus, en bevat een verdere 5386 objecten, die collectief bekend staan als de IC-objecten.

You can install new catalogs using KStars “Add-On Installer”. You can open it via the Data → Download New Data... menu item. You can choose from a list of catalogs, including (but not limited to):

• Steinicke NGC/IC Catalog: is een meer volledige NGC/IC catalogus.

• Abell Planetary Nebulae Catalog: is een catalogus van 86 planetaire nevels. De maximum magnitude (zwakste helderheid) is die van Abell 47: 19,5.

• Sharpless HII region Catalog: is de Sharpless (Sh2) catalogus van HII gebieden (diffuse nevels).

• Hickson Compact Groups: is een catalogus bestaande uit 99 compact groepen van melkwegstelsels.

• Tycho-2 Star Catalog: is een catalogus van meer dan 2,5 miljoen helderste sterren. Hierin zijn sterren met een magnitude van 8,0 tot 12,5.

• USNO NOMAD Catalog: is een catalogus met ongeveer 100 miljoen sterren met een magnitude van 12,5 tot 16,5. Let erop dat ook Tycho-2 moet zijn geïnstalleerd..

The following is a summary of catalogs in KStars:

Table 3.1. Stars Catalogs

Naam	Afkorting	Aantal objecten	Magnitude
Standaard catalogus	Standaard	~300,000	Tot aan magnitude 8
Tycho-2	Tycho2	meer dan 2,5 miljoen	8.0-12.5
Samengevoegde astronomische gegevens van de Naval Observatory	USNO NOMAD	100 miljoen	12.5-16.5

Table 3.2. Deep-sky objects Catalogs

Naam	Afkorting	Aantal objecten	Magnitude
New General Catalog of Nebulae and Clusters of Stars (OpenNGC)	NGC	7840
Steinicke NGC/IC
Abell Planetary Nebulae Catalog		86	Tot aan magnitude 19,5
Sharpless HII region Catalogus	Sh2
Hickson Compact Groups		99

Notitie

A potentially more up-to-date listing can be found in the catalog repository documentation.

The Stars section allows you to manage how stars are displayed in KStars. You can choose to see the stars or not by checking the Star catalogs checkbox. If you check it, then multiple options will be enabled. Thus, you can set how many stars are drawn on the map using the Star density: slider. You can also customize KStars to toggle star name and magnitudes. Star names are drawn next to bright stars. To display labels of fainter stars, increase the Label density: slider.

Below the stars section, the Deep-Sky Objects section controls the display of several non-stellar object catalogs. You can toggle the display of Deep Sky Objects and control the display of their names and magnitudes. By default, the list of deep-sky objects includes the Messier, NGC and IC catalogs. Addons catalogs are available via the Data → Download New Data... menu item where you can download catalogs provided by KStars team and the community through the catalog packaging repository. The DSO minimal zoom: slider controls the minimal zoom level for which the DSOs are shown. Increasing the minimal zoom level can lead to performance improvements when panning the skymap zoomed-out. The DSO cache percentage: slider regulates how much of the DSO master catalog is being kept in memory. If you experience memory issues with large catalogs, try lowering the percentage. The Label density: slider controls the perceived density of labels for the DSOs. If labels start to overlap and the skymap begins to look too crowded, try tuning this option. The Faint limit zoomed in/out: regulates up to which magnitude objects are shown on the skymap (higher magnitude is fainter). If Show objects of unknown magnitude is ticked, objects of unknown magnitude are always shown.

The following sections will detail how DSO catalogs work in KStars and how they’re managed.

De DSO catalogi-database

Notitie

This section aims at introducing the catalog database of KStars in simple but technical terms. It can be skipped without missing anything essential but helps understanding how to deal with and create (custom) catalogs.

DSO catalogs in KStars are just SQL (sqlite3) database tables. Each catalog is represented by its own table which contains all its objects and an entry in a catalog metadata table. Additionally, catalogs may be imported or exported from and into stand-alone database files.

Elk object heeft de gebruikelijke eigenschappen zoals naam en coördinaten maar heeft ook twee ID’s. De eerste ID is de unieke identifier voor het specifieke object en wordt berekend uit een hash van alle objectvelden samen met de catalogus-id. Omdat objecten in verschillende catalogi zich kunnen bevinden heeft elk object een additioneel object-id (OID) dat het fysieke object identificeert en gedeeld kan worden door verschillende objecten uit verschillende catalogi.

To speed up object lookup all enabled catalogs are merged into a master table. Each catalog has a priority number and if several objects with the same OID occur the one from the catalog with the highest priority is loaded. The objects from the master catalog are then drawn on the sky and generally available in KStars.

Currently, deduplication (the assignment of OIDs) is only supported by the tooling of the catalog packaging repository. The aim of this tool-chain is to reproducibly build catalogs in a homogeneous environment. Every catalog is implemented as a python module and provides standard methods to acquire data, parse it and find duplicates in other catalogs. All downloadable catalogs are implemented this way. If you’d like to make a catalog of your own available for KStars, it is recommended that you implement it as a package in the repository. The tooling provided there is so flexible, that it should work for you. For more information on how to do that see the catalog repository documentation. If you are not familiar with python programming you can request the addition of a catalog by opening a ticket in the repository or contacting the maintainers. KStars provides also provides means to create custom catalogs by manually entering data or importing CSV tables, but those are less flexible and offer no deduplication.

The Catalog Management GUI

The catalog management GUI is reached via the Data → Manage DSO Catalogs... menu item and is displayed below.

The DSO catalog management interface.

On the left, a list of catalogs is displayed. In this list, you can read off key catalog properties, including whether a catalog is enabled, what its ID is and what its name is. The Mutable column signifies whether the catalog can be edited or not. Catalogs which have been downloaded from the catalog repository via the Data → Download New Data... menu item are usually immutable whereas user-created catalogs aren’t. You can always Clone a catalog to make it mutable.

De knoppen in de rechtsboven hoek bieden u het toevoegen van catalogi aan de database.

Import Catalog...

Import a catalog in the .kscat format from a file.

Dit wordt gewoonlijk gedaan om nieuwe versies van catalogi uit te proberen die nog niet opgepakt zijn door de gebruikelijke downloadserver.

Met de knoppen in de rechtsonder hoek kunt u catalogi toevoegen, verwijderen, modificeren en bekijken. Hun acties verwijzen altijd naar de nu geselecteerde catalogus (de geaccentueerde rij links).

Create Catalog...

Create a new catalog. See the section called “Creating a new Catalog”.

Enable / Disable

Een catalogus in-/uitschakelen.

This is reflected in the skymap upon closing the catalog management GUI.

Remove

Een catalogus verwijderen uit de catalogusdatabase.

This is reflected in the skymap upon closing the catalog management GUI.

Export...

Export a catalog into a .kscat file.

The resulting file can be imported with Import Catalog... button.

Clone...

Maak een exacte kopie van de catalogus en voeg deze in in de database.

Dit is nuttig als u wijzigingen wilt maken in een niet te wijzigen catalogus.

Notitie

Note however that this is not the recommended way to alter catalogs that are provided by the catalog packaging repository i.e. the catalogs downloaded via the Data → Download New Data... menu item.

Colors

Open the catalog color editor (See the section called “Catalog Color Editor”.).

Dit zal een dialoog openen die het instellen van de kleuren biedt waarin objecten uit de geselecteerde catalogus getoond zullen worden voor elk kleurenschema.

More...

Open the catalog details dialog. (See the section called “Catalog Details Dialog”.)

Daarin kunt u de inhoud van de catalogus zien, evenals enige verdere metagegevensinformatie. Onder anderen kunt u ook zijn inhoud bewerken (als het te wijzigen is).

Een nieuwe catalogus aanmaken

This dialog reached through the catalog management GUI (see the section called “The Catalog Management GUI”). The ID: field will be automatically chosen but can be changed. The Color: field configures in which color the objects of the catalog will be displayed. All the other values are optional or have sensible defaults. You can, of course, change these values at a later point.

Upon clicking Ok an empty catalog with the meta data entered into the dialog will be added to the database and can then be filled with objects. (See the section called “Catalog Details Dialog” and the section called “Importing CSV (and similar formats)”.)

Catalog Color Editor

This dialog reached through the catalog management GUI (see the section called “The Catalog Management GUI”). Each button represents the color that objects will be drawn in for a specific color scheme. Clicking on a button will allow you to choose a color with a color picker. The button colors are initialized with the default colors from the catalog specification. The color “default” is the color which will be chosen for the catalog if there is no color set for a color scheme.

Catalog Details Dialog

This dialog reached through the catalog management GUI (see the section called “The Catalog Management GUI”). In the top left corner, the catalog metadata is being displayed. On the right, a table of all objects in the catalog is being shown. The search line above the table filters objects by name. Double-clicking a row opens the object details dialog (see the section called “Object Details Window”).

Selecting a row enables the Object menu on the left. Selecting multiple rows performs the single-object action for each selected object.

Edit...

Edit the catalog object. (See the section called “Adding/Editing Objects”).

Remove

Verwijdert het object uit de catalogus.

Below the Object section, the general catalog options are situated.

Edit Catalog Meta...

Edit the catalog metadata displayed in the top left. This opens the dialog described in the section called “Creating a new Catalog”.

Add Object...

Add an object to the catalog. (See the section called “Adding/Editing Objects”.)

Import CSV...

Import objects from a tabular text format (csv, tsv, etc.) into the catalog. (See the section called “Importing CSV (and similar formats)”.)

Adding/Editing Objects

This dialog allows to create or edit a deep sky object (DSO). The Basics section contains fields that have to be filled in.

Name:

De naam van het object dat getoond zal worden aan de hemel.

Type:

Het type object.

RA / Dec (°, J2000):

De coördinaten van het object in graden en met betrekking tot de J2000 epoch.

Apparent magnitude:

De schijnbare magnitude van het object.

The Optional section contains data fields that are optional, is divided into two subsections. They are set to and can be left at their defaults.

The Size Info in Arcminutes subsection. The object is modeled as an ellipse which is described by its major and minor axis.

The Misc subsection.

Long name:

Een langere, meer beschrijvende naam.

Usually, the long name is something like “Andromeda Galaxy” for the object M31. It can contain alternative designations and names in other catalogs as well.

Catalog identifier:

Een interne identifier in de catalogus.

For example the screenshot above, the object originates from the OpenNGC catalog where each row is identified by “NGCXXXX”.

Flux:

De flux van het object. Is alleen van toepassing op radiobronnen.

Position angle (°):

Als het object uitgebreid is, moet het een oriëntatie aan de hemel hebben. De positiehoek is de hoek tussen zijn majeure as en een rechte lijn naar de noordpool.

CSV importeren (en gelijksoortige formaten)

The screenshot above shows the CSV import dialog in its default state. In the Input section, you can configure the csv parser. The Comment prefix: is the character that signals commented-out lines in the input. The Separator: should be adjusted to fit your input. Usually, it is “,” or “;” but other separators can occur. Finally, you can choose to skip a number of lines at the beginning of the file. Select/Read button lets you choose a csv file to read with the above configuration. After that, the dialog will look as in the screenshot below.

In the top right you can choose whether coordinates are being expressed in degrees or hours/minutes/seconds. The Mapping section lets you map columns in the CSV file to data fields in KStars. Selecting Ignore assigns the default value for this field. Entering your own text will use this as the value for every object being read. The Type Mapping section maps strings to object types. You can add and remove mappings by clicking + or -. When you’re done mapping, you can test your settings by clicking Preview to read the first few objects from the csv. If you are satisfied you can click OK to import the whole catalog or adjust your settings and preview again. As a reference, a mapping for the OpenNGC catalog is shown in the below screenshot.