Map Editor Suggestions

Welcome to the Map Editor's suggestion box!

This is the place to share your ideas for improving the Waze Map editor.

Looking forward to reviewing your ideas,
The Waze Communities Team.


  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback
  1. 2D Hazards

    I'm not sure if this sort of thing will be covered in Permanent Hazards development, but it would be very handy to be able to define an area polygon to which a hazard report would apply.
    To me, the obvious application would be for prolonged construction zones where roads remain open but users ought to be made aware of an issue ahead.
    How I see this working:
    An editor would draw a polygon over the affected area and then choose a hazard type and add an optional comment to the polygon. It should be possible to define schedules and an…

    3 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Looking into the suggestion  ·  0 comments  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  2. Surfacing House Number Errors

    A nice feature would be to surface the real error message from house number additions. Sometimes when there is a conflict between segments, you get a generic "there was an error" type message, but the back end call has the full details which you can see through dev tools. For example:

    This segment: https://www.waze.com/en-US/editor/?env=usa&lon=-97.48797&lat=30.16312&zoom=6&segments=48240740
    Conflicts with: https://www.waze.com/en-US/editor/?env=usa&lon=-94.82458&lat=29.82488&zoom=6&segments=48240740,511847520,511847562,511847579

    When the city is listed as "none" (No City). When adding "115" to the latter, this resulted in an error (see attached)

    However, the backend error that is returned by the web request is (see attached)

    There's enough in the error message there…

    3 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Looking into the suggestion  ·  0 comments  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  3. Invisible RTC's and visible TBR's

    Add the ability to control the visibility of TBR and RTC in the client (and define it in WME).
    They say they often use the wrong type, just to match the required visibility.

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Looking into the suggestion  ·  1 comment  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  4. Selecting a search result shouldn't reset the zoom level

    When using the WME search box to find a road, it would be really nice if WME could leave the current zoom level well alone rather than always resetting it to level 3.

    Even if it just defaulted back to level 4 that'd be an improvement, but jumping back out to 3 means we then always have to zoom back in at least one step if we want to be able to select a street segment. And even at L4, anyone looking to do some work on point places would then need to zoom in one step more before they…

    0 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Looking into the suggestion  ·  0 comments  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
1 3 Next →
  • Don't see your idea?

Map Editor Suggestions

Categories

Feedback and Knowledge Base