Résultat de l’API de MediaWiki

{
    "batchcomplete": "",
    "continue": {
        "gapcontinue": "Roles_and_responsibilities",
        "continue": "gapcontinue||"
    },
    "warnings": {
        "main": {
            "*": "Subscribe to the mediawiki-api-announce mailing list at <https://lists.wikimedia.org/postorius/lists/mediawiki-api-announce.lists.wikimedia.org/> for notice of API deprecations and breaking changes."
        },
        "revisions": {
            "*": "Because \"rvslots\" was not specified, a legacy format has been used for the output. This format is deprecated, and in the future the new format will always be used."
        }
    },
    "query": {
        "pages": {
            "250": {
                "pageid": 250,
                "ns": 0,
                "title": "Road Editing in Canada",
                "revisions": [
                    {
                        "contentformat": "text/x-wiki",
                        "contentmodel": "wikitext",
                        "*": "'''<small>[[Main Page|CLICK TO GO BACK TO MAIN PAGE]]</small>'''\n\n==Road Naming==\n\n===Highways===\nFreeways, minor highways, and major highways should be named in this format:\n\n==== Nova Scotia, Ontario, Manitoba, Saskatchewan, Alberta, British Columbia, and territories ====\n'''Hwy #''' (H is capitalized, the 'wy' in lower case, followed by a number), e.g. '''Hwy 16'''. Not \"Highway #\" or the all-caps \"HWY #\".\n\n==== Quebec, Newfoundland and Labrador, New Brunswick, and PEI ====\n'''Rte #''' (R is capitalized, the 'te' in lower case, followed by a number), e.g. '''Rte 99'''. Not \"Route #\" or \"RTE #\".\n\nAutoroute is abbreviated to Aut, e.g. '''Aut 15'''.  \n\n==== For ALL of Canada ====\n''Where the signage indicates the highway based on a name (\"Lougheed Hwy\" or \"Sooke Rd\"), the name should be used. If, however, the signage refers to it by number primarily, that is to be the primary name, regardless of the local knowledge (e.g. the Sea-to-Sky Highway is signed as Hwy 99 and Wheeler Blvd is signed as Rte 15).  If a numbered highway has local named signage as above e.g. \"Lougheed Hwy\" or \"Sooke Rd\", the highway number must be used as an alternative name.''\n\n===Big green signs===\n\nSegment naming for ramps and wayfinders should follow the big green sign (BGS) text with the following rules.\n\nSegment name should generally follow signage as read, i.e. left to right, top to bottom, except all numbered highways, should be shown first, followed by destination, followed by icons if applicable. All should be separated by a forward slash (\u201c / \u201c), with a space before and after the slsh. \u00a0Most BGS layout follows this standard.\n\nAcceptable icons to use are \u201c\u2708\ufe0f\u201d for Airport and \u201c\u26f4\ufe0f\u201d for Ferry. \u00a0You must copy and paste these exact icons as these are the only ones that work correctly with text-to-speech. \u00a0Only use icons if they are used on the BGS, i.e. do not use the icon to replace a spelled out destination such as \u201cToronto Pearson International Airport\u201d or \u201cPowell River Ferry\". You may omit airport and ferry mentions for length considerations. \u00a0\n\nFor more general information on BGS segment naming, please refer to the USA Wazeopedia sections for [[usa:Junction_Style_Guide/Interchanges#Wayfinders|wayfinders]] and [[usa:Road_names#Exit_ramps_and_entrance_ramps_.28on-ramps.29|entry/exit ramps]].\n\n===Abbreviations===\nPlease follow the [https://www.canadapost-postescanada.ca/cpc/en/support/articles/addressing-guidelines/symbols-and-abbreviations.page Canada Post street-type abbreviation] at all times even if it differs from real-life road signs.\n\nNote that while Canada Post does not abbreviate \"Place\" in French, Waze does abbreviate it as \"Pl\", just like Canada Post does in English.\n\nPlease do not shorten names when they are integral to understanding the street name:\n\n  e.g. Bad: N St, S St, Ave Rd\n  e.g. Good: North St, South St, Avenue Rd\n\nIt is recommended to use the [http://greasyfork.org/en/scripts/11907 Custom Canadian WME Validator Script]. It will highlight all the incorrectly abbreviated street names.\n\n==== Street name abbreviations ====\n{| class=\"mw-collapsible mw-collapsed\" style=\"text-align:left\" border=\"1\"\n|+\n! Approved Abbreviation\n!Pronunciation\n! Do Not Use\n|-\n|Alley ||Alley ||Aly\n|-\n|Aut||Autoroute||Autoroute\n|-\n|Av||Avenue (French)||Avenue, Ave\n|-\n|Ave|| Avenue (English)||Avenue, Av\n\n|-\n|Bend ||Bend||Bnd \n|-\n|Blvd||Boulevard||Boulevard\n|-\n| Boul||Boulevard (French)||Boulevard, Blvd\n|-\n|Brg|| Bridge||Bridge\n|-\n|Bypass||Bypass || By-pass\n|-\n|Carref||Carrefour||Carrefour\n|-\n| Ctr||Centre||Centre, Center \n|-\n|Ch||Chemin||Chemin\n|-\n|Cir||Circle||Circle\n|-\n|Circt||Circuit||Circuit, Cct\n|-\n|Close||Close||Cl\n|-\n|Common||Common||Com, Cmn\n|-\n|Conc ||Concession ||Concession\n|-\n|Crnrs||Corners||Corners,Cors \n|-\n|Crt||Court||Court, Ct\n|-\n|Cove||Cove||Cv\n|-\n|Cres||Crescent||Crescent, Cr\n|-\n|Crois||Croissant||Croissant, Croiss\n|-\n|Crossing||Crossing||Cross, Xing\n|-\n|Cds||Cul-de-sac||Cul-de-sac \n|-\n|Divers||Diversion||Diversion \n|-\n|Dr|| Drive||Drive\n|-\n|\u00c9ch|| \u00c9changeur||\u00c9changeur\n|-\n|Espl||Esplanade||Esplanade\n|-\n|Estate ||Estates||Estates, Est\n|-\n|Expy ||Expressway||Expressway, Expwy\n|-\n| Exten||Extension||Extension,Ext\n|-\n|Field||Field||Fld\n|-\n|Gate\n|Gate\n|Gt\n|-\n|Gdns||Gardens||Gardens\n|-\n|Glen||Glen||Gln\n|-\n|Green||Green||Grn\n|-\n|Grnds||Grounds||Grounds\n|-\n|Grove||Grove||Grv\n|-\n|Harbr||Harbour ||Harbour, Harbor, Hbr \n|-\n|Hts||Heights|| Heights\n|-\n|Hwy||Highway||Highway\n|-\n|Hghlds||Highlands||Highlands\n|-\n|Hill||Hill|| Hl\n|-\n|Hollow ||Hollow ||Holw\n|-\n|Imp||Impasse||Impasse\n|-\n|Inlet||Inlet|| Inlt \n|-\n|Island||Island||Is\n|-\n|Knoll||Knoll||Knl\n|-\n|Landng||Landing||Landing, Lndg\n|-\n|Lane||Lane ||Ln\n|-\n|Lmts|| Limits||Limits \n|-\n|Lkout ||Lookout||Lookout\n|-\n|Manor||Manor||Mnr\n|-\n|Meadow||Meadow||Mdw\n|-\n| Mont\u00e9e||Mont\u00e9e ||Mt\u00e9e\n|-\n|Mount||Mount||Mt \n|-\n|Mtn ||Mountain||Mountain \n|-\n|Orch||Orchard||Orchard\n|-\n|Parade\n|Parade\n|Pde, Pr\n|-\n|Pk || Park|| Park\n|-\n|Pky||Parkway||Parkway, Pkwy\n|-\n|Passage||Passage||Psge, Pass\n|-\n|Ptway||Pathway||Pathway\n|-\n|Pines||Pines||Pnes\n|-\n|Pl||Place||Place\n|-\n|Plat||Plateau||Plateau\n|-\n| Plaza||Plaza||Plz\n|-\n| Pt||Point||Point\n|-\n|Port||Port||Prt\n|-\n|Pvt||Private||Private\n|-\n|Prom||Promenade||Promenade\n|-\n|Rg||Range||Rge\n|-\n|Ridge||Ridge||Rdge\n|-\n|Rd||Road ||Road\n|-\n| Rdpt||Rond-point||Rond-point\n|-\n|Rte||Route||Route \n|-\n|Rle||Ruelle||Ruelle\n|-\n|Sent||Sentier||Sentier\n|-\n|Sq||Square||Square\n|-\n| Subdiv ||Subdivision||Subdivision\n|-\n|St||Street||Street\n|-\n|Terr||Terrace ||Terrace, Ter, Tce\n|-\n|Tsse||Terrasse (French)||Terrasse, Terr\n|-\n|Thick||Thicket ||Thicket\n|-\n|Tline||Townline||Townline\n|-\n|Trail||Trail||Tr, Trl\n|-\n|Trnabt||Turnabout||Turnabout\n|-\n|Villge||Village||Village, Vlg\n|}\n\n==Road Types and Functional Classification==\n\nMany Canadian provinces and municipalities have a standardized functional classification (FC) system which was adopted by Waze Champs as part of the method for classifying roads in Waze. Overall, this resulted in use of the highway types for arterial roads in urban areas, with the primary-street type being available for collector-type roads.\n\nUnfortunately, Canada does not have standardized government-published maps, but we can implement these principles where local governments publish road classification maps. In general, we can find such maps for any city with a population exceeding ~40,000. We can adopt FC in smaller municipalities, but finding the information will be harder and the benefit less obvious.\n\nLists of existing conversions to Waze road types may be found on the province-specific wiki pages:\n\n*[[British Columbia]]\n*[[Alberta]]\n*[[Saskatchewan]]\n*[[Manitoba]]\n*[[Ontario]]\n*[[Quebec]]\n\n===Roads in cities===\n\nAs a highway enters a city/town, it often becomes a named street, and sometimes would no longer fit the usual criteria for a \"highway\".\n\nDue to a number of reasons, including long-distance routing issues, as well as appearance, the highway should remain the same type as it is when it enters the city/town. \n\nIf a freeway no longer fits the freeway criteria, it may be downgraded to major highway with preferred routing until it again satisfies freeway criteria. One examples of this includes parts of the Trans-Canada Highway that travel through national/provincial parks with frequent stops, reduced speed, and undivided portions. Another example is Autoroute 20, which becomes [https://waze.com/editor?env=usa&lat=45.38056&lon=-74.01121&zoomLevel=15&segments=60580760,60698144,60709267,60734375,60747969,60753523,60758703,60872561,60892610,68797130,68797173,68797191,68797199,68797201,68866615,71607450,75593591,75593592,75593610,78820960,78820961,78912229,78912488,78912508,78912509,78912530,78912558,78912596,78912659,78912699,78912700,78912754,78912755,78914267,78914268,78914353,78914471,78914472,501865623,501865624,501865638,501865639,513794963,513794966,513794967,521967011,521967012,521967139,521967140,524155180,524155181,528166166,530572739,530572740,531676678,531676679 Boul Harwood] in Vaudreuil-Dorion, Quebec.\n\n====Freeway (Fwy)====\n\n{{Freeway| style= display: inline-block; width: 400px; height:15px;| }}\n\nIn general, freeways will have:\n\n*multiple lanes of divided roads;\n*no cross traffic;\n*no stop lights (except for ramp meters) or stop signs;\n*no parking;\n*no stopping (except for [[:USA:Toll roads|toll booths]], freeway-access metering, movable bridges, and traffic congestion);\n*minimum speed limits;\n*limited access for pedestrians, bicycles, mopeds, and animal-drawn vehicles; and\n*entrance and exit ramps.\n\nUse these freeway criteria as a guideline. A freeway may lack one or more features but still be classified as such (e.g. Hwy 16 west of Edmonton doesn't have ramps for every junction, but meets all other criteria).\n\n====Major highway (MH)====\n\n{{Major Highway| style= display: inline-block; width: 400px; height:15px;| }}\n\nUse these for major arterial roads. Often, these have two, three, or more lanes in each direction, and may be structured to be turned into freeways eventually. Usually this means relatively few intersections, higher speed limit, and higher capacity.\n\nAdditionally, if a road enters an area as a freeway, then loses its limited-access situation, it will generally continue as a major highway.\n\nIf a municipality uses only one type of arterial road on its maps, the Waze map editor's decision between setting a MH or mH will rely on relative importance, capacity, and local classification or custom. Generally, a MH will have two or more lanes, whereas a minor may only have one. Local knowledge is especially useful - for example, many 100-level routes in Quebec are one lane in each direction yet are classified as MH.\n\n====Minor highway (mH)====\n\n{{Minor Highway| style= display: inline-block; width: 400px; height:15px;| }}\n\nUse mH for arterial roads. They are more direct than using collector roads and sometimes have slightly higher speed limits.\n\n====Primary street (PS)====\n\n{{Primary Street| style= display: inline-block; width: 400px; height:15px;| }}\n\nSuitable for collector roads through neighbourhoods and thoroughfares that aren't arterial.\n\n==== Private road (PR) ====\nPrivate roads (PR) should be used for roads or networks of roads in complexes like military bases, industrial truck access, campgrounds, cemeteries, etc.     \n\nAnother proper use of private roads is for bus-only roads or drive-through service at restaurants or banks where the only possible destination is to use that service.     \n\nUse private roads when converting any standard road that to limit through-traffic to traffic that should reach only a destination on that road (such as for long-term construction that allows only local traffic) yet must retain its speed data. PR segments record and access speed data. Parking-lot roads (PLR) do not.    \n\nUse a PLR for all other cases. See the section on [[Road Editing in Canada#Alleys and Laneways|Alleys and Laneways]] below for more information.   \n\n==== Ferry ====\nOnly map ferries that can carry standard cars. If the ferry has a toll, mark it as a [[:USA:Best_map_editing_practice#Toll_roads|toll road]]. You can find more guidance on the US [[usa:Ferries|Ferries]] page.\n\n====Narrow street / Passageway====\n\n'''Never''' use the narrow street or passageway type in North America. This street type designates segments only wide enough for a scooter and will only permit routing for users with the motorcycle type of vehicle selected.\n\n[[File:Emergency.jpg|right|300px|Emergency.jpg]]\n===Emergency-vehicle roads===\nRoads meant for \"Emergency and Authorized Vehicles Only\" are to be treated as non-drivable roads. These are found primarily through the median of divided highways to connect opposite direction lanes. We recommend not to map them in Canada. \n\n==Alleys and Laneways==\n\nAlleys and laneways (hereafter referred to simply as alleys) should be added to the map. This is a change in the Waze standard that is going into effect across all of Canada. The proper road type to use for these segments is parking-lot road (PLR), not private road (PR) no matter how much Webs101 whines.\n\n=== Principles ===\nAllowing unobstructed routing into an alley is appropriate in the following circumstances:\n\n* When no stopping is permitted on the street which the destination faces, and there is access available from the rear. (This does not mean that alleys should be omitted if stopping is allowed on the main road.)\n* The alley is used to access carriage / infill homes.\n* The alley provides access to exclusive-use parking for venues or homes. (A secondary entry point for certain venues that normally have an entrance accessed from the main road may use the alley.)\n* The alley has a street name and has addresses only accessible via the alley.\n\nHouse numbers do not provide for direct-to-door navigation on PLRs or PRs, so places with entry points (including residential place points) must be used to force routing to destinations on these segments if the destination requires a stop on the PLR.\n\n=== Editing practices ===\nAlleys should have a city name set and the \u201cNone\u201d box checked for street name unless a name is displayed on official signage or can otherwise be verified. Use a PLR even if the street has a name (previously, we would use PRs). \n\nPay particular attention to turn restrictions and directionality. Use Street View and satellite imagery to look for signage or arrows painted on the ground indicating one-way travel or turn restrictions.\n\nAfter a tile build, perform spot-testing of navigation to both named destinations as well as addresses to ensure users will not be routed into the alley inappropriately. Add places with entry points on the main road as appropriate to correct undesired routing behaviour.\n\nWhen adding alleys, pay attention to the potential for inadvertent routing into the segment. Waze\u2019s routing engine will consider contiguous PLR segments - even those linked across nodes at standard road types \u2013 to be united as one parking-lot unit. As a result, it may route users into the alley network prematurely if traffic conditions dictate. If route-testing or user reports indicate evidence of this behaviour, \"continue straight\" turn arrows can be marked as full-time difficult turns or even blocked turns between alleys.\n\nLeft turns into or out of alleys at junctions with busy roads may be set as difficult turns fully or during daytime hours to limit impact to traffic flow at editor discretion.\n\nPer standard guidance, alleys with restricted or difficult turns should be locked to L3 or higher to ensure the configuration is preserved.\n\nSome cities have a number of streets that are effectively alleys, but have addresses on them. Continue to use PLRs to map these, and add places to enable routing to these locations. If access is restricted by gates or bollards use the PR road type. Places must also be added to facilitate routing on PRs.\n\n=== Helpful scripts ===\n[https://greasyfork.org/en/scripts/26340-wme-place-interface-enhancements WME Place Interface Enhancements] (PIE) can greatly speed up the creation of places, particularly RPPs.\n\n[https://greasyfork.org/en/scripts/28690-wme-place-harmonizer WME Place Harmonizer] expedites creation of new places by standardizing names, supplying websites for known chains, and parsing phone numbers and hours of operation that editors gather from websites.\n\n[https://greasyfork.org/scripts/369629-wme-clicksaver WME ClickSaver] can streamline creation of PLR and PR segments.\n\nPlease see the [[usa:Scripts|US Wazeopedia page for scripts]] if you are unfamiliar with the basics of adding scripts for WME.\n\n==Rural Roads==\nCottaging, camping, and other backcountry activities are popular pastimes nationwide, and rural resource extraction occurs in every province and territory. As such, major logging, forestry, resource, and other similar backroads should be added to the map. \n\nThis is a change in the Waze standard that is going into effect across all of Canada. Waze\u2019s community-built map has the potential to serve destinations that are not covered by most navigation apps and by providing a framework in remote areas for users to be able to build upon, we can grow both our user base and ultimately the editing community.\n\nWe see a lot of these roads being added through Project Koifish. It behooves us to understand these rules to further the success of that undertaking.\n\n===Editing practices===\nThe proper segment type to use for these segments is more nuanced than other categories of roads because of the way they are treated by the routing engine, but the most common road type to use is off-road/not maintained (OR). \n\n'''Important:''' There are two kinds of off-road/not maintained setting. There is the standard OR road type in WME. But there is also a reason for rejection in the Project Koifish interface that lists off-road/not maintained as a reason for rejecting the suggested segment. You can see this in this screen shot:\n\n[[File:Canada-Koifish-offroad.png|810x810px|Canada-Koifish-offroad|bordure|centr\u00e9]]\n\nThis advice means that we should ignore this reason for rejection. (The same goes for alleys, which, as of this document, the standard is to map.)\n\nWaze will not use a stop point on an OR segment. Destinations along these roads must ultimately be accessed via PLR, PR, or another public road type. \n\nIf a road\u2019s existence cannot be confirmed by imagery or another eligible source, do '''not''' add it to the map. That does not necessarily mean to reject it. If there is clear indication that a road has been deactivated permanently, delete it. We do not need to add every spur road (although we should if Koifish presents any), but the primary routes should be represented.\n\nDepending on jurisdiction, this category of road is often not part of a city. The \"None\" box should be selected for city name unless a county or other secondary administrative layer has been implemented in the area. Exceptions can be made on the fringes of towns and cities to enable routing to rural homes and other venues accessed by these roads.\n\nRemote venues such as parks, recreation areas, campsites, and destination lakes/rivers should have the rural road network extended to them to facilitate navigation when possible. Note that this is applies only to logging/forestry/resource roads. Standard practice applies on the standard public or private road networks.\n\nMost jurisdictions have default speed limits which apply when no speed limit signs are posted. These speed limits should be added.\n\nSet the unpaved attribute as appropriate, including on segments using the OR segment type.\n\nRoads known to be maintained and passable year-round may use local street or higher classifications at editor discretion. \n\nRoads in this category that are gated or that are otherwise forbidden for general public use should be mapped as private (PR). Complete mapping in this instance is optional, but short stubs that branch off the main road may provide helpful visual reference for users.\n\nIn the event of significant highway closures, route-testing in the area may be prudent in\u00a0 order to confirm that these roads are not recommended to users instead of the next best highway. Additional backcountry closures can prevent undesired routing.\n\n=== Prairie grid roads ===\nStarting in northeastern British Columbia and extending to the southeast of Manitoba, there is an almost continuous network of grid roads providing access to rural properties, towns, and other destinations. The grid is based on the Dominion Land Survey that was conducted when Canada took possession of Rupert\u2019s Land from the Hudson\u2019s Bay Company. The grid spacing is typically one mile for longitudinal (north-south) roads and one or two miles for latitudinal (east-west) roads with occasional deviation to account for geography. Major highways often coincide with the lines a grid road would otherwise occupy, typically with softened corners to facilitate higher speed travel.\n\n==== Naming grid roads ====\nEach province has in place its own naming conventions. Longitudinal roads are differentiated from latitudinal roads in the naming scheme.\n\nIn British Columbia\u2019s Peace River region, grid roads are simply named Road with a number incrementing sequentially as you progress westward (starting with 201 Rd near the Alberta border) and northward (starting at 200 Rd south of Pouce Coupe). The numbers do not correspond to numbers established in the Dominion Land Survey.\n\nAlberta uses longitudinal Range Roads and latitudinal Township Roads. The Range Road numbering scheme relates to meridian lines established in the [[wikipedia:Dominion_Land_Survey|Dominion Land Survey]] (DLS). The Range Road numbering system repeats with each DLS meridian, requiring further definition to differentiate them. In Waze, we are using provincial counties as cities to serve rural areas and provide this differentiating factor. Township Road numbers increment northward from the 49th parallel in a non-repeating manner. See [[wikipedia:Alberta_Township_System|Alberta Township System]] for specifics.\n\nSaskatchewan uses non-repeating longitudinal Range Roads incrementing as you progress westward, and latitudinal Township Roads which increment northward from the 49th parallel. See [[wikipedia:Roads_in_Saskatchewan#Township_roads_and_range_roads|Roads in Saskatchewan]] on Wikipedia for specifics.\n\nManitoba uses a non-repeating scheme of sequential longitudinal roads originating at the Principal Meridian (97\u00b027\u203228.41 or -97.45789167 W) and counting upward east and west of this line. (...Rd 2 W, Rd 1 W, Meridian Rd, Rd 1 E, Rd 2 E\u2026). Latitudinal roads start at the 49th parallel and increment sequentially northward. (Rd 1 N, Rd 2 N\u2026) Manitoba grid roads are spaced one mile apart in both orientations.\n\nAbbreviations: Range and Road are abbreviated per [https://www.canadapost-postescanada.ca/cpc/en/support/articles/addressing-guidelines/symbols-and-abbreviations.page Canada Post guidelines] as Rg and Rd respectively. Township is not included on this list, but is used in a [https://www.canadapost-postescanada.ca/cpc/en/support/kb/addressing/municipal-abbreviations/municipality-abbreviations-ontario Canada Post municipality abbreviation]. As such, it is recommended for use in Waze.\n\n=== Best practices and functional classification in rural areas ===\nAs the map matures, our reach into more remote areas becomes greater. Application of our editing standards to previously untouched basemap brings the need to extend further in order to ensure optimal user experience.\n\nMapping of the national and provincial/territorial highway networks is functionally complete, but accurate mapping and classification of roads can leave these segments at a disadvantage for consideration by the routing engine.\n\nExample: 600 & 700 series tertiary highways in Saskatchewan have been mapped mostly as minor highways (mH) with a negative routing preference and are unpaved. These factors combined left them with lower standing than the surrounding basemap streets, which were originally imported as primary streets (PS) with neutral routing preference and not marked unpaved (these extra attributes did not exist at the time of import). In order to best ensure that the routing service selects the higher quality mH roads, functional classification must be implemented:\n\n* Most grid roads should use be set to be local streets.\n* Major grid roads that do not bear a highway number should use the PS segment type. These are usually visible on official maps whereas lower classified grid roads are not.\n* Tertiary highways (sometimes referred to as \"municipal roads\") are typically mapped as mH with a negative routing preference (mH-). This provides increased visibility while limiting their use in long routes.\n* Provincial highways and higher classified routes are mapped in accordance with national or local standards for functional classification.\n* Use the \"unpaved\" attribute where appropriate.\n* Soft-surfaced dirt roads may be mapped as OR if they are not suitable for through traffic on a regular basis. Roads that clearly degrade after an entrance to a property can be cut and the resulting segments classified separately to encourage routing to send users via the better road.\n* Exclusive-use roads that serve individual properties and oil rigs should be mapped as private roads.\n\n== Speed Limits==\n\nPlease refer to the [[usa:Speed_limits|USA Speed Limit]] guidelines.\n\n===Temporary construction speed limits===\n\nDo not change the speed limit due to temporary construction in general. If you are a local editor and you want to track the worksite, you may assume full responsibility for changing, tracking, and updating temporary speed limits.\n\n===Advisory speed limits===\n\nAdvisory speed limits on ramps and similar roads are not legally enforceable. These usually appear on yellow roadsigns. Read the USA [[:USA:Speed_limits/USA#Advisory_speed_limits|advisory speed-limit guidance]] for more details. \n\n===Time-based speed limits===\nAlthough some roads may display speed limits that vary by time of day, the WME cannot accept variable speed limits and the Waze apps cannot display them. For segments with variable speed limits, use the speed limit that is in effect during hours of most traffic, which usually means weekly business hours.  \n==Parking lots==\n\nPlease read the [[:USA:Best_map_editing_practice#Parking_Lots|Best Map-Editing Practice]] on [[:USA:Road_types#Parking_Lot_Road|parking-lot roads]]. All parking aisles are to be mapped. US champs recommend enabling U-turns at the end of aisles, but this should not be done in Canada.\n\n==U-Turns==\n\nWaze allows U-turns at junction nodes or over a series of segments. U-turns at junction nodes are often barely possible if at all and drivers generally dislike them. The standard in Canada is to never enable the U-turn at nodes. Unlike US editing practice, this rule also applies to parking-lot roads in Canada.\n\nWaze can recognize U-turns ove a series of segments at H or # style intersections on divided and parallel roads, like these:\n\n[[Fichier:U-turn_Roads.png|alt=]]\n\nWaze will recognize such a turn when all three of these conditions are met: \n\n#'''Three segments -''' The U-turn is a reversal of driving direction through three segments: an incoming segment&nbsp;(A), a single median/crossing segment&nbsp;(B), and an outgoing segment&nbsp;(C).\n#'''Short median -''' The median segment&nbsp;(B) is less than 15.0 metres long. Note that the WME rounds decimal places to the closest integer. A segment that is 14.8 metres long and a segment that is 15.4 metres long will both appear to be 15 metres long in the WME although they will behave differently in U-turn recognition. Always adjust such median segments to 14 metres and less or 16 metres and more to trigger the U-turn behaviour you desire.\n# '''Parallel segments in and out -''' The in and out segments (A&nbsp;and&nbsp;C) are [[usa:Routing_penalties/Controlling_U-turn_penalties#Checking_for_parallel_incoming_and_outgoing_segments|within \u00b15\u00b0 of parallel]] to each other. The sum of the angles through the U-turn must measure between 175\u00ba  and 185\u00ba .\n\n{{Mbox|type=important|text=It is possible for this method to fail to recognize a U-turn when it is the first segment of a route or it immediately follows a reroute.}}\n\nThe default condition in Canada is to have the Waze routing algorithm prevent U-turns through median segments 15.0 metres (or less) long. The US allows them. The rationale for this decision is that most standard vehicles have a turn radius of 10-15 metres, making such U-turns difficult in all but perfect conditions.  \n\n===How to prevent U-turns===\nThe best way to prevent a U-turn through a junction that would permit it by geometry is with a junction box (an editor rank of 4 or above is required to install a junction box).\n\nIf you can establish all required prevention of U-turns with that junction's standard turn restrictions, use those to prevent a U-turn. This situation is most commonly found at three-way intersections.  \n\nThe only other way to prevent U-turn routing through a geometry that would permit it is to artificially narrow the median segments to less than 15 metres. This used to be the preferred method but is now obsolete.\n\n=== How to enable U-turns===\nSometimes you have a geometry that by default would not allow a U-turn in Waze but it is important to allow one for user navigation. One example is a destination on the other side of a divided road that would otherwise require an excessive detour to get to.\n\nAgain, the easiest way to enable a U-turn through a geometry that would prevent it is with a junction box. Junction boxes overrule all default conditions inside them.\n\nThe other way to enable a U-turn through a median segment that measures less than 15 metres is to create a node on it, but we do not recommend this. Nor do we recommend artificially widening a junction to create a median segment larger than 15.0 metres.\n\n===Where to enable U-turns===\nEvery province maintains its own road code. In Quebec, for example, you can make a U-turn at any intersection unless it is forbidden by a sign or you must cross a solid lane marker line to do so. \n\nDespite provincial regulations, we generally discourage U-turns because they provide a poor experience for the Waze user. Use your discretion in accordance with local regulations.\n\nHere are the provincial regulations we have found. It is important to note that some municipalities have their own U-turn restrictions. For example, Saskatoon has rules that are not aligned with provincial regulations.\n\nBritish Columbia references - [http://www.bclaws.ca/EPLibraries/bclaws_new/document/LOC/freeside/--%20M%20--/46_Motor%20Vehicle%20Act%20RSBC%201996%20c.%20318/00_Act/96318_05.xml#section168 Motor Vehicle Act of British Columbia Chapter 318 - Section 168]\n\nAlberta references - [https://kings-printer.alberta.ca/documents/Regs/2002_304.pdf Use of Highway and rules of the road regulation - Alberta Regulation 304/2002 - Division 7 Pages 28-31] \n\nSaskatchewan references - [https://www.sgi.sk.ca/handbook/-/knowledge_base/drivers/turning#:~:text=U%2Dturns%20are%20prohibited%20at,most%20extreme%20left%20driving%20lane. Saskatchewan Driver's Handbook]\n\nManitoba references - C.C.S.M. c. H60 [http://web2.gov.mb.ca/laws/statutes/ccsm/h060e.php#191 The Highway Traffic Act: Section 191]\n\nOntario references - R.S.O. 1990, c. H.8, s. 143. [http://www.e-laws.gov.on.ca/html/statutes/english/elaws_statutes_90h08_e.htm#BK245 Highway Traffic Act]\n\nQuebec references - The [https://www.legisquebec.gouv.qc.ca/en/tdm/cs/C-24.2?langcont=fr Highway Safety Code] does not specifically mention U-turns, so they are allowed at any intersection unless expressly forbidden by signs or other restrictions such as crossing solid lines.\n\nNew Brunswick references - [https://www.canlii.org/en/nb/laws/stat/rsnb-1973-c-m-17/latest/rsnb-1973-c-m-17.html#sec162subsec1 New Brunswick Highway Act - Section 162(1)]\n\nPrince Edward Island references - [https://www.princeedwardisland.ca/sites/default/files/legislation/h-05-highway_traffic_act.pdf PEI Highway Safety Act - Section 182]\n\nNova Scotia references - [https://www.canlii.org/en/ns/laws/stat/sns-2018-c-29/latest/sns-2018-c-29.html Nova Scotia Highway Act - Section 158]\n\nNewfoundland and Labrador statute - [http://www.assembly.nl.ca/Legislation/sr/statutes/h03.htm#116_ RSNL1990 Chapter H-3: Highway Traffic Act, s116]\n==Dividing and un-dividing roadways==\n===When to divide a two-way road (and when not to)===\nGenerally, a road should not be divided unless it meets any of the requirements for dividing a road. When initially reviewing whether to divide or \"un-divide\" (merge back together) a roadway, consider these points first:\n#Consult the Local / Global Champ for your area of the country before dividing/un-dividing.\n#The default representation for any roadway is a single two-way segment, even if the physical roadway is divided. Dividing a roadway carries with it the burden of proof that the change will improve the usability and/ or simplicity of the Waze map.\n#If a road is currently working with no problem reports, consider leaving it as is.\n#Try to avoid switching roads back and forth between being divided and two-way. For example, if most of the road is clearly divided and only parts would be considered a single two-way road, consider leaving it all divided. If only a small portion seems better off divided, consider keeping it all two-way.\nCurrent guidance from Waze developers is to divide the road \"if a Corvette can't drive across the middle\". \n\nif you divide a road, you must examine all the junctions you have created for proper [[Road Editing in Canada#U-Turns|U-turn behaviour]] in accordance with the Canada standard.\n\n====A road may be divided when <u>any</u> of the following conditions are met:====\n*It is a limited-access highway using the \"Freeway\" road type.\n*GPS tracks show a clearly definable and continuous gap (blank area) between the color-by-azimuth arrows at the 100m/500ft zoom level.\n*Multiple houses or businesses with no off-street parking are located directly on the street but are not accessible from the opposite direction of travel due to a long median, obstruction, or traffic control signage.\n*U-turns are required to properly make turns from public drivable road types that are blocked by a median.\n\n====A road should <u>not</u> be divided when:====\n*There is a center turn lane (any width) between directions of travel. Dividing this type of road creates problems when people turn from the middle lane because there is no road for the navigation to follow.\n*The objective is ''solely'' for visual appearance or to make the road match another visual source like Google Maps.\nRemember that dividing and un-dividing roads each comes with its own set of problems. Each situation is unique and some issues may be more manageable with a single two-way road, and some may work fine with a divided road. Consider every aspect of routing, and carefully examine each junction before dividing or un-dividing. Regardless of whether you're dividing or un-dividing, remember that you might cause more problems than you solve and you might have to put it back the way it was before. Also remember that dividing and un-dividing each cause loss of some traffic data, which can result in poor Waze routing for a few weeks at least.\n\n===How to un-divide two one-way roads===\nUnfortunately, there is no easy way to merge two one-way roads back into a two-way road - which is why you should always give a lot of thought before dividing a road in the first place. And then think some more.\n\nWhen you come across a road in your area that has been divided but shouldn't have been, you have some major map surgery ahead of you. Because of this high complexity in this process, it is recommended NOT to merge the two one-way roads UNLESS there are update requests related to the road caused by it being divided.\n\n{{Red|The process to un-divide a road (convert from two one-way roads to one two-way road) written below has been specifically designed to preserve the underlying address information embedded in the street segments. It is very important that you do not simply delete one of the two roads because that deletes the house address data on that part of the road. They would have to be looked up and manually added back to the new road.}}\n\nThe steps below show how to properly merge two one-way roads and preserve the underlying house numbers.\n\nThis is our example road segment.  For the entire length of the road you need to:\n\n[[File:DivideRoads 2018 00001.png]]\n\n1. Select the two segments to be merged and set them both to two-way.\n\n[[File:DivideRoads 2018 00002.png]]\n\n2. Disconnect both segments from one side of the section being un-divided. It is best to disconnect alternate ends of each segment as shown.\n\n[[File:DivideRoads 2018 00003.png]]\n\n3. Bring the two disconnected ends together in the middle (and realign the roads as necessary, removing the unnecessary segments as shown). You can remove the junction point you just created by selecting it and clicking the trash can icon or using the Delete key (Fn + Delete on Mac). Please note that the two aligned sections must have matching road information (name, type, direction, speed limit, elevation, and lock) or the junction point will not allow removal!\n\n[[File:DivideRoads 2018 00004.png]]\n<br />\n{{clear}}\n[[File:DivideRoads 2018 00005.png]]\n\nThe following video was recorded by an editor merging two one-way roads so the addresses were preserved. This video follows the described steps above but may help seeing it happening in real time. Press the \"enlarge button in the lower right corner to see it full screen.\n\n[https://www.youtube.com/watch?v=6blRMtGwaYA Un-Dividing Roads and Preserve HN - Video Reference]<br />[https://youtu.be/rkrxrz-gIC0 Un-Dividing Roads WME 2018 - Video Reference]\n\nAfter BOTH sides are merged into one, you need to re-align house number to the street so that it lines up with driveway/entrance of the building the bubble is over.\n\n#With the street/road selected, click \u2018Edit house numbers\u2019.\n#From the house number editing view, you need to select each house number one-by-one.\n#With the house number selected, you see the dashed line is attached to a circle on the street.\n#Select the circle and move it along the road closest to the entrance of the driveway to the building.\n\nAlso be sure to check the following:\n\n#Remove all \"orphaned\" junctions.\n#Change the direction of the preserved segments to two-way.\n#Check/fix the connectivity of all the roads already connect to the side you kept.\n#Connect (and set connectivity) of all the roads that used to be connected to the other side.\n#Make sure all the new two-way segments are connected.\n#Adjust the geometry to move the two-way road segments to the middle of the road.\n\nNow repeat the entire process for the remaining segments matching the two opposite from each other. It isn't difficult once you have gone through the process a couple of times.\n\n'''Caveat:''' If you decide to be clever and edit the road properties of multiple segments at a time, first familiarize yourself with the known problems with mass-editing.  It can be done - but if you're not careful, you'll find that all the road segments have reverted to streets and any alternate road names are lost."
                    }
                ]
            },
            "240": {
                "pageid": 240,
                "ns": 0,
                "title": "Road Shields",
                "revisions": [
                    {
                        "contentformat": "text/x-wiki",
                        "contentmodel": "wikitext",
                        "*": ""
                    }
                ]
            }
        }
    }
}