30:T801,Plot.plot({ width, height, projection: d3 .geoOrthographic() .scale(((result_airport ? scale : 1) * width) / 1.5 / Math.PI) .rotate(d3.geoCentroid(result_airport).map((x) => -1 * x)) .translate([(0.7 * width) / 2, height / 2]), marks: [ Plot.geo({ type: "Sphere" }, { fill: "white" }), Plot.geo(graticule, { stroke: "#aaa", strokeWidth: 0.25 }), Plot.geo(land, { stroke: "#333", fill: "#ced4da" }), Plot.geo(countries, { stroke: "#fff", fill: "#ced4da" }), Plot.geo( all_airports.map((a) => Object({ type: "Feature", geometry: { type: "Point", coordinates: [a.longitude, a.latitude] }, properties: a }) ), { r: 1.8, fill: "#4c78a8", opacity: 0.3, tip: result_airport.properties.point ? true : false, title: (d) => `${d.properties.code ?? ""} ${d.properties.name ?? ""}` } ), result_airport ? Plot.geo(result_airport, { r: 5.5, fill: result_airport.geometry.type === "Point" ? "#f58518" : undefined, stroke: "#f58518", strokeWidth: 2 }) : null, result_airport.properties.points ? Plot.geo( { type: "Feature", geometry: { type: "MultiPoint", coordinates: result_airport.geometry?.coordinates ?? [] } }, { r: 3, fill: "#f58518" } ) : null, result_airport.properties.points ? Plot.text( result_airport.geometry.coordinates.map( ([longitude, latitude], i) => new Object({ longitude, latitude, code: result_airport.properties.points[i] ?? "" }) ), { x: "longitude", y: "latitude", text: "code", dy: -8, fontSize: 14, halo: true } ) : null ] })31:T458,## Airways and procedures **Airways** are predefined routes that structure air traffic between navigation points. They connect fixes and navaids to create a network used for en-route navigation. Together, these routes form the structured paths used by aircraft during instrument flight. ### ATS routes Air Traffic Service routes (ATS routes) are named en-route corridors used in IFR flight planning. They connect navigation points (fixes and navaids) and define structured paths that aircraft can follow between terminal areas. Typical route families include: - **Upper ATS routes** (e.g. `UN869`, `L888`) used at higher flight levels - **Lower ATS routes** used at lower levels and regional flows When resolving an ATS route, the result is usually a continuous geometry plus ordered metadata: - the route identifier (name) - the ordered list of points defining the route - source and variant information (when applicable) Here, `resolver.resolve({ airway: "..." })` returns one representative geometry for display, while `resolver.collections.airways(...)` can be used to explore larger sets of routes.`32:T40a,**Airway L888** is a very specific long-haul route often nicknamed the “Silk Road airway”. It runs across Western China and Central Asia, forming one of the most direct corridors between Southeast Asia (e.g. Hong Kong, Guangdong) and Europe. Its most distinctive feature is that it crosses the Himalayan region, making it one of the highest and most terrain-constrained airways in the world. Because of this, it is widely used on Europe to Southern China flows, as it significantly shortens distance compared to southern alternatives. Operationally, L888 is heavily constrained: the airway has a fixed corridor width of about 56 km and requires detailed escape route planning due to surrounding high terrain; predefined diversion paths lead to airports such as Urumqi, Chengdu, Kunming, Kashi, and Almaty. In abnormal situations (engine failure or depressurization), crews must follow these published escape routes to descend safely, which is why approval to use L888 requires demonstrating terrain-escape capability in advance.33:T55d,{ const container = yield htl.html`

`; const map = L.map(container, { scrollWheelZoom: false }); invalidation.then(() => map.remove()); const layer = L.geoJSON(l888_airway).addTo(map); const points = new Object({ type: "FeatureCollection", features: l888_airway.geometry.coordinates.map((c, i) => ({ type: "Feature", geometry: { type: "Point", coordinates: c }, properties: { ident: l888_airway.properties.points[i], airway: l888_airway.properties.name, source: l888_airway.properties.source } })) }); L.geoJSON(points, { pointToLayer(feature, latlng) { const ident = feature?.properties?.ident ?? "UNK"; const marker = L.circleMarker(latlng, { radius: 4, weight: 1, color: "#222", fillColor: "#ff8c00", fillOpacity: 0.9 }); marker.bindTooltip(String(ident), { permanent: true, direction: "right", offset: [10, -6], className: "airway-point-label" }); return marker; } }).addTo(map); map.fitBounds(layer.getBounds(), { maxZoom: 9 }); L.tileLayer("https://{s}.tile.openstreetmap.org/{z}/{x}/{y}.png", { attribution: "© OpenStreetMap contributors" }).addTo(map); }34:T5ec, Resolving a Field 15 route typically involves the following steps: 1. **Tokenization** The route string is split into individual elements (fixes, airways, `DCT`, procedures, etc.). 2. **Waypoint resolution** Each named point is matched with a navigation dataset to retrieve its coordinates and metadata. 3. **Airway expansion** When an airway appears between two points, the intermediate fixes belonging to that airway segment must be inserted. 4. **Direct segments (`DCT`)** When no airway is specified, the route corresponds to a direct segment between two navigation points. 5. **Procedure handling** When present, SID and STAR procedures connect the airport to the en-route airway network. The result is a continuous sequence of geographic segments that can be used for visualization, analysis, or trajectory processing. ### Common difficulties Resolving Field 15 routes can be challenging for several reasons: - some waypoint names are **not globally unique** - airway segments must be **validated between specific endpoints** - routes may mix **direct segments and airway segments** - procedures may introduce **additional intermediate waypoints** The library provides utilities to automatically resolve these routes and reconstruct the corresponding navigation path. ### Format and tokenization The first step in the resolution is to be able to match each token to a particular semantics, with speed and altitude modifiers, airway, waypoint or `DCT` (direct) identifiers.35:T6e7,{ const container = yield htl.html`

`; const map = L.map(container, { scrollWheelZoom: false }); invalidation.then(() => map.remove()); const layer = L.geoJSON(transatlantic, { style: (feature) => { const t = feature?.properties?.segment_type; const isDashed = t === "unresolved" || t === "NAT"; return { color: isDashed ? "#000" : "#1f77b4", weight: isDashed ? 0.5 : 2, dashArray: isDashed ? "8 6" : null }; }, onEachFeature: (feature, leafletLayer) => { const t = feature?.properties?.segment_type; const isDashed = t === "unresolved" || t === "NAT"; if (!isDashed) return; const label = `${feature?.properties?.name} (${feature?.properties?.segment_type})`; leafletLayer.bindTooltip(String(label), { sticky: true, permanent: true, direction: "top", opacity: 0.95 }); } }).addTo(map); L.geoJSON(await resolver.extractRoutePointsAsGeoJSON(transatlantic), { pointToLayer(feature, latlng) { const ident = feature?.properties?.ident ?? "UNK"; const marker = L.circleMarker(latlng, { radius: 4, weight: 1, color: "#222", fillColor: "#ff8c00", fillOpacity: 0.9 }); marker.bindTooltip(String(ident), { permanent: true, direction: "right", offset: [10, -6], className: "airway-point-label" }); return marker; } }).addTo(map); map.fitBounds(layer.getBounds(), { maxZoom: 9 }); L.tileLayer("https://{s}.tile.openstreetmap.org/{z}/{x}/{y}.png", { attribution: "© OpenStreetMap contributors" }).addTo(map); }36:[{"id":"a4f0c6bc8c28bf890997ae7abb5a4dece65ef5e74596b07a307c9d589f860428b582cb1341cafaaa5b7cddf6d03fef257f2ecefe3278262d56df2ba7d58a9a52","href":"https://static.observableusercontent.com/files/a4f0c6bc8c28bf890997ae7abb5a4dece65ef5e74596b07a307c9d589f860428b582cb1341cafaaa5b7cddf6d03fef257f2ecefe3278262d56df2ba7d58a9a52","name":"airac_2111.zip","type":"application/zip","lastModified":1772447084305.153,"size":18393270},{"id":"9956639b6d40b919311b1d00874ee4ebcc507d8949ad53b361ea038134fbd64cf144a442a72d1f230d165d5a22ea57bbeb3333f83f84687291526d25626bec31","href":"https://static.observableusercontent.com/files/9956639b6d40b919311b1d00874ee4ebcc507d8949ad53b361ea038134fbd64cf144a442a72d1f230d165d5a22ea57bbeb3333f83f84687291526d25626bec31","name":"leaflet_helper.png","type":"image/png","lastModified":1773668599943.619,"size":22857},{"id":"c2152de259df8c0c87ebae6c1e0f1b9b5bd558bff6bee0669e663dbcff8c608bbcc766274e05ab6f500272a3ab0e2c855ce37d4c9a88950f46f204ac84e0d4d5","href":"https://static.observableusercontent.com/files/c2152de259df8c0c87ebae6c1e0f1b9b5bd558bff6bee0669e663dbcff8c608bbcc766274e05ab6f500272a3ab0e2c855ce37d4c9a88950f46f204ac84e0d4d5","name":"airports.json","type":"application/json","lastModified":1773676816522.14,"size":851073}] 2e:{"title":"Navigation data","cells":[{"id":0,"value":"# Navigation data\n\nAircraft navigation relies on a large set of infrastructures and datasets. \nThese are managed by national aviation authorities, and while much of the data is public, it is often distributed across many sources and formats. Building a consistent and up-to-date dataset can therefore be challenging.\n\nThis page focuses on three main categories of navigation data:\n\n- **Airports** – locations where aircraft take off and land, including runways and operational metadata.\n- **Navigation points** – radio navigation aids (VOR, NDB, DME, etc.) and **fixes**, which are named geographic coordinates used in flight procedures.\n- **Airways and procedures** – structured routes used by aircraft, including **ATS routes**, **SID** (Standard Instrument Departure) and **STAR** (Standard Terminal Arrival Route) procedures.\n\nAirspace structures and classifications are covered on a separate page.\n","pinned":false,"hidden":false,"mode":"md"},{"id":500,"value":"toc(\"h2,h3\")","pinned":false,"hidden":false,"mode":"ojs"},{"id":503,"value":"## Airports\n\nAn **airport** is a location where aircraft take off and land. \nIn navigation datasets, airports are usually identified by standardized codes (ICAO or IATA) and include metadata such as:\n\n- geographic coordinates\n- runway information\n- elevation\n- communication frequencies\n\nAirports are also the starting and ending points for most instrument procedures such as SID and STAR.","pinned":false,"hidden":false,"mode":"md"},{"id":70,"value":"viewof airport_code_input = Inputs.text({\n label: \"Code or name\",\n value: \"EHAM\"\n})","pinned":false,"hidden":false,"mode":"ojs"},{"id":545,"value":"result_airport = resolver.resolve({ airport: airport_code })","pinned":true,"hidden":false,"mode":"ojs"},{"id":550,"value":"The resolution of the search always returns a geography `Feature`. This presents a notable advantage in Observable notebooks, that is the automatic inclusion to Leaflet widgets.","pinned":false,"hidden":false,"mode":"md"},{"id":568,"value":"FileAttachment(\"leaflet_helper.png\").image()","pinned":false,"hidden":false,"mode":"ojs"},{"id":572,"value":"{\n const container = yield htl.html`

`;\n const map = L.map(container, { scrollWheelZoom: false });\n const layer = L.geoJSON(result_airport).addTo(map);\n invalidation.then(() => map.remove());\n map.fitBounds(layer.getBounds(), { maxZoom: 9 });\n L.tileLayer(\"https://{s}.tile.openstreetmap.org/{z}/{x}/{y}.png\", {\n attribution:\n \"© OpenStreetMap contributors\"\n }).addTo(map);\n}","pinned":false,"hidden":false,"mode":"ojs"},{"id":562,"value":"The more natural metadata is available in the `properties` field.","pinned":false,"hidden":false,"mode":"md"},{"id":556,"value":"result_airport.properties","pinned":true,"hidden":false,"mode":"ojs"},{"id":1211,"value":"Queries can run with fuzzy finding:","pinned":false,"hidden":false,"mode":"md"},{"id":1043,"value":"resolver.resolve({ airport: \"Kansai\" }).then((f) => f.properties)","pinned":true,"hidden":false,"mode":"ojs"},{"id":798,"value":"If the data is not available in the first source, it tries the second one, and so on. The resolution source is available under `source`.","pinned":false,"hidden":false,"mode":"md"},{"id":795,"value":"resolver.resolve({ airport: \"LFCX\" }).then((a) => a.properties)","pinned":true,"hidden":false,"mode":"ojs"},{"id":587,"value":"We can access all the information as well:","pinned":false,"hidden":false,"mode":"md"},{"id":1092,"value":"all_airports = resolver.collections\n .airports({ source: \"fr24\" })\n .then((data) => data.map((feature) => feature.properties))","pinned":true,"hidden":false,"mode":"ojs"},{"id":579,"value":"all_airports","pinned":false,"hidden":false,"mode":"ojs"},{"id":647,"value":"$30","pinned":false,"hidden":false,"mode":"ojs"},{"id":514,"value":"### Infrastructure data (from OpenStreetMap)\n\nIn addition to accessible aviation datasets, airport surface infrastructure can also be extracted directly from OpenStreetMap through Overpass queries.\n\nHere we query the OSM area matching the airport ICAO code, then convert the response to GeoJSON for direct use in Plot and Leaflet. The query layer is integrated in `traffic.js` via `t.data.osm.fetchAirportOsmFeatures()`, with configurable tag filters (for example `aeroway=*` today). Because Overpass can be rate-limited, results are cached by ICAO (`memory` + `localStorage`) to minimize repeated requests and keep notebooks responsive.","pinned":false,"hidden":false,"mode":"md"},{"id":1587,"value":"osm_airport = {\n const icao = result_airport?.properties?.icao;\n if (!icao) return { type: \"FeatureCollection\", features: [] };\n try {\n return await t.data.osm.fetchAirportOsmFeatures({\n icao,\n tags: { aeroway: true },\n cache: true,\n cacheStorage: \"both\", // memory + localStorage\n cacheTtlMs: 24 * 60 * 60 * 1000\n });\n } catch (err) {\n return {\n type: \"FeatureCollection\",\n features: [],\n error: String(err?.message ?? err)\n };\n }\n}","pinned":true,"hidden":false,"mode":"ojs"},{"id":1627,"value":"Then we select here a subset of the downloaded data for plotting below.","pinned":false,"hidden":false,"mode":"md"},{"id":1488,"value":"osm_subset = {\n const wanted_subset = new Set([\n \"parking_position\",\n \"apron\",\n \"taxiway\",\n \"runway\",\n \"terminal\"\n ]);\n\n return {\n type: \"FeatureCollection\",\n features: osm_airport.features.filter((f) =>\n wanted_subset.has(f?.properties?.aeroway)\n )\n };\n}","pinned":true,"hidden":false,"mode":"ojs"},{"id":1634,"value":"You can try more airports here:","pinned":false,"hidden":false,"mode":"md"},{"id":1629,"value":"Inputs.bind(Inputs.text({ label: \"Code or name\" }), viewof airport_code_input)","pinned":false,"hidden":false,"mode":"ojs"},{"id":1516,"value":"Plot.plot({\n width: width * 0.6,\n height: 500,\n color: { scheme: \"tableau10\", legend: true },\n title: `${result_airport.properties.name}`,\n projection: {\n type: \"mercator\",\n domain: osm_subset, // auto center + auto scale\n inset: 20\n },\n marks: [\n Plot.geo(osm_subset, {\n stroke: \"aeroway\",\n strokeWidth: (f) => (f.properties.aeroway === \"runway\" ? 5 : 1),\n fill: \"aeroway\",\n fillOpacity: (d) => {\n const a = d.properties?.aeroway;\n const byType = new Map([\n [\"terminal\", 1],\n [\"apron\", 0.2]\n ]);\n return byType.get(a) ?? 0;\n }\n })\n ]\n})","pinned":true,"hidden":false,"mode":"ojs"},{"id":506,"value":"## Navigation points\n\nAircraft navigation relies on a network of reference points used to define routes and procedures. These points fall into two main categories.\n\n**Navaids** are radio navigation aids that transmit signals allowing aircraft to determine their position or bearing. Common examples include:\n\n- **VOR** – VHF Omnidirectional Range\n- **NDB** – Non-Directional Beacon\n- **DME** – Distance Measuring Equipment\n\n**Fixes** are named geographic coordinates without any associated radio signal. They are typically defined by latitude/longitude or by intersections of navigation signals.\n\nBoth navaids and fixes are commonly used as waypoints in flight routes and procedures.","pinned":false,"hidden":false,"mode":"md"},{"id":835,"value":"myVor = resolver.resolve({ navaid: \"TOU\" })","pinned":true,"hidden":false,"mode":"ojs"},{"id":1029,"value":"myVor.properties","pinned":true,"hidden":false,"mode":"ojs"},{"id":855,"value":"{\n const container = yield htl.html`

`;\n const map = L.map(container, { scrollWheelZoom: false });\n invalidation.then(() => map.remove());\n const layer = L.geoJSON(myVor, {\n onEachFeature(feature, markerLayer) {\n markerLayer.bindPopup(\n `

\n ${feature.properties.ident} (${\n feature.properties.frequency\n } MHz) \n
${feature.properties.name\n .toLowerCase()\n .replace(\"vor\", \"VOR\")\n .replace(\"dme\", \"DME\")\n .replace(/\\b\\w/g, (c) => c.toUpperCase())}\n

`\n );\n }\n }).addTo(map);\n map.whenReady(() => layer.eachLayer((l) => l.openPopup()));\n map.fitBounds(layer.getBounds(), { maxZoom: 9 });\n L.tileLayer(\"https://{s}.tile.openstreetmap.org/{z}/{x}/{y}.png\", {\n attribution:\n \"© OpenStreetMap contributors\"\n }).addTo(map);\n}","pinned":false,"hidden":false,"mode":"ojs"},{"id":899,"value":"Sometimes the resolution doesn't work as expect as several navigational aids may share the same identifier.","pinned":false,"hidden":false,"mode":"md"},{"id":897,"value":"resolver.resolve({ navaid: \"KLO\" }).then((f) => f.properties)","pinned":true,"hidden":false,"mode":"ojs"},{"id":901,"value":"The `near` parameter helps to select the navigational aid we expect. It accepts a string or a feature object.","pinned":false,"hidden":false,"mode":"md"},{"id":1158,"value":"resolver\n .resolve({\n navaid: \"KLO\",\n near: \"Switzerland\"\n // near: resolver.resolve({ airport: \"Zurich\" }) // this works too!\n })\n .then((f) => f.properties)","pinned":true,"hidden":false,"mode":"ojs"},{"id":1293,"value":"We can also specify the source (or sources) from where we want to search for the specific entry:","pinned":false,"hidden":false,"mode":"md"},{"id":1204,"value":"resolver\n .resolve({\n navaid: \"BAE\",\n source: \"xplane\"\n })\n .then((f) => f.properties)","pinned":true,"hidden":false,"mode":"ojs"},{"id":905,"value":"resolver\n .resolve({\n navaid: \"BAE\",\n source: [\"arcgis\", \"xplane\"]\n })\n .then((f) => f.properties)","pinned":true,"hidden":false,"mode":"ojs"},{"id":509,"value":"$31","pinned":false,"hidden":false,"mode":"md"},{"id":1222,"value":"un869 = resolver.resolve({ airway: \"UN869\" })","pinned":true,"hidden":false,"mode":"ojs"},{"id":997,"value":"{\n const container = yield htl.html`

`;\n const map = L.map(container, { scrollWheelZoom: false });\n invalidation.then(() => map.remove());\n const layer = L.geoJSON(un869).addTo(map);\n\n map.fitBounds(layer.getBounds(), { maxZoom: 9 });\n L.tileLayer(\"https://{s}.tile.openstreetmap.org/{z}/{x}/{y}.png\", {\n attribution:\n \"© OpenStreetMap contributors\"\n }).addTo(map);\n}","pinned":true,"hidden":false,"mode":"ojs"},{"id":977,"value":"$32","pinned":false,"hidden":false,"mode":"md"},{"id":962,"value":"l888_airway = resolver.resolve({ airway: \"L888\" })","pinned":true,"hidden":false,"mode":"ojs"},{"id":970,"value":"$33","pinned":false,"hidden":false,"mode":"ojs"},{"id":511,"value":"### SID and STAR\n\nIn terminal areas, more specific procedures are defined:\n\n- **SID (Standard Instrument Departure)** – routes guiding aircraft from an airport to the en-route airway network.\n- **STAR (Standard Terminal Arrival Route)** – routes guiding aircraft from the airway network toward an airport for approach.\n\nYou can query procedures directly with:\n- `resolver.resolve({ SID: \"FISTO5A\", airport: \"LFBO\" })`\n- `resolver.resolve({ STAR: \"KEPER9E\", airport: \"LFPG\" })`\n\nThis avoids ambiguity with airport lookups and returns the matching procedure geometry when available in the selected sources.`\n","pinned":false,"hidden":false,"mode":"md"},{"id":955,"value":"keper9e = resolver.resolve({ STAR: \"KEPER9E\", airport: \"LFPG\" })","pinned":true,"hidden":false,"mode":"ojs"},{"id":958,"value":"{\n const container = yield htl.html`

`;\n const map = L.map(container, { scrollWheelZoom: false });\n invalidation.then(() => map.remove());\n const layer = L.geoJSON(keper9e).addTo(map);\n map.fitBounds(layer.getBounds(), { maxZoom: 9 });\n L.tileLayer(\"https://{s}.tile.openstreetmap.org/{z}/{x}/{y}.png\", {\n attribution:\n \"© OpenStreetMap contributors\"\n }).addTo(map);\n}","pinned":false,"hidden":false,"mode":"ojs"},{"id":1375,"value":"We can also use the collections to query all procedures for an airport. \n\nFor example, here we can map the arrival procedures to both Paris airports.","pinned":false,"hidden":false,"mode":"md"},{"id":934,"value":"lfpg_stars = new Object({\n type: \"FeatureCollection\",\n features: await resolver.collections.airways({\n type: \"STAR\",\n query: \"LFPG\"\n })\n})","pinned":false,"hidden":false,"mode":"ojs"},{"id":1322,"value":"lfpo_stars = new Object({\n type: \"FeatureCollection\",\n features: await resolver.collections.airways({\n type: \"STAR\",\n query: \"LFPO\"\n })\n})","pinned":false,"hidden":false,"mode":"ojs"},{"id":1343,"value":"lfpg = resolver.resolve({ airport: \"LFPG\" })","pinned":false,"hidden":false,"mode":"ojs"},{"id":1340,"value":"lfpo = resolver.resolve({ airport: \"LFPO\" })","pinned":false,"hidden":false,"mode":"ojs"},{"id":1269,"value":"Plot.plot({\n width,\n height,\n color: { scheme: \"tableau10\", legend: true },\n\n projection: d3\n .geoOrthographic()\n .scale((20 * width) / 1.5 / Math.PI)\n .rotate(d3.geoCentroid(lfpg).map((x) => -1 * x))\n .translate([(0.7 * width) / 2, height / 2]),\n marks: [\n Plot.geo({ type: \"Sphere\" }, { fill: \"white\" }),\n Plot.geo(graticule, { stroke: \"#aaa\", strokeWidth: 0.25 }),\n Plot.geo(land, { stroke: \"#333\", fill: \"#ced4da\" }),\n Plot.geo(countries, { stroke: \"#fff\", fill: \"#ced4da\" }),\n Plot.geo(lfpg, { fill: \"icao\" }),\n Plot.geo(lfpg_stars, { stroke: \"airport\" }),\n Plot.geo(lfpo, { fill: \"icao\" }),\n Plot.geo(lfpo_stars, { stroke: \"airport\" })\n ]\n})","pinned":false,"hidden":false,"mode":"ojs"},{"id":530,"value":"## Flight plan routes (Field 15)\n\nIn ICAO flight plans, **Field 15** contains the planned route of the aircraft. \nThis route is expressed as a sequence of navigation elements such as:\n\n- fixes\n- navaids\n- airways\n- procedure names\n\nFor example, a route may combine direct segments and airways:\n","pinned":false,"hidden":false,"mode":"md"},{"id":615,"value":"field15 = \"N0430F300 FISTO6B FISTO DCT POI DCT PEPAX UT182 NIMER/N0401F240 UT182 KEPER KEPER9E\"","pinned":true,"hidden":false,"mode":"ojs"},{"id":613,"value":"$34","pinned":false,"hidden":false,"mode":"md"},{"id":618,"value":"t.data.parseField15(field15)","pinned":true,"hidden":false,"mode":"ojs"},{"id":534,"value":"### Field15 Resolution","pinned":false,"hidden":false,"mode":"md"},{"id":634,"value":"The next natural step is to match waypoints to the most probable candidate in the databases we can have access to, then split airways to the segment between the waypoints and connect the dots.","pinned":false,"hidden":false,"mode":"md"},{"id":621,"value":"flight_plan = resolver.enrichRouteAsGeoJSON(field15)","pinned":true,"hidden":false,"mode":"ojs"},{"id":624,"value":"{\n const container = yield htl.html`

`;\n const map = L.map(container, { scrollWheelZoom: false });\n invalidation.then(() => map.remove());\n const layer = L.geoJSON(flight_plan).addTo(map);\n\n L.geoJSON(await resolver.extractRoutePointsAsGeoJSON(flight_plan), {\n pointToLayer(feature, latlng) {\n const ident = feature?.properties?.ident ?? \"UNK\";\n const marker = L.circleMarker(latlng, {\n radius: 4,\n weight: 1,\n color: \"#222\",\n fillColor: \"#ff8c00\",\n fillOpacity: 0.9\n });\n marker.bindTooltip(String(ident), {\n permanent: true,\n direction: \"right\",\n offset: [10, -6],\n className: \"airway-point-label\"\n });\n return marker;\n }\n }).addTo(map);\n map.fitBounds(layer.getBounds(), { maxZoom: 6 });\n L.tileLayer(\"https://{s}.tile.openstreetmap.org/{z}/{x}/{y}.png\", {\n attribution:\n \"© OpenStreetMap contributors\"\n }).addTo(map);\n}","pinned":false,"hidden":false,"mode":"ojs"},{"id":650,"value":"In this final example, we cannot resolve, with the currently available sources, the SID `ELCOB6B`, the STAR `ROCKT2` (the route is displayed in between), one ATS route (`N756C`), one point (`ANATI`) and the `NAT` (North Atlantic track) token for that day, which is transformed into a straight line.","pinned":false,"hidden":false,"mode":"md"},{"id":653,"value":"nat_field15 = \"N0490F360 ELCOB6B ELCOB UT300 SENLO UN502 JSY DCT LIZAD DCT MOPAT DCT LUNIG DCT MOMIN DCT PIKIL/M084F380 NATD HOIST/N0490F380 N756C ANATI/N0441F340 DCT MIVAX DCT OBTEK DCT XORLO ROCKT2\"","pinned":true,"hidden":false,"mode":"ojs"},{"id":655,"value":"transatlantic = resolver.enrichRouteAsGeoJSON(nat_field15)","pinned":true,"hidden":false,"mode":"ojs"},{"id":657,"value":"$35","pinned":false,"hidden":false,"mode":"ojs"},{"id":81,"value":"height = 600","pinned":true,"hidden":false,"mode":"ojs"},{"id":84,"value":"scale = 6","pinned":true,"hidden":false,"mode":"ojs"},{"id":498,"value":"import { toc } from \"@nebrius/indented-toc\"","pinned":true,"hidden":false,"mode":"ojs"},{"id":449,"value":"import { t, countries, land, graticule } from \"@xoolive/traffic-js\"","pinned":true,"hidden":false,"mode":"ojs"},{"id":1032,"value":"/*t = {\n // For local development\n const t = await require(\"http://localhost:8001/traffic.js\");\n t.env.setTrafficBaseUrl(\"http://localhost:8001/traffic.js\");\n t.env.setThrustWasm({\n thrustModuleUrl: \"http://localhost:8002/web/thrust_wasm.js\"\n });\n t.env.setEnv({ Inputs, html, d3, Plot });\n return t;\n}*/","pinned":true,"hidden":false,"mode":"ojs"},{"id":389,"value":"resolver = new t.data.Resolver()\n .withSource(\"xplane\", await t.data.xplane.createXplaneResolver()) // TODO this can be simplified .withXplane()\n .withSource(\n \"fr24\",\n await t.data.fr24.createFr24AirportResolver({\n json: await FileAttachment(\"airports.json\").json()\n })\n )\n .withDdr(\n await t.data.eurocontrol.createEuroControlDdrResolver({\n archive: await FileAttachment(\"airac_2111.zip\").arrayBuffer()\n })\n )\n .withArcgis(await t.data.faa.createFaaArcgisResolver()) // TODO this can be simplified .withArcgis()","pinned":false,"hidden":false,"mode":"ojs"},{"id":1646,"value":"airport_code_raw = Generators.input(viewof airport_code_input)","pinned":false,"hidden":false,"mode":"ojs"},{"id":1640,"value":"airport_code = {\n const v = airport_code_raw;\n await new Promise((resolve, reject) => {\n const id = setTimeout(resolve, 500); // debounce\n invalidation.then(() => {\n clearTimeout(id); // cancel previous pending delay\n reject();\n });\n });\n return v;\n}","pinned":false,"hidden":false,"mode":"ojs"}],"files":"$W36","stdlib":"1","titling":"auto"}