1. More Choices for Route Lines
I hunt the same large ranch over and over when rock hunting. I wish BaseCamp offered more colors and line types for routes. Options for various line types - dashed, dotted, etc would be helpful. How about opening the color choices to the full 32 bit spectrum. I've already used all the reasonable choices for route color.
2. Handling of Geo-tagged Photos
Improvements are needed in Geo-tagged photo handling. Photos seem to have a minimum size - much bigger than way point icons. How about offering more flexibility such as way point like icons for photos?
3. Focus Handling
After selecting a route/way point/photo, then closing it, the item remains highlighted and in some cases larger than in the unselected state. The only way to return the item to unselected size seems to be to select something else. This is a particular problem with photos, which when closed, do not revert to minimum size until something else is selected. It is fine to use bold or highlight to show the last selected item, but please have the item return to unselected size.
4 Route Handling (Driving vs Walking)
When recording a route, I start from a home base, drive to a location, park, get out and walk around, go back to the car, drive to another location, park, get out and walk around, etc. I would like to easily be able to visually distinguish the driving parts of the route from the walking parts. I'm not an expert BaseCamp user and believe that BaseCamp has some ability to represent this kind of activity by splitting a route, changing color, etc - but it is not clear to me that this is as easy to do as it might be. It seems to me that this is likely a common scenario in route recording.
5. Exporting to KML Format
The ability to export items to Google Earth compatible .kml format is excellent and very useful - thank you. However, my usual experience is as follows: I select something in BaseCamp, export it to .kml, then click on the exported file to open Google Earth. I immediately see that route lines are way too thick, way points are too large, etc. I then go back to BaseCamp, reduce the sizes and re-export to .kml. Could a bit more thought be given to the potential size mismatches between BaseCamp and Google Earth? Possibly the export dialog could automatically resize for Google Earth or allow the user to adjust sizes in the export process.
