Just installed the add-in to Firefox and viewed an area for which a separate topic was opened. It shows ways not mapped in OSM today but are visible as service/farm tracks in Bing
ID with Strava overlay… works for me. Does that auto renew the link?
JOSM with Strava overlay (link has to be renewed every 10 days due expiration and layer set resaved).
This extension doesn’t involve any links. When your Strava session expires (the heatmap will usually be blurred), you’ll need to sign in to Strava again and navigate to Strava's Global Heatmap. The Strava cookie credentials will be used automatically.
Suppose hitting the ID Editor radiobutton is enough, same as the JOSM practise, but for retaining this refreshing, need to save the JOSM layer until next time.
Need to thest what happens if being in a edit sessions and than wanting to call in the Strava layer. Does that sign in refresh back to an open edit session? Hitting Ctrl+F5 brings up below, then what was edited is retained when selecting ‘stay on page’.
I believe you’re both referring to @ezekielf’s JOSM Strava Heatmap browser extension.
It hasn’t been updated to Manifest V3 yet, so Chrome may have automatically disabled it. You’ll need to manually re-enable it to use it.
Noticed this in (Chrome based) Vivaldi, several of my add-ons got disabled… if I wanted to keep them?
Note: Strava is rolling out new URLs for its global heatmap, causing all extensions to break.
I’m currently working on a major upgrade for my extension, which will include:
S) to show/hide the side panelAlt+SIf all goes well, I plan to release a new version in the first half of April.
Something noticed this morning, the 10 days before expiration not up, tried to refresh the link to JOSM but it just keeps telling me there’s no tiles
They’re regular site does show the heat is on.
It seems that the transfer of parameters via URL (Key-Pair-Id, Policy and Signature) no longer works. However, using a cookie according to the following scheme works:
CloudFront-Key-Pair-Id=KKK; CloudFront-Policy=PPP; CloudFront-Signature=SSS
The new URL for JOSM is:
tms[15]:https://content-a.strava.com/identified/globalheat/all/blue/{zoom}/{x}/{y}.png
Amazing work! Will eagerly wait for the new version!
I came to the forum to ask if it was just me or if it was broken for everyone, and found that you are already working on it 
thanks again for this plugin, it has been crucial for me for OSMapping
Unfortunately could not get your guidance to work. This morning though Firefox told me there was a new add on version for Strava 0.9.3. Updated and sure enough it works in ID Editor in edit mode and selecting the Strava layer. For JOSM still not. Cleared cookies and all, nada. I’ll be patient and if I really have to observe a mountain path that’s not mapped, can always flip to ID to check if it has been frequented by hikers. There’s countless, many though only used by the shepherds that keep the grassland grassland with their flocks.
edit: spelling
Indeed, there’s a new cookie required, _strava_idcf, that doesn’t appear to be configurable (at least not yet) via query parameters. For more details, check out this link.
The good news is that browser extensions can interact with cookies.
Version 0.9.3, which includes support for the new Heatmap URLs, is available for Firefox and will be available for Chrome in a few more days.
For the reasons mentioned above, it will take a bit longer to find a solution for the JOSM extension. You can follow updates from its maintainer here.
If you can’t wait, a proxy workaround might do the trick.
Yes, _strava_idcf is needed now. When I tested it, it still worked without it.
My entry in the JOSM preferences.xml file looks like this:
<map>
<tag key='max-zoom' value='15'/>
<tag key='transparent' value='true'/>
<tag key='minimumTileExpire' value='3600'/>
<tag key='name' value='Strava 2025'/>
<tag key='type' value='tms'/>
<tag key='url' value='https://content-a.strava.com/identified/globalheat/all/red/{zoom}/{x}/{y}.png'/>
<tag key='cookies' value='CloudFront-Key-Pair-Id=KKK; CloudFront-Policy=PPP; CloudFront-Signature=SSS; _strava_idcf=III'/>
<tag key='customHttpHeaders' value='{}'/>
</map>
KKK, PPP, SSS and III are placeholders.
Glad to hear you’ve got the imagery working in JOSM @whb. I had thought there might be no path forward for the JOSM Strava Heatmap extension since I didn’t see an option for adding custom http headers or cookies in the add imagery UI:
Good to know there are more advanced options available in xml behind the scenes. It looks like they should be passable via remote control as well.
Support for custom HTTP headers for TMS layers is now available (from JOSM version 19382).
Custom HTTP headers (customHttpHeaders) can also be modified via the Advanced Preferences, see imagery.entries key.
Hi everyone, could someone please provide instructions could to get at least iD Strava Heatmap working again? (Would love to get it back in JOSM too.)
In the meantime, you could use the proxy mentioned here (e.g. for JOSM and iD):
For iD, just install the latest extension version for Chrome or Firefox. Both are fully compatible with the new Strava Heatmap URLs.
Hi, I tried this extension of yours and it seems to work fine in iD. Thanks!
As for JOSM, not sure if there are any working proxys at the moment?
The freemap.sk proxy works for me.
Am i correct that after the changes you actually have to visit Strava's Global Heatmap
for the extension to display the overlay now?
It seems so to me like the credentials or something expires now everyday or so.
Previously the extension was using heatmap from some other indirect source, but now it is direct?
