If you would like to participate, please fill out this [ registration form].
Registration is open until UTC, or untill the maximum amount of participants is exceeded.
Please do not make any edits in the raid area until after the raid begins. This will allow us to get good mapraid statistics.
Goals
In order of importance:
Put correct speed limits, with emphasis on the connecting roads
Use realistic elevations where roads cross (so-called seagull edits).
Adjust segment locks, as appropriate, to meet the new Northeast locking standards.
Please also make basic common-sense edits as you work on the mapraid goals -- fix bad turns and other obviously wrong information on the segments you are editing, but keep focused on the mapraid goals. If you see bigger problems that can be addressed later, contact your group leader or record it in this form.
When working in the raid area, please set yourself to set yourself visible in WME chat. Also, turn on the Live Users layer. This will serve to collaborate smoothly and get quick help at your location if needed.
We will use Slack as the main communication platform. There is a special Slack Channels for this raid. If you are not already part of the Benelux Slack team, you will be invited shortly before the Raid starts.
Raid Area
This MapRaid has only 1 group, working together in the southern part of Belgium. We kindly urge you to stay within the raid area. Use the overlay as it clearly shows the border.
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.
Speed Limit Guidelines
Only add speed limits when there are recent streetview images in WME that can verify the allowed speed.
Use Waze Street View to find Speed Limit Signs. You may also get information from local drivers. You may use information from local ordinances posted on township, borough, or city websites. Do not rely on predicted speeds (with "verified" check box).
Some segments have unverified speed limits. These speed limits were predicted by waze. We must check each unverified speed limit. If it is correct, we can use the "Verified" check box. If it is not correct, we must replace the speed limit value.
Pennsylvania follows the US guideline for speed limits, with a few exceptions listed below.
If there is no SV, do not map SL. (No SV => No SL)
Unless you have information from someone who has recently driven on the street, or from local ordinances listing speed limits.
When a speed limit changes at an intersection, the sign for the new speed zone mighte be up to 200 feet after the intersection. If the speed limit changes more than 200 feet from the intersection, add a junction at the sign and make the speed limit change there.
Long term work zone speed limits may be mapped instead of the "ordinary time" speed limits.
Speed limit signs are supposed to be posted on every street, no further than 1/2 mile apart.
If there is SV, and SV shows there are no signs, follow the PA guidelines for streets with no signs:
35 miles per hour in any urban district.
25 miles per hour in a residence district (unless it is a numbered route classified as a local highway)
55 miles per hour in other locations.
Do not guess. If there is no SV, and if there is no information from local drivers, we cannot know if there are signs or no signs.
Summary of National Guidelines
Regulatory Yes Advisory No
Only map speeds found on regulatory white rectangular signs with black lettering.
Do not map advisory speed limits (generally an orange or amber rectangular sign with black lettering).
Where there are variable speed limits, map only the speed limit which is in effect most of the time during daylight hours (most hours of the day, days of the week).
Do not map special speed limits for special vehicles. Waze only supports speed limits for private passenger cars.
Where the speed limit changes, make it change in the map. A new junction may need to be added. But do not add a new junction for a speed limit if it will be within 200 feet of an existing junction.
Elevation Guidelines
Elevations should be mapped more-or-less realistically. Elevation numbers are relative. An overpass has a higher elevation than the road it passes over.
If a seagull can fly right under it, it’s a bridge (level greater than 0).
A road is only level = +2 if there’s another bridge (+1) running underneath it.
If it is underground and covered over, check the tunnel checkbox. The road segment must begin at least 50 feet before GPS signal is lost, and continue at least 50 feet after GPS signal is recovered.
If you see tunnels with negative (-1) elevations, leave them. If you create a new tunnel, set the lowest level to ground and set all crossing roads above that.
For every other case the road is ground level (level = Ground), even if it’s artificially elevated or dug under street level.
Tight MarkingTight Marking. We mark bridges with level = +1. In some cases we will need to split segments into two or more segments to mark only the right parts of the road as a bridge or a tunnel. This is Tight Marking.
At interchanges, where there is already a nearby junction, it will often not be necessary to use "tight" marking for an elevation change on the overpass. Use the existing junctions if at all reasonable.
Road Segment Lock Guidelines
When you edit any segment during the mapraid, please set the lock level correctly.
Any road of a certain segment type must be locked at least to the rank (level) in the chart below. Roads may be locked higher for protection and special situations (areas with construction, tricky design, frequent mistakes, incorrect images, etc.).
Moweez Minimum Locking Rank Standard
Segment Type
Statewide
Freeway
5
Ramp
Highest rank of connected segments
Major Highway
3
Minor Highway
3
Primary Street
1 (Auto)
Street
1 (Auto)
|-|-|-|-|-|-|-|-|-| Railroad |-|-|-|-|-|-|-|-|-|
2
• • • • Ferry • • • •
5
Private Road
1 (Auto)
Note: Do Not Mass Edit just to update locks to these standards
Base Map Areas
There are still many areas in Pennsylvania which have not been touched by editors since the "base map" was imported in 2009. Only touch these areas if it is necessary to reach the objectives of this mapraid. If no information is available for setting Speed Limits, and no elevation adjustments are required, do not fix these parts of the map. These areas will be addressed at a later time.
Before setting speed limits on a segment, set the road direction correctly and correct all turns and other obviously incorrect information.
If roads are very bad and very difficult to fix, you may report the problem to a group leader.
Editing Resources
Only use sources that are allowed by Waze.
Allowed sources:
Satellite Imagery and Street-view from within WME.
Websites from businesses.
...
NOT allowed sources:
Info from other Maps.
Google Maps
Google Street-view.
Warning: If you copy information from unauthorized sources, you may be removed from this mapraid. Also, every segment you edited may be removed from the map. Copying information from copyrighted sources is illegal!
PA Mapping Resources
Highways Sheet Choose a highway. Add the highway you are working on. This will help us coordinate with each other.
Pennsylvania Speed Limit Map. It is not 100% accurate where speed limit is changing. It can help you find speed limit zones. Please confirm using WME Street View.
links and descriptions to most of the editing scripts being used. Some of these are essential to good editing, and others make the editing process much easier. WME Validator, URO+, and WME Toolbox are highly recommended.
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.
record it in this form.
