# Field Operations Risk Briefing — Weather + GPS/Radio Conditions (`m_ctim/field-operations-risk-briefing`) Actor Per US location: NWS forecast and active weather alerts, plus current space-weather conditions (Kp index, GPS/HF-radio-relevant radio blackout severity, aurora latitude) in one briefing for outdoor and field operations. - **URL**: https://apify.com/m\_ctim/field-operations-risk-briefing.md - **Developed by:** [Timothy Kelvin](https://apify.com/m_ctim) (community) - **Categories:** Other - **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks - **User rating**: No ratings yet ## Pricing Pay per usage This Actor is paid per platform usage. The Actor is free to use, and you only pay for the Apify platform usage, which gets cheaper the higher subscription plan you have. Learn more: https://docs.apify.com/platform/actors/running/actors-in-store#pay-per-usage ## What's an Apify Actor? Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows. In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours, and optionally produces a well-defined JSON output, datasets with results, or files in key-value store. In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server. Actors are written with capital "A". ## How to integrate an Actor? If asked about integration, you help developers integrate Actors into their projects. You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready. The best way to integrate Actors is as follows. - **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use). - **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`. - **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`. - **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`. - **Any other language** — the [REST API](https://docs.apify.com/api/v2.md). For usage examples, see the [API](#api) section below. For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt). # README ## Field Operations Risk Briefing — Weather + GPS/Radio Conditions Give it US locations. Get back the NWS forecast and active weather alerts **plus** current space-weather conditions — Kp index, GPS/HF-radio-relevant radio blackout severity, and aurora-visible latitude — in one briefing per location, instead of checking weather.gov and spaceweather-style sites separately. Built for anyone whose fieldwork depends on both what's happening on the ground and overhead: precision-ag/survey teams relying on GPS accuracy, HF radio operators (ham, aviation, remote utility crews), and drone/UAV operations planning around both storms and radio blackouts. ### Input ```json { "locations": [ { "label": "Austin, TX", "latitude": 30.2672, "longitude": -97.7431 } ], "forecastPeriods": 4 } ``` | Field | Type | Description | |---|---|---| | `locations` | array | `{ "label": "optional name", "latitude": ..., "longitude": ... }`. US locations only — NWS coverage. | | `forecastPeriods` | integer (default `4`) | How many ~12-hour NWS forecast periods to include (4 ≈ next 2 days). | ### Output One record per location: ```json { "label": "Fairbanks, AK", "latitude": 64.8378, "longitude": -147.7164, "weather": { "city": "Fairbanks", "state": "AK", "timeZone": "America/Anchorage", "forecastPeriods": [{ "name": "Tonight", "temperature": 51, "shortForecast": "Isolated Rain Showers", "...": "..." }], "activeAlerts": [] }, "spaceWeather": { "kpIndex": 1.67, "auroraVisibleLatitude": 62.4, "radioBlackout": { "xrayFlux": 3.74e-7, "rScale": "R0", "rScaleDescription": "No radio blackout" }, "observedAt": "2026-08-08T03:00:00" }, "briefedAt": "2026-08-08T07:43:50.308Z" } ``` `spaceWeather` is the same snapshot on every location in a run — it's not a per-location measurement, current conditions are shared globally. Compare it against a location's latitude yourself (as above: Fairbanks at 64.8°N is above the 62.4° aurora viewline, so aurora is plausible there tonight). ### How it works Two official, keyless US-government JSON APIs, no scraping, no proxy: - Weather/alerts: `api.weather.gov` (National Weather Service) - Space weather: `services.swpc.noaa.gov` (NOAA Space Weather Prediction Center) — Kp index and the `0.1-0.8nm` GOES X-ray channel, classified into NOAA's own published R-scale Space weather is fetched once per run and attached to every location record — it's identical for everyone regardless of location, so there's no reason to refetch it per location. ### Related products Need just one signal instead of the combined briefing? - [US Weather Tracker](https://github.com/timmKal01/us-weather-tracker) — NWS forecast/alerts only, per location - [Space Weather Alert](https://github.com/timmKal01/space-weather-alert) — Kp/radio-blackout/aurora/NOAA alerts only, global snapshot ### Pricing note Billed per **location briefed** — the shared space-weather fetch doesn't add cost per location, so briefing 10 locations costs the same as briefing 1 for the space-weather portion. # Actor input Schema ## `locations` (type: `array`): US locations to brief. `{ "label": "optional name", "latitude": 30.2672, "longitude": -97.7431 }` ## `forecastPeriods` (type: `integer`): How many ~12-hour NWS forecast periods to include per location (4 ≈ next 2 days). ## Actor input object example ```json { "locations": [ { "label": "Austin, TX", "latitude": 30.2672, "longitude": -97.7431 } ], "forecastPeriods": 4 } ``` # API You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup. ## JavaScript example ```javascript import { ApifyClient } from 'apify-client'; // Initialize the ApifyClient with your Apify API token // Replace the '' with your token const client = new ApifyClient({ token: '', }); // Prepare Actor input const input = { "locations": [ { "label": "Austin, TX", "latitude": 30.2672, "longitude": -97.7431 } ] }; // Run the Actor and wait for it to finish const run = await client.actor("m_ctim/field-operations-risk-briefing").call(input); // Fetch and print Actor results from the run's dataset (if any) console.log('Results from dataset'); console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`); const { items } = await client.dataset(run.defaultDatasetId).listItems(); items.forEach((item) => { console.dir(item); }); // 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs ``` ## Python example ```python from apify_client import ApifyClient # Initialize the ApifyClient with your Apify API token # Replace '' with your token. client = ApifyClient("") # Prepare the Actor input run_input = { "locations": [{ "label": "Austin, TX", "latitude": 30.2672, "longitude": -97.7431, }] } # Run the Actor and wait for it to finish run = client.actor("m_ctim/field-operations-risk-briefing").call(run_input=run_input) # Fetch and print Actor results from the run's dataset (if there are any) print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}") for item in client.dataset(run.default_dataset_id).iterate_items(): print(item) # 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start ``` ## CLI example ```bash echo '{ "locations": [ { "label": "Austin, TX", "latitude": 30.2672, "longitude": -97.7431 } ] }' | apify call m_ctim/field-operations-risk-briefing --silent --output-dataset ``` ## MCP server setup ```json { "mcpServers": { "apify": { "type": "http", "url": "https://mcp.apify.com/?tools=fetch-actor-details,m_ctim/field-operations-risk-briefing" } } } ``` The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer ` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations). ## OpenAPI specification Download the OpenAPI definition: https://api.apify.com/v2/actors/dLw38jBnMo1B49gjN/builds/y9t4AOfiNNLWVf91o/openapi.json