Aerospace operations
You connect a source.You get a table.
There is no aerospace template, and none is needed. An open data source becomes a table in your workspace — with its own columns.
Sources on this board
read-only · authority stays with the provider · matched by filter and by map, never by relation
Live aircraft statesread-onlyFresh
Flight tracking · Aircraft positions · Altitude · Velocity
ACA317c06539CanadaAUA2554408deAustriaAAL2943ac791dUnited StatesWJA265c063ebCanada
19 fields mapped · 5,000 rows loaded
Aviation weatherFresh
- METAR
- TAF
- PIREP
report types straight from the source
Hazard layersFresh
- Icing
- Turbulence
- SIGMET
- AIRMET
- Ceiling
- Visibility
also: pilot reports · flight category
Orbital elementsread-onlyFresh
| OBJECT_NAME | EPOCH | MEAN_MOTION |
|---|---|---|
ISS (ZARYA) | ||
ISS (NAUKA) | ||
CSS (TIANHE) |
23 / 23 rows
A connected table is read-only — the provider keeps authority over the data.
Connect a source
From the catalogue to a loaded table.
Five steps, run on two real sources: OpenSky and CelesTrak. The fifth shows how each source gets the views its own data supports.
- 01
Open the catalogue
The catalogue opens on a globe: 5,885 mapped sources and 70+ pre-configured portals.
- 02
Look before you connect
OpenSky asks for no key, answers in real time, carries 10,000+ aircraft. Its dataset already shows the product's views — Map, Table, Calendar, Timeline, Gantt, Kanban — before you connect anything.
- 03
Map the fields
The connection assistant maps 19 fields and reads the types on its own: on_ground becomes a boolean, latitude a number, icao24 text.
- 04
Work the table
5,000 rows land in your workspace — ACA317, WJA265, real flights. You map them and you filter them, and the provider stays the source of truth.
- 05
Read the elements as they are
CelesTrak loads 23 rows out of 23 — ISS (ZARYA), CSS (TIANHE). Orbital elements describe an orbit, and the table opens on the five views they support: Table, Calendar, Timeline, Gantt, Kanban.
The composition
No published template. Nine free apps.
There is no template to apply. Nine apps, all free, and a schema that comes from the source you connect.
- Open Data CatalogA globe, 5,885 mapped sources, 70+ pre-configured portals.
- Geo LayerMap, globe or satellite. Radar and imagery as overlays.
- REST API ConnectorGive it a REST address. It maps the fields and the types.
- ArcGIS ConnectorOpens an ArcGIS MapServer and lists its sublayers.
- GeoJSON ConnectorConnects a GeoJSON file or feed as a source.
- Mind MapIdeas and their branches, laid out on one canvas.
- NewsroomAnnouncements and updates, published where the work happens.
- Document CenterProtected storage for procedures, reports and reference files.
- SlidesBuild a presentation without leaving the workspace.
Views
The data decides which views you get.
OpenSky states carry a latitude and a longitude, so their dataset opens on a map. CelesTrak orbital elements describe an orbit, so their table opens on the views those elements support. Same product, same moment — the difference comes from the rows.
- Map
- Table
- Calendar
- Timeline
- Gantt
- Kanban
openskyLiveAircraftStates
These rows carry a latitude and a longitude, so the map is offered.
celestrakStations
MEAN_MOTIONECCENTRICITYEPOCH
These elements describe an orbit. The map belongs to sources that carry a place.
Orbital elements describe an orbit, so this table opens on the views they support.
Open data
Aviation and space, already in the catalogue.
The catalogue announces 70+ pre-configured portals: OpenSky, CelesTrak, NOAA aviation weather, the ICAO API Data Service — from Montréal — and the Canadian Space Agency's 159 datasets. None of them is connected in advance; they are available, and you connect the ones you need.
- Flight tracking
- Aviation weather
- Orbital elements
- ICAO reference codes
- Earth observation
Governance
Every table tells you where it stands.
- The state of the data
- A connected table is fresh, stale, syncing or unavailable. The state shows with the date of the last refresh and the cache lifetime.
- The provider keeps authority
- A connected table is read-only. You can't create a relation to it either — you match it with your own data by filter and by map.
- Failures have names
- When a source stalls, the message names it: “celestrak gp data has not updated”, “feed updates once every 2 hours”. No generic error.
- Keys, before you connect
- Sources that need a key are labelled before you connect: Space-Track carries a “Needs key” tag. Live records ask for credentials from the provider.
Before you ask
What you can count on.
What does Nixa do with orbital elements?
It reads them and keeps them as rows, exactly as CelesTrak publishes them — OBJECT_NAME, OBJECT_ID, EPOCH, MEAN_MOTION, ECCENTRICITY. Turning elements into positions is the work of a flight-dynamics tool; Nixa hands you the elements as received, so what you read is what the provider published.
Do I need an API key?
The sources shown here answer without one — OpenSky and CelesTrak both. When a source does require a key, the catalogue says so before you open it: Space-Track carries the “Needs key” label.
Which sources open on a map?
Those whose rows carry a position. OpenSky states have a latitude and a longitude, so the dataset opens on a map and a globe, among six views. CelesTrak orbital elements describe an orbit, so their table opens on five: Table, Calendar, Timeline, Gantt, Kanban. The data decides.
Who owns the data, and how do I know it is current?
The provider owns it, and the table says so plainly: it is read-only, and it shows its state — fresh, stale, syncing, unavailable — with the date of the last refresh. When a feed stalls, the message names it, so you always know how old what you are reading is.
What about aircraft maintenance?
This product connects open data sources and reads what they publish — traffic, aviation weather, hazard layers, orbital elements. Maintenance, airworthiness and work orders belong to a product of their own.
Pick a source. We connect it.
Screen shared, live. If the source needs a key, bring the provider credentials.