Philippines/Editing resources

Map Editing Guide for the Philippines

It is presumed you have read Best map editing practice before reading this section. While most of the content in the Global Waze Wiki are applicable for the Philippine road network, the Waze map still needs to be tweaked and customized for the Philippines. Below is the general guideline for Waze map editing in the Philippines. This supersedes any generic guide wiki entries not specific to the Philippines.

Note to all would-be editors in the Philippines

Waze map editing differs from traditional cartography and other online cartography programs in that we don't just map as we see. Many well-meaning editors have attempted to edit the Waze map without carefully perusing the guidelines first, causing damage to the map and messing up navigation instead. That being said, once you have gotten the hang of the rules, much of it is common sense and logic. It is, however, expected of every editor in the Philippines to be part of the community because Waze is ever-evolving and so are community guidelines.

General guidelines on road editing

1. Creating roads: You may use aerial images or GPS tracks as a guide, or you may use your recorded drives. When drawing roads, pay careful attention where you trace. Generally it is recommended that you trace right where the GPS tracks are thickest (if available). Please make sure the Roads layer is on before tracing a new road to prevent making duplicate/overlapping roads. Note also that we don't necessarily trace exactly what we see. See Best map editing practice for specifics.

2. Set road type, some suggestions;

• Freeways – Toll Roads or Expressways where a toll fee needs to be paid
• Ramps – On and off ramps from Freeways, segments that are not at-grade or ground level, used to connect segments with different levels
• 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.
• Primary Street – Main thoroughfares of a city or municipality and/or DPWH Tertiary Roads
• Street – ordinary street, mainly residential
• Off-road / Not maintained – drivable roads but not used for routing, except when 'allow dirt roads' option is enabled or if destination is on the dirt road.
• 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.
• Ferry - Ferries that meet any of these conditions should generally not be mapped
  • Passenger ferries without vehicles
  • Ferries requiring pre-booking
  • Private ferries unavailable to the general public
  • Ferries over two hours in duration If the ferry does not meet any of the above conditions, it can be added to the map

• 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. If the road is too narrow like an alleyway and only motorbikes and tricycles can drive through it, use Street instead and restrict access to it so that only select vehicles can be routed on it.

3. Set road type attributes.

• Toll Road - Expressways where toll fees are collected
• Unpaved - If the road is a highway, primary, or a street but is unpaved. Different from off-road where only specialized vehicles can pass through
• Tunnel - If the road is underground

4. Set directionality (two way or one way)

5. 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 unless they pass under a segment already on ground level.

6. Set the speed limits in accordance with REPUBLIC ACT No. 4136 Chapter IV Article 1 (Section 35) Restriction as to speed. Check here for details.

7. Connect or create junctions (attach to existing roads) except if these are non-routable road types like Walking Trails, Pedestrian Boardwalk, Stairway, Railroad, and Runway/Taxiway

8. 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 and placed 5m apart.

9. 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 leave segments in red (unnamed). 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.

Follow the PH Road Naming convention when adding road names -

1. Always use the official name as the street name (DPWH Name)
2. Do not use multiple street names separated with a slash "/"
3. If there are local (LGU) or other name for the street, add them as an alternative name
4. Use punctuation for initials except for cardinal directions
5. N, E, W, S, NE, NW, SE, and SW without punctuation will be read as cardinal directions
6. Excluding route numbers, maximum length of street name should NOT exceed 5 words (street name)
7. Do not use the word 'to' (preposition) as the beginning of a street name, unless it is an actual street name
8. Do not use the word 'exit' (e.g. 'Exit to...') in the street name. It can be used when the street is commonly known to have one e.g. 'Marilao Exit'
9. Refer to the Philippines TTS List for a complete list of supported abbreviations https://docs.google.com/spreadsheets/d/1FsYSMh1aR7l-ZF9NAHT63h8xSVFD5S8ixeJlsM98o4w/edit?usp=sharing

10. 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 AREA, SUBDIVISION, DISTRICT or BARANGAY NAME nor should it be combined with the PROVINCIAL Name.

Take extra care on the City labels of your edits. Unlike Street names which reflects edits (or corrections) quicker and appears on the next update, City names 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 app despite any corrections made.

Stick to the official (but shortest possible) name of the jurisdiction being edited. 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.

On the matter of city labels, we omit the word "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.

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

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 Philippines Locking Policy for more details.

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

General guidelines on editing places

Adding Places - When adding Places, make sure their location is properly identified through the add Places draw function and add the address in the details as well. If a Place will cover beyond a city's or municipality'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.

• 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. Compounds and buildings fall into this place type. Parking lots should also be an Area Place and NOT a Point Place. Area place geometry should cover only the exact area of the place. Do not stretch the geometry to where it's borders touch or overlap segments. Road types are rendered differently so all segments appear the same on WME but will be displayed differently on the client app.
• 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. Establishments inside a building or compound fall into this place type.

Map Comments

Map comments are used to communicate with other editors but it is NOT an alternative to the other communication channels of the community. Use it to leave short notes to other editors (e.g. "Do not connect these segments, there's a gate here"). DO NOT use it to request for edits as map comments are too easy to overlook.