History of civil security events - Archives

>Warning: as of June 2020, this dataset is no longer updated and has been replaced. Please see https://www.donneesquebec.ca/recherche/fr/dataset/evenements-de-securite-civile for data on civil security events since June 2020. This database brings together in a structured way information related to past claims that have been systematically grouped and centralized by the Ministry of Public Security (MSP). The consequences and evolution of the events are documented and they have been categorized according to their level of impact on the safety of citizens, goods and services to the population based on criteria defined in the Canadian profile of the Common Alert Protocol. It is updated continuously by the MSP Operations Department (DO). This database will allow analyses to be carried out at regional and local levels and can be used by municipalities in the implementation of their emergency measures plans. The event history archives come from event reports and status reports that were produced by the Government Operations Center (COG) and by the regional directorates of the MSP. Among other things, we find: 1- Observations entered directly into the Geoportal by the civil security advisers of the regional directorates; 2- A compilation of information recorded in COG event reports and DO status reports distributed to MSP partners since 1996; 3- A compilation of the information contained in the files of the regional directorates. This can be information on paper, event reports or field visits, paper or digital maps, etc. The information in this database is consistent with the Canadian Common Alert Protocol Profile (PC-PAC). The PC-PAC is a set of rules and controlled values that support the translation and composition of a message to make it possible to send it by different means and from different sources. The severity level is an attribute defined in the PC-PAC. It is used to characterize the severity level of the event based on the harm to the lives of people or damage to property. This severity level is defined by the following characteristics: Extreme: an extraordinary threat to life or property; Significant: significant threat to life or property; Moderate: possible threat to life or property; Minor: a low or non-existent threat to life or property; Unknown: unknown severity, used for example during tests and exercises. The emergency level is determined based on the reactive measures that need to be taken in response to the current situation. It is defined by the following characteristics: Immediate: reactive action must be taken immediately; Expected: reactive action should be taken soon (within the next hour); Future: reactive action should be taken in the near future; Past: a reactive measure is no longer necessary; Unknown: Unknown emergency, to be used during tests and exercises. The state relates to the context of the event, real or simulated. It is defined by the following characteristics: Current: information on a real event or situation; Exercise: fictional or real information produced as part of a civil security exercise; Test: technical tests only; to be ignored by all. Confidence is defined by the following characteristics: Observed: would have happened or is currently taking place; Probable: probability of the event happening > 50%; Possible: probability of the event happening < 50%; Unlikely: probability of the event happening around 0%; Unknown: certainty unknown. When an event date was not known, the year 1900-01-01 was recorded. DESCRIPTION OF ATTRIBUTES: Observation date: date of the event or observation; Type: name of the hazard; Name: name of the municipality; Municipality code: municipal code; State and certainty: as these are real events, the state is generally “current” and the certainty is generally “observed”; Urgency: the term “past” has generally been used for events that occurred before compilation work was carried out; Imprecision: imprecision in data (the date of the event, its location, the source of the data or no inaccuracy noted).**This third party metadata element was translated using an automated translation tool (Amazon Translate).**