Location of the regional civil and fire safety offices of the Ministry of Public Security (MSP).**This third party metadata element was translated using an automated translation tool (Amazon Translate).**

The purpose of this dataset is to make it possible to locate civil security events recorded by the Operations Department of the Ministry of Public Security. It brings together in a structured way operational information related to claims that have had an impact on citizens, goods or services to the population since June 2020.It contains information concerning the date of reporting, the hazard, the municipality and the severity of the event.**This third party metadata element was translated using an automated translation tool (Amazon Translate).**

>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).**

Territory of intervention of the regional directorates of the General Directorate of Civil and Fire Safety (DGSCSI). Purpose: To know the limits of the territories covered by the various regional directorates of civil and fire safety.**This third party metadata element was translated using an automated translation tool (Amazon Translate).**

This point dataset represents both applications for a Mines Act permit and issued authorizations for mining activities proposed in the application. Applications for regional Mines Act permits are known as Notice of Work (NoW) applications. Regional mine permits are issued for mineral and coal exploration activities, sand and gravel production, quarry production, and placer mining. Major mine permits are issued for producing mineral and coal mines. Permits are issued by the chief permitting officer under section 10 of the Mines Act and administered by the ministry. Regional mines include: * Exploration — mineral, coal, rock quarry, industrial mineral or dimension stone * Sand and gravel — aggregate, rock or natural substances used for construction purposes * Placer   Most exploration and development activities require a permit under the Mines Act. A decision marks the end of the permitting process for a NoW application. The decision can either be to reject the application or to authorize the mining activities proposed in the NoW. * For new NoW authorizations, a Mines Act permit is issued * For an existing open Mines Act permit, the newly authorized mining activities are amended to the existing permit and the permit is re-issued   **NOTE:** Administrative amendments to a NoW are not captured in this dataset. We are currently working to include this addition for a more complete view of the data. For proponents, please log into https://minespace.gov.bc.ca/ to confirm any authorizations on your permits. The ministry is transitioning from point data to polygonal data for permits and authorizations. The polygon dataset is added to when data becomes available. Users should use both the point dataset and the polygon dataset in combination. Polygon representation of permits with authorizations are referred to as Notice of Work (NoW) – Permitted Mine Areas – Regional Mine - Public https://catalogue.data.gov.bc.ca/dataset/c728435d-410e-42f9-81d5-95978c90e44a The downloaded product from the BCGW is a complete set of all the NoW public records. In addition to the records that contain lat/long references to be mapped spatially, this includes records that do not have NoW lat/long or mine lat/long coordinates to spatialize. These records are listed in a CSV file (HSP_NOTICE_OF_WORK_PA_POINT_SV_NullGeom). Notice of Work categories include: Notice of Work application type, Notice of Work application status. **Notice of Work application type** Field: NOW_APPLICATION_TYPE_DESC (NW_APPTYPD) * Coal * Mineral * Placer Operations * Quarry – Construction Aggregate * Quarry – Industrial Mineral * Sand and Gravel   **Notice of Work application status** Field: NOW_APPLICATION_STATUS_DESC (NW_APPSTAD) * Approved – mining activities in the NoW application have been authorized * Client Delayed – Client needs to provide additional information or reclamation security * Government Action Required – Government needs to action; this status is triggered once a client has provided the requested information and client delay is no longer valid * Referred – Includes referral to agencies and stakeholders, and consultation with First Nations * Rejected – An application is rejected. Either the application standards are not met or requested documentation or security was not provided * Received – The NoW application has been sent from virtual FrontCounterBC to the ministry database * No Permit Required – Category when an inspector reviews the application and non-mechanized disturbance does not require a permit, for example an IP survey * Referral Complete – Referral and consultation is complete. The government needs to action the next steps * Withdrawn – Client requested the application to be withdrawn * Pending verification – Category for records needing review and verification. Typically, these are historical NoW applications with approvals. Manual review is required * NULL value – missing status and application type   **For the public view, please be aware that the ministry:** * Only shows mine commodities of gold or jade/nephrite in the MINE_COMMODITY_DESC (MN_COMD) field. All other commodity values remain NULL (empty)

Most of these events involved community evacuations, significant structural loss and/or involvement of a Ministry of Natural Resources (MNR) Emergency Response Officer. Events include those assigned to MNR by an Order-In-Council under the Emergency Management and Civil Protection Act as well as events where MNR provided requested emergency response assistance. These events fall into one of ten type categories: * dam failure * drought /low water * erosion * flood * forest fire * soil and bedrock instability * Petroleum Resource Center event * EMO requested assistance * continuity of operations event * other requested assistance This product requires the use of geographic information system (GIS) software.

The purpose of this dataset is to locate the events related to the spring 2023 floods recorded by the Deputy Directorate General of Operations of the Ministry of Public Security. All data can be viewed on an interactive map and available as WMS and WFS web services.> To monitor the status of watercourses live, please refer to the [Vigilance - Flood Monitoring] application (https://vigilance.geo.msp.gouv.qc.ca/)### List of available data:* **Open water extent polygons derived from satellite data**: extent limits of open waters derived from radar satellite images.* **Location of flood events since April 14, 2023**: points approximately locating the flood events recorded by the Operations Directorate of the Ministry of Public Security as of April 14, 2023 (derived from the [Civil Security Events] dataset (https://www.donneesquebec.ca/recherche/dataset/evenements-de-securite-civile)).* **Municipalities affected by flood events since April 14, 2023**: cartographic representation of municipalities affected by flood events since April 14, 2023.* **Sentinel-2 satellite image**: satellite image covering flooded areas and presented as a colored compound using short band infrared, near infrared, and red wavelengths.## #Note:Satellite acquisitions for the RADARSAT Constellation Mission (RCM) are planned in collaboration with Natural Resources Canada. The images obtained are processed by the emergency geomatics services of Natural Resources Canada as soon as possible and then the open water polygons are distributed as open data on Data Canada and on Data Quebec. Other optical or radar acquisitions may have been obtained by the Ministry of Public Security (MSP) from private suppliers. The Sentinel-1 and Sentinel-2 acquisitions released in open data by the European Space Agency (ESA) were processed by the Dromedaire Géo-Innovations firm. **This third party metadata element was translated using an automated translation tool (Amazon Translate).**

Public safety incidents that occurred on the territory of the City of Sherbrooke over the past three years. The location of incidents other than road accidents is reported to the intersection of the road network closest to the scene of the incident.attributs:IncidentType - Incident Type (coded value) DESCRIPTION - Description of the type of incidentDateIncident - Incident Date - Incident Date - Incident Date - Incident Date - Incident Date - Incident Date Text - Incident Date in text format (YYYY-MM-DD))**This third party metadata element was translated using an automated translation tool (Amazon Translate).**

The Canadian Wind Turbine Database contains the geographic location and key technology details for wind turbines installed in Canada.Latest update includes: Wild Rose 2, commissioned on Sept. 16, 2025This dataset was jointly compiled by researchers at CanmetENERGY-Ottawa and by the Centre for Applied Business Research in Energy and the Environment at the University of Alberta, under contract from Natural Resources Canada. Additional contributions were made by the Department of Civil & Mineral Engineering at the University of Toronto.Note that total project capacity was sourced from publicly available information, and may not match the sum of individual turbine rated capacity due to de-rating and other factors. The turbine numbering scheme adopted for this database is not intended to match the developer’s asset numbering.This database will be updated in the future. If you are aware of any errors, and would like to provide additional information, or for general inquiries, please use the contact email address listed on this page.

Polygons and surfaces representing the extent of sidewalks on the territory of the city of Saint-Hyacinthe.Technical drawing layer that does not represent the pedestrian network, but rather the sidewalk area.**Collection context** Technical drawing by civil engineering technicians.Collection by project from design plans or plans as built.**Collection method** Computer-aided technical drawings.**Attributes*** `ID_TROTTOIR_S` (`integer`): Identifier* `PRIVE` (`varchar`): Property* `TYPE` (`varchar`): Type* `ODO_INDEX_LONG` (`varchar`): Long odonym index* `ODO_INDEX_COURT` (`varchar`): Short odonym index* `ODO_LONG_COMPLETE` (`varchar`): Full long odonym* `ODO_COURT_COMPLETE` (`varchar`): Short odonym* `ODONYM` (`varchar`): Odonym* `COATING` (`nchar`): Coating* `ANNEE_INSTALL` (`nchar`): Year of installation* `LENGTH` (`numeric`): Length* `WIDTH` (`numeric`): Width* `AREA` (`numeric`): Area* `LOCATION` (`varchar`): Location* `NOTES` (`nvarchar`): Notes* `SOURCE` (`varchar`): Source* `DATE_CREATION` (`smalldatetime`): Creation date* `DATE_MODIFICATION` (`smalldatetime`): Date of modification* `USER_MODIFICATION` (`varchar`): Modified byFor more information, consult the metadata on the Isogeo catalog (OpenCatalog link).**This third party metadata element was translated using an automated translation tool (Amazon Translate).**