Do not want to include "categories" when exporting Waypoints

That would be good, even better if Basecamp will read the categories from connected GPS so it's a 2way process.

Yes, it will definitely be a two-way process. The one-way street we have right now is not something we want to repeat.

Nice (new) avatar :p Looks like a cross between Hal's all seeing eye and V for Vendetta :D

Yeah, it reminded me of V for Vendatta as well. Hal's all seeing eye is also a good one.

But I am just a programmer, not a designer, so I hope they knew what they were doing when they designed the VIRB Edit logo.

And it just felt wrong to still have the MapSource logo. :)

Don't forget V the tv series ;)

www.imdb.com/.../

The current plan is to remove that list = waypoint category link and allow the user to define waypoint categories separately (like in MapSource, but without the limitation of 16 categories).

Hopefully this will be in 4.3, but no promises.

This will definately be a huge step, at least for the zumo users.

Now, if we can figure out how to have more than one "BP" waypoint in my library, I might be back in business....

The current plan is to remove that list = waypoint category link and allow the user to define waypoint categories separately (like in MapSource, but without the limitation of 16 categories).

Hopefully this will be in 4.3, but no promises.

I certainly would not miss the "list name" being used as the category, but I think some might (after investing time into a listing scheme that comes out on the GPS in a useful way). There's nothing wrong with how it is now, but can be improved: Many months ago, I suggested adding a "tagging" feature. Seems like this could be done (similar to "categories" in mapsource, as Falagar suggests above), and then add a configuration option to export/install-on-GPS using listname, tags, or both for the "category" within the GPS.

Adding "tags" (as Falagar describes above) allows a different dimension of how to manage a collection. For instance, I have my waypoints in BC under lists named for towns. However, I'll soon be able to add categories for different tasks, like say "hiking" or "motorcycling" or "Summer2013" or "fishing" or "fuel".

Now, for being able to use BOTH list names and/or "tags" (aka categories)...
Imagine I have a GPS for my car and a handheld. I might want to send all of my Texas towns lists to a handheld, and have it use "hiking" and "fishing" tags for categories, but on the car GPS use both the list names (of towns), and the tags (e.g. Summer2014, fuel, etc) as the category. And if I had a motorcycle-only GPS, I might want to use only the lists (towns) as categories, but only send items tagged "motorcycling" in BC.

By adding a configuration option to use either or both, you'll not break the current behavior (important to users who are happy with it, and don't pay attention to the forums), while providing functionality that many users have been wanting for a long time. Please consider it.

I don't have a problem with a category being created for the waypoints in a list. I only have a problem with the fact I end up with categories for lists I didn't even transfer to the device because the same waypoints were reference in other lists. I create one waypoint for hotels, but use them in may lists. If I upload a list with one of these hotel waypoints in it, I get all the categories created which have the waypoint in them.

I've worked around this by using the waypoint in a route and then removing the waypoint from the list. The waypoint is still part of a route in that list now, but the actual waypoint isn't part of the list. It's only a waypoint in the "unlisted" folder. When I send the list to the unit I don't end up with the other categories.

This ends up causing a lot of extra work for me, but works.

So in summary, my opinion is, categories should only be create for the elements in the list(s) being uploaded to the unit, not for all lists which reference an element/waypoint. This way I can use a waypoint in multiple lists, (and have it in unlisted), but still be able to modify/move the waypoint and have the change propagate to all routes/lists referencing that waypoint.

I don't have a problem with a category being created for the waypoints in a list. I only have a problem with the fact I end up with categories for lists I didn't even transfer to the device because the same waypoints were reference in other lists. I create one waypoint for hotels, but use them in may lists. If I upload a list with one of these hotel waypoints in it, I get all the categories created which have the waypoint in them.....

I agree this is a problem. I would PREFER to have "home" were in every list for planning purposes, but if I did that, I'd get dozens of categories in my Nuvi with nothing but "home" in them.

And also, I find it annoying that my Nuvi creates "categories" for items I mark directly on the device, or for items I've searched and saved on the device... At least if it becomes a two-way category transfer, I can use those new categories to identify items not already in BC (not possible today without pen and paper), transfer them there, remove those spurious categories, and transfer back to Nuvi (hopefully causing those spurious categories inside the Nuvi to disappear).

Note that Basecamp cannot delete favorites etc on nuvis, so what you propose will work IF we get the 2 way transfer as promised BUT you will need to delete everything off the nuvi before you send the new data from Basecamp.