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

Urbanization perimeters of the City of Trois-Rivières**This third party metadata element was translated using an automated translation tool (Amazon Translate).**

Layer of points representing the intersections of the road network in the city of Saint-Hyacinthe. **Collection context** Associated with the layer of street sections of the city's road network. Topological intersection points associated with the intersections of segments of street sections. **Collection method** Computer-aided design with topological rules between the road network and the intersection nodes. **Attributes** * `ASSET_ID` (`integer`): Identifier * `TYPE_REF` (`varchar`): Type reference * `SOURCE` (`varchar`): Source * `DATE_CREATION` (`smalldatetime`): Creation date * `DATE_MODIFICATION` (`smalldatetime`): Date of modification * `USER_MODIFICATION` (`varchar`): Modified by * `LOC_SYMBOL` (`varchar`): Symbol * `LOC_ROTATION` (`numeric`): Rotation angle 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).**

Please note that a web service is currently under development and will be launched in summer 2026. To be informed as soon as it is posted online and to stay up to date with geospatial news, subscribe to our newsletter [ActuGéo.] (https://mrnf.gouv.qc.ca/ministere/cartes-information-geographique/repertoire-services-web-donnees-geographiques/actugeo/) The Quebec Address Repository (RQA) includes all municipal addresses in Quebec as well as several attributes associated with them, including the following main components: * The municipal number * The suffix * The unit (apartment/office/premises) * The name of the street (odonym) * The name and code of the municipality * The MO postal code * The main use (category) * The date of creation, modification and withdrawal * Latitude and longitude * Etc. This repository of geolocated addresses is updated monthly, and is available in a single file format (*flat file*). A [CSV file] (https://diffusion.mern.gouv.qc.ca/diffusion/RGQ/Vectoriel/Theme/Local/Odonymes_Renvois/CSV/Odonymes_renvois.csv) containing all the odonyms as well as the references is also available in the data section below. Referrals allow you to track changes in street names. The RQA is the result of the integration of data in collaboration with the municipal sector and production partners: Élections Québec, the Ministry of Municipal Affairs and Housing, and the Ministry of Transport and Sustainable Mobility. The RQA can be used in addition to the [Quebec Road Network Framework (RQRR)] (https://www.donneesquebec.ca/recherche/dataset/referentiel-quebecois-du-reseau-routier). * “Postal Code” is an official trademark of Canada Post Corporation***This third party metadata element was translated using an automated translation tool (Amazon Translate).**

The Roads database includes an inventory of road assets (roadways, blocks, intersections, sidewalks, curbs) with a spatial representation and various attached information. __Aggregate pavement-type road assets__ represent carriageways located in the public domain and which are part of the local or arterial road network. Aggregate pavements are represented by polygons that are aggregated by type of use. Among the information associated with a pavement object is the date of construction, the date of resurfacing, the date of survey, the materials of the pavement, the type of foundation, the presence of a bicycle lane, the use, etc. __Island-type road assets__ represent malls located in the public domain and which are juxtaposed to the local or arterial road network. The islands are represented by polygons that are differentiated by their configuration. Among the information associated with an island-type object is the date of construction, the date of survey, the materials of the block and the border, the presence of trees, the type of island, etc. __Intersection-type road assets__ represent road crossings located in the public domain and which are part of the local or arterial road network. Intersections are represented by polygons that are cut according to the number of traffic axes. Information associated with an intersecting object includes the construction date, resurfacing date, survey date, intersection materials, foundation type, presence of bike lanes, etc. __Sidewalk-type road assets__ represent sidewalks and curbs juxtaposed with carriageways located in the public domain and that are part of the local or arterial road network. Sidewalks and curbs are represented by polygons differentiated by category and type. Among the information associated with a sidewalk-type object is the date of construction, the date of survey, the type of sidewalk and curb, the materials of the sidewalk, the border and the developed strip, the presence of trees, the presence of a projection, the presence of a ledge, the presence of a bicycle lane, the use, etc. The __zone-type road assets__ represent the regions located between other road assets and that are not part of the local or arterial road network. The areas are represented by polygons. Among the information associated with a zone-like object is the type of zone, etc. Data is also available in separate sets on the portal to support several uses: - [Roadway and intersection] (/city-of-montreal/voirie-causee-intersection) - [Sidewalk and island] (/city-of-montreal/voirie-trottoir-ilot) - [Off-road zone] (/city-of-montreal/voirie-zone) __Warnings__ - The data released on road assets are those in the possession of the City's geomatics team and are not necessarily up to date throughout the territory. - The data released on road assets is provided for information purposes only and should not be used for the purposes of designing or carrying out works or for the location of assets. **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).**

Layers of areas where biting insects are treated**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).**

Geographic information of residual materials collection sectors on the City's territory, including availability and collection times in the form of messages. This data is derived from the [Info-collections] portal (https://servicesenligne2.ville.montreal.qc.ca/sel/infocollectes/?lang=fr). It should be noted that the data in the set is refreshed monthly, however its internal updates are ad hoc by district.**This third party metadata element was translated using an automated translation tool (Amazon Translate).**

This list contains water meters operated by the City of Montreal Water Department. The meter pool is used to carry out water balances and makes it possible to measure the water distributed to the other municipalities forming the agglomeration of Montreal. This list is a view of the situation at the time the file was generated. NOTE: The data in this set aims to have a better understanding of the number of industrial, commercial and institutional water meters installed as part of the City of Montreal's water consumption measurement strategy. For reasons of challenges in the protection of third party industrial secrets, the consumption associated with these meters will not be published.**This third party metadata element was translated using an automated translation tool (Amazon Translate).**