User:Voludu2/Mapraid/Blank View history

(→‎Important!: mapraid guidelines)
(→‎Do Not Mass-Edit: some different suggested guideline on mass editing)
 
(22 intermediate revisions by the same user not shown)
Line 1: Line 1:
{{mbox|type=warning|text=MapRaid participants: please do not edit in the area of the mapraid until the time of the official announcement in [//wazemapraid.slack.com/messages/-general/ the mapraid slack general channel]. This will allow us to get good mapraid statistics.<br/><br/>
{{mbox|type=warning|text=
{{Mapraid dates
|raidname=Mapraid South Carolina 2016
|formlink=http://waze.com
|endreg=2016-01-07T0000
|startraid=2016-01-06T0000
|endraid=2016-01-07T0000}}


This mapraid page is still under construction. Please be patient as we get it ready for the upcoming raid.}}<!--
This mapraid page is still under construction. Please be patient as we get it ready for the upcoming raid.
}}<!--


remove everything up to and including the next ">" to remove that "under construction" message. --><!--
The timed statement will automatically change if you put in the correct date/ UTC times.
Remove the "under construction" notice when the page is ready to be read.
-->
-->
<!--  
<!--  
Line 19: Line 27:
dd MMM yyyy
dd MMM yyyy
'''.  
'''.  
The group will be divided into  
The participants will be divided into  
several
several
groups, one for each section. Each group will have both local and senior editors, one of which will be the "Group leader" - listed in blue below. Please direct all questions to your group leaders. The raid hosts will be available across all areas for added support.
groups, one for each section of the map. Each group will have both local and senior editors, one of which will be the "Group leader" - listed in blue below. Please direct all questions to your group leaders. The raid hosts will be available across all areas for added support.
== Mission ==
== Mission ==
Our primary mission is to handle
Our primary mission is to handle <!-- customize this to fit the needs of the mapraid area -->
<div style="column-count:2;-moz-column-count:2;-webkit-column-count:2">
<div style="column-count:2;-moz-column-count:2;-webkit-column-count:2">
* URs
* URs
Line 33: Line 41:
__TOC__
__TOC__


==Local Hosts==
==Hosts==
*''The raid hosts and ''
*''The raid hosts and ''
* ''Every participating editor who can help answer local questions. Generally:''
* ''Every participating editor who can help answer local questions. Generally:''
Line 45: Line 53:
{{AM/Editor|XXX|6|Statewide|Map Raid Organizer|badge1=rc|badge2=gc}}
{{AM/Editor|XXX|6|Statewide|Map Raid Organizer|badge1=rc|badge2=gc}}
|}
|}
== Communication ==
The main language of this mapraid is English. You can get help for translations.
When you are editing in the raid area, please [[Waze_Map_Editor/Chat#Visible.2FInvisible|set yourself visible]] and enable the [[Map_Editor_Interface_and_Controls#Live_Users|Live Users]] layer
We will use ''#''Slack Channels. There is a [http://wazemapraid.slack.com/messages/
xxx
yyy Raid general channel] and also a channel for each raid group. {{U|Please be sure to join the slack WazeMapRaid Team and join the channels for the specific MapRaid and group you are assigned to.}} If you are not already part of the WazeMapRaid slack team, '''Click here to get your [http://bit.ly/GetWazeSlackInvite Slack invitation]. Be sure to choose {{u|WazeMapRaid}} to the MapRaid question.'''  If you have trouble getting into the slack team and channels, please reach out to one of the MapRaid organizers.
WME chat can also be used. The [http://www.waze.com/forum/viewtopic.php?f=819&t=95038 WME Chat addon] is recommended.


== Groups ==
== Groups ==
<div style="float:right;">
<div style="float:right;">
<div style="width:350px;height:500px;border: solid black 2px;">Placeholder for image map</div>
<!--  
<!--  
  An image map with width 350px goes here. generate that image map at
      Do you want to learn to make an imagemap for a mapraid?
  Online Image Map Editor (http://www.maschek.hu/imagemap/index)
      https://wiki.waze.com/wiki/User:Voludu2/How_to_make_an_imagemap_for_a_mapraid
      Online Image Map Editor (http://www.maschek.hu/imagemap/index)  
      The imagemap will look something like this:
 
<imagemap>Image:Mapraid toronto map NE.png|thumb|350px|alt=Map of Toronto Area with Mapraid Toronto areas shown
poly 347 300 362 320 357 339 333 332 300 334 298 344 274 349 255 308 339 285 [https://www.waze.com/editor/?env=usa&lon=-79.43720&lat=43.69991&zoom=0 Toronto]
poly 304 337 318 331 325 338 328 350 325 357 313 361 303 355 301 345 301 345 302 342 [https://wazemapraid.slack.com/messages/mr_can-toronto Toronto Slack]
#
</imagemap>
 
-->
-->
<div style="width:350px;height:500px;border: solid black 2px;">Placeholder for image map</div>
</div>
<!-- <imagemap>
<div style="width:350px;height:1500px; border: solid black 2px;">Placeholder for group list</div>
Image:NJGroups.png|thumbnail|none|350px|alt=Map of New Jersey with Jersey Shore map raid groups shown|Click on your map raid group to edit in your area
<!--  
poly 262 34 368 48 368 85 351 81 332 96 259 92 [https://www.waze.com/editor/?env=usa&lon=-74.15595&lat=40.42833&zoom=0 01-Bay Shore]
 
poly 261 100 338 103 360 89 379 90 370 132 264 143 253 117 [https://www.waze.com/editor/?env=usa&lon=-74.14565&lat=40.30695&zoom=0 02-Red Bank]
      replace that placeholder with the actual group list:
poly 267 147 381 133 363 177 268 178 [https://www.waze.com/editor/?env=usa&lon=-74.13741&lat=40.21867&zoom=0 03-Asbury Park]
poly 277 182 361 179 357 226 281 231 [https://www.waze.com/editor/?env=usa&lon=-74.14084&lat=40.10584&zoom=0 04-Pt Pleasant]
poly 285 236 361 233 345 297 274 288 281 259 [https://www.waze.com/editor/?env=usa&lon=-74.13501&lat=39.96705&zoom=0 05-Toms River]
poly 272 292 345 301 336 356 271 469 195 423 252 355 [https://www.waze.com/editor/?env=usa&lon=-74.25002&lat=39.71082&zoom=0 06-Long Beach Island]
poly 191 430 270 478 213 553 154 545 125 528 [https://www.waze.com/editor/?env=usa&lon=-74.47627&lat=39.39979&zoom=0 07-Atlantic City]
poly 121 532 156 554 211 556 147 631 75 609 [https://www.waze.com/editor/?env=usa&lon=-74.66956&lat=39.22048&zoom=0 08-Ocean City]
poly 70 613 147 638 78 719 16 701 [https://www.waze.com/editor/?env=usa&lon=-74.86251&lat=39.02205&zoom=0 09-Cape May]
rect 378 60 440 76 [http://wazemapraid.slack.com/messages/mr_new-jersey_01 Slack New Jersey 01-Bay Shore]
rect 380 101 443 114 [http://wazemapraid.slack.com/messages/mr_new-jersey_02 Slack New Jersey 02-Red Bank]
rect 377 137 443 151 [http://wazemapraid.slack.com/messages/mr_new-jersey_03 Slack New Jersey 03-Asbury Park]
rect 363 196 428 210 [http://wazemapraid.slack.com/messages/mr_new-jersey_04 Slack New Jersey 04-Pt Pleasant]
rect 354 257 422 272 [http://wazemapraid.slack.com/messages/mr_new-jersey_05 Slack New Jersey 05-Toms River]
rect 331 374 394 391 [http://wazemapraid.slack.com/messages/mr_new-jersey_06 Slack New Jersey 06-Long Beach Island]
rect 258 512 322 532 [http://wazemapraid.slack.com/messages/mr_new-jersey_07 Slack New Jersey 07-Atlantic City]
rect 193 587 258 602 [http://wazemapraid.slack.com/messages/mr_new-jersey_08 Slack New Jersey 08-Ocean City]
rect 140 670 204 690 [http://wazemapraid.slack.com/messages/mr_new-jersey_09 Slack New Jersey 09-Cape May]
#<!-- Created by Online Image Map Editor (http://www.maschek.hu/imagemap/index) -->
</imagemap>--></div><!--


-->
<div style=" width:350px; background-color: LightBlue;">{{Username|XXX}} -- Regional Coordinator</div>
<div style="background-color: LightBlue;">{{Username|XXX}} -- Regional Coordinator</div><!--


The team list goes here.  something like
{{#widget:Iframe
{{#widget:Iframe
|url=https://docs.google.com/spreadsheets/d/1DwKr_64jkDagTmDDYCdK2-l2f1hY4yKtE7BFpaXV_Vk/pubhtml?gid=1571469040&amp;single=true&amp;widget=true&amp;headers=false
|url=https://docs.google.com/spreadsheets/d/1DwKr_64jkDagTmDDYCdK2-l2f1hY4yKtE7BFpaXV_Vk/pubhtml?gid=1571469040&amp;single=true&amp;widget=true&amp;headers=false
Line 89: Line 97:
-->
-->


<div style="width:350px;height:1500px; border: solid black 2px;">Placeholder for group list</div>
 
<br style="clear: all;" />
<br style="clear: all;" />


Line 96: Line 104:
Please read the entire MapRaid wiki. If you are still uncertain what to do about something you see on the map, please ask your group leader '''Thank You for your help with the map.'''
Please read the entire MapRaid wiki. If you are still uncertain what to do about something you see on the map, please ask your group leader '''Thank You for your help with the map.'''


<!-- keep this list short. link to other pages where possible. include  -->
<!-- keep this list short. link to other pages where possible. -->


===Mapraid UR Rules===
===Mapraid UR Rules===
<!-- usually, special mapraid rules are as follows: -->
<!--  
<!-- We will follow the [[Update_Requests_in_Waze_Map_Editor#The_resolution_process_.2F_Etiquette|usual US UR etiquette]] with one exception: During the Map raid, the wait time is reduced to  
      Usually, mapraid rules are as follows -- set the wait time (3 or 4 days).
      Otherwise, write a whole new set of Mapraid UR rules
-->
We will follow the [[Update_Requests_in_Waze_Map_Editor#The_resolution_process_.2F_Etiquette|usual US UR etiquette]] with one exception: During the Map raid, the wait time is reduced to  
X
X
days.
days.
-->


(UR rules for this mapraid)
Do not close URs if the UR contains a tag such as [NOTE], [CLOSURE], or any other [MESSAGE]. Ask the editor who created the tag.
 
=== Edit Quality and Mass Editing ===
<!-- Choose among these paragraphs below -->
You are responsible for every edit you make, whether you make it by hand or use a script. Every edit you make should meet the goals of this mapraid AND make a noticeable improvement to the map. Do not make edits simply to gain points without improving the map. If a segment is "good enough" for the waze map, do not edit it. If you edit segments previously edited by others, your name will be on these segments. This makes you responsible for any problems left on those segments, no matter who put them there originally.
 
DO NOT perform edits that affect large numbers of segments at once. We want to know who fixed what so we can understand how problems got resolved.
 


Do not close URs if the UR contains a tag such as [NOTE], [CLOSURE], or any other [MESSAGE].
If it looks like you are making unnecessary edits or hunting for points, you may be banned from this mapraid and from future mapraids. In addition, Waze will throttle your edits and points if you use scripts excessively.


=== Do Not Mass-Edit ===
[[File:Jct 4 offset align.png|frameless|right|100px]]


DO NOT perform edits that affect large numbers of segments at once. We want to know who fixed what so we can understand how problems got resolved.
=== Micro-Doglegs ===
=== Micro-Doglegs ===
We use micro-doglegs (very short geometry sections of segments) to engineer turn- vs. stay/keep/exit instructions. Zoom in very close to see these micro-doglegs.
We use [[Glossary#Micro-dogleg|micro-doglegs]] to control turn- vs. stay/keep/exit instructions. Zoom in very close to see the closely-spaced geometry nodes. Preserve them.


=== Road Types, Names, and Functional Classification (FC) ===
=== Road Types, Names, and Functional Classification (FC) ===
Line 119: Line 135:
In  
In  
XXX
XXX
, we follow the general [[Road_types_usa#Quick_reference_chart|US standards for road types]] based on the hybrid rule of FC and Route Type.
, we ... <!-- follow the general [[Road_types_usa#Quick_reference_chart|US standards for road types]] based on the hybrid rule of FC and Route Type. -->
We distinguish the 3 different types of routes found in the state as follows:
We distinguish the
* Federal: '''I-195 E''', '''US-9'''
different types of routes found in the state as follows:
<!-- * Federal: '''I-195 E''', '''US-9'''
* State: '''SR-35 S''', '''SR-72'''
* State: '''SR-35 S''', '''SR-72'''
* County: '''CR-537''', '''CR-4'''
* County: '''CR-537''', '''CR-4'''
If a road has more than one name follow the standard for [[Road_Naming_(USA)#Concurrent_names|Concurrent names on US roads]].
-->
If a road has more than one name ...<!--follow the standard for [[Road_Naming_(USA)#Concurrent_names|Concurrent names on US roads]].-->


===Road Locks===
===Road Locks===
{{Lock Standard State|SC}}
<!--
      Copy the appropriate lock standard wiki template from the appropriate wiki page
      For US mapraids, this will be from the state wiki page
 
{{Lock Standard State|xx}}
 
      Another option is to create a lock standard table from scratch. Here is an example:
 
{{Locking Standard|lede=&nbsp;|caption=South Carolina Coastal Segment Locks
|Fwy=5
|MH=4
|mH=3
|PS=2
}}
 
-->


===Places===
===Places===


===Left Turns===
===Left Turns===
;Left turns are prohibited when:
''Will there be a lot of questions about when left turns are allowed?''
<!--;Left turns are prohibited when:
:* a posted sign prohibits the left turn
:* a posted sign prohibits the left turn
:* there are two double yellow lines Sometimes, there is a raised median or diagonal striping between.This is often seen in the form of the "bubble" prior to a dedicated left turn lane,  
:* there are two double yellow lines Sometimes, there is a raised median or diagonal striping between.This is often seen in the form of the "bubble" prior to a dedicated left turn lane,  
Line 139: Line 173:
;Left turns are allowed when:
;Left turns are allowed when:
:* They are not prohibited (see above)
:* They are not prohibited (see above)
:* Left turns are even allowed across a double-yellow line into a driveway or private road or parking lot. Double-yellow lines are usually interrupted at a public street where a left turn is permitted.
:* Left turns are even allowed across a double-yellow line into a driveway or private road or parking lot. Double-yellow lines are usually interrupted at a public street where a left turn is permitted.-->


==Mapping Resources==
==Mapping Resources==
Only use sources that are allowed by Waze, like Streetview from within WME. Do not use Google Maps. Do not use Google Maps Streetview. Websites from businesses are considered allowed sources.


<!-- include any mapping resource links if available -->
{{red|Warning: If you copy information from unauthorized sources, you may be removed from this mapraid. Also, every segment or place you edited might be removed from the map. Copying information from copyrighted sources is illegal!}}
 
== Communication ==
We will use ''#''Slack Channels. There is a [http://wazemapraid.slack.com/messages/
xxx
yyy Raid general channel] and also a channel for each raid group. {{U|Please be sure to join the slack WazeMapRaid Team and join the channels for the specific MapRaid and group you are assigned to.}} If you are not already part of the WazeMapRaid slack team, '''Click here to get your [http://bit.ly/GetWazeSlackInvite Slack invitation]. Be sure to choose {{u|WazeMapRaid}} to the MapRaid question.'''  If you have trouble getting into the slack team and channels, please reach out to one of the MapRaid organizers.
 
WME chat can also be used. The [http://www.waze.com/forum/viewtopic.php?f=819&t=95038 WME Chat addon] is recommended.


== Reference Links ==
== Reference Links ==
Line 165: Line 193:


=== Recommended Tools for MapRaid ===
=== Recommended Tools for MapRaid ===
* <span style="background-color: lightgray;">overlay link</span>
<!--
* <span style="background-color: lightgray;">[//w-tools.org/PlaceBrowser Map Raid Place Browser]</span> tampermonkey/greasemonkey required
      Replace the overlay link with the right one for your raid. 
      Here is an example from the SC raid
      [//greasyfork.org/en/scripts/10538-wme-south-carolina-overlay-6-21-2015 mapraid overlay]
 
-->
* <span style="background-color: lightgray;">mapraid overlay</span> (tampermonkey/greasemonkey required)
<!--
      Below is a generic link to all the place browsers.
      Add the query string to customize it for this map raid
      Here is an example from the SC raid
      [//w-tools.org/PlaceBrowser?group=MapRaidSouthCarolina Map Raid Place Browser]
 
-->
* [//w-tools.org/PlaceBrowser Map Raid Place Browser]
 
;[http://www.waze.com/forum/viewtopic.php?t=76488 Validator]
:highlights issues on the map and can generate a very detailed report with U.S. wiki references and possible solutions.
:* [http://chrome.google.com/webstore/detail/wme-validator/baojhpeknpmkhplkcnpdcficcaaniaih For Chrome Browser]
:* [http://greasyfork.org/scripts/1571-wme-validator GreasyFork.org For Firefox] -- Tampermonkey/Greasemonkey required
 
;WME Toolbox
:This is a script that facilitate the process of editing maps in the WME. It has a toolbar that facilitates the process of removing unnecessary nodes, cut segments, locate "Soft Nodes", or nodes with undefined directions.
:* Install for [https://chrome.google.com/webstore/detail/wme-toolbox/ihebciailciabdiknfomleeccodkdejn?utm_source=chrome-app-launcher-info-dialog Chrome]
:* Install for [http://gitlab.com/doctorkb/wme-toolbox-public/raw/master/Dist/Firefox/wmetoolbox.xpi Firefox].
 
;[http://greasyfork.org/en/scripts/2103-wme-chat-addon WME Chat Addon]
:a script that  improves the WME chat GUI. For a list of all the features check the thread [http://www.waze.com/forum/viewtopic.php?f=819&t=95038 here] --  Tampermonkey/Greasmonkey required
 
;[//wiki.waze.com/wiki/User:Rickzabel/UrComments/ UR Comments]
:a tremendous time and labor saving tool with automation and integration with URO+, to help with working URs. Read the documentation.  Tampermonkey / greasemonkey required


* [//wiki.waze.com/wiki/User:Rickzabel/UrComments/ UR Comments] - a tremendous time and labor saving tool with automation and integration with URO+, to help with working URs. Read the documentation.  Tampermonkey / greasemonkey required
;[http://drive.google.com/file/d/0B8WbeRGWGEOjQ1BvbHFtYlJSV2pIOVdyQlgtRmJzQUtHNjRz WME Reference Sheet<sup><small><nowiki>[PDF]</nowiki></small></sup>]
* The [http://drive.google.com/file/d/0B8WbeRGWGEOjQ1BvbHFtYlJSV2pIOVdyQlgtRmJzQUtHNjRz WME Reference Sheet<sup><small><nowiki>[PDF]</nowiki></small></sup>] is a printable double-sided tri-fold quick reference guide to some of the common topics used in WME.
:a printable double-sided tri-fold quick reference guide to some of the common topics used in WME.
* [http://www.waze.com/forum/viewtopic.php?t=76488 Validator] is a script that validates a map area in Waze Map Editor, highlights issues and generates a very detailed report with wiki references and solutions.
** Chrome browser: please download the script at [http://chrome.google.com/webstore/detail/wme-validator/baojhpeknpmkhplkcnpdcficcaaniaih Chrome Web Store]
** Firefox browser: please download the script at [http://greasyfork.org/scripts/1571-wme-validator GreasyFork.org] -- tampermonkey or greasemonkey required
* [http://greasyfork.org/en/scripts/2103-wme-chat-addon WME Chat Addon] is a script that  improves the WME chat GUI. For a list of all the features check the thread [http://www.waze.com/forum/viewtopic.php?f=819&t=95038 here] --  Tapermonkey/Greasmonkey required


== Mapraid edit lists ==
== Mapraid edit lists ==
Line 197: Line 250:




[[Category:Mapraid]]
<!--[[Category:Mapraid]]-->

Latest revision as of 16:07, 19 February 2016

Mapraid South Carolina 2016 ended on 07 Jan 2016 00:00:00 UTC. Please check back here for results and check the Mapraid Forum for mapraid announcements. This mapraid page is still under construction. Please be patient as we get it ready for the upcoming raid.
Placeholder for mapraid meme

Optional short intro phrase. MapRaid Location Month year will be dd Mmm through dd MMM yyyy . The participants will be divided into several groups, one for each section of the map. Each group will have both local and senior editors, one of which will be the "Group leader" - listed in blue below. Please direct all questions to your group leaders. The raid hosts will be available across all areas for added support.

Mission

Our primary mission is to handle

  • URs
  • MPs
  • PURs (Places)
  • General map verification and
  • Functional Classification.

Hosts

  • The raid hosts and
  • Every participating editor who can help answer local questions. Generally:
    • rank 3 and up
    • from the state
    • with AM area
    • has been active recently
Editor Location Roles
XXX(6) [PM [Help]]  Statewide
Map Raid Organizer

Communication

The main language of this mapraid is English. You can get help for translations. When you are editing in the raid area, please set yourself visible and enable the Live Users layer We will use #Slack Channels. There is a [http://wazemapraid.slack.com/messages/ xxx yyy Raid general channel] and also a channel for each raid group. Please be sure to join the slack WazeMapRaid Team and join the channels for the specific MapRaid and group you are assigned to. If you are not already part of the WazeMapRaid slack team, Click here to get your Slack invitation. Be sure to choose WazeMapRaid to the MapRaid question. If you have trouble getting into the slack team and channels, please reach out to one of the MapRaid organizers.

WME chat can also be used. The WME Chat addon is recommended.


Groups

Placeholder for image map
Placeholder for group list



Important / Mapraid guidelines

Please read the entire MapRaid wiki. If you are still uncertain what to do about something you see on the map, please ask your group leader Thank You for your help with the map.


Mapraid UR Rules

We will follow the usual US UR etiquette with one exception: During the Map raid, the wait time is reduced to X days.

Do not close URs if the UR contains a tag such as [NOTE], [CLOSURE], or any other [MESSAGE]. Ask the editor who created the tag.

Edit Quality and Mass Editing

You are responsible for every edit you make, whether you make it by hand or use a script. Every edit you make should meet the goals of this mapraid AND make a noticeable improvement to the map. Do not make edits simply to gain points without improving the map. If a segment is "good enough" for the waze map, do not edit it. If you edit segments previously edited by others, your name will be on these segments. This makes you responsible for any problems left on those segments, no matter who put them there originally.

DO NOT perform edits that affect large numbers of segments at once. We want to know who fixed what so we can understand how problems got resolved.


If it looks like you are making unnecessary edits or hunting for points, you may be banned from this mapraid and from future mapraids. In addition, Waze will throttle your edits and points if you use scripts excessively.

Micro-Doglegs

We use micro-doglegs to control turn- vs. stay/keep/exit instructions. Zoom in very close to see the closely-spaced geometry nodes. Preserve them.

Road Types, Names, and Functional Classification (FC)

In XXX , we ... We distinguish the different types of routes found in the state as follows: If a road has more than one name ...

Road Locks

Places

Left Turns

Will there be a lot of questions about when left turns are allowed?

Mapping Resources

Only use sources that are allowed by Waze, like Streetview from within WME. Do not use Google Maps. Do not use Google Maps Streetview. Websites from businesses are considered allowed sources.

Warning: If you copy information from unauthorized sources, you may be removed from this mapraid. Also, every segment or place you edited might be removed from the map. Copying information from copyrighted sources is illegal!

Reference Links

The Basics

Recommended Tools for MapRaid

Validator
highlights issues on the map and can generate a very detailed report with U.S. wiki references and possible solutions.
WME Toolbox
This is a script that facilitate the process of editing maps in the WME. It has a toolbar that facilitates the process of removing unnecessary nodes, cut segments, locate "Soft Nodes", or nodes with undefined directions.
WME Chat Addon
a script that improves the WME chat GUI. For a list of all the features check the thread here -- Tampermonkey/Greasmonkey required
UR Comments
a tremendous time and labor saving tool with automation and integration with URO+, to help with working URs. Read the documentation. Tampermonkey / greasemonkey required
WME Reference Sheet[PDF]
a printable double-sided tri-fold quick reference guide to some of the common topics used in WME.

Mapraid edit lists

Spreadsheets and forms are being used to streamline management of various group efforts and track important edits. Below you can find links to use these these forms, sheets, and see the lists.

Results

Check back here after the raid is completed to see the results and achievements

MapRaid Promotions

Some editors really let their bright side out, and let their community skills shine. This is even more evident in a concerted group effort with high-density editing like a MapRaid!. Editors of all ranks working closely with each other and the Champs, really lets us everyone get to know each other, and allows certain editors to be recognized for their skills and effort.

When the Champs see someone consistently editing well, interacting well with the community, and knowledgeable of the various details from the Wiki, they can issue promotions. This can be anything from the size of a managed area, to a rank increase, or even a new role.

Watch here for results of promotions during and after the raid.