StolWRX

Appearance

Uploading Flights ​

📢 - INFO

StolWRX stores your flights in the cloud so you can open them on any device and (optionally) share them publicly. This page explains what file formats are supported, how to upload, and what happens after the upload.

Supported File Formats ​

StolWRX can read:

  • CSV — flight-log CSVs with headers. Common columns supported include time, latitude, longitude, GPS/pressure altitude, ground speed, indicated airspeed, vertical speed, track/heading, and engine channels that start with E1…, E2… (manifold pressure, RPM, fuel flow, oil pressure/temp, CHTs, EGTs, fuel quantity).
  • KML — ForeFlight-style KML tracks exported from EFB apps.
  • KMZ — zipped KML.

📌 - TIP

The flight log columns don't have to match ForeFlight or Garmin conventions exactly. StolWRX parses the header row, maps what it can recognise, and ignores the rest.

How to Upload ​

  1. Open the Flight tracks dropdown (squiggle icon on desktop; the sheet menu on phones).
  2. Click Load flight track.
  3. Pick one or more files. You can multi-select.

Each file is parsed locally, plotted on the map, and pushed to the cloud in the background. Progress is indicated by a spinner on the menu icon while uploads are in progress.

📢 - INFO

Uploading flights requires a paid subscription. Free-plan users can still view flights that others share with them via a public link — see Public Shared View.

What Happens After Upload ​

Once a flight is in the cloud:

  • It appears in the flights panel (slide-out table). Each row shows the pilot-editable name, the color StolWRX assigned to the track, the start time, and row-level actions (rename, share, delete).
  • It's drawn on the 3D map as a colored polyline draped over the terrain.
  • The strip chart under the map lists the channels in the log (altitude, speed, engine values) and lets you add/remove channels to chart.
  • If the log contains engine columns, the Engine HUD appears in the top right of the map with gauges reflecting the current time position. See Engine HUD.

Cropping a Flight ​

The time range scrubber under the strip chart shows the full duration of the flight. Drag the left and right crop handles inwards to isolate a segment (a takeoff, a low approach, one circuit around a strip).

The crop affects:

  • The map — only the cropped segment of the track is drawn.
  • The strip chart — the chart zooms to the cropped range.
  • Track photos — photos outside the cropped range fade.

When you share a flight publicly, the crop you set is what the recipient sees — anything outside the crop is not included in the share. See Sharing Flights and Time Range Scrubber.

Renaming a Flight ​

In the flights panel, click the pencil icon on a row to rename the flight. The default name is the source file name; you can change it to anything (for example, "Idaho Backcountry — Johnson Creek to Big Creek").

Deleting a Flight ​

Select one or more rows in the flights panel and click Delete. This removes the flight from the cloud and from your view. Public share links to the deleted flight stop working immediately.

📌 - TIP

If a flight has track photos attached, deleting the flight also deletes those photos from storage.

Loading a Second Flight on Top ​

You can load additional flights and StolWRX will draw all of them on the map with different colors. This is useful for:

  • Comparing the same route flown on different days.
  • Lining up an approach you flew against one your friend flew.
  • Stitching a photo set together — each photo is anchored to its own flight's track.

To hide a flight temporarily (without removing it), select its row(s) in the flights panel and click the eye toggle at the top of the table.

Local vs Cloud ​

When you first pick a file, StolWRX immediately parses and plots it locally. The cloud upload happens in the background. If the upload fails (bad connection, auth issue) the local view keeps working — you can retry by clicking the row action.

Rows in the flights panel that are in the cloud are marked with a subtle indicator next to their color swatch; local-only rows don't have it. Sharing and photo-upload actions require the cloud copy to exist.