![]() Assuming that you run steadily, you could for example for a half marathon (21,000 meters) represent a point every 20 meters. If you want to show a run over several hours on a map, you will not need a point every 5 seconds of the run. Adapt the number of points in the GPX file using GPSBabel Compared to the input file 2011_HM_Gyeongju.gpx with 341.7kByte, this is already a reduction to 20% of the file size. To apply this code to the GPX file we simply use the XSLT service from online-toolz and enter its input file in the left column, the code in the right column and then I get the new GPX file with 69.2kByte, which I save under 2011_HM_Gyeongju_latlon.gpx. Nick gave me the following lines of XSLT code to eliminate the unnecessary data ( marked in red) in the GPX file: However, only the geodata are required for the display on the map, i.e. ![]() If you open the GPX file with a text editor you will find individual points of your training session in the following form: 40.5128174 Reduce number of waypoints with GPSBabel: 58 kByteĪdapt the GPX file to your needs with XSLT.Reduce data for each waypoint with XSLT: 92.2 kByte. ![]() The individual steps with their progress: ![]() All tools are available under Win, Linux and Mac. 16% of the GPX file size optimizes the loading time of a homepage without recognizing any significant losses in accuracy. Using the practical example of a half marathon with the Garmin Forerunner 305, this article shows how a reduction to approx. with WordPress and the OpenStreetMap plugin OSM. Most GPS heart rate monitors allows the individual training units to be saved as a GPX file – in addition to the geodata, other data are also included that are not necessary for the display in maps and the resolution is far above that required for integration into a homepage – e.g. ![]()
0 Comments
Leave a Reply. |