User:Flmbray View history

Latest revision as of 04:00, 20 August 2011

My Personal Tips

Handling Update Requests

A primary objective for user update requests should be to respond to them in a timely manner. Nothing looks worse to a user than getting a response to their update request from 2 years ago.

When replying, be polite and always assume the user was right. Users don't submit false reports maliciously. It doesn't mean they did it correctly or at the right location on the map, but if the response is rude or short ("i can't tell what you are talking about") then the user won't bother to reply. Replies to requests for more information are hard enough to come by as it is.
Always sign your replies (best to use your Waze username). Part of the signature (or the response) should inform the user how they can contact you - either an email or a link to compose a PM to your private message inbox in the waze forums.
Do not leave URs open because you don't have enough information. Ask for more information, and if the user doesn't respond, either:
- Take a field trip if you are close
- Close the request
When replying to a request asking for more information, make the very first part of the response a DATE that you intend to close the request if no response is received. Use a "PC" prefix on the date, meaning "Pending Close"... like this "PC 8/24 Thanks for your request"
Do not assume a user reported an error in the exact location on the map that the problem occurs. You must play detective to a certain degree. In particular, check the connectivity of all segments in the area.

Routing

Do not route onto Parking lot roads... they can be drawn on the map but should not be used for routing. I'm not sure if Waze routing algorthm does this or not, but it makes sense to document as such on the map anyway.

Splitting/Joining Roads

As the Wiki (#1) and various forum posts (#1, #2) state pretty clearly, major highways, minor highways, other roads that primarily use junctions should generally not be split, as it causes the intersections to become unnecessarily complicated, both for the user and for the routing engine.

There are times when it makes sense, however. Here is a

Error creating thumbnail: File missing

Split? Yes!

good example of when to split a junction-based road. This image was taken just south of the John Young / Princeton interchange in Orlando. It shows the southern point at which a road which is only 2 lanes in each direction separates and becomes a 3-lane road in southbound direction and a 3+3 lane in the northbound direction. The number of lanes is mostly irrelevant - the important thing is the amount of physical separation between the lanes.

Here's how NOT to split a road. How many problems can you count in this?? Trust me, however many you can count, you can triple that number if you could actually see all of the routing problems.

.

To-Do

@@ Line 1: / Line 1: @@
-[[Special:MyPage/Flaring_Roundabouts|Flaring Roundabouts]]
+* [[Special:MyPage/Flaring_Roundabouts|Flaring Roundabouts]]
+* [[Special:MyPage/TTS_And_Split_Roadways|The problem with TTS on split roadways]]
+== My Personal Tips ==
+=== Handling Update Requests ===
+A primary objective for user update requests should be to respond to them in a timely manner.  Nothing looks worse to a user than getting a response to their update request from 2 years ago.
+* When replying, be polite and always assume the user was right.  Users don't submit false reports maliciously.  It doesn't mean they did it correctly or at the right location on the map, but if the response is rude or short ("i can't tell what you are talking about") then the user won't bother to reply.  Replies to requests for more information are hard enough to come by as it is.
+* Always sign your replies (best to use your Waze username).  Part of the signature (or the response) should inform the user how they can contact you - either an email or a link to compose a PM to your private message inbox in the waze forums.
+* Do not leave URs open because you don't have enough information.  Ask for more information, and if the user doesn't respond, either:
+** Take a field trip if you are close
+** Close the request
+* When replying to a request asking for more information, make the very first part of the response a DATE that you intend to close the request if no response is received.  Use a "PC" prefix on the date, meaning "Pending Close"...  like this "PC 8/24 Thanks for your request"
+* Do not assume a user reported an error in the exact location on the map that the problem occurs.  You must play detective to a certain degree.  In particular, check the connectivity of all segments in the area.
+=== Routing ===
+* Do not route onto Parking lot roads... they can be drawn on the map but should not be used for routing.  I'm not sure if Waze routing algorthm does this or not, but it makes sense to document as such on the map anyway.
+=== Splitting/Joining Roads ===
+As the Wiki ([http://www.waze.com/wiki/index.php/Best_map_editing_practice#When_.28Not.29_to_Split_a_Two-Way_Road #1]) and various forum posts ([http://www.waze.com/forum/viewtopic.php?f=6&t=11295&p=93083&hilit=split#p93083 #1], [http://www.waze.com/forum/viewtopic.php?f=10&t=11175 #2]) state pretty clearly, major highways, minor highways, other roads that primarily use junctions should generally not be split, as it causes the intersections to become unnecessarily complicated, both for the user and for the routing engine.
+There are times when it makes sense, however.  Here is a [[Image:2011-08-19 213954.png|100px|thumb|left|Split? Yes!]]  good example of when to split a junction-based road.  This image was taken just south of the [https://descartes.waze.com/live/?zoom=5&lon=-81.41475&lat=28.56992&layers=BTTTTTTTTTTTTT John Young / Princeton interchange] in Orlando.  It shows the southern point at which a road which is only 2 lanes in each direction separates and becomes a 3-lane road in southbound direction and a 3+3 lane in the northbound direction.  The number of lanes is mostly irrelevant - the important thing is the amount of physical separation between the lanes.
+Here's how NOT to split a road.  How many problems can you count in this??   Trust me, however many you can count, you can triple that number if you could actually see all of the routing problems.
+[[Image:2011-08-19 235442.png|100px|thumb|left]]
+.
+.
+.
+== To-Do ==
+=== General Corrections ===
+https://descartes.waze.com/live/?zoom=7&lon=-81.97975&lat=28.00021
+=== Bad Road Alignment ===
+https://descartes.waze.com/live/?zoom=5&lon=-81.49793&lat=28.17471
+=== Bad Junctions ===
+https://descartes.waze.com/live/?zoom=7&lon=-81.98187&lat=27.99695 - Wilkinson Rd

Search