ImportAllTracks is essentially just a modification of ExportAllTracks that
uses the existing GpxImporter to import all GPX files found in
/sdcard/MyTracks/gpx. So that the import functionality can always be accessed,
the MyTracks Activity's MenuManager is altered so that the Tracks button shows
regardless of whether there are any tracks in the database (ImportAllTracks is
launched by a button in the lower right of the MyTracksList activity).
A Toast message shows if no GPX files are found; this serves as a hint to
users on where to put GPX files for import so that this addition should be
discoverable and useable without documentation.
Im
Instead of producing the comparison strings in the tester just as they
are produced in the tested code, use string literals, thus actually
testing that the formatting code is working as expected.
Instead of producing the comparison strings in the tester just as they
are produced in the tested code, use string literals, thus actually
testing that the formatting code is working as expected.
The only thing not allowed in 1.1 currently used is the track color
tag, which is moved into the "<extensions>" tag to make it conform to
the 1.1 schema.
The only thing not allowed in 1.1 currently used is the track color
tag, which is moved into the "<extensions>" tag to make it conform to
the 1.1 schema.
The only thing not allowed in 1.1 currently used is the track color
tag, which is moved into the "<extensions>" tag to make it conform to
the 1.1 schema.
The only thing not allowed in 1.1 currently used is the track color
tag, which is moved into the "<extensions>" tag to make it conform to
the 1.1 schema.
The GPX schema requires waypoints to come before the track.
Waypoints are not currently used in TCX export, so there are no
changes there.
In KML files, both tracks and waypoints are "Placemark"s, so it
doesn't matter what order they come in there.
This does change the order they appear in CSV files, which could
potentially invalidate some assumptions made in downstream tools.
The GPX schema requires waypoints to come before the track.
Waypoints are not currently used in TCX export, so there are no
changes there.
In KML files, both tracks and waypoints are "Placemark"s, so it
doesn't matter what order they come in there.
This does change the order they appear in CSV files, which could
potentially invalidate some assumptions made in downstream tools.
The GPX schema requires waypoints to come before the track.
Waypoints are not currently used in TCX export, so there are no
changes there.
In KML files, both tracks and waypoints are "Placemark"s, so it
doesn't matter what order they come in there.
This does change the order they appear in CSV files, which could
potentially invalidate some assumptions made in downstream tools.
The GPX schema requires waypoints to come before the track.
Waypoints are not currently used in TCX export, so there are no
changes there.
In KML files, both tracks and waypoints are "Placemark"s, so it
doesn't matter what order they come in there.
This does change the order they appear in CSV files, which could
potentially invalidate some assumptions made in downstream tools.
Addresses issue #299 and ensures Latitude and Longitude are formatted
correctly as well.
Also orders the elements in the waypoint correctly according to the
schema: <ele> and <time> need to come before <name> and <desc>.
Addresses issue #299 and ensures Latitude and Longitude are formatted
correctly as well.
Also orders the elements in the waypoint correctly according to the
schema: <ele> and <time> need to come before <name> and <desc>.
Addresses issue #299 and ensures Latitude and Longitude are formatted
correctly as well.
Also orders the elements in the waypoint correctly according to the
schema: <ele> and <time> need to come before <name> and <desc>.
David Piggott