Interference map
Where did position reports look degraded?
Open the per-day GeoJSON files that kshana interference-map writes from openly licensed aircraft (ADS-B) and ship (AIS) tracking data. Each file is drawn as its own map, with its licence, attribution and method shown beside it. Files you open here are read in this page and never uploaded.
What this is, and is not. A description of what published position reports looked like on a past day. It is not a measurement of any receiver, not a forecast and not proof of interference: a degraded or anomalous cell has several possible causes, listed under each map. A cell that is not drawn was not observed. That is not evidence of a clear cell. Advisory information only.
Open map files
Choose one or more adsb-<dataset>-YYYY-MM-DD.geojson or ais-<dataset>-YYYY-MM-DD.geojson files. ADS-B and AIS files are always shown as separate maps and never combined: their licences differ (an ADS-B file carries its source's licence, ODbL 1.0 for the built-in source; AIS files are public domain or NLOD 2.0) and so does what a cell means.
Nothing open yet.
Build a map here
Run the engine in this browser on a CSV of ADS-B or AIS position reports and get one map file per UTC day, then see it below. Rows and columns are described in the interference-map guide. The data is read in this page and never uploaded; the engine fetches nothing. A dataset preset needs the data you obtained under that dataset's own licence; with custom you state the licence and attribution yourself, and they are written into the file.
Route exposure here
How much of a planned route lay in degraded cells on each day, from the maps open on this page (opened or built here). Pick a route (a GeoJSON line, or a CSV of lat,lon lines; waypoints are joined by straight lines, so add points on long legs) and, if you like, limit the days. Not a forecast; a cell nobody observed is not evidence of a clear route.
Reading these maps
- The demo files are synthetic: every count is made up, on a made-up region, with no tracking source, partner data or real day behind them. Their data block says so.
- Maps inherit the coverage of their source: volunteer ADS-B receivers leave open sea sparse, and open AIS data omits some vessel classes. Read the coverage notes in each file.
- No coastline or basemap is drawn and nothing is fetched from any server; the grid is latitude and longitude only.
- No identifier of any aircraft or vessel is in these files; cells with too few distinct aircraft or vessels are not published at all, and an AIS count of one or two is withheld.