☰

WME UR Comments Custom List

This script is for Custom comments to be used with my other script UR comments

目前為 2014-12-12 提交的版本，檢視 最新版本。

  1. // ==UserScript==
  2. // @name           WME UR Comments Custom List
  3. // @description    This script is for Custom comments to be used with my other script UR comments
  4. // @namespace      RickZabel@gmail.com
  5. // @grant          none
  6. // @grant          GM_info
  7. // @version        0.0.1
  8. // @match          https://editor-beta.waze.com/*editor/*
  9. // @match          https://www.waze.com/*editor/*
  10. // @author         Rick Zabel '2014
  11. // @license        MIT/BSD/X11
  12. // ==/UserScript==
  13.  
  14. /* Changelog
  15.  * 5th update to the format
  16.  * 0.0.1 - initial version
  17.  */
  18.  
  19. //I will try not to update this file but please keep a external backup of your comments as the main script changes this file might have to be updated. When the custom comments file is auto updated you will loose your custom comments. By making this a separate script I can try to limit how often this would happen but be warned it will eventually happen.
  20.  
  21. //if you are using quotes in your titles or comments they must be properly escaped. example "Comment \"Comment\" Comment",
  22. //if you wish to have blank lines in your messages use \n\n. example "Line1\n\nLine2",
  23. //if you wish to have text on the next line with no spaces in your message use \n. example "Line1\nLine2",
  24.  
  25. //Custom Configuration: this allows your "reminder", and close as "not identified" messages to be named what ever you would like.
  26.  
  27. //the position in the list that the reminder message is at. (starting at 0 counting titles, comments, and ur status). in my list this is "4 day Follow-Up"
  28. window.UrcommentsCustomReminderPosistion = 3;
  29.  
  30. //this is the note that is added to the the reminder link  option
  31. window.UrcommentsCustomReplyInstructions = 'To reply to this request go to the following link and click the map pin, then click on the conversation button.';
  32.  
  33. //the position of the close as Not Identified message (starting at 0 counting titles, comments, and ur status). in my list this is "7th day With No Response"
  34. window.UrcommentsCustomCloseNotIdentifiedPosistion = 6;
  35.  
  36. //This is the list of Waze's default UR types. edit this list to match the titles used in your area! 
  37. //You must have these titles in your list for the auto text insertion to work!
  38. window.UrcommentsCustomdef_names = [];
  39. window.UrcommentsCustomdef_names[6] = "Incorrect turn";						//"Incorrect turn";
  40. window.UrcommentsCustomdef_names[7] = "Incorrect address";					//"Incorrect address";
  41. window.UrcommentsCustomdef_names[8] = "Incorrect route";					//"Incorrect route";
  42. window.UrcommentsCustomdef_names[9] = "Missing roundabout";					//"Missing roundabout";
  43. window.UrcommentsCustomdef_names[10] = "General error";						//"General error";
  44. window.UrcommentsCustomdef_names[11] = "Turn not allowed";					//"Turn not allowed";
  45. window.UrcommentsCustomdef_names[12] = "Incorrect junction";				//"Incorrect junction";
  46. window.UrcommentsCustomdef_names[13] = "Missing bridge overpass";			//"Missing bridge overpass";
  47. window.UrcommentsCustomdef_names[14] = "Wrong driving direction";			//"Wrong driving direction";
  48. window.UrcommentsCustomdef_names[15] = "Missing Exit"; 						//"Missing Exit";
  49. window.UrcommentsCustomdef_names[16] = "Missing Road";						//"Missing Road";
  50. window.UrcommentsCustomdef_names[18] = "Missing Landmark";					//"Missing Landmark";
  51. window.UrcommentsCustomdef_names[19] = "Blocked Road";						//"Blocked Road";
  52. window.UrcommentsCustomdef_names[21] = "Missing Street Name";				//"Missing Street Name";
  53. window.UrcommentsCustomdef_names[22] = "Incorrect Street Prefix or Suffix";	//"Incorrect Street Prefix or Suffix";
  54.  
  55.  
  56. //The comment array should follow the following format,
  57. // "Title",     * is what will show up in the UrComment tab
  58. // "comment",   * is the comment that will be sent to the user currently 
  59. // "URStatus"   * this is action to take when the option "Auto Click Open, Solved, Not Identified" is on. after clicking send it will click one of those choices. usage is. "Open", or "Solved",or "NotIdentified",
  60. // to have a blank line in between comments on the list add the following without the comment marks // there is an example below after "Thanks for the reply"
  61.    // "<br>",
  62.    // "",
  63.    // "",
  64.  
  65. //Custom list
  66. window.UrcommentsCustomArray2 = ["Errors with no descriptive text",
  67. 			"Waze did not send us enough information to fix your request. Would you please let us know what went wrong with the route Waze gave you? Would you tell us your destination as you entered it into Waze? Thanks!",
  68.             "Open",
  69.             "4 day Follow-Up",
  70.             "Just a reminder: We haven't received a response on your report. If we don't hear back from you we'll have to infer everything is okay and close the report. Thanks!",
  71.             "Open",
  72.             "7th day With No Response",
  73.             "The problem was unclear and volunteers didn't receive a response. As you travel, please feel welcome to report any map issues you encounter. Thanks!",
  74.             "NotIdentified",
  75.             "Fixed",
  76.             "Thanks to your report we've found and fixed a problem with the map. The fix should reach handheld devices within a week, but on rare occasions it can take closer to two weeks. ",
  77.             "Solved",
  78.             "Valid Route",
  79.             "We reviewed the issue and did not find any map errors. It looks like Waze had a valid route. If you feel yours is correct keep driving that way. If it is indeed faster Waze will learn from your drives and route you and others the faster route. Thanks!",
  80.             "Solved",
  81.             "Thanks for the reply",
  82.             "Thank you for the reply this request will be closed. As you travel, please feel welcome to report any map issues you encounter.",
  83.             "Solved",
  84.             "No further communication received",
  85.             "No further communication was received, this request will now be closed. As you travel, please feel welcome to report any map issues you encounter. Thanks!",
  86.             "Solved",
  87.             "No further communication received",
  88.             "No further communication was received, this request will now be closed. As you travel, please feel welcome to report any map issues you encounter. Thanks!",
  89.             "NotIdentified",
  90.             "Address fishing",
  91.             "Waze does not tell us your starting or ending destinations. Would you tell us the address you are having problems with as you entered it into Waze? Thanks!",
  92.             "Open",
  93.             "Problem appears corrected",
  94.             "Just a reminder: The problem appears to be corrected. Please let us know if you are continuing to have the issue. If we do not hear from you in a few days we will close this report. Thanks!",
  95.             "Open",
  96.             "<br>",
  97.             "",
  98.             "",
  99.             //Default URs  6 trough 22 are the different types of UR that a user can submit
  100.             "Incorrect turn", //6
  101.             "Would you please let us know what turn you are having a problem with? Thanks!",
  102.             "Open",
  103.  
  104.             "Incorrect address", //7
  105.             //new "Waze did not send us enough information to fix your request. In order for us to help you we need to know a couple of things what is the address as you entered it into Waze and what was the problem you were having with this address?",
  106.             "Waze did not send us enough information to fix your request. Would you tell us the address as you entered it into Waze? What is the problem you are having with this address? Thanks!",
  107.             "Open",
  108.  
  109.             "Incorrect route", //8
  110.             "Waze did not send us enough information to fix your request. Would you please let us know what went wrong with the route Waze gave you? Would you tell us your destination as you entered it into Waze? Thanks!",
  111.             "Open",
  112.  
  113.             /*
  114. 			"Missing roundabout",						//9
  115.             "",
  116.             "Open",
  117. 			*/
  118.  
  119.             "General error", //10
  120.             "Waze did not send us enough information to fix your request. Would you please let us know what went wrong? Would you tell us your destination as you entered it into Waze? Thanks!",
  121.             "Open",
  122.  
  123.             "Turn not allowed", //11
  124.             "Would you please let us know what turn was not, or should not be, allowed and the street names at the intersection? Thanks!",
  125.             "Open",
  126.  
  127.             "Incorrect junction", //12
  128.             "Waze did not send us enough information to fix your request. Would you please let us know what went wrong with the route Waze gave you? Would you tell us your destination as you entered it into Waze? Thanks!",
  129.             "Open",
  130.  
  131.             "Missing bridge overpass", //13
  132.             "Would you please let us know what overpass you believe is missing? When moving at highway speeds, Waze deliberately chooses not to display some nearby features to avoid cluttering the screen. Would you tell us as much as possible about the missing overpass. Thanks!",
  133.             "Open",
  134.  
  135.             "Wrong driving direction", //14
  136.             "Waze did not send us enough information to fix your request. Would you please let us know what went wrong with the route Waze gave you? Would you tell us your destination as you entered it into Waze? Thanks!",
  137.             "Open",
  138.  
  139.             "Missing Exit", //15
  140.             "Waze did not send us enough information to fix your request. Would you please let us know as much as possible about the missing exit? Thanks!",
  141.             "Open",
  142.  
  143.             "Missing Road", //16
  144.             "Would you tell us as much as possible about the road you believe is missing? Thanks!",
  145.             "Open",
  146.  
  147.             /*
  148. 			"Missing Landmark",							//18
  149.             "",
  150.             "Open",
  151. 				
  152. 			"Blocked Road",								//19
  153.             "",
  154.             "Open",
  155. 			
  156. 			"Missing Street Name",						//21
  157.             "",
  158.             "Open",
  159. 			
  160. 			"Incorrect Street Prefix or Suffix",		//22
  161.             "",
  162.             "Open",
  163. 			*/
  164.  
  165.  
  166.             "<br>",
  167.             "",
  168.             "",
  169.             //End of Default URs  
  170.  
  171.             "User Followed Waze's route",
  172.             "It appears that you ended up going the route Waze suggested, what was the problem you were having? Would you tell us your destination as you entered it into Waze? Thanks!",
  173.             "Open",
  174.             "Alley Interference",
  175.             "Waze doesn't tell volunteer editors where you were going, although it was probably adjacent to the alley. If you would, please supply your destination as you entered it into Waze it may be helpful in correcting the route. Thanks!",
  176.             "Open",
  177.             "Road Closed",
  178.             "Would you please let us know the following, what road is closed; between which intersections is this road closed; do you know how long this road is scheduled to be closed? Thanks!",
  179.             "Open",
  180.             "Area Entrances (Airport, amusement,  parks)",
  181.             "We have had problems with Google pins being placed in the center of a large landmarks. Delete your previous search and do a new search for the location. Go to the bottom of the auto fill list to see more results and make sure you pick the Waze search engine. ",
  182.             "Open",
  183.             "48 Hour Reply",
  184.             "Please allow 48 hours for changes to be reflected in the live map.",
  185.             "Open",
  186.             "Clear Saved Locations",
  187.             "You should remove the location from your favorites and recent searches and then re-search for the location to update the result.",
  188.             "Open",
  189.             "Clear TTS Cache",
  190.             "If you continue to have this problem you will need to clear your Text to Speech cache. Go to navigation screen and type cc@tts in search field and hit search. You should get a pop up message that the TTS file has been cleared. It will take a few days for the file to build back up with all the spoken street names.",
  191.             "Open",
  192.             "Address - Incorrect Position",
  193.             "Thank you for your report. Would you please let us know what address you're reporting the problem with? You can also use the Report -> Places feature in Waze to mark the location. It is helpful that after taking a picture, if you move near the location your marking to save the place. Also, please do not submit pictures containing faces, license plates, or similar personal details. Thanks!",
  194.             "Open",
  195.             "Address - Missing from Map",
  196.             "Thank you for your report. Would you please let us know where the address you're reporting is? The live map doesn't have all the street numbers for that street and Waze is interpolating in error. You can also use the Report -> Places feature in Waze to mark the location. It is helpful that after taking a picture, if you move near the location you’re marking to save the place. Also, please do not submit pictures containing faces, license plates, or similar personal details. Thanks!",
  197.             "Open",
  198.             "Address - Search Results Bad",
  199.             "Thank you for your report. The search feature retrieves results from a number of locations, including Google. Scrolling to the bottom the Navigate screen, you'll see more results for 'name.' Select that and Waze will list locations Around You. From there, you can also select results from other search engines.",
  200.             "Open",
  201.             "Detours / Odd-Routing",
  202.             "We can't find anything in the map to explain route Waze gave you. Waze wants to save you time every way it can and sometimes it suggests complex detours just to shave a few seconds off your trip. Waze may recommend a detour even after the traffic has cleared up because: it doesn't know yet, other Wazers may have reported a temporary street closure, or daily traffic patterns. In any event, we are very sorry to say that the volunteer map editors can't be much help here. Thanks!",
  203.             "NotIdentified",
  204.             "House Number Adjustment",
  205.             "I've forced Waze to re-register the house number for your destination. I believe this should correct your issue. Please allow 48 hours for changes to be reflected in the live map. If the location is in your saved searches or favorites, please remove them and search for them again to pick up the change in the live map. Please let me know if you continue to experience the problem. Thanks!",
  206.             "Open",
  207.             "Missing Bridges or Roads",
  208.             "The roads here have been pretty thoroughly mapped and we volunteers can't see anything missing that should ordinarily be there. Waze probably simply chose not to show you the feature in question. When moving at highway speeds, Waze deliberately chooses not to display some nearby features to avoid cluttering the screen. If you are certain a feature is missing from the map, please reply and tell us as much as possible about it. Thanks!",
  209.             "Open",
  210.             "Road Closure Request - Temporary",
  211.             "How long is the road going to be closed? For closures of only a few days, we volunteer map editors can't be much help. It takes at least that long for our edits to make it to devices! When you encounter short-term road closures in the future, please use the Report->Closure feature in the Waze app. If this is a long-term closure please respond and let us know as much as you can. Thanks!",
  212.             "Open",
  213.             "Traffic - Stale Information",
  214.             "Volunteer map editors can't do anything about Waze's traffic reporting. Waze relies on data from people using Waze to assess traffic. In the case of a fresh accident or slowdown, Waze may not yet have any data on the situation. Once Waze has detected a traffic situation, it can remember it for awhile, sometimes long after the situation changes.",
  215.             "NotIdentified",
  216.             "Traffic - Jams ",
  217.             "To report traffic jam conditions, please use the Report -> Traffic Jam options in the Waze app. This will tell Waze about the problem in real-time. Traffic Jam reports can help route you and other Wazers around traffic problems.",
  218.             "NotIdentified",
  219.             "Signal Avoidance Bug",
  220.             "I do not see any issues with the current turn restrictions in the area. This appears to be part of the known signal avoidance bug. Waze's developers are working on a fix for the issue but we do not have an ETA. Please feel free to take the turn until the issue is resolved. Thanks!",
  221.             "NotIdentified",
  222.             "Manual Refresh",
  223.             "You can try a manual refresh by going to Settings > Advanced > Data transfer > refresh maps.",
  224.             "Open"
  225. 	        ];
  226. //end Custom list
  227.