10 results found

1. Improve the GPS points layer

   To branch off the discussion from the WME release topic:

   RichardPyne כתב:
   I would find GPS points much more useful if they were color coded by age rather than direction. Th arrows provide useful direction, but in areas where traffic patterns are changing due to construction, knowing the age of the trace would be far more useful.

   dchary2418 כתב:
   It could help if the GPS traces were the same original color, but shaded darker for older data.

   Glodenox כתב:
   I'd be all for somehow showing the age of the GPS points. Especially the more recent data seems of interest to me. Something like "last 7 days", "last 30 days" or "older" would work great as brackets for colouring, I think.

   The issue with that is probably that it would allow you to track certain users in areas with not as many users. With no indication of age, this is a lot harder to do right now. But in theory this could be taken into account by not showing the age when there is little data.

   To branch off the discussion from the WME release topic:

   RichardPyne כתב:
   I would find GPS points much more useful if they were color coded by age rather than direction. Th arrows provide useful direction, but in areas where traffic patterns are changing due to construction, knowing the age of the trace would be far more useful.

   dchary2418 כתב:
   It could help if the GPS traces were the same original color, but shaded darker for older data.

   Glodenox כתב:
   I'd be all for somehow showing the age of the GPS points. Especially the more recent data seems of interest to… more

   172 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   Not right now  ·  7 comments  ·  General  ·  Delete…  ·  Admin →

2. Directly edit water layer

   The water layer should be editable.

   The water layer import is outdated and frequently lakes and ponds are drawn where roads and houses now exist.

   We can add hacks to WME to suppress the display of these water features in the Waze app but this is not ideal.

   125 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   3 comments  ·  General  ·  Delete…  ·  Admin →
   Not right now  ·  AdminWaze Team (Admin) (Admin, Waze) responded

   Hi all, 

   
   

   Unfortunately this isn't possible at the moment. Many thanks for the suggestion, and we'll update if and when the status changes for this. 

   
   

   Best, 

   Waze Communities Team

3. Automatically send UR reminders and mark as 'not identified' if no reply

   User Reports (URs) come in by the truckload. Despite a message from an investigating editor, only 10% of URs will receive a reply. This represents a significant amount of time by editors, particularly senior editors managing large areas, to the manual handling of individual URs. Since 90% of the URs result in the same process, help us streamline and automated it so we can focus our valuable time on productive investigations and edits that will value add to Waze.

   I propose an additional tick box under "Follow conversation" that says along the lines "Auto reminder and mark as not identified."

   When ticked:

   • and a user replies, the auto remind and close is disactivated
   • and a user does not reply, the user is automatically sent a reminder message after 4 days of the last editor reply, and after 7 days, the UR is automatically marked "not identified" and the last editor to reply is credited with the UR closure.

   The "Auto reminder and mark as not identified" flag can only be toggled on if a message is sent. The flag can be toggled off however without a message being sent.

   Possible visual presentation: https://imgur.com/VMIGTEW

   Access to this feature can be controlled by a country level permission, ideally level 3 and above as default.

   User Reports (URs) come in by the truckload. Despite a message from an investigating editor, only 10% of URs will receive a reply. This represents a significant amount of time by editors, particularly senior editors managing large areas, to the manual handling of individual URs. Since 90% of the URs result in the same process, help us streamline and automated it so we can focus our valuable time on productive investigations and edits that will value add to Waze.

   I propose an additional tick box under "Follow conversation" that says along the lines "Auto reminder and mark as not identified."

   … more

   109 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   9 comments  ·  General  ·  Delete…  ·  Admin →
   Not right now  ·  AdminWaze Team (Admin) (Admin, Waze) responded

   Thank you for this suggestion.

   At the moment this solution won’t be implemented. Yet, the dev team will look at the issue presented here to try and find another solution for it.

   Thanks

4. Map Comments

   In Map Comments there is an expiration to remove the MC. I would really like to see a notification or email for a known date that would happen in the future, for instance a new business opening or visa versa, construction that is going to happen, etc. Many editors have just had to add to an external calendar event to get a reminder

   80 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   3 comments  ·  General  ·  Delete…  ·  Admin →
   Not right now  ·  AdminWaze Team (Admin) (Admin, Waze) responded

   This is a great idea, and could fit into a larger solution we are looking into for more dynamic reminders in the WME. We've made a note to include this in the larger project, and will circle back when relevant. 

5. Edit Toll Prices in the WME

   The procedure to edit toll prices is complex and only certain users per community can edit those prices.

   Toll prices should be editable directly in the WME to avoid a complex process.

   64 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   3 comments  ·  General  ·  Delete…  ·  Admin →
   Not right now  ·  AdminWaze Team (Admin) (Admin, Waze) responded

   Hey!

   Thank you for this great suggestion.
   This was also raised in the past and we understand the importance of it. With that being said, for the time being this is not planned, as it is a complex project which will need a lot of resources which are invested in a higher priority WME tasks.

   Thank you
   Hezi

6. Allow the WMEb "BETA" indicator to link back to the production WME

   In the latest beta, there is now a [• BETA] indicator in the header. Please consider adding a way to use this indicator as a shortcut back to the production WME.

   Perhap click to open a tab of with the PROD wme at the same spot, and hover+CNTL+C (or right click) to copy a PROD wme permalink.

   We'd like to encourage users to edit the BETA wme as much as possible, but when collaborating or posting to public forums, we should make it as easy as possible to share PROD permalinks.

   64 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   0 comments  ·  General  ·  Delete…  ·  Admin →
   Not right now  ·  Tam (Waze Team) responded

   Thanks for your feedback. At this time, this doesn't fit on our roadmap, but we'll keep it in mind for future product planning.

7. In WME: Force L1 & L2 editors to be "visible"

   To actively follow the edits of new editors in WME, it would be helpful to force them to be "visible." This would be limited to L1 and L2 editors. Perhaps this could be incorporated as part of the new L1 edits approval process.

   (Moved from "Other" category of UserVoice)

   60 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   1 comment  ·  General  ·  Delete…  ·  Admin →
   Not right now  ·  Tam (Waze Team) responded

   Thanks for your feedback. At this time, this doesn't fit on our roadmap, but we'll keep it in mind for future product planning.

8. All 1-way roads should automatically be A→B

   There's no need for 1-way roads to be either A→B or B→A.
   They should only be able to be A→B.

   This will solve a lot of issues us editors encounter, for example when adding road closures.
   I saw another suggestion here to apply A→B closure also on B→A segments, but it would be much better to just get rid of B→A segments.

   Let me know if there are any questions.

   44 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   6 comments  ·  General  ·  Delete…  ·  Admin →
   Not right now  ·  Tam (Waze Team) responded

   Thanks for your feedback. At this time, this doesn't fit on our roadmap, but we'll keep it in mind for future product planning.

9. Show conflict choice option on deleting junction node

   (Copied over from https://www.waze.com/forum/viewtopic.php?f=1525&t=229014)

   If you try to delete unneeded junction node, but it can't be deleted due to a conflicting option between then, at the moment you need to inspect each segment to see what the differences are. This is especially frustrating when there may be a hidden speed limit set on a one way segment.

   Can a dialog box pop up on deletion of a junction node if there is a conflict to allow the editor to select one of the conflicting settings for the newly joined segment?

   OR

   Create an error message saying the junction node cannot be deleted because of <a-b speed limit> conflicting, for example.

   (Copied over from https://www.waze.com/forum/viewtopic.php?f=1525&t=229014)

   If you try to delete unneeded junction node, but it can't be deleted due to a conflicting option between then, at the moment you need to inspect each segment to see what the differences are. This is especially frustrating when there may be a hidden speed limit set on a one way segment.

   Can a dialog box pop up on deletion of a junction node if there is a conflict to allow the editor to select one of the conflicting settings for the newly joined segment?

   OR

   Create an error message saying the junction node… more

   29 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   1 comment  ·  General  ·  Delete…  ·  Admin →
   Not right now  ·  AdminWaze Team (Admin) (Admin, Waze) responded

   Hey,
   Thank you for this suggestion!

   At the moment we are not going to move forward with this suggestion, as it is not aligned with our road maps and plans for JB. more info will be shared in the near future.

10. The fact that all segments entering a Junction Box are 'locked' is a real pain. Why not do a little 'behind the curtain magic'.

    Here is how I suggest you do this: when any segment entering a JB is 'touched' in a way that would currently cause a 'flag' to warn the user that the segment is locked, WME would instead 'take a quick snapshot' of everything involved in the JB and save that information.
    A pseudo picture of the JB would be created where every segment entering the JB would be 'cut' where it crosses the boarder line of the JB.
    The portion of each segment within the JB would retain the current segment # and other information as appropriate. The portion of the crossing segments remaining outside would be assigned NEW 'temporary' segment # and get their data as if the segments had actually been cut at the border at the time the JB was originally created.
    When a 'save' is done, the process would be reversed with restoration of original data where nothing has been touched. Where changes were actually made outside the JB to a segment that entered the JB, appropriate data merger would take place automatically, retaining the segment # for the portion of the segment entering the JB and assigning a new number to the portion that has been created by the cutting.

    Here is how I suggest you do this: when any segment entering a JB is 'touched' in a way that would currently cause a 'flag' to warn the user that the segment is locked, WME would instead 'take a quick snapshot' of everything involved in the JB and save that information.
    A pseudo picture of the JB would be created where every segment entering the JB would be 'cut' where it crosses the boarder line of the JB.
    The portion of each segment within the JB would retain the current segment # and other information as appropriate. The portion of… more

    27 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    2 comments  ·  General  ·  Delete…  ·  Admin →
    Not right now  ·  AdminWaze Team (Admin) (Admin, Waze) responded

    Improvements to Junction Boxes are not currently planned as they do not fit our roadmap or current plans for JBs. We will update the community with news about JBs in the near future.