Bug Reporting and Funny Maps
Goof below. But first, some tie in.
It’s always a good idea to make bug reporting as easy as possible for your users. With the project summary pages, for instance, we made it very easy to report a problem with project meta-data by putting the link right on the page and doing our very best to pre-fill in the bug with as much pertinent information as possible. I was wishing there was something like that on the Google Maps page when I encountered this recommended walking route:
Hmmm, not so much.
I can think of a lot of ways to walk between these two points but this is definitely not one of them. Admittedly this is the scenic route as it goes through the Columbia Gorge National Scenic Area, but I think a 48 hour walking trip might be a bit much.
I wanted to report this, particularly since walking routes are in beta mode, but on the whole screen there is nowhere to easily do so. Do I give up now because they don’t want me to report it? Or do I persist in trying to figure out how to report the bug? If I’m the average user I’m not going to bother. Maybe Google doesn’t need the data, but if they do, it should be a lot easier to give it to them.
Posted December 3rd, 2008 by Karl Matthias in category: Uncategorized
You can skip to the end and leave a response. Pinging is currently not allowed.
4 Responses to “Bug Reporting and Funny Maps”
Leave a Reply
You must be logged in using your Eclipse Bugzilla account to post a comment.
Darin Swanson Says:
December 3rd, 2008 at 7:42 pm
I propose the fix would be to add a long run list entry
Karl Matthias Says:
December 3rd, 2008 at 7:50 pm
Hey, good idea! Or maybe a checkbox that says “Don’t route me through the Columbia Gorge Scenic Area”. Maybe right now it takes that as the default preferred setting.
Denis Roy Says:
December 3rd, 2008 at 8:28 pm
You folks in Portland are quite active and fit, and I think Google knows this, hence the challenge. Take pictures along the way!
Cole Says:
December 8th, 2008 at 3:49 pm
I passed this along to a friend at Google who sent it through the internal channels. It’s quite likely they’ll get the route mix up fixed, but hopefully they’ll address the user-feedback issue as well.