Florida Raid View history

Mapraid
Revision as of 00:39, 1 March 2015 by Driving79 (talk | contribs)
 MapRaid! Florida has begun on 2015-02-13, Friday. 00:00 UTC. The raid will last for roughly 7 days.
Registration for the MapRaid! is now closed. To hear about future MapRaids please join the MapRaid #Slack.

Welcome to Florida!

Mission

Our primary mission is to fix what is broken as well as fine tune what is already working. This will be handled through a variety of ways:

  • Handling URs, PURs, and MPs
  • Fixing streets (correcting elevation, turns, extra nodes, alternate names, etc)
  • Routing corrections (usually found in URs or by randomly attempting to route between points and looking for irregularities)
  • FC errors (but do not downgrade without getting local guidance! See FC warning immediately below.)

Local Hosts

ggrane (PM [Help])   - Florida SM

t0cableguy (PM [Help])   - Florida SM

jakflash (PM [Help])   - Florida SM

Important!

 Please DO NOT EDIT ANYTHING IN OR NEAR A THEME PARK!!! It does not matter what rank you are, do not touch it. This means, no editing roads, URs, PURs, MPs, or anything else in or near a theme park/major attraction. If you find anything wrong, please ask one of the SM's Local Hosts.


Please do not alter any of the following road types without first consulting a Local Host (unless changes are being made to match Functional Classification (FC)): Freeway, Ramp, Major Highway, minor Highway, Primary Street. You may edit these roads, but do not change the type of the segment (excluding FC work). Confirmation should be obtained before making changes to any of these road types that go against FC.

Please do not mass-edit Do not perform edits which will affect large numbers of segments at once. The edit history of segments is highly valuable in the process of solving URs. Mass editing effectively mass erases this history, permanently. We ask that all necessary processes which might affect large portions of the map, or long stretches of roads, be reserved until near the end of the MapRaid. This includes the “Select entire street” function. To facilitate this process in an orderly fashion, we have the Scheduled Edits list below. Please document any mass edits which are required, and you will be given first chance to make those edits when the time is right.

Anything locked at 5 or 6? Please check with a local editor before making changes.
If you are a rank 5 or 6 editor - consider keeping highlights active for locks 5 and 6.

Close nodes We make extensive use of the " micro-dogleg" technique, where a geometry node is carefully placed, at full zoom, directly next to a junction node, in order to set the angle to create a desired Turn/Stay/Exit prompt. Please watch for these if you move any junction node, and be sure to recreate the same angle at the new location.

Local Guidance

Functional Classification

Functional Class: FL DOT Functional Class or you can install the free ARCGIS viewer and download the FC layer.

In the United States, we set our road types using a national standard called Functional Classification (FC). You can read a detailed explanation in our Road Type Wiki

FL DOT functional classification classifies roads as

  • A Principal Arterial-Interstate or Principal Arterial-Freeways and Expressways is a  Freeway 
  • A Principal Arterial-Other is a  Major Highway 
  • A Minor Arterial is a  Minor Highway 
  • An Major or Minor Collector is a  Primary Street 
  • All other roads are to be classified as  Street 

Locking Standard

 The Lock Standard State template cannot display the locking scheme because it does not recognize the state/province/region specified: FL

Elevation

In general, all freeways should have an elevation of ground. Roads running over or under the freeways will have an elevation of +1 or -1. Where two freeways cross, the overpass should generally have +1 elevation. More complicated junctions may need more complicated treatment; apply the principal of "freeway defines ground level whenever possible" and keep elevations as sensible as possible. Remember that this region is not very hilly.

UR & MP Guidance

Responding to Update Requests (URs), and Map Problems (MPs) will be the primary focus of the MapRaid teams. Please make sure to follow the guidance on dealing with URs and MPs as they are clearly explained in the UR wiki page. Be especially careful to always leave a comment when closing a UR to explain why you are closing it, or how you fixed it. If there is no problem with the map to fix, don't mark it as solved, mark is Not Identified".
Our only variation for the MapRaid from the general guidance on handling URs, is that we are reducing the 7 day wait periods to 3 days. You still must comment and wait 3 days, then comment again before closing a UR as "Not Identified". If you are able to fully diagnose and fix the problem, then comment what the fix was, and close it as "Solved".

We should not be sending reminder comments after the 3 days. We send one comment asking for info, if there is no response after 3 days, close the UR. Please try to solve the UR, if that's not possible mark it as Not Identified. (We should still be sending a closing comment before closing, and it's OK to send follow up comments if you need additional information after the first response.)

As per Texas UR policy please keep UR response comments to a minimum, short and to the point. Aim for not more than 3-4 lines total. The UrComments script (link below) already has a long list of canned UR responses which have been vetted by a group of senior editors.

As we have now reached 3 days since the beginning of the Raid, and URs are being closed, please double check that the UR you are closing still is not/cannot be solved. Sometimes a question has been left for verification, and a map correction delayed, pending a response/no response. Please make sure to attempt to fix or get help if need before closing any UR. Also, DO always leave a closing comment; no UR should be closed without one.

Place Editing

Not only were our URs and PURs out of control, Places from both editors and trusted users have become a major issue. Misspelled names, wrong categories, missing addresses (EVERY business place should have an address!!), poor location, and incorrectly assigned photos are all over the map. Use the powerful Place Browser (link below) and the information on the Place editing section of the Texas page to get these places corrected.

Please use good judgement when approving photos. Any photo which has nothing to do with the actual place, reject. This is including, but not limited to body parts, car parts, bathrooms, children, & animals. If you're not sure, please ask one of the senior editors.

Gas Stations
Gas Stations should be locked to level 3 but, only after all data fields in the gas station have been filled. At least ensure that Brand, Name and Address have information. Remember to ask a local host if you need help identifying gas station information.

For editors below rank 3, once you have completely filled out a gas station with the minimum required information, please lock to your level and then ask for a lock request.

Finally, DO NOT USE THE BRAND "UNBRANDED". If it is a no brand gas station, just leave the brand field blank.

Locking Standard

  • Lock at rank 5: hospitals, universities, park and ride lots, arenas, airports.
  • Lock at 3: any other place that has at least a correct category correct name, and correct address with house number..
  • If you cannot lock high enough because of rank, lock as high as you can, and get help from a higher-ranked editor to lock properly. You can keep a personal list of Permalinks to share with the other editor.

Toll Roads / HOV / HOT

It is our custom to mark the toll checkbox on the entire sections of Toll Roads to include those ramps which are tolled. HOV and HOT road types have already been set correctly according to our local practices. If you have a question about one of these lanes, please contact a Local Host.

Construction

DFW Is going through an explosion of neighborhoods and new subdivisions. There may be some of these which are not on the editor, so if you see a missing road, see if there is an actual neighborhood by turning on the GPS tracks. There are a number of major construction projects in process within the overall MapRaid area. These construction projects can cause frequent intermittent road closures. Many closures change daily and cause great numbers of URs to appear. When handling URs in one of these areas, be aware that reports of "Turn not allowed", "Missing road", "Wrong driving direction" are common, but may not indicate a map problem that can be fixed, because the physical road situation will change before our edits can take effect.

LINKS:

Texas driving conditions and road construction


U-turns

In Texas, U-turns are generally allowed unless unsafe, or specifically denied by signage. In general we can confirm, lock or "harden" U-turns (click to remove the Purple question mark indicating a soft turn -- see the Wiki). U-turns are not named unless there as an official sign. All U-turns along freeways are normally named "Turnaround."

Alleys

Alleys are not mapped in the State of Texas and should be deleted. This has been confirmed per txemt.

Private Roads

Private roads are used only for specific purposes. Before creating new private roads or working with existing private roads, please consult txemt.

Cameras

Speed Cameras are illegal to use in the State of Texas

Red light cameras Are used in various places -- check for information for each municipality.
For a list of DFW cameras, please click here: DFW Cameras

Mapping Resources

Functional Class: TxDot Functional Class

Communication

Communication will be handled primarily in #Slack Channels and WME chat can also be used. The WME Chat addon is recommended. Special Slack channels will be set up and named by raid location and group. Please be sure to join the slack WazeMapRaid Team and join the channels for the specific MapRaid and group you are assigned to.

Click here to get your Slack invitation. Be sure to choose WazeMapRaid to the MapRaid question.

If you have an issue getting into the slack team and channels, please reach out to one of the MapRaid organizers.


Unlock and lock requests

Unlock and lock requests should be handled in your teams slack channel. Each team has at least one rank 5 editor, most have more, and all but one team has a rank 6 editor. If you cant get a response in your teams channel, you can try the general MapRaid! Dallas channel.

Due to the close group and rapid time frame for editing, we can accomplish things much faster if we handle it all in-house. There is no need to post unlock requests to the forum for MapRaid! related edits.

Unlock requests should include the permalink preferably without layers, the changes you would like to make, and the reasoning behind the changes you'd like to make.

Reference Links

The Basics

Recommended Tools

  • UrComments - a tremendous time and labor saving tool with automation and integration with URO+, to help with working URs. Read the documentation. By: Rickzabel (PM [Help])  
  • Place Browser - This tool lists all places in the specified area, and flags some things that MIGHT be problems. It is up to you to decide what to do with this information. Be sure to apply the global, national, and local guidelines for places. Be sure to click the About tab to get an overview of the tool. By: Joyriding (PM [Help])  
  • 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.
    Download links:
    • For Chrome browser please download the script at Chrome Web Store
    • For Firefox browser please download the script at GreasyFork.org
      Note: for Firefox browser you also need Greasemonkey or Tampermonkey installed.
  • WME Chat Addon is a script that improves the WME chat GUI. For a list of all the features check the thread here. By: Dummyd2 (PM [Help])  
    • Tapermonkey/Greasmonkey is required to use this script
 Click here to view the MapRaid! Texas forum thread

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.

Scheduled Edits

These are edits which need to be completed but must be postponed in order to retain history for UR Solving. These edits are designated to specific editors to complete, once they get the green light from the MapRaid! leaders.

These editing tasks have been delegated to specific editors for future completion at the end of MapRaid! Florida Raid. Please DO NOT EDIT or try to fix any of these items unless you are the designated "Editor to Complete" for that item in the list. These edits may only be completed once the "Continue When" instructions on the row for that item are met. If you have any questions please ask one of the listed Local Hosts.


Please enter new information on this form

Click here to view this list in fullscreen

Boots on the ground

We need local boots on the ground to check things. Please add requests for locals to go and scout things in person, as in on the road. Some examples when this would be used include to check and see if:

  • The street view is accurate,
  • A road is really closed,
  • A turn really allowed/prohibited, etc.

To make a new request, or respond to an existing request, please use this form.

Click here to view this list in fullscreen

Retrieved from "https://beta.waze.com/wiki/Mauritius/index.php?title=Florida_Raid&oldid=97278"