cl_maintenanceAndUpdateFrequency

RI_536

92 record(s)
 
Type of resources
Available actions
Topics
Keywords
Contact for the resource
Provided by
Formats
Representation types
Update frequencies
status
Scale
From 1 - 10 / 92
  • Categories  

    Map of Quebec City railways.**This third party metadata element was translated using an automated translation tool (Amazon Translate).**

  • Categories  

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

  • Categories  

    The Aboriginal Lands of Canada Legislative Boundaries web service includes legislative boundaries of Indian Reserves, Land Claim Settlement Lands (lands created under Comprehensive Land Claims Process that do not or will not have Indian Reserve status under the Indian Act) and Indian Lands. More specifically it includes the following lands: 1) Indian Reserves that include: 1.1) surrendered lands or a reserve, as defined in the Indian Act (this definition excludes Indian Settlements and Indian Communities); and 1.2) Sechelt lands, as defined in the Sechelt Indian Band Self-Government Act, chapter 27 of the Statutes of Canada, 1986; 2) Land Claim Settlement Lands that include: 2.1) Category IA land or Category IA-N land, as defined in the Cree-Naskapi (of Quebec) Act, chapter 18 of the Statutes of Canada, 1984 (category 1B and category II Lands are excluded from this definition); 2.2) Settlement land, as defined in the Yukon First Nations Self-Government Act, and lands in which an interest is transferred or recognized under section 21 of that Act (only Yukon First Nations Settlement Lands, which were surveyed and the survey plan recorded, are included in the map service); 2.3) Inuit Owned Lands as defined in the Agreement between the Inuit of the Nunavut Settlement Area and Her Majesty the Queen in Right of Canada given effect and declared valid by the Nunavut Land Claims Agreement Act (it includes all parcels that have been surveyed and those that do not require a survey (this includes the islands)); 2.4) Gwich’in Lands as defined in the Gwich’in Comprehensive Land Claim Agreement, given effect and declared valid by the Gwich’in Land Claim Settlement Act; 2.5) Inuvialuit Lands as defined in the Western Arctic (Inuvialuit) Claims Settlement Act; 2.6) Sahtu Lands as defined in The Sahtu Dene and Métis Comprehensive Land Claim Agreement given effect and declared valid by the Sahtu Dene and Métis Land Claim Settlement Act; and 2.7) Tlicho lands, as defined in the Tlicho Agreement, given effect and declared valid by the Tlicho Land Claims and Self-Government Act; 3) Indian Lands that include: 3.1) Lands in the Kanesatake Mohawk interim land base, as defined in the Kanesatake Mohawk Interim Land Base Governance Act, other than the lands known as Doncaster Reserve No. 17. The data available for download is the former Geobase-Aboriginal Lands product. There are some attribute differences between the data available for download and the web service; however both contain the same underlying data. Please refer to the Supporting Documents for additional information on the Geobase - Aboriginal Lands dataset. Work is under way to align these two data products.

  • Categories  

    Linear layer illustrating the lot divisions present in the graphic matrix in the case of properties containing several lots. **Collection context** Maintenance process in collaboration with the evaluation department. **Collection method** Computer-aided mapping. **Attributes** * `ID_MAT_DIV` (`integer`): Identifier * `DATE_CREATION` (`smalldatetime`): Created on * `DATE_MODIFICATION` (`smalldatetime`): Modified on * `USER_MODIFICATION` (`varchar`): Modified by * `MAT10` (`varchar`): Number * `ID_MAT_DIV_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).**

  • Categories  

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

  • Categories  

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

  • Categories  

    Counts of vehicles, cyclists and pedestrians at the majority of intersections equipped with traffic lights, as well as some intersections where the installation of lights was under consideration. For each of these intersections, all located in the 19 boroughs, the number of vehicles and pedestrians was recorded at different times of a typical day. Counts may sometimes not take into account certain users (pedestrians, cyclists, trucks for example). NOTE: since 2009, the surveys also include the passage of cyclists. The counts were carried out as part of the harmonization of fires. These are therefore counts from the central services and they do not include the counts made by the boroughs.**This third party metadata element was translated using an automated translation tool (Amazon Translate).**

  • Categories  

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

  • Categories  

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

  • Categories  

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