Layers of airspace protection zones in the City of Trois-Rivières**This third party metadata element was translated using an automated translation tool (Amazon Translate).**

Linear layer illustrating the lot divisions present in the graphic matrix in the case of properties containing several lots. **Collection context** Maintenance process in collaboration with the evaluation department. **Collection method** Computer-aided mapping. **Attributes** * `ID_MAT_DIV` (`integer`): Identifier * `DATE_CREATION` (`smalldatetime`): Created on * `DATE_MODIFICATION` (`smalldatetime`): Modified on * `USER_MODIFICATION` (`varchar`): Modified by * `MAT10` (`varchar`): Number * `ID_MAT_DIV_OLD` (`varchar`): Old id For 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).**

Polygons of evaluation units of the graphic matrix. **Collection context** Update process in collaboration with the evaluation department. **Collection method** Computer-aided mapping. **Attributes** * `ID` (`integer`): Identifier * `ADM01A` (`varchar`): Municipality code * `SI0318A` (`smalldatetime`): Registration date * `SI0317C` (`varchar`): Registration * `SI0528C` (`varchar`): Neighborhood unit * `DATE_CREATION` (`smalldatetime`): Created on * `DATE_MODIFICATION` (`smalldatetime`): Modified on * `USER_MODIFICATION` (`varchar`): Modified by * `X_FIC_JOINT` (`varchar`): Attached file * `ID_OLD` (`varchar`): Old id For 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).**

Point layer of civic number ranges on the front of the lot. Taken from the graphic matrix using the assessment roll. **Collection context** Taken from the assessment roll **Collection method** Cartographic integration through the process of updating the graphic matrix. Data integration method and manual positioning. **Attributes** * `ID` (`integrate`): ID * `ADM01A` (`varchar`): Geographic code * `SI0314A` (`smalldatetime`): Registration date * `SI0314B` (`integer`): Scale * `SI0314C` (`varchar`): Civic number * `SI0314D` (`varchar`): Police * `SI0314E` (`numeric`): Size * `SI0314F` (`numeric`): Orientation * `SI0314G` (`varchar`): Anchor * `LOC_X` (`numeric`): X * `LOC_Y` (`numeric`): Y * `SI0317C` (`varchar`): Registration * `DATE_CREATION` (`smalldatetime`): Creation date * `DATE_MODIFICATION` (`smalldatetime`): Date of modification For 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).**

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

Point layer of points of interest and place names. Schools, pools, municipal buildings, etc. **Collection context** Manual collection and additions/withdrawals according to procedures between departments. **Collection method** Computer-aided mapping. **Attributes** * `ID_PDI` (`integer`): Identifier * `GROUPE_PDI` (`varchar`): Group * `NO_PDI` (`varchar`): Number * `PDI_NAME` (`varchar`): Name * `NO_CIVIC` (`varchar`): Civic number * `ODO_INDEX_LONG` (`varchar`): Long index odonym * `ODO_COURT_COMPLET` (`varchar`): Full short odonym * `ODO_LONG_COMPLETE` (`varchar`): Full long odonym * `ODO_INDEX_COURT` (`varchar`): Short index odonym * `URL` (`varchar`): URL * `CHARACTER` (`varchar`): Character * `POLICE` (`varchar`): Police * `scale` (`integer`): Scale * `USE` (`varchar`): Utility * `NOTES` (`varchar`): Notes * `SOURCE` (`varchar`): Source * `DATE_CREATION` (`smalldatetime`): Created on * `DATE_MODIFICATION` (`smalldatetime`): Modified on * `USER_MODIFICATION` (`varchar`): Modified by * `ICONE` (`varchar`): Icon For 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).**

Position of address points. **Collection context** Initial source of the Qc address databases, the urban planning department, the engineering department and the DGE. Analysis and coupling of the various sources to create a comprehensive research layer for the needs of the city's internal users. Timely maintenance using the address change reports from the urban planning department and changes to the property records from the assessment department. **Collection method** Computer-aided mapping. **Attributes** * `ID_ADRCIV` (`integer`): Identifier * `NOCIVQ` (`integer`): Civic number * `NOCIV_SUFX` (`varchar`): Number suffix * `ODO_INDEX_LONG` (`varchar`): Long index odonym * `ODO_INDEX_COURT` (`varchar`): Short index odonym * `ADQNBUNITE` (`integer`): Number of Qc address units * `CODE_POST` (`varchar`): Postal code * `MAT10` (`varchar`): Number * `SOURCE` (`varchar`): Source * `DATE_CREATION` (`smalldatetime`): Created on * `DATE_MODIFICATION` (`smalldatetime`): Modified on * `USER_MODIFICATION` (`varchar`): Modified by * `DATE_ARCHIVE` (`smalldatetime`): Archive date * `ODO_LONG_COMPLETE` (`varchar`): Full long odonym * `ODO_COURT_COMPLET` (`varchar`): Full short odonym * `ODONYM` (`varchar`): Odonym * `LOC_X` (`numeric`): x * `LOC_Y` (`numeric`): y For 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).**

The RADARSAT Constellation is the evolution of the RADARSAT Program with the objective of ensuring data continuity, improved operational use of Synthetic Aperture Radar (SAR) and improved system reliability. The three-satellite configuration provides daily revisits of Canada's vast territory and maritime approaches, as well as daily access to 90% of the world's surface. RCM is tasked solely by the Government of Canada, to acquire data, first and foremost in support of Government of Canada services and needs. RCM data and services contributes to ensuring the safety and security of Canadians; monitoring and protecting the environment; monitoring of climate change; managing Canada’s natural resources; and stimulating innovation, research and economic development. In addition to these core user areas, there are expected to be a wide range of ad hoc uses of RADARSAT Constellation data in many different applications within the public and private sectors, both in Canada and internationally. The current data set reflects the acquisition plans that are designed to meet the RCM SAR imaging demands of the Government of Canada. These are being made available publicly in advance of the acquisitions. To meet the data needs of the Government of Canada, acquisitions may be changed without notice. After their acquisition and processing, the RCM image products listed in the current data set, will be delivered to the Earth Observation Data Management System - EODMS (https://www.eodms-sgdot.nrcan-rncan.gc.ca/index-en.html) portal of Natural Resources Canada. Users can register to the EODMS portal as public users to retrieve the RCM image products. For those requiring a greater access to RCM imagery consisting of product types or spatial resolutions not available to public users: you may apply to upgrade your public account to an ‘RCM external vetted entity’ EODMS user type account. For more information on this process, please contact the Canadian Space Agency using the information available at the following link : https://www.asc-csa.gc.ca/eng/satellites/radarsat/access-to-data/how-to-become-a-user.asp Publication frequency : I. Future acquisition plans are published every two weeks for a two-week window that starts two weeks from the publication date. As an example, acquisition plan published on April 1st covers acquisitions from April 14 to 27. The next plan is published on April 14th and covers from April 28 to May 11. II. Past acquisitions plans are published monthly and covers a period of one month from the first to the last day As an example, acquisition plan published on April 1st covers acquisition made between the March 1 and March 31. The next plan covers the month of April.

These datasets include information on Licences under the Water Act collected by Alberta Environment and Protected Areas, for both active and inactive authorizations for surface water and groundwater diversions under a Licence (defined as a “diversion of water” under the Water Act).

Layers of current and active bike paths in the City of Trois-Rivières**This third party metadata element was translated using an automated translation tool (Amazon Translate).**