Bart Youngblood
My feedback
14 results found
-
2,354 votes
An error occurred while saving the comment An error occurred while saving the comment Bart Youngblood commentedThis needs to be tread on very lightly.
Trapster grew to have dozens of report types, and over time, the map became hopelessly cluttered (even when it was moderated) because of it.
As mentioned over and over again, there's no point to reporting moving police. As soon as the cop turns off the street in question, the report is useless.
-
7,029 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 Bart Youngblood commentedWaze staff repeatedly says they won't do it for liability issues.
My assumption is they fear that if a truck/RV is using Waze in truck mode, and ends up on a height/weight/route restricted road that wasn't flagged as such, the driver will try to pin the blame on Waze...even though they drove by multiple signs saying they shouldn't be there.
An error occurred while saving the comment Bart Youngblood commentedWe can tag streets in the editor to restrict them from being used by certain types of vehicles, its just that Waze hasn't done anything with the data yet.
Like so many things in Waze, it will probably be here "soon"
-
92 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.
Bart Youngblood supported this idea · -
32 votesAdminElla (Waze Team) (Admin, Waze) respondedBart Youngblood supported this idea ·
-
2,342 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 Bart Youngblood commentedAgreed. Things like police checkpoints, flooded roads, etc., affect both sides of the road.
Bart Youngblood supported this idea · -
1,258 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 Bart Youngblood commentedYou must be someone who likes to report "Rain" and "Vehicle Stopped on Shoulder Ahead!"
In a word, NO.
-
91 votes
Great thinking! We’ll share with the team; they’re always interested in new feature ideas.
An error occurred while saving the comment Bart Youngblood commentedAs a L5 editor, I can get behind this. Make it where it has to be approved by a L4+ editor to take effect.
On another note, in the US, if you go through the mentoring program, you can be promoted to L3/L4/L5 with less than the number of edits listed in the wiki.
Bart Youngblood supported this idea · -
11 votesBart Youngblood supported this idea ·
-
5 votesAdminElla (Waze Team) (Admin, Waze) responded
An error occurred while saving the comment Bart Youngblood commentedThis is something that we were told was coming "soon" back in 2014. For now, most editors usually just create a UR on the livemap and tag it with a [NOTE] annotation so that certain scripts will pick up on it and make it stand out.
-
181 votes
An error occurred while saving the comment Bart Youngblood commentedWhile it is a nice idea, it isn't really practical. Doing so in some locations would require rather substantial detours around the school. Remember that not everyone lives in a place where there is another road half a mile a way to detour on to.
If there have been a bunch of accidents/injuries/deaths in an near school zones, sounds like you need to get the attention of the local authorities and have them put the police out there instead of patrolling the local interstate.
-
54 votes
An error occurred while saving the comment Bart Youngblood commentedI've been asking for this for over 2 years now. There needs to be an unpaved road feature vs an "off road vehicle" road. Some people don't like driving down dirt/gravel roads unless they absolutely have to, but at the same time, you've got other mapped roads that aren't suitable for all vehicle traffic (ie., Forest Service Roads)
-
155 votes
An error occurred while saving the comment Bart Youngblood commentedRather often, either when editing, or using the app myself, I see Waze suggest a rather odd route, or down a side street, to attempt to save time on the drive. While laudable in intent, it unfortunately has the side effect of presenting a confusing route or one that doesn't really result in enough time saved vs the amount of time spent driving.
For example, an average driver is probably not going to want to turn off a main route to potentially save one minute to avoid a red light on a one hour drive. Instead of simply using a pre-determined amount of time saved (ie., 30 seconds-1 min) to suggest a detour around a known area of average low traffic speeds, Waze should instead calculate a detour around a low speed route or traffic jam if the time saved exceeds a certain percentage (5-10% at minimum) of the total ETA.
Bart Youngblood supported this idea · -
197 votes
An error occurred while saving the comment Bart Youngblood commentedI agree. There needs to be a more significant amount of time saved based on the total length of the trip before it defaults to one that results in a significantly longer route. I, too, find myself checking the routes before I go to make sure I'm not driving an extra 4-5 miles just to save (on average) 1 minute of driving time.
An easy way to solve this would for the routing server to look at the average time and distance of all three choices. If the shortest time wise is also the longest distance and exceeds the next fastest route by a certain percentage of the average route length BUT saves a significant amount of time (15-20%) over the average travel times, then it will still take the longer route. However, if the time saved is insignificant, it will take the next fastest route.
Simply put, saving 1 minute on a 30 minute drive isn't significant enough to make me want to drive even 2-3 miles longer. Same goes for some of the really odd routes it suggests at times to avoid making left hand turns (going straight through, pulling a u-turn, then turning right at the desired intersection, for example). Instead of simply basing route choice off of a fixed amount of time, it needs to be tied to the time saved as a percentage of the total route time.
-
1,670 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 Bart Youngblood commentedAgreed. As a map editor, it is my observation that a good number of them are incorrectly placed (there was a KFC ad around the corner from where I work that was placed on the FedEx SuperHub ramp, the nearest actual KFC is about 3-4 miles away!) and it is hard to get the advertisers or Waze staff to fix them. I wouldn't mind paying a small annual fee (hell, for the amount of time I've put in editing the map, I should just get the ad free version for free!) to do away with the ads.
Bart Youngblood supported this idea ·
This thread is 7 years old and the road closure interface hasn't hardly changed at all in that time. It is really difficult for people to report closures in the app if you're not right at the intersection. Needs to be a way you can tap the affected street instead of tapping turn arrows. Granted, there is no perfect solution since people should be concentrating on driving, but it could be better.