Posts: 2
	Threads: 1
	Joined: Dec 2010
	
	
 
	
	
		When I open a Google Earth 5 KMZ file, make some changes in RouteConverter and save as "Google Earth 5 Compressed (*.kmz)" file, RouteConverter changes all the Track Names to "Track: <last 8 characters of existing track name>".
Is there a way to keep the original track name when saving as "Google Earth 5 Compressed (*.kmz)"?
	
	
	
	
	
 
 
	
	
	
		
	Posts: 7,536
	Threads: 232
	Joined: Aug 2007
	
	
 
	
	
		 (11.12.2010, 05:27)FlyingDutchman Wrote:  Is there a way to keep the original track name when saving as "Google Earth 5 Compressed (*.kmz)"?
Currently no. The Track prefix helps to set the display as a blue track line. If you change the type of the display to waypoints, RouteConverter uses Placemarks in folder - maybe that fits better?
	
 
	
	
--
Christian
	
	
 
 
	
	
	
		
	Posts: 2
	Threads: 1
	Joined: Dec 2010
	
	
 
	
	
		Thanks for the quick reply!
I tried the Waypoint List, but that's not at all what I'm looking for, I really want the Tracks. However, when I was testing out the Waypoint List, I noticed that the problem actually lies in having a slash (/) in the track name. RouteConverter removes everything before the last slash (/) and replaces it by "Track: ". I can work around that by changing the slash (/) to dash (-) in my dates 
Suggestion for improvement: allow Track names to have slash (/) in them.
	
 
	
	
	
	
 
 
	
	
	
		
	Posts: 7,536
	Threads: 232
	Joined: Aug 2007
	
	
 
	
		
		
		16.12.2010, 15:31 
(This post was last modified: 16.12.2010, 15:31 by routeconverter.)
		
	 
	
		 (12.12.2010, 03:45)FlyingDutchman Wrote:  Suggestion for improvement: allow Track names to have slash (/) in them.
I don't think this is an improvement. Let me explain why:
- KML files can have a rather arbitrary structure
 
- RouteConverter interprets <Folder> and their <name> as places where gps data may reside
 
- typically a slash(/) is used to separate path segments
 
- the path of the folders is used as the name of the position list and displayed in the combobox
 
- and the same path is used when converting KML files to and from other file formats
 
- this logic breaks if I choose another character or make it configurable
 
Does this sound understandable? Do you have ideas how to shape this into an improvement?
	
 
	
	
--
Christian