Difference between revisions of "Šablóna:Key press"

From Wazeopedia
m (2 revízie)
 
(25 intermediate revisions by 3 users not shown)
Line 1: Line 1:
A new program is being tested that links volunteer pilots with Waze volunteer map editors.  The pilots submit aerial photographs of new and changing roads so that Waze users can have the most accurate and up-to-date navigation available.
+
{{key press/core|{{{1|}}}}}<!--
 
+
-->{{#if:{{{2|}}}|{{{chain first|{{{chain|+}}}}}}{{key press/core|{{{2}}}}}}}<!--
==Information for Requesters==
+
-->{{#if:{{{3|}}}|{{{chain second|{{{chain|+}}}}}}{{key press/core|{{{3}}}}}}}<!--
 
+
-->{{#if:{{{4|}}}|{{{chain third|{{{chain|+}}}}}}{{key press/core|{{{4}}}}}}}<!--
In addition to the [[Munching#Munching|Munching]] system for confirming new roads and GPS points in the [[Waze_Map_Editor|Waze Map Editor]], map editors can request aerial photographs of places that are confusing or represent changes since the last satellite images were taken.  By having a recent photograph, map editors can ensure the road topology is correct, account for on/off ramps, etc.
+
-->{{#if:{{{5|}}}|{{{chain fourth|{{{chain|+}}}}}}{{key press/core|{{{5}}}}}}}<!--
 
+
-->{{#if:{{{6|}}}|{{{chain fifth|{{{chain|+}}}}}}{{key press/core|{{{6}}}}}}}<!--
Look at the example pictures (BELOW).  You can expect aerial photographs to confirm
+
-->{{#if:{{{7|}}}|{{{chain sixth|{{{chain|+}}}}}}{{key press/core|{{{7}}}}}}}<!--
new roads and intersections, see ramps, see direction markings on the roads.  You will
+
-->{{#if:{{{8|}}}|{{{chain seventh|{{{chain|+}}}}}}{{key press/core|{{{8}}}}}}}<!--
not be able to see things like road signs.
+
-->{{#if:{{{9|}}}|{{{chain eighth|{{{chain|+}}}}}}{{key press/core|{{{9}}}}}}}<!--
 
+
-->{{#if:{{{10|}}}|{{{chain ninth|{{{chain|+}}}}}}{{key press/core|{{{10}}}}}}}<!--
===Format for Requests===
+
-->{{#if:{{{11|}}}|[[Category:Wikipedia keypress template parameter needs fixing]]}}<noinclude>
 
+
{{documentation}}
During the trial phase of Aerial Photograph Requests, map editors should submit requests to the Waze Forum (HERE-TBD).  The format of a request should include in the subject line A)geographic part of a state and B) nearest major city (avoid township names).  Example: "Central PA, Harrisburg area"
+
<!-- add category and language links to the /doc sub-page, not here -->
 
+
</noinclude>
The content of the forum request should include:
 
 
 
* link to [[Waze_Map_Editor#Permalink|Permalink]] to the area of interest that has the roads of interest highlighted.
 
* a description of what the picture should convey
 
 
 
The description should highlight of the editor is needs a broad picture of an area, or focus on just one particular intersection.
 
 
 
==Information for Pilots==
 
 
 
Since Waze uses a "crowd sourced" map using content from volunteer editors, pilots can help the process by providing aerial photographs of new and changing roads.  When pilots are practicing and looking for a good excuse to go fly, snapping pictures along the route can help the volunteer editors and ultimately the driving community.
 
 
 
===Getting Started===
 
 
 
A list of participating pilot volunteers is (HERE at bottom of page).  Sign up or contact wazeflyer at gmail dott com for assistance.  Showing your availability will help Waze map editors know that there is a pilot in their area and encourage filing requests.  In addition browse the request area (HERE TBD) to see if any there are any requests in your area already.
 
 
 
*Create a Waze login (HERE) (so you can see the map)
 
*Create a Waze Forum login (HERE) (so you can interact with editors and pilots)
 
 
 
===General Guidelines===
 
 
 
Guidelines for participating:
 
 
 
*Be current! (physical, BFR)
 
*Be safe!
 
*#if possible have a copilot take the pictures (brief them on the location before beginning the flight)
 
*#clearing turns before circling an area
 
*#eyes watching for traffic!
 
*#watch airspeed while turning
 
*Fly in good wx (no point photographing a road through clouds!)
 
 
 
Pilots are strictly volunteering their time to support the map editors and fellow drivers.  There is no compensation availability from Waze for volunteers.
 
 
 
===Guidelines for taking pictures===
 
 
 
*use a good camera if you have access to one
 
*best is to photograph straight down from above (to reduce distortion in road lengths and angles)
 
*if possible and safe select a lower altitude (eg, 1000-2000 ft AGL)
 
*it may help to take multiple pictures of the area from different angles
 
 
 
 
 
===Guidelines for submitting pictures===
 
 
 
*respond to the forum request first with an approximate time frame you expect to complete the "mission"
 
*after taking the photograph, upload the picture online (a free google account will allow this)
 
*respond to forum request with an online link to the photograph
 
 
 
==Available Pilots==
 
 
 
{| border="1" cellpadding="2"
 
|- align="center"
 
! scope="col" width="100pt" bgcolor="#0080FF" | Username
 
! scope="col" width="200pt" bgcolor="#0080FF" | Flying Area
 
! scope="col" width="200pt" bgcolor="#0080FF" | Comments
 
 
 
|- align="center"
 
| [http://www.waze.com/forum/memberlist.php?mode=viewprofile&u=16949243 Cpttim]
 
| SE and Central PA
 
|
 
 
 
|}
 
 
 
 
 
For help adding your name to the pilot, send message to [http://www.waze.com/forum/memberlist.php?mode=viewprofile&u=16949243 Cpttim].
 

Latest revision as of 20:52, 19 June 2016

Documentation icon Template documentation[view] [edit] [history] [purge]

This template automatically displays a documentation box like you are seeing now, of which the content is transcluded from another page. It is intended for pages which are transcluded in other pages, i.e. templates, whether in the template namespace or not.

Usage

Normal

<noinclude>{{documentation}}</noinclude>
 - or -
<noinclude>{{doc}}</noinclude>
 - or -
<noinclude>{{documentation|template:any page/doc}}</noinclude>

This code should be added at the bottom of the template code, with no extra space before "<noinclude>" (which would cause extra space on pages where the template is used). The parameter can be used as shown above to transclude an arbitrary documentation page.

Add categories and interwiki links to the documentation page inside <includeonly> tags.

If the documentation page contains includeonly or noinclude tags as part of the documentation, replace the "<" with "&lt;", and the ">" with "&gt;.

Customizing display

Overrides exist to customize the output in special cases:

  • {{documentation|heading=}}: change the text of the "documentation" heading. If this is set to blank, the entire heading line (including the first [edit] link) will also disappear.
  • {{documentation|content=}}: for extremely simple documentation notes, enter the message desired with the |content= parameter. The text provided with this parameter appears in a box similar to the doc subpage, without any other notations in the boxes. For more complex documentation descriptions, use a full doc subpage.

Functions

If the documentation page doesn't exist, the "edit" link includes a preload parameter so that clicking it will pre-fill the edit form with the basic documentation page format.

Rationale

This template allows any page to use any documentation page, and makes it possible to protect templates while allowing anyone to edit the template's documentation, categories, and interwiki links. It also reduces server resources by circumventing a technical limitation of templates (see a developer's explanation).

The above documentation is transcluded from Template:Documentation/doc.
Please add categories to the /doc subpage.
Subpages of this template.