alexs001
My feedback
39 results found
-
102 votes
This idea currently isn't planned, but we will update if it becomes feasible in the future.
Thanks to all who pushed for this idea!
alexs001
supported this idea
·
-
33 votes
An error occurred while saving the comment alexs001
supported this idea
·
-
3 votesalexs001
shared this idea
·
-
325 votes
Hi all,
Thank you for voting for this suggestion!
We’d like to know if this is still relevant, or if the issue was solved through auto-complete for prioritized Waze addresses.
Please let us know in the comments if it was, so we can close the suggestion.
Thanks!
-Staffalexs001
supported this idea
·
-
11 votesalexs001
supported this idea
·
-
24 votes
Hi all,
Thanks for this suggestion. We currently have other features which can account for this, like Roadshields and the towards option.
Editors should continue to avoid creating short segments where they aren't necessary, however this issue will be resolved by other future feature releases.
Many thanks,
Waze Communities Team
An error occurred while saving the comment alexs001
commented
The staff response suggests that the intent of this suggestion was not understood. We're not talking about wayfinders, we're talking about what happens when an editor unknowingly makes a segment that is short enough to cause routing issues. Alternately, the routing engine could be patched to eliminate this issue in the first place...
alexs001
supported this idea
·
-
379 votesalexs001
supported this idea
·
-
2,028 votes
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.
alexs001
supported this idea
·
-
10 votesalexs001
supported this idea
·
-
20 votesalexs001
supported this idea
·
-
25 votes
An error occurred while saving the comment alexs001
commented
In the case of divided roads, we need some means to attach an 'other side' report to the segment going in the other direction instead of the undrivable 'other side' of the one-way segment we're traveling on.
-
145 votes
Thank you for this suggestion.
We are looking into its feasibility on our end, and will update accordingly
Best,
alexs001
supported this idea
·
-
158 votesalexs001
supported this idea
·
-
68 votes
Thank you to all who submitted and voted for this suggestion, however it is currently not planned due to PII issues associated with tracking URs in this manner. Please make sure to include the UR ID when reporting abusers on the map so that Staff can properly track the case. Often times we are unable to investigate due to no longer having the UR ID once the UR is closed and deleted.
alexs001
supported this idea
·
-
278 votes
Hi all,
Thanks for voting for this suggestion!
It will be integrated into the new Waze Chat feature, and is currently on the roadmap for a later phase.
We’ll be sure to update when we have a clearer picture of the timeline.
alexs001
supported this idea
·
-
212 votes
Since bilingual support is a bigger issue affecting not just the WME, this is a company-wide decision that we will bring to the relevant teams.
alexs001
supported this idea
·
An error occurred while saving the comment alexs001
commented
It always surprised me that Waze, coming from a trilingual country (with each language using different writing systems) did not support this from day one.
-
13 votes
Hey,
We would like to get some examples with permalinks in order to be able to check this suggestions.
Any example will be highly appreciated.
Thank you!
An error occurred while saving the comment alexs001
commented
Sure: PL for the example I gave originally: https://www.waze.com/editor/?env=usa&lon=-119.47970&lat=49.87797&zoom=6&venues=157614579.1576276860.468041
The classic use case is where a park meets a water body. Usually the park is small compared to the water body and renders on top, when we'd almost always prefer the water body to remain visible.
Some others that come to mind: https://www.waze.com/editor/?env=usa&lon=-101.38732&lat=50.96689&zoom=2&venues=169476606.1695028201.3988981
https://www.waze.com/editor/?env=usa&lon=-107.99231&lat=50.66551&zoom=1&venues=165151227.1651577803.7316989
Hope that helps.An error occurred while saving the comment alexs001
commented
I saved a demonstration of what I am describing here: https://imgur.com/a/Fu9B9eH
alexs001
shared this idea
·
-
6 votesalexs001
supported this idea
·
-
32 votesalexs001
supported this idea
·
-
259 votesalexs001
supported this idea
·
I was thinking about how to implement this today as adding an RPP next to a public venue point is highly redundant. I have a few possibilities in mind:
A: add a 'trust this address' property to public places in WME
B: automatically add addresses to the database when a place is edited by a sufficiently trusted editor
C: add addresses to the database when a place is locked to L3 or higher (perhaps configurable by country?)