Estonia 🇪🇪 Transpordiamet Registry

Name	ee-transpordiamet-registry
Country	Estonia
Registration prefix	ES-
Data source	https://transpordiamet.ee/ohusoidukite-register
Format	HTML table (single fixed page)
Run frequency	Weekly (Tuesday, 20:10 UTC)
Depends on Mictronics for ICAO hex	Yes — this runner does not publish ICAO hex addresses; registrations are resolved via RediSearch against Mictronics records (idx:aircraft:mictronics). Must run after the mictronics runner.

How it works

The Estonian Transport Administration civil aircraft register page is fetched directly (no index-page discovery needed — the URL is fixed) and its single HTML table is parsed with BeautifulSoup. The first two rows are header rows and are skipped. Each data row's registration mark has internal whitespace stripped (e.g. ES- FCC → ES-FCC) before it's used as the RediSearch lookup key against Mictronics. Every written record explicitly sets military: false — this register is exclusively civil, and the explicit value ensures a stale military: true flag (from Mictronics or a prior record on a reused hex) is corrected on re-registration.

Columns

The table has 9 positional columns (0-based); most are blank spacers.

Source column	Imported	Notes
Registration mark (col 1)	✅	ES-prefix; whitespace normalized; used as the Mictronics lookup key
Type of Aircraft (col 4)	✅	→ aircraft.model
Serial number (col 5)	✅	→ aircraft.serial_number
Owner (col 6)	✅	→ registrant.names[0]
Operator (col 7)	❌	Parsed but not stored
Blank spacer columns (0, 2, 3, 8)	❌	No data present

See specs/data-dictionary.yaml (ee-transpordiamet-registry entry) for full column semantics and cross-source schema notes.

Example Output

Read back the merged record for a given ICAO hex (combines this runner's data with Mictronics and any other sources that have written to the same key):

docker run --rm --network host redis:latest redis-cli EVAL "$(cat ./shared/lua/merge_aircraft.lua)" 0 51105A | python3 -m json.tool --sort-keys --no-ensure-ascii

{
    "aircraft": {
        "manufacturer": "CESSNA",
        "manufacturer_model": "CESSNA 172 Skyhawk",
        "model": "Cessna 172M",
        "serial_number": "17262412",
        "type_designator": "C172"
    },
    "data_sources": [
        "mictronics",
        "ee-transpordiamet-registry"
    ],
    "icao_hex": "51105A",
    "military": false,
    "registrant": {
        "names": [
            "AS Tackmer Air"
        ]
    },
    "registration": "ES-FCC"
}

docker run --rm --network host redis:latest redis-cli EVAL "$(cat ./shared/lua/merge_aircraft.lua)" 0 511153 | python3 -m json.tool --sort-keys --no-ensure-ascii

{
    "aircraft": {
        "manufacturer": "AIRBUS",
        "manufacturer_model": "AIRBUS A-320",
        "model": "Airbus A320",
        "serial_number": "2689",
        "type_designator": "A320"
    },
    "data_sources": [
        "mictronics",
        "ee-transpordiamet-registry"
    ],
    "icao_hex": "511153",
    "military": false,
    "registrant": {
        "names": [
            "Bank of America, N.A."
        ]
    },
    "registration": "ES-SAY"
}

Configuration

See Data Runners for the full list of environment variables every runner reads. This runner writes aircraft:registry:{icao_hex} with a fixed 14-day TTL (ENRICHMENT_TTL_SECONDS in shared/timing.py).

MQTT

Published once, at the end of a run, to SkyFollower/runner/ee-transpordiamet-registry/statistic/{name} (all retained):

Topic suffix	Value	Format
records_imported	e.g. 271	Integer as string
last_run_at	e.g. 2026-07-07T14:32:01.123456+00:00	ISO 8601 UTC
last_run_status	Success or Failure	String

Home Assistant autodiscovery configs are also published (retained) to homeassistant/sensor/SkyFollower_runner_ee_transpordiamet_registry_{name}/config for each of the three stats above.