Sync Magene Cycling Data to Strava/Garmin: Fix GCJ-02 GPS Offset
Why Your Magene/Onelap Route Looks Wrong on Strava
The culprit: incompatible coordinate systems.
- GCJ-02 (Mars Coordinates): Mandated by China's State Bureau of Surveying for all map products distributed within China. Magene switched to GCJ-02 after a firmware update. Note most domestic cycling apps (Onelap, Xingzhe, Blackbird) still use standard WGS-84.
- WGS-84 (World Geodetic System): GPS native coordinates, the global standard used by Google Maps, Strava, and Garmin Connect.
GCJ-02 applies a non-linear offset of 100-700m on top of WGS-84. When your perfectly circular Magene-recorded ride hits Strava, the route warps into a distorted polygon. Segment matching and pace calculations are thrown off too.
Which Devices Produce GCJ-02 Data?
The FIT file standard defaults to WGS-84, and most domestic bike computers and cycling apps generate WGS-84 FIT files. Currently, only Magene changed its FIT coordinate system from WGS-84 to GCJ-02 after a firmware update, causing issues in these scenarios:
- Magene bike computers (C406, C506, etc.) — post-firmware-update FIT files use GCJ-02
- Magene smart trainers (T200, T300) used with the Magene app
Onelap, Blackbird, Xingzhe, iGPSport, and other domestic platforms still output standard WGS-84 FIT files and typically don't need correction. If unsure, sync one activity to Strava and check whether the track aligns with the actual road.
3 Steps to Offset-Free Sync with GarSync
Step 1: Connect Source and Target
In GarSync, add your Magene/Onelap/Blackbird/Xingzhe account as the source, and Strava or Garmin as the target.
Step 2: Enable FIT Auto-Repair
When creating the sync task, enable FIT Data Repair in the configuration options. GarSync auto-detects the coordinate system and batch-converts GCJ-02 to WGS-84 before uploading. You can also set per-account whitelists — enable correction only for Chinese apps to avoid double-processing already-correct WGS-84 data.
Step 3: Verify
After syncing, open the activity on Strava and check the map. If the track now perfectly follows your actual route with no offset, the correction worked. Compare the FIT files before and after — GPS lat/lon values shift by tens to hundreds of meters.
Beyond Coordinates: What Else GarSync's FIT Repair Fixes
- Device ID rewriting: Rewrite Chinese bike computer/app device IDs as Garmin for better platform compatibility
- Heart rate/power zone completion: Auto-calculate and fill missing zone distributions
- Cadence field completion: Some power meters encode cadence data in the power telemetry stream — GarSync extracts and fills it into the FIT file
- Timestamp correction: Fix timezone offset errors from some domestic devices
- Auto-lap generation: Add missing lap markers by kilometer or mile
FAQ
Q: How do I know if my data is GCJ-02 or WGS-84?
A: Quick rule: if you recorded outdoors in China using a domestic app or bike computer, it's 99% GCJ-02. If your route on Strava shifts off the road into adjacent buildings or rivers, it's GCJ-02. GarSync doesn't auto-detect — you need to enable "FIT Data Repair" in the sync task settings and whitelist your Chinese-platform accounts.
Q: Does coordinate correction affect other data fields (pace, power, HR)?
A: No. Only GPS lat/lon fields (position_lat / position_long) are modified. Heart rate, power, cadence, speed, and all other data fields remain untouched. The FIT file structure is preserved.
Q: Can SyncMyTracks or RunGap fix this?
A: No. Both are developed by teams outside China and have no awareness of GCJ-02. They pass through raw coordinates untouched, so your tracks remain offset on Strava. This is why many Chinese cyclists notice "my Garmin-recorded route is accurate, but the same route from Magene is warped on Strava."
Q: Does FIT repair cost extra?
A: No. FIT data repair including coordinate correction is built into GarSync's sync engine at no extra charge. Sync pricing: free trial + pay-as-you-go (bulk migrations capped), or subscribe at $4.99/month for unlimited free sync.