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

From Wazeopedia
m (2 revízie)
(8 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 driving navigation available.
{{key press/core|{{{1|}}}}}<!--
-->{{#if:{{{2|}}}|{{{chain first|{{{chain|+}}}}}}{{key press/core|{{{2}}}}}}}<!--
-->{{#if:{{{3|}}}|{{{chain second|{{{chain|+}}}}}}{{key press/core|{{{3}}}}}}}<!--
| type = important
-->{{#if:{{{4|}}}|{{{chain third|{{{chain|+}}}}}}{{key press/core|{{{4}}}}}}}<!--
| textstyle = color: red;
-->{{#if:{{{5|}}}|{{{chain fourth|{{{chain|+}}}}}}{{key press/core|{{{5}}}}}}}<!--
| text = This is a new test program and the content is subject to change.  Check back often.  Feel free to help update this page.
-->{{#if:{{{6|}}}|{{{chain fifth|{{{chain|+}}}}}}{{key press/core|{{{6}}}}}}}<!--
-->{{#if:{{{7|}}}|{{{chain sixth|{{{chain|+}}}}}}{{key press/core|{{{7}}}}}}}<!--
-->{{#if:{{{8|}}}|{{{chain seventh|{{{chain|+}}}}}}{{key press/core|{{{8}}}}}}}<!--
[[File:Aerial2.jpg|400px|Example Aerial Photograph]]
-->{{#if:{{{9|}}}|{{{chain eighth|{{{chain|+}}}}}}{{key press/core|{{{9}}}}}}}<!--
-->{{#if:{{{10|}}}|{{{chain ninth|{{{chain|+}}}}}}{{key press/core|{{{10}}}}}}}<!--
==Information for Requesters==
-->{{#if:{{{11|}}}|[[Category:Wikipedia keypress template parameter needs fixing]]}}<noinclude>
In addition to the Waze [[Munching#Munching|Munching]] system for confirming new roads and display of GPS tracks in the [[Waze_Map_Editor|Waze Map Editor]], volunteer 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, update detours, etc.
<!-- add category and language links to the /doc sub-page, not here -->
Look at the [[Aerial_Photograph_Requests#Guidelines_for_taking_pictures|example pictures here]].  You can expect aerial photographs to:
*confirm new roads and intersections
*see ramp details
*see direction markings on the roads (turn, one way, etc)
*see updates to new housing developments
*see construction detours
*not be able to be able to see road signage
===Format for Requests===
To submit Aerial Photograph Requests, map editors should use [https://docs.google.com/forms/d/1LyN_vapJoR5J8x3lfb1lVN2koHjl7mSBUIzbqmTFiCw/viewform THIS FORM].  All fields are required.  Do not leave unnecessary information in the [[Waze_Map_Editor#Permalink|Permalink]] (keep only Satellite Imagery and Roads).  The description might highlight if the map editor needs a broad picture of an area, or just one particular intersection.
==Information for Pilots==
Since Waze uses a "crowd sourced" map using content from volunteer editors and drivers, pilots can help the process by providing aerial photographs of new and changing roads.  When pilots are making practice flights and looking for a good excuse to go flying, they can practice finding landmarks and snapping pictures along the route that can help the volunteer editors and ultimately the driving community.
===Getting Started===
A list of participating pilot volunteers is [[Aerial_Photograph_Requests#Available_Pilots|here]].  Sign up or contact wazeflyer at gmail dott com for assistance.  Showing your availability here 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 [http://www.waze.com Waze Login] (so you can see the Waze map)
*Create a [http://www.waze.com/forum/ Waze Forum login] (so you can interact with editors and pilots)
*Browse picture requests [https://docs.google.com/spreadsheets/d/1ZIQB1O5LeOWuGdUyQzNsF6E9e9rjXe09ldkvGGIEUzk in this Google Doc]
===General Guidelines===
Guidelines for participating:
*Be current! (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 (perhaps flaps if slowing down)
*Double check [http://skyvector.com/ airspace requirements] and TFRs.  You can request time from ATC to do aerial photography over an area inside controlled airspace.
*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 available from Waze for volunteers (Waze is a for-profit company).
===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)
*the GPS coordinates are on the web page in the requestor's map link
*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
[[File:Aerial1.jpg|700px|Example Aerial Photograph]]
===Example Garmin Setup===
For a Garmin GPSmap portable:
*go to Menu/Setup/Location and change Location Format from hddd&deg;mm.mmm to hddd.ddddd
*in map view, move the cursor to the approximate area and click Enter to create a Waypoint
*edit the name (eg 0W001, starting with 0 will keep it at beginning of list)
*edit the Location to match the longitude/latitude coordinates from the Waze Editor
*do "show map" to make sure it's in the right location
*(delete the waypoints later when done)
===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).  Use the highest resolution available.
*respond to the forum request with an online link to the photograph(s)
Also be sure to:
*invite fellow pilots to help during their flights
*become a Waze map editor yourself, time permitting
*have fun finding the roads, taking pictures, and helping fellow drivers
===Unsolicited Contributions===
In addition to fulfilling requests from volunteer Waze map editors, you can also submit pictures of new roads that you discover while flying.  Use [https://docs.google.com/forms/d/1aIrjLdBU75Osa_4SOTjr9-0ibdgSccJfRg9oHX8XbBs/viewform this link].
These are the things that would be of interest to map editors
*new roads (in particular, those not on current google satellite photos of the area)
*new developments
*recent road changes due to construction (eg, rerouting lanes)
These things would not be useful:
* a new parking lot
* a new driveway
* a new home on an existing road
==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].
==Key Links==
*[https://docs.google.com/forms/d/1LyN_vapJoR5J8x3lfb1lVN2koHjl7mSBUIzbqmTFiCw/viewform Aerial Picture Request Form]
*[https://docs.google.com/spreadsheets/d/1ZIQB1O5LeOWuGdUyQzNsF6E9e9rjXe09ldkvGGIEUzk List of Requests]
*[https://docs.google.com/forms/d/1aIrjLdBU75Osa_4SOTjr9-0ibdgSccJfRg9oHX8XbBs/viewform Pilot unsolicited contributions]

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.



 - or -
 - 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.


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.


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.