Street segments of the road network.attributes:ID - Unique identifierToponymy - Full street nameNorte - Road numberCivic NumberOriginLeft - Civic number that originated the segment on the left side according to the direction of digitalizationNumberCivicOriginRight - Civic number that originated the segment on the right side according to the direction of digitalizationCivic NumberDestinationLeft - Civic number destined for segment on the left side according to the direction of digitalizationCivic NumberDestinationRight - Civic number to the segment on the right side according to the direction of DigitalNameGeneric - Short name of the streetType - Street typeStreet typeStreet typeSegmentStreet - Hierarchical class of the segment in the networkSpeed - Speed limit displayTypesUnique - Indication relating to the presence of a one-way wayMunicipal - Municipal code - Municipal codeHeavy traffic - Indication relating to heavy traffic**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 modificationFor 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`): IconFor 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).**

List of public schools and complete addresses, including: school number, name of school, district, sector, civic address, community, county, postal code, grades offered, language of instruction, website, and year of construction.

The set contains resources that present, for each civic address, information related to polling divisions, polling stations, and electoral districts by district.**This third party metadata element was translated using an automated translation tool (Amazon Translate).**

Point layer of public and private standpipes.**Collection context** Maintenance by the engineering department.**Collection method** Computer-aided drawing.**Attributes*** `ASSET_ID` (`integer`): Identifier* `NO_BF` (`varchar`): Number* `FIC_JOINT` (`varchar`): Attached file* `BF_TYPE` (`varchar`): Type* `NO_CIVIC` (`varchar`): Civic number* `ODO_COURT_COMPLET` (`varchar`): Full short odonym* `ODO_INDEX_LONG` (`varchar`): Long index odonym* `LOCATION` (`varchar`): Location* `SECTEUR_DESC` (`varchar`): Sector* `MODELE` (`varchar`): Model* `DATE_INSTALLE` (`integer`): Installed on* `ELEV_RADIER` (`numeric`): Radius elevation* `ELEV_SURF` (`numeric`): Surface elevation* `PRESSURE_STAT` (`integer`): Static pressure* `DEBIT` (`integer`): Rate* `NOTES` (`varchar`): Notes* `SOURCE` (`varchar`): Source* `DATE_CREATION` (`smalldatetime`): Created on* `DATE_MODIFICATION` (`smalldatetime`): Modified on* `USER_MODIFICATION` (`varchar`): Modified by* `COORD_XY` (`varchar`): Coordinates* `LOC_ROTATION` (`numeric`): Symbol rotation* `BF_MOUCHE` (`nchar`): Mouth* `DRAINAGE` (`nchar`): Drainage* `DRAINAGE_INSPECTION` (`nchar`): Drainage inspection* `INSPECTE_BY` (`nchar`): Inspected by* `DATE_INSPECTION` (`smalldatetime`): Inspected the* `NFPA_TEXT` (`varchar`): NFPA code* `NFPA_DESC` (`varchar`): NFPA descriptionFor 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).**

Work in progress during the current day on the territory of the City of Sherbrooke.attributs:ID - Unique identifierMunicipality - Municipality codeType - Type of workSub-type - Sub-type of workDescription - Description of the workDescription - Description of the workDescription - Description of the workConstruction - Construction unit - Unit of realization of the workLocation - Unit of realization of the workLocation - Street affected by the workIntersection - Intersection affected by the worksCivic number - Civic number concerned by the worksCivic number concerned by the worksCivic number concerned by the worksCivic number concerned by the worksConstruction - Unit of completion of the workLocation - Street affected by the workIntersection - Intersection affected by the worksNo_Civic - Civic number concerned by the worksCivic number concerned by the worksCivic number concerned by the worksCivic number concerned Voie_de - Cross lane from which the street is affected (see LOCATION) WAY_A - Cross lane up to which the street is affected (see LOCATION) DATE_START - Construction start date (UTC or local depending on the various formats offered) DATE_END - Construction end date (UTC or local depending on the various formats offered) TRAFFIC - Effect on trafficSignaler - Presence of signalersPresence of signalsSpeed - Modification of the speed limitSpeed - Modification of the speed limitPolice - Increased police presenceCoureWater - Cutoff in the drinking water supplyPerteAccess - Temporary loss of access to vehicle entrancesCommon transport - Possible disruption of public transitSchool - Presence of a school or school corridorCommerce - Presence of businessesSubsequent workSubsequent work - Planned subsequent workNote - Additional clarificationsDebuthe date - Construction start date (Eastern time) “YYYY-MM-DD HH:MM"datefinHE - Date of completion of work (Eastern time) “YYYY-MM-DD hh:mm”**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`): yFor 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).**

This dataset provides the results obtained by Health Canada’s Radiological Monitoring Network (CRMN) for tritium content in atmospheric water vapor sampled from monitoring stations in Ontario, Quebec and New Brunswick. More information about the CRMN network can be found on the Health Canada website (see link below). The results provided are for tritium activity concentration, expressed in units of becquerels per cubic meter (Bq/m3). Atmospheric water is sampled monthly for determination of tritium content. The majority of such monitoring activity occurs in close proximity to nuclear power plants. Until 1996, Health Canada monitored the areas near Darlington, Bruce and Pickering in Ontario, Gentilly in Quebec, and Point Lepreau in New Brunswick. In 1996, Health Canada’s monitoring of the Ontario stations was terminated to avoid redundancy, since a similar initiative was underway through the Ontario Ministry of Labour. Currently, the CRMN monitors six sites in the vicinity of Point Lepreau, four sites in the vicinity of Gentilly, and a single site in the Greater Toronto Area. The average tritium concentration for the CRMN stations is 0.22 Bq/m3 for the time period from 2004 to 2013. This is consistent with results reported for other monitoring stations in close proximity to Canadian nuclear power stations, and the levels are considered to be safe from a health perspective. Note that the tritium values are measured using liquid scintillator measurements. This requires removing the background contribution from the measurement. The uncertainty associated with each measurement, can lead to reported values of less than zero. The map shows the approximate sampling location for each monitoring station. Stations are found within the associated location range.

Broad management guidance is applied across each Cervid Ecological Zone (CEZ) to help set local population and habitat objectives. CEZs reflect the overarching cervid management intent at the landscape level. The foundation for CEZs is Ontario’s Ecological Land Classification, with consideration given to: * cervid species ranges * landscape level variations in habitat and climate CEZs build on the existing Wildlife Management Unit network while recognizing that species and habitat ranges fluctuate over time.