Do not want to include "categories" when exporting Waypoints

Lists are exported as categories. If you don't want lots of categories you'll need to rearrange your data into fewer lists.

Lists are exported as categories. If you don't want lots of categories you'll need to rearrange your data into fewer lists.

Huh? I mean, I understand technically what you said, but.... if I have, for example, an "Arkansas" folder, and under that, I have 10 lists, each representing a ride event where each event (list) has 2 to 5 tracks. Now suppose I have 50 Arkansas waypoints that I want shared across all 10 lists. Now suppose I want to export a single list (3 tracks along with the 50 waypoints). I don't want the resulting GPX file to have all 10 lists repeated as "categories" for all 50 waypoints. How is that helpful to anyone? Worse, perhaps I'm working on a super-secret event and now that event (list) name is exposed in that unrelated GPX file I shared.

Rearranging data to minimize lists is clearly not the answer as it partially defeats the purpose of having an organizational system built into the application.

On the other hand, BaseCamp is a general program that has to supply whatever information any device, from any time period might use, not just yours or mine. It would be difficult to maintain special export routines for every device ever made and fundamentally wrong to drop something that another device could use.

I would think all super-secret projects would have a code name :). But a more realistic solution would be to look for some freeware to scrub your gpx file before making it available. If MapSource will run on your system, then transfer your data by copy and past and export the gpx file. If any categories appear in MapSource select all the waypoints, right click and edit with waypoint(s) properties.

Perhaps JAVAWA(?) has something that does this.

I am curious why every list a waypoint is on has to be exported, i.e. what are all the uses the programmers (BaseCamp and Device) plan for this information. Perhaps they need to rethink things?

Huh? I mean, I understand technically what you said, but.... if I have, for example, an "Arkansas" folder, and under that, I have 10 lists, each representing a ride event where each event (list) has 2 to 5 tracks. Now suppose I have 50 Arkansas waypoints that I want shared across all 10 lists. Now suppose I want to export a single list (3 tracks along with the 50 waypoints). I don't want the resulting GPX file to have all 10 lists repeated as "categories" for all 50 waypoints. How is that helpful to anyone? Worse, perhaps I'm working on a super-secret event and now that event (list) name is exposed in that unrelated GPX file I shared.

I agree with you and have asked the same question. If I'm sending a list to the unit I only want the points and categories I've asked to be exported. If I want the other categories I'll export send those lists to the gps too. Like you, I have many common waypoints used in many lists. Hotel waypoints, etc. Why would I want a category from a previous trip in my gps if I'm just reusing a common waypoint.

I don't understand the logic to programming Basecamp this way??

Thanks for the support, all. It would be interesting to see if any one chimes in with a reason they like having a waypoint exported with a section that shows all the lists that waypoint is a part of. I mean, if there is some legitimate usefulness to this functionality, I'd like to understand that.

I use a GPSmap 62s and it does not make use of "categories" so really don't need them to be part of the GPX data.
My current practice is to load ONLY the routes and way points for a specific upcoming trip...the BC category is un-important.
Like it or not/need it or not...category data is part of the GPX files. It can be seen when examining a file with a text editor.
When that trip is done, that data is removed from the device and the next trip is loaded.
John

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.

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.

Awesome! Thanks for being responsive to our requests and for keeping us up to date!!

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 remember the discussion re: Categories=Lists and how that could be a real problem in the future. Glad to see the future is being considered.

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.

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