Data table containing the odonyms of city streets.The names were checked with the Quebec Toponymy Commission.**Collection context** Periodic manual additions and changes.**Collection method** Notifications by city legal departments.**Attributes*** `ID_ODONYME` (`integer`): Odonymous identifier* `ODONYM` (`varchar`): Odonym* `GEN_ODO` (`varchar`): Generic odonym* `LINE_ODO` (`varchar`): Odonymous link* `GEN_COURT` (`varchar`): Short generic* `ODO_COURT` (`varchar`): Short odonym* `ACTIVE` (`integer`): Active* `OFFICIAL_STATUS` (`integer`): Official status* `NOTICES_DESC` (`varchar`): Descriptive notice* `OLD_NAME` (`varchar`): Old name* `DISTRICT` (`varchar`): Distrito* `USER_MODIFICATION` (`varchar`): Modified by* `DATE_CREATION` (`smalldatetime`): Creation date* `DATE_MODIFICATION` (`smalldatetime`): Date of modification* `DATE_OFFICIEL` (`smalldatetime`): Date of officialization* `ODO_COURT_COMPLET` (`varchar`): Full short odonym* `ODO_LONG_COMPLETE` (`varchar`): Full long odonym* `ODO_INDEX_COURT` (`varchar`): Short index odonym* `ODO_INDEX_LONG` (`varchar`): Long index odonymFor 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 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).**

Central lines for the layout of street sections.**Collection context** Maintenance by the geomatics division in collaboration with the engineering department.**Collection method** Computer-aided mapping.**Attributes*** `ASSET_ID` (`integer`): Identifier* `Odonym` (`varchar`): Odonym* `Jurisdiction` (`varchar`): Jurisdiction* `Status` (`varchar`): Status* `NIV_HIERARC` (`varchar`): Hierarchical level* `Circulation` (`varchar`): Traffic* `Coating` (`varchar`): Coating* `NB_VOIE` (`integer`): Number of channels* `LENGTH` (`numeric`): Length* `display_class` (`varchar`): Display class* `ODONYME_INT_A` (`varchar`): Odonym intersection A* `ODONYME_INT_B` (`varchar`): Odonym intersection B* `ADR_DEBUT_G` (`integer`): Address start left* `ADR_FIN_G` (`integer`): End left address* `ADR_DEBUT_D` (`integer`): Right start address* `ADR_FIN_D` (`integer`): Right end address* `NOTES` (`varchar`): Notes* `SOURCE` (`varchar`): Source* `DATE_CREATION` (`smalldatetime`): Created on* `DATE_MODIFICATION` (`smalldatetime`): Modified on* `USER_MODIFICATION` (`varchar`): Modified by* `ODO_LONG_COMPLETE` (`varchar`): Full long odonym* `ODO_INDEX_COURT` (`varchar`): Short index odonym* `ODO_INDEX_LONG` (`varchar`): Long index odonymFor 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`): 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).**

The entire road network of the City of Rouyn-Noranda. Only the lanesPublics with an odonym are included.**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).**

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

Geochronology is a discipline of geoscience which measures the age of earth materials and provides the temporal framework in which other geoscience data can be interpreted in the context of Earth history. This knowledge helps to answer questions such as when did a volcano last erupt, what is the rate of crustal uplift in a specific area, are rocks at one gold prospect the same age as those at another.Distributed from [GeoYukon](https://yukon.ca/geoyukon) by the [Government of Yukon](https://yukon.ca/maps) . Discover more digital map data and interactive maps from Yukon's digital map data collection.For more information: [geomatics.help@yukon.ca](mailto:geomatics.help@yukon.ca)

Across the Canadian North, Arctic Char, Salvelinus alpinus, are culturally important and critical for maintaining subsistence lifestyles and ensuring food security for Inuit. Arctic Char also support economic development initiatives in many Arctic communities through the establishment of coastal and inland commercial char fisheries. The Halokvik River, located near the community of Cambridge Bay, Nunavut, has supported a commercial fishery for anadromous Arctic Char since the late 1960s. The sustainable management of this fishery, however, remains challenging given the lack of biological data on Arctic Char from this system and the limited information on abundance and biomass needed for resolving sustainable rates of exploitation. In 2013 and 2014, we enumerated the upstream run of Arctic Char in this system using a weir normally used for commercial harvesting. Additionally, we measured fish length and used T-bar anchor tags to mark a subset of the run. Subsequently, we estimated population size using capture-mark-recapture (CMR) methods. The estimated number of Arctic Char differed substantially between years. In 2013, 1967 Arctic Char were enumerated whereas in 2014, 14,502 Arctic Char were enumerated. We attribute this marked difference primarily to differences in weir design between years. There was also no significant relationship between daily mean water temperature and number of Arctic Char counted per day in either year of the enumeration. The CMR population estimates of Arctic Char (those ≥450mm in length) for 2013 and 2014 were 35,546 (95% C.I 30,513-49,254) and 48,377 (95% C.I. 37,398-74,601) respectively. The 95% CI overlapped between years, suggesting that inter-annual differences may not be as extreme as what is suggested by the enumeration. The population estimates reported here are also the first estimates of population size for an Arctic Char stock in the Cambridge Bay region using CMR methodology. Overall, the results of this study will be valuable for understanding how population size may fluctuate over time in the region and for potentially providing advice on the sustainable rates of harvest for Halokvik River Arctic Char. Additionally, the results generated here may prove valuable for validating current stock assessment models that are being explored for estimating biomass and abundance for commercial stocks of Arctic Char in the region.

Historical finds of Coleophora serratella