The map now shows weather for the time matching the marker position and/or zoomed portion. This is useful for out and back or lapped routes.
Marker near start:
Marker near end (the wind has picked up a bit):
The map now shows weather for the time matching the marker position and/or zoomed portion. This is useful for out and back or lapped routes.
Marker near start:
Marker near end (the wind has picked up a bit):
In theory weather indicators should no longer overlap.
looks awesome
Does the weather data become a custom stream? i.e. could we then for a highlighted section (up a strava segment say) and then we could create a calculated field for average yaw or % tailwind etc
Not yet but I am going to be doing a bunch of those soon. Been getting the basics right, selecting a good set of points from a GPS route to get weather for etcâŚ
I will also add some interval fields derived from these (e.g. average yaw angle).
Also going to do wind rose and yaw angle rose plots.
Really like looking at the wind and temp info on the map. Thanks.
One question, presently my map is displaying the temp in Celsius (good) and the wind speed in MPH (not as good). Iâd prefer KPH for the wind speed if possible ( which I see it is from your screen shot above). What am I missing?
I checked my settings and distance and temp are set to Kilometers and Celsius. I checked units and it is set to pounds, which is good for body weight. I did flip it to kilograms to see if it would make a difference, it didnât.
It uses the same units as the weather forecast dialog. I have added drop downs for these to the map options panel:
Thanks works great!
This is a really nice update to the map.
I am amused by the weather being shown on my Zwift ride maps!
The map will display but it should not have any weather on it. If it does please msg me a link to the activity.
The weather data is now generated for all supporters as activities come in. To get weather on old activities you need to do Actions â Re-analyse or open the map. Historical weather is available back to approximately 2021.
I have added some weather traces for the timeline chart. Click âChartsâ and look for âF Tempâ, âFeels likeâ, âWindâ, âGustsâ and âWind directionâ.
I will be adding more shortly and also summary stats on activity and intervals.
âWeather Analysisâ is now a premium (supporters only) feature.
Another trace that could be useful might be wind-direction relative to direction of travel? So a straight headwind would be 0 (or 180, canât quite figure which), a crosswind 90 or 270 etc. Could be made as a custom stream I guess, but having it as standard would be nice.
I have been working on that one. Was wondering about the name and for now have âApparent Windâ. I am planning to use this scheme for the angle unless someone has better ideas?
Headwind:
Tailwind:
So negative is left, positive is right. The absolute value is 0 to 90 (headwind) 91 to 180 (tailwind).
But maybe better to just do normal compass thing so 0 to 359 degrees with tailwind from 90 to 270.
The ConnectIQ app WindField includes a Wind Factor field in fit files which takes into account wind direction and strength. I donât know how itâs calculated, but it might be worth a look.
Personally, I donât like plotting angles versus time in this case because of the discontinuities that occur when the angle oscillates around zero. In relation to my CIQ data field, Ventus, which provides live wind data, I decided to use a wind components representation (longitudinal and lateral). I use this approach in in Garmin Connect charts and in the custom chart I provided for intervals (this includes components, absolute magnitud and accumulated wind for each direction).
Itâs an option you may consider.
Something we use in air traffic is the term Headwind Effect (HWE); itâs the headwind component of the wind based on the wind direction and direction of travel. A lot more simple in air traffic on final approach as aircraft donât tend to weave about as much (usually!!).
Not sure if this would be of interest/use but I can dig out some old equations if so.
Isnât HWE the longitudinal component I referred to in my previous post?