Philippines/Editing resources: Difference between revisions View history

Line 21: Line 21:
3. Set directionality (two way or one way)
3. Set directionality (two way or one way)


4. Set the elevation level (Ground, Tunnel = '''-1''', Flyover = '''1''', '''2''', '''3''', etc.). Only tunnels or underground roads are to be set to -1, if one road passes over another, the bottom road is Ground and the one that passes over is 1.
4. Set the elevation level (Ground, Tunnel = '''-1''', Flyover = '''1''', '''2''', '''3''', etc.). Only tunnels or underground roads are to be set to -1, if one road passes over another, the bottom road is Ground and the one that passes over is 1. Tunnels should at least be 100m in length, otherwise leave them as ground level.


5. Connect or create junctions (attach to existing roads)
5. Connect or create junctions (attach to existing roads)

Revision as of 09:54, 8 January 2015

Map Editing Guide for the Philippines

1. Create road (whether tracing aerial images/gps points, or from recorded drives)

2. Set road type, some suggestions;

  • Freeways – Toll Roads
  • Major Highway – DPWH Primary Roads or roads that connect cities of > 100,000 population
  • Minor Highway – DPWH Secondary Roads or roads that connects other cities (i.e. <100,000 population), ports, ferry terminals, airports, tourist service centers, and other national government infrastructure to the primary network.
  • Ramps – On and off ramps from Freeways, segments that are not at-grade or ground level, used to connect segments with different levels
  • Primary Street – Main thoroughfares of a city or municipality and/or DPWH Tertiary Roads
  • Street – ordinary street, mainly residential
  • Service RoadsThis type has been deprecated, use Street type instead. usually access roads leading to or from an establishment, an intersection, that is in parallel with a major or minor highways or freeways (expressways)
  • Dirt-roads / 4x4 Trails – drivable roads but not used for routing, except when 'allow dirt roads' option is enabled or if destination is on the dirt road. You can also select this if the road is too narrow like an alleyway, an unpaved road for 4x4 rigs, or only motorbikes and tricycles use it.
  • Parking Lot Road – drivable roads within a commercial or private parking lots, used for routing but with a high time penalty. If the parking lot is covered, do not create any parking lot roads or if it is a parking building or structure and it does not have a roofdeck, do not create any parking lot roads. Map only the main roads leading to and out of the parking area, DO NOT map all the lanes inside the parking area.
  • Private Road – drivable roads within gated communities, subdivisions, villages, or compounds. Not used for routing except when destination is on the private road. All roads within the area must be the same private road type. Put '(sticker required)' on the main entrances to these areas where a pass or sticker is required.
  • Walking Trails, Pedestrian Boardwalk, Stairway, Railroad, Runway/Taxiway – other non drivable and non-routable roads, do not map these unless they are used to landmark an area or to help in navigation.

3. Set directionality (two way or one way)

4. Set the elevation level (Ground, Tunnel = -1, Flyover = 1, 2, 3, etc.). Only tunnels or underground roads are to be set to -1, if one road passes over another, the bottom road is Ground and the one that passes over is 1. Tunnels should at least be 100m in length, otherwise leave them as ground level.

5. Connect or create junctions (attach to existing roads)

6. Set turn restrictions and if u-turns are allowed on junctions, the easiest and fastest way to do this is to click on the junction node and hit 'w' on your keyboard. This will set all turns to enabled or green. Leaving a turn restriction disabled does not mean that Waze will not route to it, Waze can still route a turn to it since it is connected. To prevent routing, a segment needs to be totally disconnected from a junction.

7. Name the road, if you don't know the street name add the city name and mark the street name as 'None'. Somebody else could edit it. Do not name roundabouts, the road name will not wrap around the roundabout segments and will not look right on the map. It will also break the routing instructions for the roundabout

8. When naming streets, omit "City" and "Street". e.g. "Pasig City" to "Pasig" only and "Dela Rosa Street" to "Dela Rosa" only. Except when they are not "Streets" like "Kamias Road", "Aurora Boulevard", "Ayala Avenue", etc. If you are going to abbreviate, make sure you follow Waze Abbreviations and TTS standards so that our street names are ready for TTS (Text To Speech).

The City field should only contain the CITY or MUNICIPAL Name and NOT the AREASUBDIVISION, DISTRICT or BARANGAY NAME nor should it be combined with the PROVINCIAL Name.

Please give extra care on labeling the City of your edits. Unlike Street names which reflects edits (or corrections) quicker and appears on the next update, City names unfortunately embeds much longer on the City tiles in the servers. So misspelled City names reflected during an update will appear for a long time in the client (waze) despite any corrections made.

Kindly stick to the official (but shortest possible) name of the jurisdiction being edited. Also, if you are unsure of the political boundaries of the "city" you are editing, leave it at that for the moment. let's leave it to the more experienced and knowledgeable editors to sort this matter out.

Another matter of city labels, we omit the "city" to derive the shortest possible official political name of the area. The only exceptions are Quezon, Cebu, Davao, Cavite, etc as these cities have a provincial counterpart.

This will distinguish Quezon City with the province of Quezon, Cebu City with the province of Cebu, and so on.

All other cities or municipalities will stand on its own without the label "City" or "Municipality", provided it does not have a same Province name.

Currently waze has a global issue with cities having duplicate names (with the exception of North America). We are hoping to resolve this in the future by having the Province label (equivalent to State) activated. For the time being, to address this issue, the  province's initial, to which the city or municipality belongs to, is added (suffixed) to the name. e.g. Alaminos (L) for Laguna, Alaminos (P) for Pangasinan. Kindly refer to this link of repeating city names for a complete listing of all the cities and municipalities within the Philippines.

9. Do not split roads unless they are Expressways, Major, and Minor Highways. Even if they are Major or Minor highways, do not split them if they do not have wide median barriers. Split roads complicate routes and are harder to maintain.

Some formal guidelines for splitting roads in the Philippines - A road should' be split if:

  • There is at least 5 meters of non-drivable surface between directions of travel. (This means a median of some type like cement, planter boxes, trees, or just grass.
  • GPS tracks show a clearly definable gap/blank area between the color-by-azimuth arrows at the 100m zoom level.
  • U-Turns are required to properly make turns that are blocked by a median.

A road should not be split because:

  • There is a curb or non-drivable media less than 5m wide between lanes of travel. This means a turn lane, even a wide one, between directions of travel, does not count because it is drivable.
  • There are a lot of roads intersecting which can only turn onto the nearest direction of travel.
  • Google Maps or other mapping source show it as a split road
  • The non-drivable median is interrupted by a cross segment at most intersections.

Turn Lanes or at-grade connectors - First and foremost, the need to have the turn lanes mapped needs to be established. As the driver approaches an intersection, Waze has usually given at least one warning that a turn is imminent, and we can assume that the driver is already looking for turn lanes. For most intersections, that is enough to guide the driver into the proper lane and to turn at the proper time; in other words, it is enough that the two roads intersect without separately mapped turning lanes. There are only a few situations in which connectors are called for in an intersection:

  • When the turn lane physically separates from the main road well in advance of the intersection
  • When the turn lane is far enough from the point of intersection on the map (due to the size of the intersection or the angle at which the roads meet) that the driver might overshoot while waiting for a delayed "turn" audible, or that the Waze client might become confused and disrupt navigation
  • When the area is "busy" enough that the driver may not get any advance warning that a turn is coming up--in which case a connector lets you notify the driver a little earlier
  • When there are user complaints (update requests) that the audible was too late, or that the map should have shown a connector
  • When you get an automated report (map problem) that the roads are too far apart due to the intersection being too far from the turn lane
  • When in doubt, leave it out. Each connector complicates the map and adds to your workload when the time comes to check connectivity, direction, name, etc

10. When you are confident on an area you have mapped,lock the roads to prevent any changes or edits on the roads. While we appreciate the help of newbie waze editors in editing our maps, they are prone to creating errors if not informed and educated properly on our map editing guidelines. It would be great if we can direct them to read this guide first before they start doing any edits. Read the Phillipine Locking Policy below for more details.

11.Adding Area Places, Point Places, and Gas Stations; When adding Places or a Gas Station, make sure their location is properly identified through the add Area Places, Point Places, or Gas Station draw function and add the address in the details as well. If an Area Place will cover beyond a city's/minicipality's boundary or will cover more than one city/municipality, mark the city address as none. For bodies of water like creeks, rivers, lakes, sea, etc. mark the city address as none, this is so that their area will not be added to the city tile.

The main differences for these are; Area Places - These primarily POI locators but also serve another function on the Waze map. They serve as navigation aids and cues so if a landmark serves as a navigation cue and is more than 50m on it's X or Y coordinates, you can add it. If it is smaller than 50m, consider adding a Point Place.

Point Places - These are the main POI locators for establishments that you want to add on the map. Adding these makes these places searchable on the Waze app. If there is already an Area Place, do not add a Point Place and vice versa.

Gas Stations - Gas station establishments, when adding these and X or Y coordinates are not long enough, consider adding a small spike on one of the sides so that it goes over 50m in length so that it gets displayed on the client app.

Refer to the Places Policy for more details on what can be added.

DO NOT MAP MILITARY INSTALLATIONS OR BASES

12. KISS! - Keep It Simple, Stupid! Our maps should work best if they are kept simple rather than complex, therefore simplicity should be the main objective in our maps and unnecessary complexity should be avoided.

Guidelines for Resolving Update Requests (UR)

  • Introduction

User submitted Update Requests, compared to Waze generated Map Issues, are more difficult to fix because the report might not contain enough information or there might not really by a map issue. This page is intended to document guidelines for the Philippine on how to resolve Update Requests or URs

  • Priority URs

We should prioritize URs which have been on the map for a long time, these URs are identified by their color. Red URs should have the highest priority since they have been on the map for more than 15 days. Orange URs are next on the priority and the least priority are the yellow URs. The reason for this is that if the URs need more information or detail, the reporters for old URs might not remember the reason they reported the update request and thus need to be contacted the soonest.

  • Steps on resolving URs

The most common update requests are 'General Map Error' and 'Wrong driving directions', users report these update requests because Waze is routing them to other streets but they want to continue on the route had in mind. For these kinds of update request, there is might be nothing to fix. Waze will take into account how many times it has suggested a route and how many times users disregarded the suggestion and create a Waze generated map issue. The solution for this is discussed in the waze generated map issue section. If you are not familiar with the area, leave the UR for editors who know the area or more senior editors. It is preferred that comments asking for more details is posted on the UR if unsure of the details.

For the vague "General map error" URs which does not have a description nor a User drive (GPS Trace) and/or Waze provided route. Leave a comment to ask for more details.

Some "General map error" URs have a User drive (GPS Trace) and/or Waze provided route or a description. When you check the route, nothing is wrong. This could mean that Waze suggested a different route and the user reported it as an error or the issue might have been fixed already. Depending on how complicated the waze suggested route is compared to the reporter’s recorded drive, you can mark this as “Solved” if it looks like it is fixed or leave a comment to ask for more details.

Other valid "General map error" URs that may have one or more of the following; User Drive, Waze provided route, and description. And if you check, the roads indeed need to be fixed based on the information provided. Fix the road to the best of you knowledge if you know the area. If not, other editors could resolve the map issue.

"Incorrect Junction" URs could mean that there is a road where there shouldn't be one. Another could be two roads linked but is permanently blocked.

"Missing bridge overpass" when there is one (flyovers and bridges) could mean that the reporter might have been reporting a missing pedestrian overpass, which we do not (and should not) include in the maps. Or the reporter did not know that Waze does not show any difference between flyovers, bridges, and roads unless it is a ramp. Mark these as "Solved" if waze already has them on the map.

"Wrong driving direction" URs are usually waze suggested routes that the reporter didn't want to follow and instead reports it as a wrong driving direction UR. Leave this one marked as "Solved" because it isn't really an issue. The valid URs can be determined if you analyze the waze suggested route and it doesn't look logical or simple. It is usually caused by wrong street direction, incorrectly enabled or disabled turn restrictions, missing streets, missing junctions, etc. Check for any of these to resolve the issue "Missing exit" URs are usually on Expressways or missing roads by highway roads. Check GPS points or aerial and add the missing exit/road.

Valid "Turn not allowed" URs can be seen if more than one UR on the same intersection has been reported. This can be verified through GPS points. Most URs of this kind are reported because the route suggested was not followed and reported as not allowed instead.

"Missing exit" URs, these URs are supposed to indicate missing exits from Expressways but they get reported on the Waze map by Wazers when streets are missing or turns were not allowed.

"Missing road" as described by the UR, check GPS points or aerial and add the missing road. If you need more detail on an Update Request, leave a comment asking for one so that the reporter can help you fix the issue.

NOTE: As a general rule when resolving issues, always put a comment on what you did on the map. If the UR does not have information necessary to resolve the issue, post a comment and ask for more details. No one can lay a claim on URs, anyone can resolve them as long as the information at hand is sufficient in resolving it. We don't have a rule where the first to post a comment claims ownership of that UR and only he gets to resolve it. However, no one should close a UR with an existing conversation unless the following conditions are met;

  • a. X days have passed since last conversation and reporter has not replied, mark the UR as Not Identified. The Wazer who submitted the UR will be notified via email that their Update Request is closed. They can still try to contact you through a private message if they do have more information or they can do the fix themselves on the map editor. X days are discussed in the Update Request closing policy
  • b. reporter has agreed that UR is not an issue, mark the UR as Solved
  • c. issue has been resolved, mark the UR as Solved

Update Request (UR) closing policy

The Philippine Area Managers and champs have discussed and agreed upon a new policy on how long we would wait for a reply on URs before marking them as 'Not identified'. The new policy is based on the UR density of an area. The UR density is determined by zooming into the an area 100m/500ft scale and counting the number of URs (MPs excluded).

Heavy > 10 Mid 5 to 10 Light < 5

In areas with heavy UR density, the wait time before closing a UR with no response will be 3 days. For mid UR density, it will be 5 days. And for light UR density, it will be 7 days.

For URs that have replies from the reporter but has follow up questions, the wait count will be reset and will be based on the date of the last reply or follow up question. Wait time will still be based on the UR density for that area.

The reason for this new policy is to eliminate URs that are invalid and have a quick resolution for the valid ones. The logic is based on the premise that problems in high traffic areas will have a greater probability of getting reported again in detail or will get a timely response from another active Wazer. On roads less traveled, issues will have a lesser probability of getting reported again if the URs are closed so a longer wait time is allowed.

Another reason is that only 20% of reporters reply to our query for more details. Those that reply do so immediately or within the day, if the UR has no replies within 24 hours, it is probably not going to get a reply from the reporter. This just adds to the UR clutter on the map.

Philippine Locking Policy

  • Introduction

This policy should act as a guideline on when and why segments are locked in the Philippines. Senior editors (AM and CM) are encouraged to follow these guidelines. This should also answer questions from lower level editors why roads are locked. Inspired by the UK locking policy

The primary reason for locking an area or segments is because they are;

  • 1. Already 95% complete and accurate. If an area is already considered greater than 95% complete, they may be locked to Level 5 (all roads in NCR, R3, and R4 and Freeway/Major/Minor Highways elsewhere) and Level 4 (Primary and everything else). The reasoning for this is if the area is 95% complete, why would anyone else need to edit it. If it needs editing, an unlock request can be submitted.
  • 2. Changes or edits to these segments are seldom done or does not happen that often.
  • 3. Segments that are high value roads where incorrect edits will result in routing issues.
  • 4. Vandalism on the Waze maps
  • 5. Bad edits are being introduced and the Wazers involved do not reply or cannot be contacted

Areas listed (Cities and Municipalities) below are at least 95% map coverage and have roads locked to Level 4.

  • Makati
  • Pasig
  • Caloocan
  • Las Pinas


  • Road Types

NOTE: In NCR and nearby areas, since the area has the most number of Wazer, it is in the community's best interest that roads and segments are locked to Level 4 or higher.

Expressways - are to be locked to L5, including exit and on-ramps. These are high value roads and are most probably complete and accurate. As such, they need to be protected and locked to maintain their correctness. Editing will only be done by level 5 editors or CMs

Major Highways - should be locked to level 4 since this is another high value road. This will allow CMs and senior editors/AMs to make necessary edits.

Minor Highways - are another high value road but their locking depends on their location. They should be locked to level 4 if they are within Metro Manila or other outlying areas and level 3 elsewhere. Editing can be done by CMs and senior editors/AMs.

Primary Streets - should be locked to level 3 so that they can be managed by their respective Area Managers. However, CMs and senior editors can lock these segments to level 4 if the segments are frequented by bad edits.

Railroads - should be locked at L5 to prevent accidental edit and deletion.


  • Other Situations

Junctions / Intersections and Roundabouts These involve several segments & includes several Turn Nodes, depending on complexity, these may be locked above or higher than the Lock Levels of roads to & from these items to prevent erroneous edits and Turn Restrictions.

Ordinary Streets and other road types When the senior editor group (CMs and AMs) have decided that an area is already 90% complete and accurate, all segments within that area can be locked to level 3 and level 2 (within Metro Manila, and outside Metro Manila respectively).

Roads Not Matching Aerials With the change to Google aerial imagery, there will be areas where the current road layout will not match the images. It is recommended that these areas are locked to level 5 to prevent well-meaning editors "correcting" them by re-aligning them to the aerials.

Landmarks There are landmarks that are of high value, these could be those that took a lot of effort to draw, should be locked. For example, sea, lakes and rivers, and gas stations.


  • What not to lock

Unnamed roads and segment should not be locked so that they can be edited and named by anyone with proper knowledge on the segment(s) concerned.

Philippine Places Policy

Introduction

This will serve as a guide for Waze Philippines on what should be posted, approved, and rejected for Places submissions. If a submission is going to be rejected, add a comment why (future feature).

Before taking a picture and submitting (approving for us editors) it, put yourself in the shoes of someone who will be going to that place and does not know where to go or look. The picture should be something that will make it easier for anyone to find that place.

Every user (trusted or not) can become blacklisted and banned from adding places once they have tried adding a certain amount of places or updates which have been rejected. We also track places that have been flagged and removed - if we see a pattern where a certain user created many of these, he might be blacklisted.

Refer to this link for more details; Places Wiki

Approve

  • Clear image of entrance/facade
  • Clear image of building or structure
  • Images including a signage / billboard of the establishment displaying its name &/or address
  • House or residence images set to private viewing

Reject

  • House or residence images set to public viewing
  • Images with faces
  • Dark images
  • Blurred images
  • Images with clear plate number of vehicles
  • Interior images of buildings
  • Images showing incorrect place
  • Pornographic images

Other Questions and Tips for the Pinoy Waze Editor

Here are the most asked questions from Pinoy Waze Editors

  • Is there a manual for Waze map editing?

There is a Waze Map Editor that applies to both the US and World map servers. The topics on the wiki may or may not apply to our Philippine Roads.

A Map Editing Guide for the Philippines is available in the Editing Resources for the Philippines and is a compilation of suggestions and made into a guide on how we should edit our Waze maps for the Philippines. A lot of map issues and update requests are due to incomplete or incorrect information on our map. A lot of these issues could be avoided if we follow the Best map editing practice guide in the wiki. However, some items listed are specifically for our pinoy roads and driving habits.

  • Why am I not leveling up to Level 3?

We have implemented a policy which will limit Level 3 to senior Area Managers. This means all Waze editors will remain at Level 2 regardless of their map edit count. New Area Managers are also not automatically promoted to Level 3 and will remain on their level until the local champs agree to promote based on the quality of edits. In order to be eligible to level up to Level 3, a Level 2 Wazer needs to meet the requirements required to be an Area Manager. The reason for this is that a Level 3 Wazer has the same editing permissions as a senior Area Manager. Waze Area Managers help keep the map accurate by fixing Update Requests (URs) and Map Problems (MPs). Other Level 3 map editors who are not Area Managers can compromise the accuracy of the Waze maps by editing or changing segments currently locked to Area Managers. Instead of helping, they become a detriment and damage already working and accurate maps. This may result in inaccurate roads and cause issues with Wazers using the app. We are also having problems communicating with these Level 3 editors who are not Area Managers since they do not frequent the Waze forum.

  • How do I apply to be an Area Manager?

To become an Area Manager, use the Waze Map Editor and position the map and set the zoom level to show the area you want to manage. Click on Permalink and then copy the address from the address bar in your browser. Fill out the Philippine Waze area-management request form and submit. There is also a wiki page on Area Manager. The Philippines is part of a group of countries that practices 'self-management' wherein the approval will come from Philippines Waze Champs identified by Waze. Please bear with us if it takes several days to have your application approved, all the Waze champs are just volunteers and we have other day jobs :)

  • How long does it take until my edits gets displayed on my waze client?

It usually takes a couple of days for edits to get reflected on the waze client. If it takes more than that then maybe there is an issue with the map updates, check out waze status page for more details. If your edits still don't display on the client and the map update should have included your edits, you can force a map update on your client by selecting on your client settings > advanced > data transfer > refresh map of my area

  • When I encounter traffic on the road, what type do I report?

You can report a road traffic or Waze will sometimes prompt you if it detects a slowdown or you are stopped for a period of time. Here are the traffic types;

Standstill traffic - only select this option if you are in a bumper-to-bumper situation and movement is approximately one car length every 10 minutes and above, and you are not at a traffic light junction (signalized intersection)

Heavy traffic - Bumper-to-bumper situation but the speed is from 1 to 10 kph, and you are not at a traffic light junction (signalized intersection). This is the usual EDSA or C5 traffic where walking is sometimes faster than driving.

Moderate traffic - Speed is usually 10 to 25 kph

  • I see traffic cameras everywhere and report their locations, why doesn't Waze display them when I pass by them again?

The cameras that should be reported are speed trap cameras, red light cameras or fake cameras. Right now, there are only a few roads which have fixed or static speed cams, they are Commonwealth Ave, Macapagal Blvd, NLEX, and SLEX. There may also be mobile speed cameras on those roads. There are no other speed cameras elsewhere and there are no red light cameras or fake cameras anywhere in Metro Manila. Red light cameras snaps a picture of your car and license plate when you run a red light. The cameras you see on top of traffic lights or intersections are just plain CCTV cameras and they only monitor the road conditions.

As of 6/19/2014, speedcameras have been disabled on our maps based on our request during the June meetup. You will still be able to report them but they will no longer appear on WME and you will not get any points for them

  • What is the difference between Map Issues and Update Requests?

Map issues are Waze generated and based on analyzed wazer traffic. Update Requests or URs are waze user submitted requests to fix user identified map issues.

  • How do I fix Map Issues?

Waze generated map issues are the following, street not connected to a junction, missing street, turn restriction disabled, incorrect street direction, and route not followed by users. Almost all except the last one are fairly easy to fix. Here are some suggestions on how to resolve these issues;

1. Street not connected - drag the street to the nearest street or junction indicated by the average or latest drives, set the turn restrictions, select solved and save.

2. Missing street - draw a new street by following the aerial map, GPS points, or the average or latest drives, set direction, set the turn restrictions, select solved and save.

3. Turn restriction disabled - enable the turn restriction based on the average or latest drives, select solved and save.

4. Incorrect street direction - set the direction based on average or latest drives, select solved and save.

5. Route not followed by user - this one is a bit tricky to fix. It could be that somewhere down the route, there is a turn restriction disabled, a disconnected road, a missing road, wrong street direction, or it could just be that the road isn't the 'best' route to take. You must look for something that is making waze route to the least popular route. If you can't find anything, it's best to leave it and don't mark it as 'not identified' as this will be forwarded to IGN editors and they are not familiar with our roads.

  • Waze keeps on routing an illegal U-Turn on an intersection, how do I stop this while keeping the road design simple?

On the Waze Map Editor (WME), select the road where Waze routes an illegal U-Turn. The properties for that segment are displayed on the left side of the editor. Drag either point A or point B so that the length of the segment is equal or less than 10 meters. Waze will no longer route the U-Turn on this segment.

  • Waze does not use the U-Turn segment I created between two roads, what could be the problem?

Check the turn restrictions, if the turn restrictions are already enabled, the distance of points A and B could be less than or equal to 10 meters. Drag either of the points to make the segment longer than 15 meters.

  • Are there any shortcut keys for the Waze Map Editor?

You can view the wiki page on Keyboard shortcuts

  • Waze keeps routing me on roads inside gated subdivisions, how do I edit the roads to prevent this?

Select all the roads within the gated subdivision and change the road type to "Private Road". This would prevent Waze from using these roads for routing unless your destination is within the subdivision.

  • I'm trying to edit a road but it is locked, how do I unlock it and why is it locked?

You can request for an unlock in the Philippines - Waze Forum

or in the Philippine Waze Users Facebook Group.

While we appreciate the help of newbie waze editors in editing our maps, they are prone to creating errors if not informed and educated properly on our map editing guidelines. If you would like to manage an area local to you or you are very familiar with, apply for area manager permissions.

  • The city names are wrong, I've edited them but the correct name still isn't displayed. What do I need to do to correct this?

The problem with the city names is that city tiles takes a while to update. So even if we fix incorrect city names, the errors are still displayed on the client as well as the editor maps through the city layer. There is really no schedule nor any notice for the city tile updates, we just have to wait until the correction appears.

  • There is a road near my area which, depending on the time allows you to drive through it, how can I set this road to do this?

You can add Time or Scheduled restrictions to the road or turn. For more details on how to do this, you can visit the Scheduled restrictions wiki.

  • Search function doesn't work, how do I fix it?

This is a known issue that has been working on and off. The quick fix is to uninstall and install the app on your device.

  • I'm editing a road but I keep on getting this message "While you were editing, the elements you're trying to save have been modified and/or deleted.". What do I need to do?

If refreshing the map editor does not work, go to the waze status page and check for any announcement from waze about any map tiles update (please note for that date of the update) if the problem persists after the tiles update try to edit around the ghost segment to force the update of the tiles (remember to check the status page for the tiles update a few days later).

  • How do I report flooding so that wazers will not be routed on a flooded road?

Road closure reports were added for this, to ensure that routing will not be done on the reported road. Road hazard reporting will not affect routing and will only pop up on the client as a notification. This is the main difference between a "Hazard" report and a "Closure" report.

To report flooding on a road, select Closure on the Waze app, select the road that is flooded by tapping on the arrow pointing to the road, tap Continue, select the closure type Hazard. You can add "flood", "unpassable", or whatever you wish to describe the road closure on the detail field and then tap Send.

Notes:

  • If one user reports a road closure - it will only affect that user's view of the map. In order to affect all users, a number of users need to report the same closure.
  • The number of reports needed to close the roads for all the users varies based on the road's weight, the user's rank and the country.
  • The road will be opened when a number of users drive through the road.

Philippine Waze Area Manager

What is an Area Manager and what does it entail:

  • An Area Manager is a Waze community member (a user) who wishes to take an active and proactive role in maintaining specific areas of the Waze map. How deeply involved and how much time an Area Manager spends maintaining the Waze map varies greatly. Duties of an Area Manager include, but not necessarily limited to:
  • Seek to continuously improve the maps for navigation, i.e. naming un-named roads and setting turns properly.
  • Make changes to the map when road geometry needs to be changed, or roads added or removed from the map.
  • Edit road construction areas, especially for closures so that users are not routed into those areas.
  • Respond to and act on Update Requests from Waze drivers.
  • Maintain speed and red-light cameras, processing reports of devices from Waze drivers.
  • Process and resolve Map Errors or Problems as shown on that layer in the Waze Map Editor.
  • Act as a mentor to other editors, offering advice in the forums and when you see improper edits on the map.

By being an Area Manager, you agree to be reachable and available to respond to communication from your fellow Waze editors. Being an Area Manager is not for your convenience so you can edit the map at a higher level but rather it entails the responsibilities listed above.

When you become inactive or unreachable for a long period of time, your AM permissions and level will be revoked.


The following are the conditions or requirements for approval of AM applications:

  • Approval of at least current Area Managers, if possible the same AMs for the location applied, upon review of the map edits of the AM applicant.
  • Meets 'X' number of edits for area applied
    • City wide or permalink wide - 10k map edits
    • Metro Manila, Metro Cebu, & Metro Davao wide - 20k map edits
    • Province wide - 25k map edits
    • Region wide - 50k map edits
    • Luzon, Visayas, or Mindanao Island Groups - 100k map edits
    • Countrywide - CM only or 250k edits
  • Must have at least 10 posts in Waze forum or FB group page (must be related to waze and have sense)
  • Must have resolved at least 100 update requests
  • Must have at least 2,500 existing kilometers
  • Must be an active member of the Philippine Waze forum and/or FB group page
  • Must attend at least waze meetup per year. Waze has a quarterly meetup. This can be waived if the applicant is not from Metro Manila
  • Must pass an online exam. (Currently under process)


List of Philippines Area Managers

This list is based on the recently approved Area Managers, those approved after the Philippines became self-managed. Those approved before self-management are not listed, send a message to kazmuth on the forums if you have been previously approved and wish to be added. You can send these wazers a message in the forums if you want to have an issue fixed in their respective areas.

* - Country Manager permissions

Waze Username Area Since
daxky Angeles 11/18/2013
deadlockprocess Bacolod, Silay 2/17/2014
shogsbro Baguio 2/17/2014
daxky Batangas City 11/18/2013
junrex Bicol (Region V) 6/24/2013
M-a-r-s Bislig 8/22/2013
daxky Boracay Island 12/31/2013
kid_ant Cabanatuan 8/2/2013
deadlockprocess Kabankalan, Ilog 2/17/2014
mponteres Cabuyao 8/22/2013
ericbishop CALABARZON (Region IV-A) 7/5/2013
monz98 CALABARZON (Region IV-A) 6/28/2013
Ungas CALABARZON (Region IV-A) 6/29/2013
deadlockprocess CALABARZON (Region IV-A) 2/17/2014
tcajita Calamba 1/11/2014
atjcamacho Cavite Province 6/23/2013
BRM-BLK-BMW Cavite Province 7/4/2013
abecedarian2380 Cebu Province 8/2/2013
gerix28 Cebu Province 6/22/2013
pinoyoutdoor Cebu Province 7/7/2013
warfab Cebu City 8/14/2013
world_32m24hzt Cebu City 7/26/2013
world_8eidg3mz Cebu City 7/20/2013
Calicantzaros Central Luzon (Region III) 7/2/2013
kwithoor Central Luzon (Region III) 1/11/2014
SEELE_01 Central Luzon (Region III) 1/29/2014
gerix28 Central Visayas (Region VII) 6/28/2013
nobs98 Central Visayas (Region VII) 7/8/2013
M-a-r-s Eastern Mindanao 12/5/2013
monz98 Eastern NCR 6/27/2013
RangeRoverHSE Eastern Visayas (Region VIII) 1/27/2014
deadlockprocess Iloilo City 2/17/2014
deadlockprocess Iloilo Province 3/3/2014
crgandionco Leyte 9/9/2013
daxky Lipa 11/18/2013
foruboru Luzon Island Group 8/8/2013
ivanatorprime Mandaluyong 10/11/2013
warfab Mandaue 8/14/2013
world_8eidg3mz Mandaue 7/20/2013
markking1991 Manila 6/23/2013
mponteres Muntinlupa 8/22/2013
atjcamacho NCR 6/23/2013
bdo2v NCR 7/4/2013
zy_pher NCR 1/11/2014
Calicantzaros NCR 7/2/2013
daxky NCR 11/18/2013
furuboru NCR 6/23/2013
kwithoor NCR 1/11/2014
M-a-r-s NCR 7/7/2013
mirallwood NCR 8/18/2013
RangeRoverHSE NCR 1/11/2014
SEELE_01 NCR 1/29/2014
SkipperBoo26 NCR 7/7/2013
BRM-BLK-BMW NCR 7/4/2013
deadlockprocess NCR 2/17/2014
deadlockprocess Negros Occidental Province 3/3/2014
RenzDeion Pampanga 6/22/2013
zy_pher Pangasinan 7/12/2013
evs_13 Pangasinan 7/12/2013
* baldugaras Philippines 8/7/2013
iceden Philippines 6/25/2013
* kazmuth Philippines 11/13/2012
* rider111 Philippines 6/21/2013
* SpeedDzel Philippines 11/13/2012
markhaggai Puerto Princesa 8/30/2013
ongandy86 Quezon City 8/30/2013
crgandionco Samar 9/9/2013
crgandionco Southern Leyte 12/21/2013
tcajita Sta Rosa 1/11/2014
kwithoor Ilocos Region (Region I) 3/11/2014
kwithoor Cagayan Valley (Region II) 3/11/2014
shogsbro Northern Luzon 6/22/2014
swisspound2 NCR 3/31/2014
deadlockprocess Central Luzon (Region III) 4/20/2014
deadlockprocess Central Visayas (Region VII) 4/20/2014
deadlockprocess Western Visayas (Region VI) 4/20/2014
Grand_Master_Jedi Central Visayas (Region VII) 4/26/2014
Grand_Master_Jedi Visayas Island Group 5/16/2014
zy_pher Luzon Island Group 5/16/2014
deadlockprocess Mindanao Island Ground 6/2/2014
Adabadada Cavite Province 6/22/2014
albertcong Cabadbaran 6/25/2014
albertcong Surigao City 6/25/2014
albertcong Butuan 6/25/2014
albertcong Bislig 6/25/2014
palin_1274 NCR 6/27/2014
palin_1274 CALABARZON (Region IV-A) 7/1/2014
monz98 Eastern NCR 7/3/2014
monz98 CALABARZON (Region IV-A) 7/3/2014
albertcong Caraga (Region XIII) 7/10/2014
SpeedyGonzalesAT Metro Cebu 8/5/2014
kanamits Negros Occidental Province 8/5/2014
gerix28 Region VII 10/6/2014
Guardian4ngel Luzon Island Group 10/9/2014
Adabadada NCR and Cavite 11/2/2014
cryptmaster Bulacan Province 11/29/2014
SpeedyGonzalesAT Cebu Province 11/29/2014

Note: Eventhough approved as an area manager, management for an assigned area will be lost after three months of inactivity or waze editing.