Routeconverter interprets kml differences incorrectly

[hvdwolf]

Hi,

kml files can have the following setup for "Point".
longitude, lattitude, height as in
<Point><coordinates>8.199620,46.843810,0</coordinates></Point>

or longitude, lattitude as in
<Point><coordinates>8.199620,46.843810</coordinates></Point>
(kml 2.x version)

Routeconverter interprets the second format with only two coordinates incorrectly. It interprets the first <Point> correctly. Consecutive <Points> miss the longitude as Routeconverter seems to add the longitude as height (displayed as an integer). The longitude field remains empty.

Next to that: When this happens also the <name> blah blah </name> is no longer displayed.
(as in <Placemark> <name> blah blah </name> <Point> <coordinates> long,lat </coordinates> </Point> </Placemark>)

[hvdwolf]

Hi,

kml files can have the following setup for "Point".
longitude, lattitude, height as in
<Point><coordinates>8.199620,46.843810,0</coordinates></Point>

or longitude, lattitude as in
<Point><coordinates>8.199620,46.843810</coordinates></Point>
(kml 2.x version)

I just found out that there more options =blush=

[routeconverter]

Routeconverter interprets the second format with only two coordinates incorrectly. It interprets the first <Point> correctly. Consecutive <Points> miss the longitude as Routeconverter seems to add the longitude as height (displayed as an integer). The longitude field remains empty.

Do you have a small example? I guess you're referring to the "optional" in
http://code.google.com/apis/kml/document...oordinates ?

[hvdwolf]

Please find attached a zip from a .kml that is a walking track from my Navigon 1410.

This time a "command line" zip without the __MACOSX rubbish.

[routeconverter]

Please find attached a zip from a .kml that is a walking track from my Navigon 1410.

I've modified the latest prerelease to let RouteConverter read your file. Does it work for you?

[hvdwolf]

Please find attached a zip from a .kml that is a walking track from my Navigon 1410.

I've modified the latest prerelease to let RouteConverter read your file. Does it work for you?

It works fine now. Thanks a lot for your quick response and enhancement. All tracks are now read correrctly.
I will also get in contact with Navigon to ask why they add the elevation as part of the <name> instead of adding it as the third option in <coordinates> where it belongs.
But even if they respond I think it will take much longer for a new version than it took for a new RouteConverter from you.