[FEATURE] Convert Hitrava export (tcx) to Garmin without Strava-interaction

[mic13esk]

Is your feature request related to a problem? Please describe.
Related to the "problem" of Strava only allowing you to upload 100 activities / day.
If you have lots of activities, then this will be a hassle.

Describe the solution you'd like
The script "corrects" the Hitrava tcx-files into Garmin import-ready files.
This way you wont have to import and export as much.
Normal procedure:

1. Hitrava extraction of the Huawei Activities
2. Import to Strava (max 100 activities / day)
3. Export from Strava (to make it Garmin-ready)
4. Import to Garmin

You can now skip this procedure. Using the script directly on the Hitrava export and afterwards import to Garmin Connect.

Additional context
More details in the readme.txt

HitravaConvert2Garmin.zip

[CTHRU]

Hi, that looks like some great work you did there.

If I understood correctly, you created a script that 'corrects' the output from Hitrava so the TCX files can be imported in Garmin directly.

I don't have the time nor energy currently to integrate your findings / these changes into Hitrava.

However, if you want to create your own repository for your script, I will be glad to reference it in the README of this project.

[mic13esk]

I understand if you dont wanna mess with things that work :)
I created a repository for this that you can link to if you want.
https://github.com/mic13esk/Hitrava2Garmin
Thanks a lot for creating Hitrava!

[CTHRU]

I have added a link to your repo in the Hitrava README file ('TOC' and 'Uploading to Garmin Connect' paragraph).

It is really a nice feature that will help out the Hitrava users that want to upload directly to Garmin Connect.
I will leave your feature request open. If you are OK with it, I might look how I can integrate your findings into Hitrava in the future.

[jiaweixiao]

Good job, I found the same problem that the TCX file cannot be imported to Garmin.
And I wrote a bash shell script to fix activity names and timezone issues as well:
https://github.com/jiaweixiao/Hitrava/blob/garmin/strava_to_garmin.sh

In addition, I think the Cadence value should be x2.
Because the unit of Cadence is strides/minute in Strava TCX but steps/minute in Garmin TCX.

Hitrava/Hitrava.py

Lines 1740 to 1743 in e64bc8b

	# [Verified] Strava / TCX expects strides/minute (Strava displays steps/minute
	# in activity overview). The HiTrack information is in steps/minute. Divide by 2 to have
	# strides/minute in TCX.
	el_run_cadence.text = str(int(data['s-r'] / 2))

[HuaYuXiao]

I understand if you dont wanna mess with things that work :) I created a repository for this that you can link to if you want. https://github.com/mic13esk/Hitrava2Garmin Thanks a lot for creating Hitrava!

其实没有你想得那么复杂

TrainingCenterDatabase

无需特意转换。佳明对于Hitrava解析得到的已经兼容。

运动类型大小写问题

无需特意转换。佳明对于大小写都支持。

时区问题

只要对_get_tz_aware_datetime方法略作修改即可。

def _get_tz_aware_datetime(naive_datetime: dts, time_zone: tz):
    """ All datetimes in the HiActivity are represented as UTC datetimes and are parsed as time zone unaware
    (naive) datetime objects. This method returns the equivalent time zone aware datetime representation using the
    time zone information of the HiTrack activity (if any). If the Hitrack activity has no time zone information,
    UTC (GMT) time zone is assumed.

    :param naive_datetime:
    :type naive_datetime: datetime.datetime
    :param time_zone:
    :type time_zone: datetime.timezone
    :return:
    The (time zone) aware datetime corresponding to the naive datetime in the naive_datetime parameter
    """
    utc_datetime = dts.replace(naive_datetime, tzinfo=tz.utc)

    return utc_datetime

[CTHRU]

Fyi, i don't have the time to look into the extra functionality. Furthermore, there is some new Garmin API Brand Guideline one probably must adhere to when adding this functionality. Kept the link here for future reference.