Home /Search
Search datasets
We have found 53 datasets for the keyword "odonyme". You can continue exploring the search results in the list below.
Datasets: 103,468
Contributors: 42
Results
53 Datasets, Page 1 of 6
Table of official street names - Saint-Hyacinthe
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).**
Street sections - Saint-Hyacinthe
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).**
Specific civic addresses - Saint-Hyacinthe
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).**
Road network
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).**
Sidewalk surfaces - Saint-Hyacinthe
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).**
Points of interest and place names - Saint-Hyacinthe
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).**
Fountains - Saint-Hyacinthe
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).**
Clam Beds - Coastal Resource Information Management System (CRIMS)
Distribution of clam beds in coastal Beds in British Columbia showing relative abundance (RA) and aboriginal, biological, commercial and recreational relative importance (RI) and overall RI. RI is based on project region and not on the province as a whole. and productivity. Other attributes include season dates, productivity and species. CRIMS is a legacy dataset of BC coastal resource data that was acquired in a systematic and synoptic manner from 1979 and was intermittently updated throughout the years. Resource information was collected in nine study areas using a peer-reviewed provincial Resource Information Standards Committee consisting of DFO Fishery Officers, First Nations, and other subject matter experts. There are currently no plans to update this legacy data.
FADM - Pulpwood Agreement
The spatial representation for a Pulpwood Agreement, which is a 25 year term agreement, replaceable every ten years, that allows the holder of a wood-fibre processing facility to harvest Crown pulp timber if sufficient quantities of raw material are not available to the holder from other sources. Covers a large area in one or more Timber Supply Areas or TFLs.
Mean fork length of Atlantic salmon (Salmo salar) from 1971-2021
Mean fork length for returning adult Atlantic salmon (Salmo salar) that spent one or two years (1SW and 2SW, respectively) in the marine environment for 16 rivers throughout Eastern Canada spanning an 10° latitudinal gradient. These data were collected as part of monitoring programs for Atlantic salmon returns run by Fisheries and Oceans Canada (DFO). Data from at least eight populations, spanning all provinces in Atlantic Canada, over a 50-year period (1970-2021) will be included in this meta-analysis.These data, as well as mean fork length for returning adult Atlantic salmon from three rivers in Québec (1979-2021) collected as part of monitoring programs for Atlantic salmon returns run by the Ministère de l’Environnement, de la Lutte contre les changements climatiques, de la Faune et des Parcs, Government of Québec, are also available at: http://doi.org/10.17605/OSF.IO/78PWT.
Tell us what you think!
GEO.ca is committed to open dialogue and community building around location-based issues and
topics that matter to you.
Please send us your feedback