Closed GoogleCodeExporter closed 9 years ago
Now using Gingerbread and latest MyTracks version 1.1.8 Chart axes now appear
to be correct but chart still shows no data. The chd url parameter is still as
per chart.txt attached in the previous report.
Original comment by bigya...@gmail.com
on 26 Aug 2011 at 10:31
Now using MyTracks version 1.1.10 Chart still shows no data - that is - no
traces are charted. Note however the chart axis are now correct. For some
reason the data is being reploaced with a comma. Refer to chart.txt attached
above.
Original comment by bigya...@gmail.com
on 17 Oct 2011 at 11:24
As per jshih@
Add as an enhancement. The KML file is working as intended.
The KML file doesn't include elevation. The user would like us to include it.
Hence Marking this as an Enhancement.
Thanks,
Original comment by nage...@google.com
on 19 Nov 2011 at 12:19
Ver 1.1.13 on Samsung Galaxy S with Gingerbread
The KML "End" icon bubble shows a blank chart (has for a year - probably
longer). That chart is titled "Elevation"; Y axis shows delta height change and
the x axis shows the distance travelled. However there is no plot of the data.
The chart is blank. The URL that summons the Google Chart does not have the
data concatenated to the end of that URL. Not sure how the KML can be working
as ended, if the user is shown a blank chart, especially when the axises are
correct for the route taken.
Program is getting better all the time :--))
Original comment by bigya...@gmail.com
on 5 Jan 2012 at 6:37
In the next release, the KML end point marker will no longer contain the
elevation chart. However, the KML track will now include the elevation data.
Thus in Google Earth, you can click "Show Elevation" to see the elevation graph.
I decided to remove the elevation chart in the end point marker because
1. It can contain at most 250 samples of the elevation data due to the chart
server limit.
2. The elevation data is now included in KML and can be viewed in Google Earth
Original comment by jshih@google.com
on 29 Feb 2012 at 10:55
Original issue reported on code.google.com by
bigya...@gmail.com
on 11 Mar 2011 at 1:58