Convert CSV, GPX, GPI, OV2, KML, XML, OV2,TXT, etc. POI converter for Garmin, Google Earth, TomTom, and more. Use any GPS POI file on your GPS, no matter what brand. Jun 28, 2016 In order to convert to FIT, I need a 3rd party software package. I'm using JaVaWa RTWtool and that woks fine. If I create a TCX or a GPX in route format, and convert it into FIT, then put it into the New Files folder - where it should go I believe - it works as it should. My question is 'How do I create a FIT file?' No answer as yet.
![]()
Google Maps used to allow users to convert navigating directions into a KML/KMZ file; or you could import the URL for your Google Map directions into a GPX file using an app like.Google have disabled that very useful functionality and you now have to register, give your credit card, get an API code and then do the conversion. You do get $300 free credit before being charged, but I don't know how many conversions that lasts for. So I prefer not to sign up.I have tried a manual workaround for a route with only 10 or so directions, by plucking latitude and longitude data off a route in Google Maps and plugging it into GPS Visualizer. But it is too time consuming for a route with many directions.Does anyone know of a better workaround?Bob M. Google Maps used to allow users to convert navigating directions into a KML/KMZ file; or you could import the URL for your Google Map directions into a GPX file using an app like.Google have disabled that very useful functionality and you now have to register, give your credit card, get an API code and then do the conversion. You do get $300 free credit before being charged, but I don't know how many conversions that lasts for. So I prefer not to sign up.I have tried a manual workaround for a route with only 10 or so directions, by plucking latitude and longitude data off a route in Google Maps and plugging it into GPS Visualizer.
But it is too time consuming for a route with many directions.Does anyone know of a better workaround?Bob M. Edit: Besides using Google you can also use the OSMand app to plot a route for you between two points.I thought that the OSMand app would probably be able to save a plotted route as a GPX file so I did a search. It looks like the Android version can.
Also, after getting the directions you can reroute the route you where given (e.g. Visit a town a short distance away from the track their directions give). Read about OSMand's navigation features at the link below.
The part dealing specifically about your question is the last section of the file. Google Maps used to allow users to convert navigating directions into a KML/KMZ file; or you could import the URL for your Google Map directions into a GPX file using an app like.Google have disabled that very useful functionality and you now have to register, give your credit card, get an API code and then do the conversion. You do get $300 free credit before being charged, but I don't know how many conversions that lasts for. So I prefer not to sign up.I have tried a manual workaround for a route with only 10 or so directions, by plucking latitude and longitude data off a route in Google Maps and plugging it into GPS Visualizer. But it is too time consuming for a route with many directions.Does anyone know of a better workaround?Bob M. I had a quick look at MyMaps.
It is good, but for a brand new route (ie no downloadable WPs or tracks available) you have to manually place all your waypoints (WP) to create your map, adding nav instructions if desired at each WP.The big advantage of plain vanilla Google Maps is that I can create a walking route from A to B by simply inputting A and B. Google Maps automatically generates all the WPs and associated nav instructions for a walking route. It is remarkably accurate for the few Israel routes I have created so far - and I can easily 'drag' the route to fix minor anomalies.
The other big plus of Google Maps for my routes is that a surprising amount is available in Street View, which enables a 'virtual walk' through many sections.It saves a huge amount of work, but as I said earlier, Google no longer allows free conversion to any other format for export to other apps. And I prefer not to use Google Offline maps as a workaround. There is also some web chatter that you can't use Google Offline maps to actually navigate a walking route, but that may be rubbish.Bob M.
Edit: Besides using Google you can also use the OSMand app to plot a route for you between two points.I thought that the OSMand app would probably be able to save a plotted route as a GPX file so I did a search. It looks like the Android version can. Also, after getting the directions you can reroute the route you where given (e.g. Visit a town a short distance away from the track their directions give). Read about OSMand's navigation features at the link below.
The part dealing specifically about your question is the last section of the file. I got a bit carried away with my quickie review.Both Locus Map and OsmAnd use OpenStreetMaps (OSM) as their underlying map source, which is why the maps are so cheap. OSM maps are usually excellent, often amazingly so. You have to pay an extra ($5.99) for OsmAnd contour overlays, but contours/topo information is free in Locus Map Pro.Both apps show routes for many well-known walks eg Via Francigena, the various Ways of St James (Europe); the INT and Jerusalem Trail in Israel (my current project country).The free version of Locus Map gives you 3 free maps. You can buy more maps using Locus ‘coins’ (nothing like bitcoin, just accounting tokens which are non-tradeable and useless anywhere else). 100 coins cost me $A1.45, and a typical map of say Italy might cost 30 or 50 of these ‘coins’. Some tiny countries (eg Solomon Islands) cost only about 5 coins.
The point being that map costs are negligible.OsmAnd Unlimited costs $14.99 to buy (there is also a subscription option), but you get unlimited downloads. Locus Map Pro costs $10.99 to buy, but you pay extra for new maps.Both OsmAnd and Locus Map use BRouter (so does OruxMaps) as their underlying ‘auto route generator’. The version of BRouter on Locus Map gives you about 1400MB of free map tiles (ie map regions which ‘tile’ the entire globe). The tile for Israel (which also includes Lebanon, Jordan, parts of Syria and Iraq), was only 14MB.But generating an automatic route in Locus Map Pro using BRouter is frustratingly non-intuitive and clunky. The reason is that BRouter is a plugin and not tightly integrated into Locus Map and you have to pick your way through its complexity.By contrast, OsmAnd is a pleasure to use because BRouter has been coded into the app and is invisible to the user. You just choose the start and end points and the app produces an excellent route with an elevation chart and other metrics (so does Locus Map).
I used OsmAnd to make a hiking route for a part of Israel I plan to walk and the app routed me off main roads where walking tracks existed. Even better, the route looked sensible, with no crazy diversions, which minimizes clean-up work and tweaks.BTW, any of these ‘auto route generators’ only work if the map shows actual roads and tracks. If you are hiking in forest with no (or changing) tracks like parts of the Via Francigena for example, they are useless.If your route is straightforward and simple it would probably be better to plot your own WPs instead of using an auto-generator to produce a draft which you have to tweak. Both OsmAnd and Locus Map have good tools for manual route creation, although it is a bit of a pain doing it on a small phone screen.There is a learning curve with both these apps.
It seems to me that anything out of the ordinary in any nav app requires patience to figure out and get right. And you have forgotten it when you come to do the same thing months later! Or is it only me?There is plenty of jargon to master and it is not always easy to find exactly what you need among all the options and menus. Both apps have a large degree of functionality that can be a bit confusing. It’s my biggest gripe with Locus Map Pro.
There is so much functionality built in that it can obscure the basic essentials. OsmAnd seems to have a simpler interface – at least on my very quick superficial look at it.Both apps are excellent and there is little to choose between them. The choice might come down to aesthetics and which app you find the least complicated and easiest to use.
But if I were choosing purely on the auto-generate feature to create routes, OsmAnd would win hands down. It’s fantastic and I will test more of its nav features.Bob M.
Googe Earth is great, but the 'auto-generate' feature for creating routes does not exist in Google Earth so far as I can tell. You have to create a route manually in Google Earth I think - please correct me if I am wrong on that.Google Maps and other apps like OsmAnd OruxMaps and Locus Map Pro allow you to 'auto-generate' a route for driving, cycling, hiking etc by simply entering the start and end points. It saves time for long hikes with maybe 30+ WPs per stage, because you only have to clean up the auto-generated route instead on manually plotting every WP to create a route from scratch.Google Maps used to allow users to convert an auto-generated route and nav instructions to a GPX file which made it easy to import into a nav app (eg Locus or OsmAnd) on your phone. Google have blocked that convenient functionality (unless you register and pay), presumably because it was being abused. I was looking for a (legal) hack to get around that limitation.Many people just use Google Maps (offline) to navigate with, using its auto-generated routes. Great for driving and walking around cities; but for hiking I much prefer to use a dedicated nav app like Locus (or an equivalent) because their topo maps are so much better than Google Maps.
It's a personal choice.Bob M. I will be the only person using my GPX files.
My Locus Map of Israel is in English, which makes planning at home a bit easier.Unfortunately, the Locus Map route creator is irritatingly clunky (as I mentioned in an earlier post). OsmAnd has an excellent route creator option (although its Israel map is in Hebrew), so I will experiment with it to create my routes and export the GPX files to Locus.BTW, I have also developed a manual workaround to turn Google Maps auto-generated routes into GPX files for import into Locus Map. I copy and paste the coords of each Google Maps WP and nav instructions into a spreadsheet and use to convert that data into a GPX file which is easy to upload into Locus Map. It is practical for short, uncomplicated stages with maybe 20 WPs max.So, with the help of everyone here I now have a couple of workable solutions to experiment with.Bob M. I will be the only person using my GPX files.
My Locus Map of Israel is in English, which makes planning at home a bit easier.Unfortunately, the Locus Map route creator is irritatingly clunky (as I mentioned in an earlier post). OsmAnd has an excellent route creator option (although its Israel map is in Hebrew), so I will experiment with it to create my routes and export the GPX files to Locus.BTW, I have also developed a manual workaround to turn Google Maps auto-generated routes into GPX files for import into Locus Map. I copy and paste the coords of each Google Maps WP and nav instructions into a spreadsheet and use to convert that data into a GPX file which is easy to upload into Locus Map. It is practical for short, uncomplicated stages with maybe 20 WPs max.So, with the help of everyone here I now have a couple of workable solutions to experiment with.Bob M. The interface is not 'pretty' (or simple to figure out) but GPS Visualizer is a very flexible app with many conversion options.You can choose various options for file conversion spreadsheet to GPX: The default output is WPs, but you can also choose 'track' or 'route' the latter being navigable, the former not.
You can also add a column for notes, directions etc for each WP. Finally, you can choose to have the app add elevation data - very useful if your route is taken from Google Maps, which has no elevation data.Bob M. Plus, it colour codes the elevation profile to show the slope. I would definitely have a celebratory swig of vino rosso after successfully slogging up a long 20% slope. Or maybe before, to dull the pain.Google Maps usually produces several suggested routes for the same start/end points. I might compare a couple of stages near Jerusalem where the elevation rises from roughly 70m up to 750m, with ups and downs in between.On a related subject, there are rules for correcting walk times for net elevation gain.
I add 1 hour for every 300m net gain, but I am not sure if that is a commonly-accepted rule. My Brierly guide to the Camino Frances used a variant of this method, which seemed great at the time to figure out the time to walk each stage.is another such rule.Bob M. Wikiloc would be the better choice for this. It has the profile for a chosen route already and can show it, the track and a base map at the same time. Also you can slide along the profile and see the position of a point of the profile on the track and map. So, for example, you may see a steep rise on the profile so you slide your finger/cursor to the base and on the map you may see a trail going around the hill that looks like a faster or better way to go. The map might even show that there is a tram going up the hill.
It beingIt allows you many other ways to color code, e.g. Speed, track, latitude, elevation, heart rate, course heading and more. It allows captions, computes elevation gain/loss, puts in waypoints or not and cooks your eggs to order. You just have to learn it and that isn't the easiest thing to do. I've learned a number of things it can do but I have trouble remembering what I have to do to make the tool do them.
Sometimes I worry that the sever might cut me off because I've hit the 'Draw the profile' button so many times with different input. I'm not sure net gain is the most useful measure, but if it works for you, there is no compelling reason to stop using it. Time adjustment techniques can generally be traced back to a 'rule' developed by a Scot named Naismith in the late 19th C. The basic rule has had improvements and corrections over time. Naismith and his successors used total gains and losses, sometimes referred to as the cumulative climbs and descents. Brierley's formulation gives slightly different results to the formulation I normally use when I am bushwalking, but this is not enough to be really significant in most places. I decided to try a search like this.
The US state of New Hampshire has 48 mountains above 4,000 feet elevation. A guide has them listed so hikers can check them off once done. Peg and I decided to save Wildcat Mountain for last because there is a ski lift that runs all year that could carry non-hiking friends up to celebrate with us (though a good day came and we did it instead on the spur of the moment).
We used the Appalachian Trail for the ascent.Looked this hike up on Wikiloc and a base map does show the lift runs.
ChangeLog:Version 6.2. Added iGPSPORT iGS50E. Added Sigma Rox 12.0Version 6.1. Fixed an issue in the time stamp tool where TCX files could not be time stamped. The time stamp tool can now work on GPX, TCX, and FIT files. Added Suunto Spartan Ultra. Added Garmin Edge 830.
Fixed an issue where accumulated distance would not be retrieved from FIT files.Version 6.0. Added Garmin Fenix 6x SapphireVersion 5.9.
Added the ability to discard trackpoints. You can discard up to every 10th trackpoint. This is useful if you have 1 second recording turned on during a very long activity. If your file is too big, Strava or Garmin Connect will not accept your file. The feature helps with that.
Changed the 'Ignore Big Gaps' feature so that the user can customize the size of the gaps which are to be ignored.Version 5.8. Added Forerunner 645 GPS. Added Edge 530 GPS.Version 5.7. Added Coros Apex GPS. Added Bryton Rider 450 GPS. Added Bryton Rider 530 GPS.Version 5.6. Fixed issue where certain streams could not be read from certain GPX file formats.
Changed the requirement on the time stamp tool so that you do not need latitude and longitude to run the tool. If you do a time-shift, that will still work fine, but if you try to add calculated time stamps based on position, it will produce a file with zero time. I decided to open this up, though, because I have been finding that people are now uploading multiple and varied files to the time stamp tool. I may change it back or provide a warning note because people think that the tool failed when in reality, they did not have any position data to calculate the time from. Added ability to time-stamp TCX and FIT files (beta - let me know if this does or does not work for you). Fixed an issue related to Safari for our kind donors.
If you donated with Safari, that browser will only let us store the fact that you dontated for one week. I wrote a work-around so that your Safari browser will remember your donation for 10 years. Sorry if you got multiple nag screens.Version 5.5. Fixed an issue where cadence could not be read from certain FIT files.Version 5.4. Combined the Time Stamp Tool with the File Merge Tool.
For file mergers, this makes no difference - but for Time Stampers, the tool will look a little different and run a lot faster! Right now, you can only time-stamp GPX files (import/export), but I plan to add time stamp ability to all file types. Also, I plan to give the ability to reverse the GPS tracks.
Moving forward, you will see release notes here for the Heart Rate tool, Time Stamp Tool, and File Merge tool because they are now all using the same engine. This allows me to maintain one set of high quality code as opposed to scrambling to release updates/improvements to 3 separate tools. In the Change log, I will try and identify changes that are specific to just one of the tools. Time Stamp Tool: Improved smoothing and speed estimation when user selects the 'Consider Elevation When Calculating Speed'. Added ability to Ignore Big Gaps in distance accumulation for TCX files. If you are merging rides with a boat or ferry ride (for example) in the middle, you probably don't want to get credit for that distance.
If so, choose to Export in TCX format, Choose 'Calculate Distance', and selecte the new 'Ignore Big Gaps' button. If the distance between two points is greater than 5 miles and the time gap is more than 10 minutes, this distance will not be added to your final file.
Added verbiage to help users identify problems with the zip files they upload. Specifically, we do not allow zip files to contain sub folders.
If your GPX,TCX or FIT file are in a sub folder within the ZIP file, they will be ignored. Now, the site lets the user know what happened.
Removed the Legacy Heart Rate Combine tool.Version 5.3. Added ability to detect swim workouts on French Language Devices. Added ability to merge swim files that have no position data.
Fixed an issue where certain GPS types may not be auto selected (this would happen if one of the files you uploaded had a device ID that did not correspond to any known GPS name)Version 5.2. Noted that some manufacturers are recycling product ID numbers. Therefore, I added a method to detect manufacturer number as well to better identify GPS units. Added a nag screen that asks for donations if a person has done more than 5 combines. The nag screen is just a reminder and you can dismiss it forever by donating or by saying you donated. Hopefully you did do that.
I am working all day at this - sometimes spending hours to add features for certain individuals. I do this work for free.
Note that the browser remembers if you dontated - but if you switch to another browser or delete your cookies, it will nag you again. Increase the number of cycles where the tool looks for streams. Previously, to save processing time, the tool only looked 50 trackpoints deep for data. Now it looks 100 points deep. This will help with activities where no data is recorded at the beginning of the activity. Improved verbiage to help people learn if they should export in GPX or TCX format. For outdoor activities on Strava, I recomment GPX.
For all other activities that need cadence or power and websites other than Strava, I recommend TCX.Version 5.1. Worked on issue where time zone cookie may not have been stored. Not sure if it is working yet in all browsers. Rewrote the cookie reset code so that it forces the browser to reload my javascript (in case there have been any changes).
This makes sure that you have the latest version of the javascript in your browser cache. Added versioning to display. This way, you can make sure that you are viewing the latest version of the page as opposed to a cache. I cannot think of how you would be viewing an older version of the page - but certainly your browser could have an older version of the javascripts loaded.Version 5.0. Added a new option so that when tracks are overlapping, users can select to only include trackpoints that have position data.
This will help some users upload their files to certain platforms (other than Strava and Garmin Connect which have no problem accepting trackpoints that are missing position data).Version 4.9. Added ability to select Zwift as a GPS type. Added Strava supported Activity types like skiing, virtual rides, etc. Differentiated between Garmin and Strava accepted Activity types. Set javascript to pre-select virtual ride fro Zwift, Wattbike, and FulGaz. Added ability to select Zwift as a GPS type.
Reduced clutter in GPS type list. Some GPS units have been assigned more than one Product ID by Garmin. Previously, I was just listing every single product by Product ID. Now, if the same product ID appears twice, it ignores all subsequent product IDs ULESS the device that you uploaded from happens to have one of the multiple product IDs.
If that is the case, then your device/product ID is automatically selected.Version 4.8. Fixed an issue with distance calculations for indoor workouts.
This only would happen if you had selected to use the embedded distance data. The bug resulted in calculated distances that were too high.Version 4.7.
Fixed an issue with Safari where the tool would not store your time zone settings. This has to do with Safari blocking pages from setting cookies from an iframe. The Time zone entry is only necessary for people who are doing trainer rides - because the time zone may not be included in the file, and then when you go to the 2nd page, the graph makes it look like you started your activity at an odd time (unless you live along the Prime Meridian). The tool doesn't need you to enter time zone from outdoor files because it takes the very first GPS point and looks up the location in a time zone database, which is pretty reliable.
Added Bryton 330 GPS and also made the GPS detection method for FIT files able to pick up some outliers. Certain manufacturers have different ways of coding the GPS product ID into their file. Fixed an issue where you would have to reconnect to Strava even after you got the new access token. This is because I had the access token expiring after 6 hours (which id does). But my tool assumed that if the access token was expired, you were no longer connected. Now, that is not the case, and the tool looks to the refresh token to keep you connected to Strava.Version 4.6.
NEW! Now you can upload ZIP files containing either TCX or GPX files! This will allow you to bypass the 10Mb file upload limit. The ZIP files are still capped at 10Mb, but you can fit a LOT more TCX and GPX data into a zip file. I'm not accepting ZIPPED FIT files because FIT files are already compressed and contain a TON of data that will overwhelm the server.
The reason for the file size limitation has to do with the Server's ability to process data. Also, it saves you upload time & saves the server badnwidth.Version 4.5. Fixed an issue where GPS types would not be read and pre-populated from TCX files.
Added ability to read activity type from TCX files.Version 4.4. Fixed an issue where Turbo/Trainer rides would have power data drop to zero periodically with certain output settings. Fixed an issue where certain types of GPX file inputs would not be recognized after the first lap.
Fixed an issue where files that did not have any stream data within the first 10 points would not receive a steam option. Now, the tool looks 50 points deep to see if there are any values for each stream. The reason we don't read the entire file is to save bandwidth/resources.
Investigated an issue where cadence was not detected in certain FIT files. This appears to only apply to running activities. Still unresolved. Although this tool is oriented around Strava and Garmin Connect, I fixed an issue last week with uploading to Training Peaks if the device happened to be an Apple Watch. Fixed an issue where if you uploaded files that contained certain streams. But the streams had values of zero, the stream would show in the list. Now, if those values are empty, the stream does not show up on the Sorted Graphical Representation Page.MergeHeartRateTCXWithPositionTCXLegacy Note.
Hi guys. I have been working on this tool 15 hours a day for the last 5 days in a row. Many people have written me asking about the old heart rate tool - especially people using trainers. Eventually, I want to retire the old tool, so please use this new one first.
If it doesn't work, you need to contact me, and I will ask you to email me files so I can make the new tool do what you want. For every person who has written me about the new tool not working for them, there used to be just as many people who were asking for the features that I added to the new tool! So if you miss the old tool, remember there is another person who is happy that the new tool works for them. This new tool will eventually become a one-tool-does-it-all. But to make that happen, I need your files and situations that aren't working.
I need detail. Believe it or not I am spending hours every day helping tons of people. I am one person, and this is more than a full time job (I don't have an other job)! I've gotten to help with people climbing Everest, and some pretty crazy, long bike rides that people have done that were too much for the tool to handle. Thank you for reading, and please consider making a donation for all my hard work to help you voluntarily. Remember: if the new tool doesn't work for you, I need you to let me know what isn't working. I can make it work, but I need to know what your specific problem is.
The tool already works for 95% of cases, so I need to iron out bugs with the remaining 5%.Version 4.3. Big Changes! I have combined the Heart Rate + GPS tool in with the Merge Tracks Tool. One tool can now do it all!. I have been thinking about the concept of data 'streams' for a long time with this tool.
My idea was to parse every single uploaded file into it's components - a list of heart rate values, a list of position values, a list of cadence. You get the idea. Then, sort everything by time, and let the user decide which streams to include. This allows the user to process overlapping files (though partial overlaps may be confusing), and it allows the user to merge turbo/trainer files - one with heart rate and one with power.
Basically, the hope is that this will eventually become a universal tool for merging GPS files for Strava. Added Javascript to notify users BEFOREHAND that they are trying to upload files that are too big or unsupported. This saves the user time. Previously they wouldn't find out until after it had been uploaded.
Changed the way that the XML is parsed. I now use code that runs a lot more efficiently and uses less memory. This will hopefully help prevent some of the blank pages for people who were uploading massive FIT files. Upgraded to PHP7. This version of PHP is supposedly faster. Included some error catching to prevent division by zero.
Sometimes, when creating the TCX files, the tool would try to calculate the distance between each point. The problem was that if there were any bad points, we might get a division by zero error that would cause the app to give a 500 error. I Gave the user the freedom to select which streams would be included in the final track.
Note that if you have overlapping tracks, in some instances it may cause wonky tracks if you include two sets of the same data. Try different things if you have problems. I Gave the user choice in where distance data comes from in TCX files. We only recommend TCX output for indoor workouts. Strava lets us use the Cluetrust schema, which means we can include the 4 big hitters with GPX: Power, Heart Rate, Cadence, and Temperature. With TCX, we cannot include temperature.
TCX output is good for trainer workouts, though, because it does not require GPS position data. I Re-did the Connect to Strava link. Strava is switching to an accesstoken/refreshtoken scheme, and in the last couple weeks, many new users reported that the connect to Strava did not work for them. You may have to reset your cookies to get the connect to Strava feature working again, but once you do, hopefully you won't have to do it again for a while.Version 4.2. Added more GPS units including Garmin Edge 520 plus, Garmin X40, Fenix 5 Plus, Acque Libere, Vivosmart 3 and 4, Forerunner 645 Music, Polar Vantage V and M, Garmin 130.Version 4.1.
Improved ability for the tool to read GPX file extensions. Added temperature export in GPX file type.Version 4.0. Big Changes to the Uploader and the Site.
Globally implemented HTTPS instead of HTTP. This was to comply with more modern standards of privacy and security. Updated the Privacy Policy and the Terms of Service.
Have a look at these if you get the chance. Changed the uploader to use Javascript.
This allows me to give you a progress indicator as your files are uploading to Strava. This feature DOES NOT come into play if you just download your file. If you are sending directly to Strava, however, the javascript will tell you the status of your file as it is being sent to Strava. Previously, some of you may remember a similar indicator. The problem was that once I shifted from HTTP to HTTPS, the output buffer was not being flushed. This means that when I tried to use PHP to send you progress updates, you wouldn't get anything until the whole process was done.
Obviously, this isn't very useful. If you have Javascript turned off, please turn it on if you want this feature to work. The upload will still work without Javascript - but the page will look weird.Version 3.9.
Made a change that fixed an issue with certain types of TCX files not being parsed correctly.Version 3.8. Fixed an issue where FIT files from Wahoo devices were not always recognized. Added ability to export Temperature (GPX only). Also improved power and heart rate export in GPX files. Switched recommended export format from TCX to GPX. This is due to smaller file size, the ability to send temperature to Strava, and better reliability in general. Expanded digit recognition from 20 to 30 decimal places in very precise GPX files from Garmin Connect.Version 3.7.
Added more GPS units including TomTom Sport watch, Fenix 5, Fenix Chronos, Forerunner 35, etc.Version 3.6. Removed the 'DistanceMeters' tag from the TCX output. Well, it was causing some people issues. The DistanceMeters tag is useful for people who are using trainers (for example) because trainers do not record Latitude and Longitude. With a distance entered in between each track point, that allows people to still get a mileage for a file that has zero trackpoints. Of course, any software worth it's beans will re-calculate the distance like we were doing.
So, it's a bit redundant. Removing it makes the TCX file that much smaller as well. I also remembered that this app doesn't accept files without Lat/Long anyway (sorry swimmers and trainer users). I feel it is much more important to have a combined track in instances where there is a map to be displayed, so we intend to focus on combining those types of files instead. While I was in there coding, I noticed a bug where Power and/or Cadence would be lost from the output files under certain circumstances. I'm happy to have that fixed, as occasionally I receive reports that people didn't have power data in their combined file.Version 3.5.
Recently encountered a rare issue where a FIT file from an unknown device had timestamps without corresponding latitude/longitude. When uploading the resulting file to Strava, the user experienced an unusually long ride duration - in spite of the fact that there were no errant points in the resulting file. Changed the code so that if you’re uploading a FIT file, then we will NOT INCLUDE any trackpoint (i.e. What does this tool do?This tool will allow you to take GPX, TCX, or FIT files and combine them into one single file for upload to Strava. There are two ways that people commonly combine files. The first is if their GPS dies during a ride, and they start another activity (on their phone, for example).
![]()
In this scenario, the user uploads both ride files, and then combines them into one, single GPS file. This is a concatenation of files. The other thing this tool can do is combine overlapping files. For example, a user has a Wahoo device that records heart rate, and TCX output from their indoor trainer. Both devices record at the same time, but the user wants to merge the heart rate data with the ride data.
This tool can do that too! Just select the stream you want from each file.What File types do you accept?The tool accepts FIT, GPX, and TCX files. We also allow you to ZIP your GPX or TCX files and upload a ZIP file. No other formats are accepted. It can combine any combination of files. Two FIT files and one GPX file? One GPX file and one TCX File?
Three FIT Files? You get the idea.What if my files are too big?I am one person providing this service for free. I can only afford a certain amount of server power - so really big rides with tons of sensor data (think: temperature, power, cadence, etc.) plus 1-second recording enabled may be too much for the tool to handle. Therefore, I have capped the upload sizes. FIT files may appear to be small - but they actually are compressed with a LOT of data.
The tool needs to iterate through all of that data, so even an 800Kb FIT file may be overwhelming. Meanwhile, the tool can handle 10Mb GPX and TCX files farily easily. To save you time uploading GPX or TCX files - which by nature are uncompressed - I allow you to zip these types of files and upload them. This may help you bypass the size limits. It looks like you are getting a lot of use out of this tool!I am glad that this tool is helping you out, and I hope you keep using it. Please consider making a donation to help keep me motivated to continue making updates and to help pay for the server. Every little bit counts - but please keep in mind that a donation of $1 is mainly a donation to paypal, not the developer.
If you donate one US dollar, about 40% goes to PayPal, and 60% goes to the developer. If you donate $10, then 5% of your donation goes to PayPal and 95% goes to the developer of these apps. Thank you for your support!
Also, if you cannot afford to donate, don't worry - I still aim to keep these apps free; thankfully, people who are able to donate have helped keep me inspired. StreamsTime: Every GPS file should have at least one stream: time. If there isn't a time stamp in your file, it will not work with this tool. Everything you import into this tool is ordered by the UTC time stamp. If the time in your device is settable (and doesn't rely on GPS), you need to make sure that the time is set correctly. If it is not set correctly, your files may not overlap properly.The remaining streams can be added to the final file by checking the boxes for each desired stream. By default, we include all streams - but this is not always a good idea.
For example, if you are trying to merge two files that occurred at the same time (for example you recorded heart rate on one device and position on another), then you need to choose just one stream from each file. If you try to select position from two overlapping files, you may get wonky results!Why is the distance stream grayed out? You can make choices about the distance stream down below. We offer 3 options: Leave it out, Recalculate, and Use Embedded. The only time the existing distance stream will be included is if you decide to use the embedded distance tags. See the help on those options to learn about caveats of including distance and when you want to include it.
Note that this only applies to TCX file export. TCX vs GPXStrava accepts a special type of GPX file format that allows us to embed power, cadence, heart rate, and temperature info. GPX is a great output format if you are uploading the combined file to Strava and it was an outdoor activity. Other websites don't accept this special format - so if you are having trouble with our GPX files on another website, please try TCX. Note that TCX allows for power, cadence, and heart rate - but does NOT Allow temperature. Sorry; we did not make those rules!
So, if you decide to use TCX, you are going to lose the temperature stream.GPX files are strictly position based - they were invented for tracking location. The TCX file format was designed more for workouts, allowing for Heart Rate, Cadence, Power, etc. WITHOUT position being required. As such, We recommend that you use TCX format if you will be uploading a position-less file to Strava. Examples of position-less files are turbo rides, trainer rides, treadmill runs, pool swims, and indoor activities.
The drawbacks to TCX are that the file size is bigger, and you lose temperature data. If those two items don't affect you, please go with TCX. If TCX does not work for some reason, give GPX a try. What is 'Randomize ID Tag?'
.In a TCX file, Strava will read the time stamp between the tags. If the time stamp is within a minute or two of an activity that you have already uploaded to Strava, the activity will be considered duplicate.
This is the only method that Strava currently uses to determine duplicity. So, if we just move the time stamp back in time two to 15 minutes, it will appear as a new activity. If you check this box, we will randomly move the time stamp back in time. If you don't check this box, the time stamp will be the same one from the first file you uploaded. When I say 'First File' I mean the activity with the earliest time; presumably your first GPS track of the day.For GPX files, the time stamp is not in the tags - it is in the tags.
The concept is the same; we just change that time stamp instead. My GPS is not listed.The TCX file format embeds a ProductID tag and a Device Name. There is no public list of the IDs, so I'm building it as we go along. If your device is not listed, and I will add it. I'll need for you to email me your TCX or FIT file (GPX files are of no use).
I will also need for you to tell me which Make and Model GPS you have.Garmin only embeds the GPS name and Product ID in the TCX file. In the GPX file, this information is absent, but for Strava, we are using the Cluetrust Extension that allows us to spoof the GPS type. Note that this is only promised to work with Strava, not other websites.
Calculating DistanceOnly TCX and FIT files have the distance between trackpoints already calculated. Therefore, these options are only available for TCX output (we do not output FIT). We recommend that you do not calculate distance between trackpoints for outdoor workouts. It is slower and Strava will recalculate your distance anyway.Do Not Embed DistanceThe best choice for outdoor workouts uploaded to Strava.
If you select this option, the DistanceMeters tag will be left out of the TCX file. That is not a problem if you have GPS points because Strava will just re-calculate the distance anyway.Calculate DistanceWe will calculate the distance between every single point in your GPS file. Remember that this ONLY WORKS if you have a position stream selected above!
If there is no position data (such as an indoor workout) we cannot calculate distance. An example of a file with no position data could be an indoor workout or turbo/trainer file. Now you can also Ignore Big Gaps. Let's say you want to combine two rides with a ferry ride in the middle - but do not want the ferry ride distance to show on Strava.
Using the default settings, if the time between points is more than 10 minutes AND the distance between points is more than five miles, when you check this box, the accumulated distance will be removed from the TCX file. This only applies to TCX as GPX does not support accumulated distance. As of Nov 10, 2019, you can now customize the distance / time to be ignored.Use Existing Embedded DistanceThe best choice for indoor workouts.
If you are trying to merge Heart Rate file with a turbo/trainer/treadmill workout file. And the files overlap (i.e. They happened at the same time as opposed to end-to-end), you will want to select this option. This will use the distance data already present in your file so you get credit on Strava. If you choose this option, make sure that you choose ONLY ONE distance stream in the table.
If you check multiple distance streams, you will get very strange results! Overlapping TracksSome files may overlap. This may be intentional if you're using two devices on a trainer (for example). Maybe you're recording speed with a Garmin and heart rate with a Polar. In other instances, the overlap may be less intentional. For example, maybe you see that your Garmin is on 1% battery, so you decide to start recording on your iPhone before the Garmin dies. Either way, we need to decide how to deal with the overlap.The first option is to Keep All Trackpoints.
We suggest you try this option first. If you have trouble uploading the resulting file to a 3rd party site, try the Remove Duplicate Trackpoints option. I have tested on Strava and Garmin Connect, and this option works. This option takes all of your selected streams from both devices, and if they both have recorded a point at the same second, a duplicate entry goes into the final file.
I did some testing, and Strava accepts this. I even tested with two overlaid position files, and saw some micro-zig-zagging due to the slight position differences between the two GPS units. Programs other than Strava may not accept the Keep All Trackpoint option because you really should only have one entry per second.The second option is to Remove Duplicate Trackpoints. This will prioritize the streams from the first file (that would be the uppermost file in the graph).
You will be losing some data. I tried this with two Garmin GPS units running at the same time, and I found that the losses did not affect the final recording in a big way. Removing duplicates should also result in a smaller file, and choosing this option may fix problems encountered when uploading to certain 3rd party websites.The third option is to Only Include Trackpoints that have Position. I found that some platforms have trouble with 'missing data.' Let's say that your heart rate device records a point every second, but your GPS device is on Smart Recording, and only records every few seconds. If I try to include all of the data, there will be trackpoints that only have heart rate data - but no position data.
Each platform handles this differently. Strava and Garmin Connect do not seem to have an issue with this. Other platforms may give you exceedingly high distance. If that is the case, give this option a try. Send To StravaWe can upload directly to Strava on your behalf. The first time, you will need to click the 'Connect With Strava' button.
Strava will ask you if you want to give us permission to make uploads on your behalf. If you agree, in the future, you can just check this box (it will remain checked and saved in your cookies as a preference), and the file will go directly from our website to Strava's. This will save you from having to download the file and then uploading it again.If you are having trouble uploading to Strava, please. We are migrating people to a more secure connection to Strava, so if you haven't used GOTOES tools since March 23, 2019, we recommend that you reset your connection and re-authorize GOTOES. Your old authorization will stop working October 2019. Time Shift.If you check the Time Shift box and your GPX file has time stamps in it, we will set the very first point in your ride to the time stamp you supply in 'Activity Start Time.' We will then calculate the difference in time between the time you supplied and the time provided in the track.
We will apply that time-shift to every point in the track. This way, the exact speed you traveled is maintained; the only difference is the time that you did it. If you select this option, 'Desired Average Speed' and 'Consider Elevation in Calculating Speed' will be ignored. The time zone you supply is important - if you supply the wrong time zone, your track may be time-shifted by more (or less) than you expect. Desired Average Speed.This works by the tool taking each and every point and analyzing the distance between them.
From there, it takes a simple distance over time calcuation to produce a speed. The tool takes your desired speed and calculates the time between these two point to achieve that. Since the granularity of the tracks can differ, you may get some sketchy speeds - mostly this happens in instances where the trackpoints are too close together (like when you are hanging around at the coffee stop instead of riding.
If you leave this field blank, the tool will just assume 20 miles per hour. What is 'Consider Elevation in Calculating Speed?' .If you do not check this box, the track we spit out will be basically a flat line of speed. In other words, you will be going the speed you specify for the entire duration of the track. If there are hills, and you specify 20mph, you will be climbing the hills at 20mph. That is not very realistic. If you check this box, we will implement a special algorithm in calculating your speed.
As the grade increases, the tool will slow down your speed on the track. As the grade heads downhill, your speed will be increased. Note that this algorithm is tailored for moderate, touring cycling.
Run results may not be very accurate - especially trail runs.
![]() Comments are closed.
|
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
March 2023
Categories |