Concept

My Astrometry was shaped by a long iterative requirements process. The guiding rule is simple: observation data must stay traceable, derived values must be reproducible from OBS80 columns, and long-running operations must always show progress.

Data contract

Every analysis starts from OBS80 columns. ADES input is supported, but it is converted before calculations start. Optical observations are the intended basis for the application.

Observatories

MPC observatory codes are checked against the cached MPC list. If a station cannot be resolved, location-dependent charts are not produced from guessed coordinates.

Sky context

Sun, Moon, elongation, Moon illumination, azimuth and altitude are calculated for every observation where the required input exists. Twilight, Moon effects and impossible geometry are highlighted.

Windows workflow

The application keeps a classic Windows style: menus, movable child windows, saved window layouts, sortable tables and explanatory hover text on fields, headers and buttons. Chart windows can be arranged, saved, restored and refreshed individually.

Large files

OBS80 files can contain tens or hundreds of thousands of rows. My Astrometry therefore uses background calculations, progress dialogs, ETA, caches, optional nightly midpoint reduction and manual refresh for expensive views.

Movies and reports

The movie wizard creates MP4 output from selected charts. It asks for resolution, fps, runtime, intro/outro, end pause, music and output paths. HTML reports include charts but avoid bulky analysis tables for large datasets.

Privacy by design

The application does not automatically send data to Jost Jahn. External services such as WAMO, MPC or CDS Aladin are used only when the matching function is invoked. Private caches, logs, layouts, music indexes and input files are not shipped with the public installer or website.