"See bottom for general descriptive information. --- # Releases ## [1.9.0] 2025-12-17 ### Add parameterization to auth requests * authorization URL now defined by variable set for environment ## [1.7.3] 2025-06-05 ### 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.5.0] 2025-03-25 ### Add spatial filter capabilities ### Add capability to specify multiple flight levels ## [1.4.1] 2025-03-18 ### Fix access parameter for winds aloft ## [1.4.0] 2025-02-26 ### Add winds aloft API --- # Winds aloft API information _last updated for v1.5.0_ See documentation for complete request parameter definitions. Each object in winds aloft API response is for one grid point (lat/lon location) at one flight level at one time. Thus it can require many objects to cover a large spatial area. The data fields provide temperature, wind speed, and wind direction values. Response data is in GeoJSON format. See Postman collection for description of properties in response feature objects. ## 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. "