Specific location of addresses, excluding apartment numbers.Attributes:Municipality - Municipality Code - Municipality CodeNo_Civic - Civic NumberType_Lane - Road Type_Lane - LinkName_Lane - LinkName_Lane - Link Road - Name of the wayOrientation - Name of the wayOrientation - Orientation of the lane (N, S, E, O) STREET - Full name of the streetAddress - Address**This third party metadata element was translated using an automated translation tool (Amazon Translate).**

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

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

Planned routes of new streets or street extensions.attribut:ID - Unique identifier**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).**

All the specific addresses of the City of Rouyn-Noranda. **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 angleFor 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).**

The Site / Structure Addresses layer represents the location of a site, or structure, or the location of access for the site, or structure, for the City of Whitehorse. Site / Structure addresses may also represent landmarks. Address points have the ability to locate sites that otherwise may not geocode correctly using the road centreline data, areas of unusual addressing, and other areas where the data is available.Data was modeled using the NENA NG9-1-1 GIS Data Template (NENA-REF-006. 2 -202 2 ).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)

Public parking spaces in downtown Sherbrooke.attributes:Location - Location of the parking spaceName - Name of the parkingNumber - Number of the parking meterType - Type of parkingLevel - Level of the parking spaceLevel - Level of the parking space**This third party metadata element was translated using an automated translation tool (Amazon Translate).**