Stay organized with collections
Save and categorize content based on your preferences.
We strongly recommend that the <area> entity defines the geographic area to be
notified, not the incident area.
In the case of a tropical storm, we recommend that the <area> entity contains
<polygon> or <geocode> elements that denote the places where you expect
impacts from strong winds, heavy rain, or other threats from the storm. If a
storm is still offshore, then don't set the <area> entity of your CAP alert
to the storm's current location.
Similarly, in the case of a forest fire, we recommend that the <area> entity
data also includes towns or places where you expect impacts from smoke or other
threats from the fire.
area entity sub-elements
Element name
Optionality
Type
CAP and Google notes and requirements
<areaDesc>
REQUIRED
string
To generate the location text string used in the alert title or
headline, Google might use an <areaDesc> element. Keep
the <areaDesc> value short (less than 50
characters).
<polygon>
OPTIONAL
string
The paired value points in a <polygon> element
define a polygon that delineates the area to alert in an alert message.
We recommend that you represent the <polygon> element
by a whitespace-delimited list of
WGS84
coordinate pairs.
Polygons must meet the following requirements:
They must be closed.
They can't overlap.
Holes (like in donut-shaped polygons) and intersections aren't
supported.
A minimum of four coordinate pairs are required. The first and last
pairs of coordinates must be the same.
<circle>
OPTIONAL
string
The <circle> element consists of paired
point-and-radius values that delineate the area to alert in the form of
an alert message. We recommend that you represent the
<circle> element by a central point: a WGS84
coordinate pair followed by a space character and a radius value in
kilometers.
Note: If you specify a circle with zero or a very small radius, Google
can't show the alert to our users.
<geocode>
OPTIONAL
string
Define the <geocode> element with values from a accessible
and open dataset of polygons. As an example, in the US, these values come
from the following data sources:
FIPS6
UGC code
SAME
US Zip Code
If you use geocodes, provide Google with a fixed list of
geocode-to-polygon and shapefile maps. To post notices of updates to this
list, use a separate channel, preferably as RSS or email alerts. For
example, US NOAA publicly publishes their
geocode updates.
<altitude>
OPTIONAL
float
The value of the <altitude> element is the specific
or minimum altitude of the affected area of the alert message. Provide
this measurement in feet above mean sea level according to WGS84
datum.
<ceiling>
CONDITIONAL
float
Use the <ceiling> element only if the
<alert> entity contains an
<altitude> element. The value of the
<ceiling> element is the maximum altitude of the
affected area of the alert message. Provide this measurement in feet
above mean sea level according to WGS84 datum.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-28 UTC."],[[["\u003cp\u003eThe \u003ccode\u003e<area>\u003c/code\u003e entity in a CAP alert should define the geographic area expected to be impacted by the event, not the event's location itself.\u003c/p\u003e\n"],["\u003cp\u003eWhen defining the alert area, use \u003ccode\u003e<polygon>\u003c/code\u003e, \u003ccode\u003e<circle>\u003c/code\u003e, or \u003ccode\u003e<geocode>\u003c/code\u003e elements to specify the impacted locations.\u003c/p\u003e\n"],["\u003cp\u003eFor alerts covering multiple, non-continuous areas, create separate \u003ccode\u003e<alert>\u003c/code\u003e messages for each distinct area.\u003c/p\u003e\n"],["\u003cp\u003eEnsure the alert area remains within your organization's jurisdiction to avoid publishing issues with Google.\u003c/p\u003e\n"],["\u003cp\u003eEach \u003ccode\u003e<area>\u003c/code\u003e block must include at least one \u003ccode\u003e<polygon>\u003c/code\u003e, \u003ccode\u003e<circle>\u003c/code\u003e, or \u003ccode\u003e<geocode>\u003c/code\u003e sub-element for accurate location specification.\u003c/p\u003e\n"]]],["The `\u003carea\u003e` entity should define the impact zone, not the incident's location. For events like storms or fires, use `\u003cpolygon\u003e` or `\u003cgeocode\u003e` to specify areas affected by threats, not the storm's position. Use separate `\u003calert\u003e` messages for noncontinuous areas. All `\u003carea\u003e` blocks must include at least one of: `\u003cpolygon\u003e`, `\u003ccircle\u003e`, or `\u003cgeocode\u003e`. Ensure the areas are within your jurisdiction. Additional elements like `\u003careaDesc\u003e`, `\u003caltitude\u003e` and `\u003cceiling\u003e` are also defined.\n"],null,["# area\n\nWe strongly recommend that the `\u003carea\u003e` entity defines the geographic area to be\nnotified, not the incident area.\n\nIn the case of a tropical storm, we recommend that the `\u003carea\u003e` entity contains\n`\u003cpolygon\u003e` or `\u003cgeocode\u003e` elements that denote the places where you expect\nimpacts from strong winds, heavy rain, or other threats from the storm. If a\nstorm is still offshore, then don't set the `\u003carea\u003e` entity of your CAP alert\nto the storm's current location.\n\nSimilarly, in the case of a forest fire, we recommend that the `\u003carea\u003e` entity\ndata also includes towns or places where you expect impacts from smoke or other\nthreats from the fire.\n| **Important:** For noncontinuous areas under the same alert level and type, create separate `\u003calert\u003e` messages rather than a single `\u003calert\u003e` message that includes disjointed areas.\n| **Important:** Make sure that you only include areas to alert that are within your jurisdiction. If the alerting area in your `\u003calert\u003e` message includes locations outside of the jurisdiction of your organization, Google reserves the right to not publish your alert.\n| **Important:** In all `\u003carea\u003e` blocks, you must include at least one of `\u003cpolygon\u003e`, `\u003ccircle\u003e`, or `\u003cgeocode\u003e` sub-element.\n\n`area` entity sub-elements\n--------------------------\n\n| Element name | Optionality | Type | CAP and Google notes and requirements |\n|--------------|-------------|----------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| `\u003careaDesc\u003e` | REQUIRED | `string` | To generate the location text string used in the alert title or headline, Google might use an `\u003careaDesc\u003e` element. Keep the `\u003careaDesc\u003e` value short (less than 50 characters). |\n| `\u003cpolygon\u003e` | OPTIONAL | `string` | The paired value points in a `\u003cpolygon\u003e` element define a polygon that delineates the area to alert in an alert message. We recommend that you represent the `\u003cpolygon\u003e` element by a whitespace-delimited list of [WGS84](https://gisgeography.com/wgs84-world-geodetic-system/) coordinate pairs. Polygons must meet the following requirements: - They must be closed. - They can't overlap. - Holes (like in donut-shaped polygons) and intersections aren't supported. - A minimum of four coordinate pairs are required. The first and last pairs of coordinates must be the same. |\n| `\u003ccircle\u003e` | OPTIONAL | `string` | The `\u003ccircle\u003e` element consists of paired point-and-radius values that delineate the area to alert in the form of an alert message. We recommend that you represent the `\u003ccircle\u003e` element by a central point: a WGS84 coordinate pair followed by a space character and a radius value in kilometers. Note: If you specify a circle with zero or a very small radius, Google can't show the alert to our users. |\n| `\u003cgeocode\u003e` | OPTIONAL | `string` | Define the `\u003cgeocode\u003e` element with values from a accessible and open dataset of polygons. As an example, in the US, these values come from the following data sources: - FIPS6 - UGC code - SAME - US Zip Code If you use geocodes, provide Google with a fixed list of geocode-to-polygon and shapefile maps. To post notices of updates to this list, use a separate channel, preferably as RSS or email alerts. For example, US NOAA publicly publishes their [geocode updates](https://www.weather.gov/gis/FireZones). |\n| `\u003caltitude\u003e` | OPTIONAL | `float` | The value of the `\u003caltitude\u003e` element is the specific or minimum altitude of the affected area of the alert message. Provide this measurement in feet above mean sea level according to WGS84 datum. |\n| `\u003cceiling\u003e` | CONDITIONAL | `float` | Use the `\u003cceiling\u003e` element only if the `\u003calert\u003e` entity contains an `\u003caltitude\u003e` element. The value of the `\u003cceiling\u003e` element is the maximum altitude of the affected area of the alert message. Provide this measurement in feet above mean sea level according to WGS84 datum. |\n\nExample\n-------\n\n \u003carea\u003e\n \u003careaDesc\u003eCavite\u003c/areaDesc\u003e\n \u003cpolygon\u003e14.473860833486,120.9718174024 14.347454023196,121.01386683476\n 14.142014336735,121.03024107602 14.063075455227,120.85558468426\n 14.221664765773,120.59001887699 14.473860833486,\n 120.9718174024\u003c/polygon\u003e\n \u003cgeocode\u003e\n \u003cvalueName\u003eSAME\u003c/valueName\u003e\n \u003cvalue\u003e042100000\u003c/value\u003e\n \u003c/geocode\u003e\n \u003c/area\u003e\n\n \u003carea\u003e\n \u003careaDesc\u003e107 km SouthWest DENPASAR-BALI\u003c/areaDesc\u003e\n \u003ccircle\u003e-9.63,115.12 300.0\u003c/circle\u003e\n \u003c/area\u003e"]]
