BryceCampbell
My feedback
25 results found
-
172 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.
An error occurred while saving the comment BryceCampbell supported this idea ·
-
27 votes
BryceCampbell supported this idea ·
-
46 votes
BryceCampbell supported this idea ·
-
38 votes
BryceCampbell supported this idea ·
-
14 votes
An error occurred while saving the comment BryceCampbell commented
So I have done this in Western Canada - when creating the shelter, my naming is not only generic, but also harmonised.
We benefit in where our province has one central emergency management ESS programSo the "Title" is the harmonised/generic name (the result) and any support details, like the name of the shelter association/business/building I'll place in the description. (sometimes will do alt name)
Main titles I'm uses are
ESS Reception Centre / Reception Centre
Donation Centre
Elders Room
Evacuee Animal ShelterPublic Cooling Space (Portable Water Fountain)
Public Cooling Space (Wading Pool)
Public Cooling Space (Misting Station)
Public Cooling Space (Spray Park)
Public Cooling Space [general for say just a library/organisation]The only issue I have with rolling out more shelters, isn't creating them, but managing them.
Right now you have to go to each shelter to enabled/disable. If I have 100+ across the province, thats time consuming.I want to see a shelters tab within "Events" that I can filter regions (provinces/states) and just be able to toggle on/off from there.
Something that is fast and easy. As many shelter sites are reused when ESS is established, going to each venue is wasting time and in an emergency, having these rolled out promptly is important.
-
9 votes
An error occurred while saving the comment BryceCampbell commented
Extension support is very important and something that should be very easy to implement.
We already have the button to call, if we have the hyperlocal knowledge, we should absolutely be mapping/providing it for the user.
There is nothing worst, especially when mobile, to have to navigate a phone system menu, which is absolutely distractive.BryceCampbell supported this idea ·
-
13 votes
BryceCampbell shared this idea ·
-
12 votes
BryceCampbell supported this idea ·
-
163 votes
Great timing! We’re currently working on displaying the date of the satellite image. Keep an eye out for updates on the WME.
BryceCampbell supported this idea ·
-
20 votes
Great thinking! We’ll share with the team; they’re always interested in new feature ideas.
BryceCampbell supported this idea ·
-
32 votes
BryceCampbell supported this idea ·
An error occurred while saving the comment BryceCampbell commented
Will happily resurrect this thread for 2024!
With permanent hazards now, it would be amazing to have one-lane (crossing)/yield to on-coming traffic for situations just like this.
In British Columbia Canada, I've been working on doing some basemap updating and we have a lot of two lane highways. They are critical for essential access but they don't have the traffic volumes (or sometimes space, or both) to justify building a two-lane bridge.
As such these crossings are one-lane traffic, the one direction (general outbound) will have the rightaway, while the other direction will yield to the on-coming. So its going to essentially have a two-part hazards - one a PH of one-lane bridge(traffic) and another for one-lane bridge plus a yield.
Having this hazard would be anxcellent enhancement to the Permanent hazard alerts.Couple of Streetview examples
WB one-lane with yield https://maps.app.goo.gl/m157W2fqNwcQXkzj6
EB one-lane w/o yield https://maps.app.goo.gl/aKToCLVnuXV5nigq9This bridge has single lane approaches you'll yield to traffic, along with another yield to traffic at the bridge crest.
https://maps.app.goo.gl/8JeWJ163FJt4QzyAA -
2 votes
An error occurred while saving the comment BryceCampbell commented
Sounds like something to get in-touch with the editor community and/or enroll your company into the Waze for Cities partner program.
https://sites.google.com/view/wazertowazer/partners
https://sites.google.com/view/wazertowazer/resources-for-everyone/join-community-channels
https://sites.google.com/view/wazertowazer/resources-for-everyone/join-community-channels
-
15 votes
BryceCampbell shared this idea ·
-
47 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.
An error occurred while saving the comment BryceCampbell commented
Russ' example is spot on! There are imports of commercial/residential complexes that will be like 10+ (I've seen 20-30) units spread across the property, but in reality they are all in one area.
Cannot merge cause you have to pick on set of chargers.Another example too is where the importer will generate one EVCS for the L3 DCFC and another for the L2 unit. Both these units are in the same location, same price, and same network. There really isn't any benefit to having these separate in most of these cases.
Again we cannot merge them cause merging EVCS feed places makes you select one or the other.BryceCampbell supported this idea ·
-
1,215 votes
BryceCampbell supported this idea ·
-
11 votes
An error occurred while saving the comment BryceCampbell commented
will vote this up. While Waze is primarily a commute/driving app, it is used for inter-city travel and on non-controlled 2-lane highways, its quite common to go 20-50 km without a "safe" passing lane.
While one "can" pass while the yellow-line is dashed (least in Canada) its stressful and dangerous. If the Waze app detects a slowdown for a set time, it could have a popup (like the speed limit reduction/high accident zone popup) that says Passing lane x km).
BryceCampbell supported this idea ·
-
504 votes
Thank you for your valuable feedback. We're pleased to confirm that this suggestion is planned and we appreciate your input as we continue to enhance our product.
BryceCampbell supported this idea ·
-
50 votes
BryceCampbell supported this idea ·
-
137 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.
BryceCampbell supported this idea ·
-
3,952 votes
BryceCampbell supported this idea ·
Being we have 30 and 7 days already, it really shouldn't be much to add a custom attribute and even a ranged attribute (ie. within last 3 days, but no longer than 7 days (or something)
Wouldn't definitely help attended to URs (and PURs) without the need for additional scripts/scripts running in the background