"See bottom for general descriptive information. --- # Releases ## [1.10.2] 2026-06-24 ### Put constraints on QVA flight levels * flightLevel must be one of: 50, 100, 150, 200, 250, 300, 350, 400, 450, 500, 550, 600 (top-of-range values, e.g. 350 for the FL300-FL350 range) ## [1.10.1] 2026-06-04 ### Correct endpoint name for active volcanoes for consistency with other endpoints * Made `activeVolcanoQvas` ## [1.10.0] 2026-05-07 ### Initial addition of QVA (Quantitative Volcanic Ash) endpoints * ash cloud (IWXXM parsed) * spatial filters * time filters (fromDateTime, untilDateTime, insertedAfter, insertedThrough) * volcano filter (volcanoid) * event type filter (OPERATIONAL, EXERCISE, TEST, ALL; defaults to OPERATIONAL) * intersection parameter * deterministic ash concentration polygons * spatial filters * time filters (fromDateTime, untilDateTime, insertedAfter, insertedThrough) * model run time filter (modelDateTime) * flight level, minimum concentration, and volcano filters * event type filter and intersection parameters * geometry always returned as MultiPolygon for consistent GeoJSON * latest run selected per volcano (not per VAAC) to support multi-volcano scenarios * probabilistic ash concentration polygons * spatial filters * time filters (fromDateTime, untilDateTime, insertedAfter, insertedThrough) * model run time filter (modelDateTime) * flight level, minimum probability, minimum threshold concentration, and volcano filters * event type filter and intersection parameters * geometry always returned as MultiPolygon for consistent GeoJSON * latest run selected per volcano (not per VAAC) to support multi-volcano scenarios * active volcanoes * returns volcanoes that have at least one IWXXM ash cloud with validdatetime >= NOW() * GeoJSON FeatureCollection with Point geometry at volcano location * fields: volcanoid, volcanoname, iavceinumber, elevation_m, vaacname, vaacdesignator, latestissuetime, latestmodelrundatetime, hasiwxxm, hasdeterministic, hasprobabilistic, eventtype * vaacid filter matches against both vaacdesignator (e.g. EGRR) and vaacname (e.g. LONDON) * event type filter (OPERATIONAL, EXERCISE, TEST, ALL; defaults to OPERATIONAL) * use this endpoint to discover valid volcanoid values for the other QVA endpoints ### Increase Envoy proxy timeout from 15 seconds to 60 seconds * Some EFH queries can exceed the previous 15-second limit * Envoy timeout updated to 60 seconds to accommodate longer-running requests ## [1.9.0] 2025-12-17 ### Initial addition of SWPC NOAA Scales space weather endpoints * space weather * raw data as directly provided by SWPC * default provides very latest saved * can specify recent timeframe for data saved then * parsed data with descriptive details * default provides very latest saved for all event types and periods * can specify recent timeframe for data saved then * can specify particular event types and periods * explanation providing information about possible data value ### Add parameterization to auth requests * authorization URL now defined by variable set for environment ## [1.7.4] 2025-07-01 ### Initial addition of jet stream axis endpoint * jet stream axis * spatial filters * speed and altitude filters ## [1.7.3] 2025-06-05 ### Define default model run selection to be from latest complete for data type * determines and uses model run time with full set of source files for requested data type * only matters during period when new model run is being ingested but a data for it not yet available * provide parameters to override default * can select specific model run time * can set to allow to pull from not-yet-complete partial model run ### Add constraints to temporal parameter values * make request fail if parameter is set to something that would obviously not correspond to available data * are sanity checks, as still possible to specify time values for which data cannot be provided ## [1.7.2] 2025-05-15 ### Enhanced Flight Hazards (EFH) turbulence/icing updates * Turbulence * change to return unsmoothed data * add consolidate parameter * Icing * change to return unsmoothed data * add consolidate parameter ## [1.7.0] 2025-05-05 ### New Enhanced Flight Hazards (EFH) data types * Nowcast * spatial filters * minimum EDR filter * HIWC * spatial filters * minimum concentration filter ## [1.6.0] 2025-04-16 ### New Enhanced Flight Hazards (EFH) data types * thunderstorms * spatial filters * minimum vertical velocity and minimum top filters * ozone * spatial filters * concentration category filter ### Add handling for icing FL080 and fix icing docs ## [1.5.0] 2025-03-25 ### Initial addition of first Enhanced Flight Hazards (EFH) data types * turbulence * spatial filters * minimum EDR filter * icing * spatial filters * icing category filter --- # Enhanced Flight Hazards (EFH) information _last updated for v1.7.3_ See documentation for complete request parameter definitions. Response data is in GeoJSON format. See Postman collection for description of properties in response feature objects. ## Data types Requests can be made to endpoints handling the following... ### turbulence Forecasted turbulence accounts for boundary layer, mountain wave, and clear air types. Data provide Eddy Dissipation Rate (EDR) values representing the intensity of the turbulence. Forecasts are hourly for 29 flight layers and out to 36 hours in the future. ### Nowcast Rapid Update Convective forecast is updated every ten minutes. It emphasizes dynamic strong convective weather and provides a forecast for one hour ahead of the present time. Data will be for a very recent model run time, likely 10-20 minutes ago. Forecast valid timeframe is for between one hour and two hours after the model run time, so a little less than 1-2 hours ahead of the current time. ### icing Forecasted icing data provide categories to the degree of icing where expected. Four distinct forecasts are provided for four sizes of aircraft -- fixed wing small, imtermediate, and large, plus helicopters. Forecasts are hourly for 9 flight layers, except fewer for helicopters which do not operate at the higher levels, and out to 36 hours in the future. ### high ice water content (HIWC) Forecasted HIWC gives information for levels above those for which regular icing data are available. Data indicate ice crystals at notable and severe concentrations. Forecasts are hourly for 11 flight layers and out to 36 hours in the future. ### thunderstorms Forecasts for thunderstorms provide hourly spatial coverage out 36 hours in the future. Data include vertical velocity (updraft) values which correlate to degrees of turbulence and icing as well as top height to indicate vertical extent. ### ozone Forecasts for ozone provide spatial coverage out 36 hours in the future for 6-hour periods. Data indicate where cabin ozone concentrations would be expected to exceed moderate (between 0.10ppm - 0.25ppm above FL270) or high (greater than 0.25ppm above FL270) amounts. Each forecast period overlaps adjacent periods by 3 hours, which affects what data are returned in a response. A request for data valid at 16Z can be expected to include an object for the 12Z-18Z period and an object for the 15Z-21Z period. ### jet stream axis Forecasts for jet stream axis provide spatial coverage out up to 24 hours in the future for 2-hour periods. Data include the speed and altitude values for the core axes of jet streams. Because each forecast period has duration of only 2 hours requests for particular times or short periods can fail to align with available data. Valid data periods are 00-02Z, 06-08Z, 12-14Z, and 18-20Z. A request for data valid at, e.g., 1630Z will not provide a result. A particular single valid time must fall within one of those periods, or a valid timeframe must overlap with at least one of those periods. Only data from the latest model that supplies a given forecast period are available. Unlike some other data types there are not parameters available to select a particular model run time or an insert timeframe. Data from a model run should be available some time between 4 to 6 hours after the run time. For example, a 12Z model run could be able to provide its jet stream data at 1715Z and cover forecast periods of 12-14Z (in the past at that available time), 18-20Z, and the next day's 00-02Z, 06-08Z, and 12-14Z. ## Spatial filters These allows to select data within a specific area. Only one may be used per request. * Bounding box - Defines rectangular area set by furthest southwest location and furthest northeast location. * Polygon - Defines area enclosed by series of points. Response behavior is unpredictable if created shape is self-interesting other than last point matching first point. * Circle - Defines area from center point and radius. The larger the defined area, the more its shape on projected map will differ from true circle on spherical coordinates. Constraint is set to limit radius and thus circle size. Request will fail or have unpredictable response behavior if circle area crosses the antimeridian (180W/180E longitude). * Corridor - Defines area from series of points defining a (not necessarily straight) line and halfwidth that tells distance from line to encompass. Constraint is set to limit halfwidth, though line length not limited. However response behavior is unpredictable for long distances between points. Request will fail or have unpredictable response behavior if corridor area crosses the antimeridian (180W/180E longitude). ## Temporal filters These allow to select based on time-related characteristics on data. Parameters can limit responses to data valid at a particular time or within a timeframe, ingested/saved within a timeframe, and for data from forecast models corresponding to specific model run times. * valid at - Allows to specify an exact time to limit to data valid then. * from/until - Allows to set a timeframe to limit to data whose valid periods overlap at all with that timeframe. * inserted after/through - Allows to set a timeframe to limit to data ingested/saved at some time within that period. This is useful for chaining requests to continually acquire newly available data, like by setting the \"after\" time as the latest insert time seen from a previous request and the \"through\" time as the current time. * model run time - For forecasted data like enhanced flight hazards allows to specify which model run time from which to pull data. Default behavior is to take from the latest model run for which there is complete data for the requested data type. However, a specific model time or using the `allowPartialModelRun` can override that behavior to pull available data from perhaps and earlier run or a later run that has not been completely ingested yet. "