How to flag issues with course creation

When creating your course, near the top-left corner of the map is a dropdown that lets you select map providers. The default map provider is Google, but you can change the provider to OpenStreetMaps. I was able to reproduce the problem you describe (I tried to create a route from the Colorado Railroad Museum to the intersection of Ridge Road and Easley Road) when using Google Maps. I cannot reproduce the problem with OpenStreetMaps.

Interestingly enough, when trying to create a route through that intersection using Google, I noticed that you can drop points on the road or around the road and they don't snap to the road like they would normally do. I'm curious what is going on with that.

Travis

Yes, I found that interesting too. I'm not sure what the drop-down does. I'm guessing that Garmin has old maps, because if I actually go and map that on GoogleMaps (www.google.com), it routes correctly. This appears to be something with Garmin....

The dropdown determines what service Garmin uses for display and routing data. Garmin does not maintain a copy of the map data provided by Google. Garmin just presents that data to you from the Garmin Connect website. You can easily reproduce the problem on Google Maps by trying to create a route from the Colorado Railroad Museum to the intersection of Ridge Road and Easley Road as I mentioned above. It does not route directly using the automatic routing method. See for yourself here.

If you change the routing mode to cycling or driving, it seems to work just fine, but if you use automatic or walking it is broken. This leads me to believe that the problem isn't with the map data itself. It appears that Garmin is using Google's automatic or walking routing methods when it should allow you to select which mode you want.

I'm not sure what you mean...using GoogleMaps in cycling mode, it automatically routes up the switchback. See here:
https://maps.google.com/maps?saddr=W+44th+Ave&daddr=Easley+Rd&hl=en&sll=39.76362,-105.195379&sspn=0.035958,0.075359&geocode=FeTRXgIdjL26-Q%3BFdvmXgIdv-C6-Q&oq=lookout&t=h&dirflg=b&mra=ltm&z=16&lci=bike

Are you seeing something different?

Apparently you didn't take the time to read my post, specifically the second paragraph. I even provided a link to the map directly on Google Maps that shows the problem there, and you didn't even look at that.

Apparently you didn't take the time to read my post, specifically the second paragraph. I even provided a link to the map directly on Google Maps that shows the problem there, and you didn't even look at that.

Sorry - I apologize for not being more specific. I did look at your link - my apologies for not reflecting that in my reply - I meant no offense.

When I went to your link, the two points that you indicated did not have the shortest route being up the switchback to Easley Road, so when I went to look at it (by clicking on your link), it shows the path going Easley Way. As such, I'm not exactly sure what your two points were relating to.

As I said, I meant no offense - the link you provided seems to show a path on Easley Way, which happens to be the most direct route according to roads. Did you see the same thing about Easley _ROAD_ when you put the points as I indicated?

Thanks,
Brett

By the way, when I click on your link, the directions are:

1. Head southeast toward W 44th Ave
2. Turn right onto W 44th Ave
3. Take the 1st right onto Easley Way
4. Turn right onto Easley Rd

Let me know if you are seeing something different.

Apparently I'm not being a very effective communicator. Open up a Google Maps window and set the routing method to walking. Play with that for a while. You will notice that Google Maps won't route you from W 44th Avenue to Easley Road when configured this way. You can use Google Map Maker to inspect that section of Easley Road, and you will see that someone has flagged that section as not suitable for foot traffic. That is why Google Maps won't let you create the walking route.

What does that have to do with Garmin Connect? Well, this issue is consistent with what is seen when using Garmin Connect maps (when using the Google map provider). This tells me that Garmin Connect is using the walking routing method to create courses. This is not ideal because it won't allow you to automatically route over sections of road that allow bike traffic but don't allow foot traffic, and it might route you over a section of path that allows foot traffic but is closed to bikes.

To summarize, there is a problem here. You had said that you believed it to be related to the map data and wanted to flag the map data as invalid. I'm suggesting that the map data itself is correct and that the problem is that Garmin is accessing the data incorrectly for how it will be used. i.e., If you want to create a bicycling course, you want to use routing instructions that are valid for cycling. Garmin doesn't currently allow for you to make this decision, and that is the source of the problem.

Thanks! Sorry for the miscommunication - I couldn't understand why you were suggesting I use the walking mode of Google Maps. Your explanation was very well done - sorry I didn't get it earlier. So, as you said, there is a problem here. I'm just wondering now how to flag this to a Garmin group.

For right now, I've given up on creating maps in the Garmin interface and use Strava, Google Maps, MapMyRide, and RideWithGps to do all the stuff I need to do. Hope Garmin fixes this sometime soon!

Thanks again for your patience. I really do appreciate the help and analysis on this issue!

I think the workaround (until Garmin uses the correct routing mode) is to select OpenStreetMap as the map provider. It isn't without its disadvantages, but it is a simple workaround.