Changes

From Wazeopedia

Philippines/Editing resources

7,452 bytes added, 1 year ago
m
General Guidelines on Road Editing
== Map Editing Guide for the Philippines ==
It is presumed you have read [[wazeopedia.waze.com/wiki/Global/Best map editing practice|Best map editing practice]] before reading this section. While most of the content here 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 exactly as we see. There are very specific ways to map out roads and places on the Waze Map Editor for routing to be correct, going far beyond seeing something and drawing it on the map. 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.
1=== Map Editing Priorities ===Higher level editors especially Area Managers, are expected to maintain and update the area where they live. Create road (whether tracing aerial images/gps pointsThis means, or from recorded drives)L3+ editors '''SHOULD''' first work on their immediate vicinity. The reason for this is because you should have first hand information and should be familiar with your areas. You don't need to send messages to reporters to ask questions, this should facilitate for a faster resolution of URs.
The suggested way to clear your area is;# Go to maximum zoom in level (10)# Go to your location# Zoom out one level at a time# Resolve and UR, MP, PUR, etc.# Repeat step 3 and 4By doing this, you should be able to clear hole near your area. Even if you clear until zoom level 3 only, you would have cleared 12 sq km or an area within 1.5 km radius from your location. '''The following should be prioritized if you are not working in your immediate area:'''# Update Requests - Do this first to reduce the number of URs.# Place Update Requests - Do this next if you have cleared ALL URs.# System Detected Problems - Also known as Map Problems, these need checking as they may be valid issues.# Place Points - Move place points to their exact locations, use personal knowledge or street view to accurately move place points to the correct locations.'''The following are NOT priorities, work on the previous list instead of these:'''# Speed limits - Don't be a points whore. You shouldn't be after points anymore since we don't look at it for level promotions.# Alignment of place shapes - Seriously, you don't need to align every place to its perimeter. There is no added benefit to this for navigation. If even part of the place is within the perimeter or if the entry point is correct, Wazers will be led to the right location. You are just doing this for points if you do this. # Aligning roads to aerials - It is impossible to exactly align segments to their exact locations based on the aerial images. You need to factor in elevation of the roads, parallax effect due to the angle of the satellite, accuracy of how the images were set in WME, etc. The tolerance for the map stickiness is around 20-30m so even if the segment is 20m off its location, Waze should still be able to handle it. Do something useful instead like doing the items on the priority list instead of this. == 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 [[wazeopedia.waze.com/wiki/Global/Best map editing practice|Best map editing practice]] for specifics. 2. Set Setting the 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 connect 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
* 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 Setting 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 Setting directionality (: This is fairly straightforward for most roads. However, take note of the rules for splitting segments before mapping two parallel one-way segments going in opposite directions. Many Philippine roads should be mapped as two -way segments despite being split in reality (e.g. subdivisions with a guard house between the entrance and exit) 5. Setting the elevation level (Ground, Tunnel = '''-1''', Flyover = '''1''', '''2''', '''3''', etc.): Only tunnels or underground roads are to be set to -1. If one way)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.
56. Set the elevation level (Ground, Tunnel = '''Setting speed limits: Do this in accordance with [http://www.lto.gov.ph/component/jdownloads/send/9-republic-act/70-republic-act-1''', Flyover 4136?option= '''com_jdownloads REPUBLIC ACT No. 4136] Chapter IV Article 1(Section 35) ''Restriction as to speed', '''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 levelCheck [[Philippines/Speedlimit|here]] for details.
67. Set the speed limits in accordance with [httpConnecting or creating junctions (attaching to existing roads)://wwwBefore attempting to connect roads, make sure both roads are within your editing level.lto.gov.ph/component/jdownloads/send/9-republic-act/70-republic-act-4136?option=com_jdownloads REPUBLIC ACT No. 4136] Chapter IV Article 1 If any segment is above your level you will not be able to make a connection (Section 35they are not connected even if they look like they are) ''Restriction as . All you will have succeeded in doing was to speed''put an end node on top of a segment. Check [[PhilippinesYou will know that you have successfully made a connection/Speedlimit|here]] for detailsjunction when you see the roads "snap" together, and turn direction arrows appear.
7. Connect or create junctions (attach to existing roads) except if these are Do not make a connection/junction between non-routable road types like (e.g. '''Walking Trails''', '''Pedestrian Boardwalk''', '''Stairway''', '''Railroad''', and '''Runway/Taxiway) '''and routable road types, even if they are connected in real life. This will cause routing problems.
8. Set Setting turn restrictions and if u-turns are allowed on junctions: This is straightforward - red is disallowed, the green is allowed. The easiest and fastest way to do this allow all turns 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.
9Leaving a turn restriction disabled does not mean that Waze will not route to it, Waze might still route a turn to it since it is connected. Hence, for cases where driving through is physically impossible (e.g. there is a gate or wall between segments), the segments need to be totally disconnected from and placed 5m apart. Name  For u-turns at junctions (those fish-hook u turns at the roadends of segments), if the default is still to leave them disabled.  9. Naming roads: 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 -
# Always use the official name as the street name ([http://www.dpwh.gov.ph/dpwh/2016%20DPWH%20Road%20and%20Bridge%20Inventory%20v.2/2016%20DPWH%20Road%20and%20Bridge%20Inventory/index.htm DPWH Name]) . # Do not use multiple street names separated with a slash "/" except if it will immediately fork into two exits. Or the exit leads to two separate turns
# If there are local (LGU) or other name for the street, add them as an alternative name
# Use punctuation for initials except for cardinal directions
# N, E, W, S, NE, NW, SE, and SW without punctuation will be read as cardinal directions
# Excluding route numbers, maximum length of street name should NOT exceed 5 words (street name)
# Do not use the word 'to' (preposition) as the beginning of on a street name, unless it is an actual street name . It will not sound right when using 'Adora' or non English TTS # 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' . Segment names are not localized so it will sound awkward when the rest of the instructions are in Filipino.
# Refer to the Philippines TTS List for a complete list of supported abbreviations <nowiki>https://docs.google.com/spreadsheets/d/1FsYSMh1aR7l-ZF9NAHT63h8xSVFD5S8ixeJlsM98o4w/edit?usp=sharing</nowiki>
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 [https://docs.google.com/spreadsheet/lv?key=0AgVtBjo5tTNgdG5vVHN5RmVzaWdlWk1VLTRzYUhGN0E&lt Waze Abbreviations and TTS] standards so that our street names are ready for TTS (Text To Speech).
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 '''[https://www.facebook.com/groups/WazePhilippines/doc/494500773906457 repeating city names]''' for a complete listing of all the cities and municipalities within the Philippines.
11. Splitting roads: Most Philippine roads can be mapped as a single road despite being split in reality. '''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 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 and continuous gap/(blank area ) between the color-by-azimuth arrows at the 100m /500ft zoom level.* Multiple houses or businesses with no off-street parking are located directly on the street but are not accesible from the opposite direction of traved due to lengthy median, obstruction, or traffic control signage.
* U-Turns are required to properly make turns that are blocked by a median.
A road '''should not''' be  '''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(see exceptions above).* The non-drivable median is interrupted by a cross segment at most intersections.* There are is a lot center turn lane (any width) between directions of travel. Dividing this type of roads intersecting which can only road creates problems when people turn onto from the middle lane because there is no road for the nearest direction of travelnavigation to follow.* Google Maps or other mapping source show it as It is possible and legal to make a split driver side turn/u-turn everywhere along the road* The non-drivable median objective is interrupted by a cross segment at most intersectionssolely for visual appearance or to make the road match another visual source like Google Maps. '''12. 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 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
13. Locking roads: When you are confident on an of the 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 |Philippines Locking Policy]] for more details. 14. '''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 == Places are the equivalent of Points of Interest (POIs) in other navigation systems. Unlike traditional cartography or other online maps, we do not map every single place/POI we see. We only add places that are likely to be useful for navigation. Hence, we do not map generic places such as fishball stands, sari-sari stores, plants, pedestrian footbridges/overpasses, etc. That is also why we try to avoid generic names such as "basketball court", "fountain", "store", etc. for places we've deemed worth mapping. See our [[philippines:Philippines/Places_Policy|Places Policy]] for more details.* '''Area Places''' - These are POIs that are useful visual landmarks and are mapped to be visual cues on the client app. . * '''Point Places''' - Most establishments should be mapped as a point place. These are searchable on the Waze app but not visible unless chosen as a destination == General Guidelines on other WME Objects == === 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.  See next section for guidance on use of Map Comments with Real Time Closures.  === Real Time Closures ===A Real Time Closure (RTC) is a temporary closure that is added to the map for segments that are impassable in one or both directions for any reason but does not need to be modified (i.e. no change in turn restrictions, etc.). This should NOT be used for lane closures. Read [[global:Real_time_closures|here]] for more details. At present, editors level 4 and above are able to add and remove real-time closures to roads in the Philippines. Special permissions have also been given to our CCP partners such as the MMDA. For urgent closures, contact a local champ to facilitate the addition or removal of an RTC. When setting RTCs based on information coming from an external source, the best practice is to add a Map Comment with a link to the source. This will be helpful for local editors to verify the info, and make changes if needed. It is also recommended to lock the map comment to a higher level, and set an expiration date matching the closures end date. But please consult with your local community on that.  If you need to set an RTC that is more than a month long, make sure you check on it at least once a week. There have been a lot of instances where RTCs for several months have been placed and then never checked again. This resulted in segments being closed off from routing long after they have reopened. URs were piling up on the area due to this and routing has been severely affected on the area.  Watch a tutorial on adding Map Comments to RTCs [https://www.youtube.com/watch?v=VB9cvebD4cs&feature=youtu.be here]. === Speed Cameras ===Adding any form of camera from the app has been disabled. This can only be added on WME by high level editors. === Major Traffic Events ===A Major Traffic Event (MTE) is an event that involves road closures. Read [[global:Real_time_closures#Major_Traffic_Events_.28MTEs.29|here]] for more details.  Before making any MTE, please coordinate with local champs first. This is to prevent duplication of events and to make sure all closures are created and placed correctly.
12. '''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=== Subdivisions, riversVillages, lakesGated, seaRestricted, 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'''. Private Compounds and buildings fall ===In order to not break routing into this place type. Parking lots gated areas, all roads inside these areas should also be an Area Place and NOT a Point Place. Area place geometry should cover only the exact area of the placePrivate road type. Do not stretch the geometry to where it's borders touch or overlap segments. Road types If there 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 multiple entrances to add on the map. Adding these makes these places searchable on areas, consider implementing suggestions from the Waze app[[global:Private_Installations|Private Installations]] wiki. If there is already an Area Place, you are unsure how to do not add a Point Place and vice versa. Establishments inside a building or compound fall into this place type.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 avoidedcontact your area manager or a senior editor.
[[Category:Philippines]]
58
edits