Just found this link to support.trainerroad.com which describes the file formats TrainerRoad accepts, and in the comments Mihai Tintea describes how to create an MRC file from a gpx and import into TrainerRoad. He evens adds a video of the activity to TrainerRoad!
Export information in CSV format, or import information if CSVFILE is specified. When importing, the CSV file must be in exactly the same format as the exported file. The first row of the CSVFILE must be the ExifTool tag names (with optional group names) for each column of the file, and values must be separated by commas. A special "SourceFile" column specifies the files associated with each row of information (and a SourceFile of "*" may be used to define default tags to be imported for all files which are combined with any tags specified for the specific SourceFile processed). The -csvDelim option may be used to change the input/output field delimiter if something other than a comma is required.
import garmin tcx file matlab
When importing, empty values are ignored unless the -f option is used and the API MissingTagValue is set to an empty string (in which case the tag is deleted). Also, FileName and Directory columns are ignored if they exist (ie. ExifTool will not attempt to write these tags with a CSV import), but all other columns are imported. To force a tag to be deleted, use the -f option and set the value to "-" in the CSV file (or to the MissingTagValue if this API option was used). Multiple databases may be imported in a single command.
Use JSON (JavaScript Object Notation) formatting for console output, or import JSON file if JSONFILE is specified. This option may be combined with -g to organize the output into objects by group, or -G to add group names to each tag. List-type tags with multiple items are output as JSON arrays unless -sep is used. By default XMP structures are flattened into individual tags in the JSON output, but the original structure may be preserved with the -struct option (this also causes all list-type XMP tags to be output as JSON arrays, otherwise single-item lists would be output as simple strings). The -a option is implied when -json is used, but entries with identical JSON names are suppressed in the output. (-G4 may be used to ensure that all tags have unique JSON names.) Adding the -D or -H option changes tag values to JSON objects with "val" and "id" fields, and adding -l adds a "desc" field, and a "num" field if the numerical value is different from the converted "val". The -b option may be added to output binary data, encoded in base64 if necessary (indicated by ASCII "base64:" as the first 7 bytes of the value), and -t may be added to include tag table information (see -t for details). The JSON output is UTF-8 regardless of any -L or -charset option setting, but the UTF-8 validation is disabled if a character set other than UTF-8 is specified. Note that ExifTool quotes JSON values only if they don't look like numbers (regardless of the original storage format or the relevant metadata specification).
If JSONFILE is specified, the file is imported and the tag definitions from the file are used to set tag values on a per-file basis. The special "SourceFile" entry in each JSON object associates the information with a specific target file. An object with a missing SourceFile or a SourceFile of "*" defines default tags for all target files which are combined with any tags specified for the specific SourceFile processed. The imported JSON file must have the same format as the exported JSON files with the exception that options exporting JSON objects instead of simple values are not compatible with the import file format (ie. export with -D, -H, -l, or -T is not compatable, and use -G instead of -g). Additionally, tag names in the input JSON file may be suffixed with a # to disable print conversion.
While you can find a number of posts complaining about how unusable or how unfriendly this file format is, the reality is that XML is an extremely robust choice, and, as we will show shortly, this format is relatively easy to be read by computers, and it can be converted into other formats (like CSV) or imported into a data frame, which is a structured data format used in most data science work.
For all bitmap image exports mentioned below, you can save an image in any resolution and, when applicable, to either 8- or 24-bitcolor depth. The resolution setting is often of importance when submitting a graph for publication; DPlot has you covered. You can save an image in any resolution and to any size that your system is capable of handling. Bitmap exportBitmap export, RLE compressed, 77Kb. Choose from 8- or 24-bit color depth, and optionally choose run-length encoding for 8-bit files. Though RLE-encoding of bitmaps is not often used, it is supported by most popular graphics applications and results in a significantly smaller file for typical DPlot graphs. By way of example, the size of the linked picture is 77Kb with RLE compression, or 431Kb uncompressed, or 1285Kb if you used copy/paste of the same image with a 24- or 32-bit display.
JPEG image exportJPEG image export, 96Kb. The plugin automatically selects "good" quality, which is about the minimum acceptablequality that doesn't produce too many unsightly artifacts. The same picture saved as an RLE bitmap is stored to a 96Kb JPEG file. For a better quality plot in a smaller file, wehighly recommend PNG.
Portable Network Graphics (PNG) image exportPortable Network Graphics (PNG) image export, 28Kb.Unlike JPEG, PNG compression is lossless. And unlike GIF, 24- or 32-bitimages can be saved. Compression of DPlot plots is generally superior to the poorest quality JPEG files and is generally comparable to GIF. By way of comparison, the BMP example mentioned above is saved to a 28Kb PNG file.
Graphic Interchange Format (GIF) image exportGraphic Interchange Format (GIF) image export, 40Kb.This image is saved to a 40Kb GIF file. Like all GIF images, it is limited to 256 colors. For XY plots this is generallynot a limitation, but may result in loss of detail in 3D images with many colors.
Tagged Image File Format (TIFF) image export. This plugin will always use LZW compression. Files saved with this plugin will generally be larger than the corresponding PNG image.
Garmin GPX/Training Center filesThis plugin will read GPX files from most Garmin devices as well as Garmin Training Center TCX files, and produce a plot of latitude vs. longitude, altitude, speed and heartrate vs. elapsed time, altitude, speed and heartrate vs. date/time, and/or altitude, speed and heartrate vs. distance. (Heartrate not available with all files for obvious reasons.) This plugin may work with GPX files from other sources. If you have a GPX file that does not work properly with this plugin, let us know at support@dplot.com and it is possible we'll be able to add support for your file.Latitude vs. Longitude from Garmin Edge 205Elevation vs. Distance from Garmin Edge 205
NASA Shuttle Radar Topography Mission (SRTM) Elevation dataIn February 2000 the Space Shuttle Endeavour flew an 11-day mission to map elevations for nearly all of the Earth'ssurface. Data files in 1x1 blocks are available free of charge from the SRTM web site. For the United States these files consist of elevations at 1 arc-second intervals (roughly every 85 feet); for the remainder of the world the interval is 3 arc-seconds. DPlot will read SRTM files and produce a surface plot:Vicksburg, from SRTM data. (White areas indicate voids in the data.)Pike's Peak, Contour LinesPike's Peak Mount St. HelensMount St. HelensPlease note: 2ff7e9595c
Comentários