For the complete documentation index, see llms.txt. This page is also available as Markdown.

Man-made Sample

This page provides a complete sample response for a man-made hazard from the Active Hazards API endpoint. The MANMADE type covers human-caused or human-driven crises that are not classified under the geopolitical types (COMBAT, TERRORISM, CIVILUNREST, ACCIDENT) — the sample below is a famine. These hazards are curated by PDC analysts and entered manually, so the record uses the generic PDC incident envelope.

Man-made-Specific Properties

Incident Data

This hazard uses the generic PDC incident envelope in incident.properties — the common shape shared by all PDC-curated and manually entered hazards, regardless of type.

Key properties on a manually curated hazard:

  • Incident_Type - The hazard type ("MANMADE")

  • name / hazardName - Hazard title

  • description / hazardDescription - Analyst-written narrative

  • eventDate / reportDate / createDate / endDate / expires - Event and lifecycle timing (ISO 8601)

  • casualties - JSON string with killed/injured totals, or "null" when not reported

  • hazard - JSON string carrying the hazard's uuid and severity

  • hazardUUID / masterIncidentId - Identifiers linking the incident to its hazard

  • sourceName - "PDC Manual Hazard" for analyst-entered records

  • sourceResourceLocations - JSON array of source references

  • incidentLatitude / incidentLongitude / locationDescription - Location

  • glideUri / charterUri / sncUrl - External references, when assigned

  • overrideDescription / overrideStartedAt - Analyst overrides of derived values

  • roles - Visibility ("PUBLIC")

Features

The features collection has two features: an INCIDENT point at the reported location, whose properties mirror the incident envelope, and a SMART_ALERT polygon defining the notification boundary. The features collection carries metadata, incidentType, and sourceId at collection level alongside type and features, and each feature's geometry object embeds a copy of the feature's properties. See Feature collections.

Exposure Areas

Manually curated hazards use a single exposure level (level 0, "Limited to No Damage Expected") drawn as a polygon around the affected region. The exposureAssessment block is populated from it, with country and admin breakdowns.

Source

source is null on manually curated hazards; provenance is carried in incident.properties.sourceName.

Sample Response

Note: Coordinate arrays have been replaced with [...] for brevity. In actual API responses, these properties contain complete GeoJSON coordinate arrays. Long text fields have been truncated. All other values are verbatim from the production API as of 2026-09-11.

Last updated