PesachZ wrote:The banner pointing to this thread at the top of the page is part of the banner notifying that this page is nominated to be a global page, and the link is to discuss the nomination.

On the talk page there is a link to the forum thread to discuss changes on the page.

bummerdude69 wrote:Is that SOP, to have a link to the thread on the talk page?

I've always heard (and so never looked) that the talk page was not used. If it's not SOP, I think it would be a good one.

PesachZ wrote:It is not *used* to have a discussion, but since it the defacto place for discussions in other wikis, it is commonly SOP to put a link there pointing to the direct thread for discussion since many editors will look there first.

<!--if the section parameter is defined, do not place the visible banner, only as the code block for the top of a section-->{{GlobalMark/visible}}

PesachZ wrote:The code comment you are seeing is not telling you to do anything. it is a byproduct of the implementation of {{GlobalMark}} and the fact that is employed using substitution which includes the wiki comments. This comment explains the operation of the template. I guess we should remove it so it isn't pulled into pages.

robindlc wrote:I found in this page https://wiki.waze.com/wiki/Map_Editing_ ... de#U-Turns a section about U-turns which in my opinion is not accurate or does not apply to all countryes:

NOTE: As of November 2014, it is OK but not necessary to allow the U-turn arrow where appropriate. At this time, Waze completely ignores the U-turn arrow in routing. At some time in the future, Waze might become capable of using the U-turn arrow. This advice replaces the advice from June 2014, which was to disable all U-turn arrows. As of November 2014, it is no longer necessary to disable u-turn arrows because Waze ignores them.
If you observe Waze using a u-turn arrow in routing for any reason, please notify regional or global champs immediately.
Fortunately, the lack of U-turn support can be mitigated with a workaround. User demand for U-turns usually concentrates on divided highways where drivers must make a U-turn to reach a destination on the other side of the road. If such a highway is already divided in Waze, a U-turn may be supported via a double-turn at a box junction or a hard turn at a bowtie junction. If such a highway is not divided in Waze and U-turn capability is demanded, a short section of the road near the intersection may be divided and a bowtie junction, or partial bowtie junction, inserted with the hard turn enabled. This approach effectively allows U-turn voice guidance using ordinary turn instructions. The need to support U-turns is one of the factors involved in deciding when and when not to divide a road in Waze.

As far as I know, U-turns are currently in productive with no problem (except for countries which decided not to use such feature)