Operations Manual
A step-by-step guide to setting up and using ARIA, from downloading the file to generating your first sector-specific CAP alert descriptions.
Download and open ARIA
ARIA is a single HTML file, available in two versions. There is nothing to install. It runs in your web browser.
Go to lastlarch.com and click Download tool →. Choose one of the two versions.
| File | Size | Choose it when |
|---|---|---|
ARIA.html | About 0.3 MB | You have an internet connection each time you open ARIA. It loads its map, database and file-reading libraries from public servers when it opens. |
ARIA-offline.html | About 2 MB | You need ARIA to open without a connection, for example in the field or on a restricted network. Those libraries and the fonts are built into the file, which makes it about six times larger. |
Tools/ARIA/.Double-click the file you saved. It opens in your default web browser. Chrome, Edge, Firefox, and Safari all work. The standard version needs an internet connection to open. The offline version does not.
You will see a map on the right and a sidebar on the left. A sample dataset (European city points) is preloaded so you can test the tool immediately.
How ARIA works
ARIA is a three-step wizard. Each step builds on the last.
Load your GIS data sources, then draw or paste a polygon representing the hazard footprint. ARIA queries every active source and shows what is inside: schools, health facilities, roads, or whatever else your data contains.
Choose which layers to include, set the hazard type and severity, and connect your ARIA-Lex library and AI model. This is where ARIA grounds the output in validated language before the AI adds local specifics.
ARIA produces sector-specific <headline> and <description> blocks ready to paste into your CAP editor. Each block is tagged to show whether it came from your library or was newly generated.
Every step has a ← Back button so you can return and adjust at any time. You can change your polygon, add a source, or change the hazard settings without losing your work. The step indicators at the top show where you are and which steps are complete.
Load a locally saved file
Use this for GeoJSON files or shapefiles stored on your computer. Your data never leaves your machine.
The easiest way. Drag a .geojson, .json, or .zip (shapefile) file from your file explorer and drop it anywhere on the ARIA window. It loads instantly and appears in the sources list.
Click + Add source in the sidebar. Enter a name, select Shapefile (.zip) from the type dropdown, click File, and browse to your file. Click Add source.
A toggle switch shows it is active. The badge shows the format. If you have already drawn a polygon, the query runs automatically.
Connect an ArcGIS layer
ARIA can query ArcGIS Online FeatureServer layers directly. It also accepts web map URLs and extracts all layers automatically.
ARIA accepts three URL formats. Paste whichever you have:
| Format | Example | |
|---|---|---|
| FeatureServer | Recommended | …/FeatureServer/0 |
| FeatureServer (no index) | Auto-fixed | …/FeatureServer → ARIA appends /0 |
| Web Map Viewer URL | Auto-extracts all layers | arcgis.com/home/item.html?id=… |
ArcGIS sources are queried live when you draw a polygon. The features inside your polygon are fetched directly from the service. No data is cached locally.
Connect a WFS endpoint
WFS (Web Feature Service) is a standard used by many national spatial data infrastructures and open data portals.
A WFS URL typically looks like:https://example.com/geoserver/ows?service=WFS&version=2.0.0&typeName=layername
ARIA appends a bounding box filter derived from your polygon when querying. You do not need to add BBOX parameters yourself.
Load a GeoJSON from a URL
If your data is hosted online as a GeoJSON file, ARIA can fetch it directly.
Paste a direct URL to a .geojson or .json file, for example a GitHub raw file URL or an HDX download link.
ARIA fetches and caches the file in memory. It shows a green success message with the source name. The data is now available for polygon queries without a network request each time.
Draw a polygon on the map
Use this when you want to define the hazard footprint manually or when exploring data coverage.
Pan and zoom the map. If you have local data loaded, click ⊕ Fit map to data to jump straight to the right area.
In the top-left of the map, click the pentagon-shaped draw icon. Your cursor changes to a crosshair.
Click once for each corner of your polygon. Click the first point again (or double-click) to close the shape. The query runs automatically as soon as the polygon is closed.
Click the edit (pencil) icon in the map toolbar to drag vertices. The query re-runs automatically when you save the edit.
Paste a polygon from a warning
Use this when you have coordinates from a meteorological service, a flood model output, or any other external source. ARIA accepts three formats.
It is below the data sources list. Click into the text area.
| Format | Example |
|---|---|
| Lat/lng pairs | -1.94, 30.06One pair per line. Comma or space separated. |
| GeoJSON | {"type":"Polygon","coordinates":[[...]]}Feature, FeatureCollection, or geometry object. |
| WKT | POLYGON((30.06 -1.94, 30.14 -1.94, ...))Standard Well-Known Text format. |
ARIA draws the polygon on the map, zooms to it, and runs the query automatically.
Load ARIA-Lex
ARIA-Lex is the seed library of pre-validated early action messages. Loading it means the AI uses approved language as its foundation instead of generating everything from scratch.
Go to lastlarch.com and download ARIA-Lex.db. Save it alongside ARIA.html or in a known location.
In the top-right corner of ARIA, a small indicator says No library loaded. Click it to open the library settings panel.
Drag ARIA-Lex.db onto the drop zone, or click it to browse. The library loads in seconds. The indicator turns green and shows the message count.
.db file directly onto the main ARIA window at any time. It is sent to the library loader automatically.You need to reload it each time you open ARIA, because no data is stored between sessions. This keeps your data local and private.
Set hazard type, severity and authority level
These three settings control which library messages are retrieved and how the AI frames the output.
Hazard type
| Option | DB code | Use for |
|---|---|---|
| Cyclone / Hurricane | cy | Tropical cyclones, hurricanes, typhoons |
| Flood | fl | River flood, flash flood, urban flooding |
| Heatwave | hw | Extreme heat events |
| Wildfire | wf | Forest fire, bushfire |
| Earthquake | eq | Seismic events. No library messages yet, so all output is AI-generated. |
| Tsunami | ts | Coastal wave events |
| Cold wave / Freeze | cw | Extreme cold, frost, snowstorm |
| Disease outbreak | do | Epidemic, pandemic risk areas |
Severity
| Level | CAP urgency | Use when |
|---|---|---|
| Extreme | Immediate | Threat to life, take action now |
| Severe | Expected | Significant impact likely, prepare now |
| Moderate | Future | Impact possible, monitor and prepare |
| Minor | Future | Limited impact expected |
Authority level
| Option | Use when |
|---|---|
| Auto (infer from data) | Let the AI decide based on the scale and type of your GIS data. Good default. |
| National | Alert is being issued by a national agency, for national distribution |
| Regional / Provincial | Alert targets a province, region, or state |
| Local / Operational | Alert targets a district, municipality, or specific facilities |
| Individual / Household | Alert language is directed at members of the public |
Connect an AI model
ARIA works with any OpenAI-compatible API, including a model running on your own computer or network. You provide the API key when one is needed. It is stored only in your browser and is never sent to Last Larch.
| Preset | Provider | Get API key at |
|---|---|---|
| Claude | Anthropic | console.anthropic.com |
| GPT-4o | OpenAI | platform.openai.com/api-keys |
| Gemini | aistudio.google.com | |
| Custom | Any OpenAI-compatible API on an allowed host | Enter the endpoint URL and model name. See the note below. |
Click the preset button for your provider. The endpoint and model name fill in automatically. Paste your API key into the key field.
Select Custom and enter the endpoint URL and model name of an OpenAI-compatible API, for example OpenRouter at https://openrouter.ai/api/v1/chat/completions. For an endpoint reachable on the open internet, ARIA sends the request through its relay worker, and the worker only forwards to api.anthropic.com, api.openai.com, generativelanguage.googleapis.com and openrouter.ai. A public endpoint on any other host is refused.
Select Custom and enter the address of a model running on your own computer or local network, for example http://localhost:11434/v1/chat/completions for Ollama. ARIA recognises addresses like localhost, 127.0.0.1 and private network ranges (10.x, 172.16–31.x, 192.168.x) and calls them directly from your browser. The request never reaches the relay worker or the open internet. The field below the endpoint says which mode is active.
| Server | How to allow it |
|---|---|
| Ollama | Set the environment variable OLLAMA_ORIGINS=* before starting it, for example OLLAMA_ORIGINS=* ollama serve. Set it permanently in your system's environment variables to avoid repeating this. |
| LM Studio | In the local server tab, turn on Enable CORS before starting the server. |
| llama.cpp server, text-generation-webui, and similar | Start the server with its CORS or --allow-origin flag set to allow all origins, or place a reverse proxy in front of it that adds an Access-Control-Allow-Origin: * header. |
Generate and read the output
Click Generate alert descriptions → and ARIA does the rest. You can also use Library-only mode to skip the AI entirely.
If you have ARIA-Lex loaded and want to work on an air-gapped machine (use the offline version) or without any AI API, tick the Library only checkbox next to the Generate button. ARIA looks up matching pre-validated messages by hazard, severity and authority level and renders them directly. Library only mode makes no network calls. With the offline version it works with no internet connection at all. With the standard version, a connection is needed only to open the tool.
ARIA first queries your library, then calls the AI. The loading message tells you what is happening, for example: "Grounding against 24 library messages then contextualising…"
Every sector card has a tag in the top-left telling you where the language came from:
On Library and Contextualised cards, a green panel shows the exact library messages the AI used as its source. This lets you verify the AI stayed true to your validated language.
Copy and export descriptions
Once you have query results in Step 1, a green ↓ CSV button appears in the results panel. Click it to download a flat CSV of every feature found across all layers, with source name, geometry type, coordinates, and all properties. Use this file to confirm what the query found before you generate alert language.
Click the Copy button on any sector card. Both the <headline> and <description> are copied to your clipboard, formatted for pasting directly into a CAP editor.
Click Download .txt at the bottom of the results. You get a plain text file with all sector descriptions, each labelled with its source tag ([LIBRARY], [CONTEXTUALISED], or [SYNTHESISED]) and the hazard and severity.
Troubleshooting
The map background (Esri World Street Map) needs an internet connection in both versions. When it cannot load, ARIA shows a short notice and switches to a simplified offline basemap: country borders and a coordinate grid, built from Natural Earth data and included in the file. It is for orientation, not precise measurement. Drawing, local files, the spatial query and Library only mode are unaffected either way, since they work from your data's coordinates, not from the map image.
The standard version loads its libraries from public servers when it opens. If you have no connection, or your network blocks those servers, the page cannot start. Use ARIA-offline.html instead. It has the libraries built in.
ARIA shows an error naming the address and mentioning CORS. This means your local model server is either not running or has not been told to accept requests from ARIA. Confirm the server is running and reachable at the address you entered, then see Connect an AI model for how to enable CORS in Ollama, LM Studio, and similar tools.
Open the URL in your browser directly. If you see a login page, the layer is private. If you see JSON, the issue is likely CORS, meaning the server is blocking browser requests. Try downloading the data as a file and loading it locally instead.
Check that the source's toggle is switched on (green). Click ⊕ Fit map to data to confirm the source data covers the area where you drew your polygon.
The most common causes are a wrong API key, a wrong endpoint URL, or a misspelled model name. Check all three. For Claude, the key starts with sk-ant-. For OpenAI, it starts with sk-.
The current hazard/severity combination may not have entries in your library file. Check the library preview in Step 2. The AI still generates descriptions, and they are tagged Synthesised.
Check that ARIA-Lex is loaded (the indicator in the top-right should be green). Then confirm that the hazard and severity combination you selected has entries in the library. The preview in Step 2 shows this. If it says "No library messages for this combination", try a different severity level or check that the correct .db file is loaded.
Email fysh@lastlarch.com with a description of what you were doing and what happened. Screenshots help.
Running the local data server
If you have GIS files stored on your computer and want ARIA to load them automatically, without dragging and dropping them each time, you can run a small local server that watches a folder and serves those files to ARIA.
Open a terminal (Command Prompt on Windows, Terminal on Mac/Linux) and type:
If you see a version number of 3.7 or higher, you are ready. If not, download Python from python.org. The free installer takes two minutes. On Mac and Linux, the command is usually python3, so use python3 --version here and python3 aria-server.py in step 4.
Create a folder anywhere on your computer, for example Documents/ARIA-Library/. Put your GeoJSON files in it. ARIA loads everything in this folder automatically.
aria-server.pyCopy and save the following into a file called aria-server.py inside your library folder:
# ARIA Local Data Server (Last Larch) # Save this file in your GeoJSON library folder and run it. # ARIA will connect to it automatically on localhost:8765 import http.server, json, os, urllib.parse FOLDER = os.path.dirname(os.path.abspath(__file__)) PORT = 8765 def layer_files(): return sorted(f for f in os.listdir(FOLDER) if f.lower().endswith(('.geojson', '.json')) and not f.startswith('.')) class Handler(http.server.BaseHTTPRequestHandler): def respond(self, code, body=b''): self.send_response(code) self.send_header('Access-Control-Allow-Origin', '*') self.send_header('Content-Type', 'application/json') self.send_header('Content-Length', str(len(body))) self.end_headers() self.wfile.write(body) def do_GET(self): path = urllib.parse.unquote(urllib.parse.urlparse(self.path).path) if path == '/layers': layers = [{'name': os.path.splitext(f)[0], 'filename': f} for f in layer_files()] self.respond(200, json.dumps(layers).encode()) elif path.startswith('/file/') and path[6:] in layer_files(): with open(os.path.join(FOLDER, path[6:]), 'rb') as f: self.respond(200, f.read()) else: self.respond(404) def do_OPTIONS(self): self.send_response(204) self.send_header('Access-Control-Allow-Origin', '*') self.send_header('Access-Control-Allow-Methods', 'GET') self.send_header('Access-Control-Allow-Headers', '*') self.send_header('Content-Length', '0') self.end_headers() def log_message(self, *args): pass # suppress terminal output print(f'ARIA library server running. Watching {FOLDER}') print('Open ARIA and click Connect in the sources panel.') http.server.ThreadingHTTPServer(('localhost', PORT), Handler).serve_forever()
In your terminal, navigate to the folder and run:
A confirmation message appears. Leave the terminal window open. Closing it stops the server.
Open ARIA in your browser. At the top of the sources panel, Local data server not connected appears. Click Connect. ARIA loads all GeoJSON files from your folder and checks for changes every 10 seconds, so you can drop new files into the folder while ARIA is open and they appear automatically.
License
ARIA is free and open source under the MIT License. You may use, adapt, and share it, including for commercial purposes. The one condition is that the copyright and license notice stay with any copy.
You are free to:
- Use and share: copy, publish, and distribute the tool in any medium or format
- Adapt: modify, merge, and build upon the tool for any purpose, including commercially, and sublicense or sell it
Under the following terms:
- Notice: include the copyright notice and the MIT permission notice in all copies or substantial portions of the tool
- No warranty: the tool is provided "as is", without warranty of any kind
When you use or adapt ARIA, keep the copyright and license notice that ships with it. A credit line such as the following is also welcome:
The full text is in the LICENSE file in the ARIA repository. You can also read the MIT License at opensource.org/license/mit.
If you are deploying ARIA within a national authority, UN agency, or research institution and would like support, customisation, or a formal partnership, contact Last Larch at fysh@lastlarch.com.