Why alerts API does not return polygon

[long-nguyen]

Hi, does anyone know why some alert item does not have 'geometry' field?
API: https://api.weather.gov/alerts/active

"features": [
        {
            "id": "https://api.weather.gov/alerts/urn:oid:2.49.0.1.840.0.6e4c40b25fca4e54f9f785c46758df04ea96ce08.001.1",
            "type": "Feature",
            "geometry": null,
            "properties": {
                "@id": "https://api.weather.gov/alerts/urn:oid:2.49.0.1.840.0.6e4c40b25fca4e54f9f785c46758df04ea96ce08.001.1",
                "@type": "wx:Alert",
                "id": 

[sullynole]

There are different types of alerts. This should help explain: https://www.weather.gov/media/documentation/docs/NWS_Geolocation.pdf

[JJKraw]

For alerts that do not contain an explicit polygon, you can use the geometries associated with the zone codes included in the alert. Those are found at /zones/{type}/{zoneID}

Make sure you request geo+json.

I keep a cache of these so I don't have to fetch every time.

[sullynole]

Public/fire/coastal zone and county maps are also available here as services: https://mapservices.weather.noaa.gov/static/rest/services/nws_reference_maps/nws_reference_map/MapServer

Note: WFOs generally can update their zones twice per year in spring and fall, so take that into consideration for your application. Those changes are announced here when they occur: https://www.weather.gov/notification/#scn

[ephcoding]

@scadergit for the inoperable query params (ie. include_geometry), would it be worth me shooting an email to the [email protected]?

[scadergit]

Sure, but probably low priority.

[ephcoding]

@JJKraw @sullynole @scadergit thank you guys for all the help.

[JJKraw]

https://lexmaweather.info

Nothing professional. Just hobby coding for me and info for people in my town.

Example of maps / zone usage: https://lexmaweather.info/advisoryJson.php?coverage=sew