That is good to hear! Are you a beta tester or are you still using the latest version on the App Store?I was getting black areas in about 25% of my hikes and walks, but haven't seen it in about a month so appears to be fixed!
I will add the battery level request to my list.Would it be possible to add sensor battery levels to the end of activity summary screen? Ideally listed under the 'done' button. I know you can set alerts for them, but I'm not sure I really want to be alerted about it in the middle of a run, and the end of a workout is the best time to stick the things on charge.
If it is doable then colour coded would be even nicer, say red for <10%, and yellow for <20%.
I think this is has already been mentioned, but I would like to always use a manual start rather than the countdown. An option for that would be lovely.
Finally, I've switch my HRM to be paired inside WorkOutdoors, rather than WatchOS and I've really appreciated having the extra certainty that it's actually connected, so thank you for that and I recommend doing it that way to everyone else (2 connection device limit aside).
I'm a beta tester.That is good to hear! Are you a beta tester or are you still using the latest version on the App Store?
That's good. I did make a little tweak in the code that may have helped with the black areas, so it's good to know that it may have worked.I'm a beta tester.
Since the power and other new metrics are available in the OS 9 betas, is there a WOD beta version available now with access to those metrics?Yes, WOD should be able to access all the new running metrics. I am hoping to release a version with them just after watchOS 9 is released.
I don't know about Thunderforest but Mapbox used to take weeks or months when I last looked into it a few years ago.Question about maps: does anyone know how often do Mapbox/Thunderforest update their OpenStreetMap data? In other words, how soon would any changes made in OSM appear on the maps in WOD?
I don't know about Thunderforest but Mapbox used to take weeks or months when I last looked into it a few years ago.
Remember that WOD caches all maps so you will not see updated maps unless you clear the cache.
The current beta is for a bug fix version, which I plan to release soon. After that I will release a beta with the new watchOS 9 running dynamics.Since the power and other new metrics are available in the OS 9 betas, is there a WOD beta version available now with access to those metrics?
That would be too expensive. I have to pay for every tile downloaded so offering the ability to update every tile that someone had in their cache would cost me a lot of money. At least if someone clears the cache then they will only download the maps they really want afterwards.Maybe it would be a good idea to offer an option to refresh the cache additionally to clearing it?
The latest version of the app includes all the GPX points in the exported file, whereas it previously only included most of them. This confuses Basecamp and some other apps which don't smooth the data. The next version of the app will go back to the old approach with the option of including all points if you want. If you need it now then please email me at info@workoutdoors.net and I will add you to the beta program.Hello, when I export the GPX file and open with Garmin Basecamp from PC I get strange things. For example the real statistics of the mtb route are 40km and 700m ascent, WOD is pretty good calculating 39.5km and 675m, but in Basecamp I get 46km and 750m ascent... any idea why? I thought that Basecamp shoud give me exact the same results as WOD, being the file generated from WOD...
That would be too expensive. I have to pay for every tile downloaded so offering the ability to update every tile that someone had in their cache would cost me a lot of money. At least if someone clears the cache then they will only download the maps they really want afterwards.
It's the main downside of the app's business model of a one-off payment instead of a subscription: I can't make it easy for people to download large numbers of map tiles. But I figure that most people can live with that if it means they don't have to pay a subscription.
That would be too expensive. I have to pay for every tile downloaded so offering the ability to update every tile that someone had in their cache would cost me a lot of money. At least if someone clears the cache then they will only download the maps they really want afterwards.
It's the main downside of the app's business model of a one-off payment instead of a subscription: I can't make it easy for people to download large numbers of map tiles. But I figure that most people can live with that if it means they don't have to pay a subscription.
It's great to hear that people would pay for a subscription, but my worry is that it would put people off buying the app in the first place. I think subscriptions are becoming more acceptable but they still put me off buying an app.
Never say never but I have absolutely no plans to switch to the subscription model at the moment.
If I ever add a subscription it will only be for features that I can't add without it because they have ongoing costs. For example larger map downloads, the ability to create routes, weather data etc. I won't make any currently included features require a subscription. But, as I say, I don't have any plans for a subscription at the moment.It really depends on the pricing model and the implementation from my perspective.
What I really hate are aggressive models that really nag the user to buy an overpriced subscription that offers not much value.
So a model where one pays a fair price for the app, like WOD does, and a subscription with a reasonable price per month/year for a set of premium features that are no necessity to run the app in the first place but still offer a good value, would be something.
Also, what I really dislike is moving features that were previously free to the subscription step by step. My typical reaction is than to abandon the app.
thanks for adding me. now the export to basecamp is doing better. I'll keep you postedThe latest version of the app includes all the GPX points in the exported file, whereas it previously only included most of them. This confuses Basecamp and some other apps which don't smooth the data. The next version of the app will go back to the old approach with the option of including all points if you want. If you need it now then please email me at info@workoutdoors.net and I will add you to the beta program.
This weekend I ran over a bridge in an area where no one ever runs and noticed Strava had a big dip in the elevation. That was when I noticed for the first time that Strava isn't using the elevation that WOD stores in the FIT file. I came across the device mapping documentation on Strava's site which made me curious what the manufacturer and product name are in the WOD produced FIT files. Turns out the manufacturer is "development" and the product is "WorkOutDoors". It seems like if something besides "development" could be placed in the manufacturer field, maybe WOD could be registered with Strava. Sure this is more or less something for physical devices but it seems like Strava could be reasonable and make an exception. Now I'm curious what the manufacturer/product is in a FIT file produced by the Apple Workout app.Perhaps you can request it? https://developers.strava.com/docs/uploads/#device-mapping
Apple watches are not one the Strava Baro device list.This weekend I ran over a bridge in an area where no one ever runs and noticed Strava had a big dip in the elevation. That was when I noticed for the first time that Strava isn't using the elevation that WOD stores in the FIT file. I came across the device mapping documentation on Strava's site which made me curious what the manufacturer and product name are in the WOD produced FIT files. Turns out the manufacturer is "development" and the product is "WorkOutDoors". It seems like if something besides "development" could be placed in the manufacturer field, maybe WOD could be registered with Strava. Sure this is more or less something for physical devices but it seems like Strava could be reasonable and make an exception. Now I'm curious what the manufacturer/product is in a FIT file produced by the Apple Workout app.
Edit: just checked a FIT file from the watchOS 9 Workout app and it's "development"/"Watch6,4" for my S6.
I think he's on to a solution to have Strava accept the device name (Apple Watch Sx) in the Strava activity, not the altitude data itself.Apple watches are not one the Strava Baro device list.
“At the moment, Apple Watch devices are not considered to be trusted devices and will not show the data on its barometric altimeter.”
I have asked Strava support about it some days ago
I have noticed that the WOD Thunderforest maps update in just a few days after making OSM changes. Mapbox can take 1-2 weeks.Question about maps: does anyone know how often do Mapbox/Thunderforest update their OpenStreetMap data? In other words, how soon would any changes made in OSM appear on the maps in WOD?