Interesting Google Earth "bugs"

[routeconverter]

I've got GE 6.1.0.5001, and as I said, I'm not sure what version of kml it's saving in as it doesn't give me an option (or am I missing something).

It's KML 2.2 (called Google Earth 5 in RouteConverter).

But you would be interpreting the kml and using the correct format? I understand that writing a kml v5 loading into RC and saving as a kml v3 would mean some things get lost.

Yes, the KML 2.0 the GE 3 uses is rather different from the KML 2.2 the GE 5 and 6 use.

I don't think RC should be a kml editor, so if this is getting too complex it's OK, I'll just ensure that I finish with RC before I edit in GE

Good idea

[scribbly]

I don't think RC should be a kml editor, so if this is getting too complex it's OK, I'll just ensure that I finish with RC before I edit in GE

Good idea

What might be a good idea, to be completely transparent, is to warn the user that existing data with kml will be lost if saved with RC: then strip it out completely?

What I'm thinking is that if you aren't offering a complete kml editing experience then any of the extra kml stuff should be removed on save?

Just thoughts...

[kumo]

What might be a good idea, to be completely transparent, is to warn the user that existing data with kml will be lost if saved with RC: then strip it out completely?

This would require some kind of disclaimer at the begin of the 'Save as..' menu or at least when opening the file type selector box:

'Different file types may support different data. Columns, i.e. the height information, may get lost when coverting into a file type which does not support this data.'

[routeconverter]

What I'm thinking is that if you aren't offering a complete kml editing experience then any of the extra kml stuff should be removed on save?

Actually I'm aiming at keeping all the data not only the stuff that RouteConverter understands. Unfortunately, this is not implemented for KML so far.

[routeconverter]

This would require some kind of disclaimer at the begin of the 'Save as..' menu or at least when opening the file type selector box:

'Different file types may support different data. Columns, i.e. the height information, may get lost when coverting into a file type which does not support this data.'

Well, this is in the nature of a conversion tool: you cannot keep all the data. So far nobody complained about this (just for keeping all the data when staying within the same format which is reasonable). How about adding this to the features/tour section of the site?

[scribbly]

What I'm thinking is that if you aren't offering a complete kml editing experience then any of the extra kml stuff should be removed on save?

Actually I'm aiming at keeping all the data not only the stuff that RouteConverter understands. Unfortunately, this is not implemented for KML so far.

OK: That would be perfect Thought from previous comment that... oh, anyway, doesn't matter -- if you're planning on keeping that would be absolutely perfect.

Thanks!

[kumo]

This would require some kind of disclaimer at the begin of the 'Save as..' menu or at least when opening the file type selector box:

'Different file types may support different data. Columns, i.e. the height information, may get lost when coverting into a file type which does not support this data.'

Well, this is in the nature of a conversion tool: you cannot keep all the data. So far nobody complained about this (just for keeping all the data when staying within the same format which is reasonable). How about adding this to the features/tour section of the site?

Yes, good idea. I believe 'Features' would be the best place.

Here - quick and dirty - a text phrase:

Conversion into other GPS File formats

RouteConverter 'understands' more than 70 different GPS file formats as input files. Most of this formats can be written, as well.

Conversion into a other format is done via the file type selector in the menu File/Save as...

Be aware that different file types may support different data. Columns, i.e. the height information, may get lost when a position list is saved in a format which does not support the data for all columns of the position list.