Quebec data
Type of resources
Topics
Keywords
Contact for the resource
Provided by
Formats
Representation types
Update frequencies
status
-
Electoral division of the 2017 election. **Collection context** Creation of districts in collaboration with the legal services and the electoral data of the Chief Electoral Officer (DGE). Balancing of districts according to anthropogenic constraints and number of voters. **Collection method** Computer-aided mapping. **Attributes** * `ID_SEC_DIS` (`long`): Identifier * `NAME_DISTRI` (`varchar`): District name * `NO` (`long`): District number * `AREA` (`varchar`): Area * `ADVISORY_NAME` (`varchar`): Name of the advisor * `SOURCE` (`varchar`): Source * `DATE_CREAT` (`date`): Creation date * `DATE_MODIF` (`date`): Date of modification * `USER_MODIF` (`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).**
-
Pedestrian trail network. **Collection context** Updates provided by the recreation department. **Collection method** Computer-aided mapping. **Attributes** * `ID_PIETON` (`integer`): Identifier * `Type` (`varchar`): Type * `LOCATION` (`varchar`): Location * `LABEL` (`varchar`): Label * `Coating` (`nchar`): Coating * `DATE_INSTALLE` (`smalldatetime`): Installed on * `Project` (`varchar`): Projected * `LENGTH` (`numeric`): Length * `NOTES` (`varchar`): Notes * `SOURCE` (`varchar`): Source * `DATE_CREATION` (`smalldatetime`): Created on * `DATE_MODIFICATION` (`smalldatetime`): Modified on * `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).**
-
Polygon layer of the footprints of buildings on the territory of the city. **Collection context** Collection process based on site plans or location certificates provided by the urban planning department,. Secondary collection based on orthophotographs. **Collection method** Integration from plans or technical drawings using cartographic tools. **Attributes** * `ID_BUILDING` (`integer`): Identifier * `TYPE` (`integer`): Building type * `Usage` (`varchar`): Usage * `MAT10` (`varchar`): Number * `AREA` (`numeric`): Area * `SOURCE` (`varchar`): Source * `DATE_CREATION` (`smalldatetime`): Creation date * `DATE_MODIFICATION` (`smalldatetime`): Date of modification * `USER_MODIFICATION` (`varchar`): Modified by * `PLAN_DETAIL` (`varchar`): Location map 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).**
-
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 odonym 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).**
-
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 modification 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).**
-
Point layer of the registration points (centroids) of the evaluation units of the graphic matrix. **Collection context** Update provided by the evaluator or evaluation department. **Collection method** Computer-aided mapping. **Attributes** * `ID` (`integer`): Identifier * `ADM01A` (`varchar`): Municipality code * `SI0317A` (`smalldatetime`): Registration date * `SI0317B` (`integer`): Representation scale * `SI0317C` (`varchar`): Registration * `SI0317D` (`varchar`): Location * `SI0102C` (`varchar`): Section * `SI0103C` (`varchar`): Division * `UNIT_V` (`varchar`): Neighborhood unit * `NOTES` (`varchar`): Notes * `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).**
-
1 kilometer buffer zone around railway stations and rail yard areas. **Collection context** Buffer zone of 1000 meters. **Collection method** Applying a stamp using geoprocessing. **Attributes** * `Id` (`long`): Identifier * `BUFF_DIST` (`double`): Distance * `ORIG_FID` (`long`): FID 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).**
-
Polygonal zoning layer. **Collection context** Maintenance and modifications by the urban planning department according to the amendments to the zoning regulations. **Collection method** Computer-aided mapping. **Attributes** * `ID_ZONAGE` (`integer`): Identifier * `NUM_ZONE` (`varchar`): Zone number * `GROUPE_USAGE_DOM` (`varchar`): Dominant user group * `LABEL` (`varchar`): Label * `ZON_AREA` (`numeric`): Area * `ZON_PER` (`numeric`): Perimeter * `DATE_CREATION` (`smalldatetime`): Created on * `DATE_MODIFICATION` (`smalldatetime`): Modified on * `USER_MODIFICATION` (`varchar`): Modified by * `Source` (`varchar`): Source * `GRILLE_URL` (`varchar`): Link to grid 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).**
-
Sectoral division of leisure districts. **Collection context** Historical breakdown provided by the recreation department. **Collection method** Computer-aided mapping. **Attributes** * `ID_SEC_LOISIR` (`integer`): Identifier * `SECTOR_NUM` (`varchar`): Sector number * `SECTOR_NAME` (`varchar`): Sector name * `SOURCE` (`varchar`): Source * `DATE_CREATION` (`smalldatetime`): Created on * `DATE_MODIFICATION` (`smalldatetime`): Modified on * `USER_MODIFICATION` (`varchar`): Modified by * `NEIGHBORHOOD` (`varchar`): Neighborhood 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).**
-
Linear layer of the city's bicycle network. Includes multi-use trails, bike lanes, on-street networks, etc. **Collection context** Manual collection through an update process in collaboration with the engineering departments and the recreation department. **Collection method** Computer-aided mapping. **Attributes** * `ID_CYCL` (`integer`): Identifier * `VOI_NAME_CYCL` (`varchar`): Name * `WAY_TYPE` (`varchar`): Type * `PROJECT` (`varchar`): Projected * `NEIGHBORHOOD` (`varchar`): Neighborhood * `DATE_INSTALLE` (`integer`): Installation date * `LENGTH` (`numeric`): Length * `WIDTH` (`numeric`): Width * `SOURCE` (`varchar`): Source * `NOTES` (`nvarchar`): Notes * `DATE_MODIFICATION` (`smalldatetime`): Date of modification * `USER_MODIFICATION` (`varchar`): Modified by * `DATE_CREATION` (`smalldatetime`): Creation date 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).**
Arctic SDI catalogue