In progress

:bulb:

Ability to import Workout Routes directly to the Arc timeline

The Apple Watch is capable of recording location data while recording workouts (eg running, walking, etc). This location data is available to Arc when it imports workouts. However currently Arc does not attempt to import the location data directly into the timeline.

So this planned feature (already in development) is for doing just that: when a workout is imported which includes route data, the route data will be inserted directly into the Arc timeline (if it is possible to do so without creating a nonsense timeline).

30 votes

Tagged as New feature

Created 21 July 2019 by Matt Greenfield

  • Sign in to comment and vote. Sign in by email
  • 21 July 2019 Matt Greenfield created this task

  • avatar

    Really looking forward to that!

    02 September 2019
  • avatar

    I love this idea.

    12 January 2020
  • avatar

    Just make sure that imports from the watch don’t mess up the phone recordings. A clear cut (from time stamp XX:XX to time YY:YY use watch data) might help to keep control.

    06 March 2020
  • avatar

    Any news on that one? I would be really great to be able to leave the phone at home for outside activities and still have them added to the timeline. 🙏

    27 July 2020
  • avatar

    Any external track import is welcome for ARC. But I would first like a simple import as possible. Just give me a GPX import and selection of begin and end location. Arc should overwrite its recording with GPX data between those locations. Is there anything easier as UI goes?

    27 July 2020
  • avatar

    Sascha, I just restarted working on this one a few days ago. I’m moving the code to the open source Arc Mini project on Github (https://github.com/sobri909/ArcMini), as part of the longer term goal of open sourcing all of Arc/LocoKit’s import and export functionality.

    As long as I don’t have to sidetrack to anything more urgent, I should be able to finish up the Workout Route importing for the next Arc update. Which I’m hoping to have ready next week!

    28 July 2020
  • avatar

    Hi Jani!

    Importing GPX and having that overwrite Arc recorded data would be a bad idea. The GPX format only supports a tiny fraction of the information that Arc records, so you’d be losing accelerometer data, step counts and cadence, and … well, a whole lot of important stuff.

    The only kind of import that I’d allow to completely overwrite existing data would be Arc JSON imports, because those include the full spectrum of information that Arc records, so there wouldn’t be any inherent information loss.

    As far as easy UI, I’m not sure what you mean by that?

    28 July 2020
  • avatar

    Marvellous! 🤩

    29 July 2020
  • avatar

    GPX import is meant to fix segments where Arc has a data gap or junk useless track that goes straight from one point to another (actually jumping over there). UI for this should be fairly simple. Import GPX to a staging store and mark on the timeline from which timestamp to which timestamp there is GPX data (shading or some red vertical line). Then let me chose the start and end locations on the timeline (pop up menu) where Arc should replace its location data with GPX. If you think there is other useful data recorded at that time you may leave it as is. Such edited tracks could be drawn with a dashed line indicating manual intervention. I’m thinking about exporting existing Arc track GPX to a GPX editor, fixing travel route where important and reimporting it back to Arc. This could be a temporary tool until (if ever) you decide to add a track editor. I know this solution is not ideal, but at least I could fix my movement in Arc while I still remember.

    30 July 2020
  • avatar

    I’m thinking about exporting existing Arc track GPX to a GPX editor, fixing travel route where important and reimporting it back to Arc.

    This is something that will never be supported, for the above stated reason. (The GPX format lacks the majority of Arc’s recorded details, so replacing Arc samples with GPX data would result in data loss).

    For replacing existing data with a hand edited data file, then the best option would be Arc JSON. Importing Arc JSON will eventually be supported. That work will most likely be done in the open source Arc Mini project, then shipped in both Arc Mini and Arc App.

    However there’s two different things going on which I think are getting conflated.

    1) There’s situations where there’s a data gap, ie complete lack of data for a period of time, and Arc is drawing a line from one point to another to bridge the gap. Inserting samples into that gap wouldn’t be replacing data, it would be filling in a gap. That could be done with imported GPX data without resulting in data loss.

    2) If you want to make changes to data that Arc has recorded, then that should ideally be done inside Arc’s UI, and not with external tools. So far there are very few editors that support Arc/LocoKit JSON, so Arc is the best option for that at this stage. In those cases I recommend using the Indvidiual Segments view in Arc, and also the Segment Splitting feature, to make changes to the recorded data.

    31 July 2020
  • avatar

    Any update on ARC for Apple watch?

    Tuesday
  • avatar

    Hi Steve! There won’t be an Apple Watch app any time soon. watchOS doesn’t allow for apps like Arc to exist on it yet.

    However this particular feature of being able to import workout routes that were recorded on Apple Watch (or any other wearable that imports into the Health app) is coming soon! It will be the main feature of the next major release, which I’m working on finishing up now.

    Wednesday