The `v=...' parameter in Google satellite-imagery URLs is presumably to peg a version of the tile-database; we're currently using "v=53", and John's fix in osm-gps-map was to raise that number to 89 (which appears to work, as far as I can tell). What we're seeing with v=53 is presumably just a result of Google `aging out' their older imagery-databases.
It looks like the current number (which is in use on <http://maps.google.com/>) is 92, so I guess we might as well use that.
Checking osm-gps-map, which should face the same issues as we do with tile-providers, I see that John recently added a google-fix: https:/ /github. com/nzjrs/ osm-gps- map/commit/ d1e6825c5be58eb 9ae96abe8e6b6d6 e4e5ecefbf
The `v=...' parameter in Google satellite-imagery URLs is presumably to peg a version of the tile-database; we're currently using "v=53", and John's fix in osm-gps-map was to raise that number to 89 (which appears to work, as far as I can tell). What we're seeing with v=53 is presumably just a result of Google `aging out' their older imagery-databases.
It looks like the current number (which is in use on <http:// maps.google. com/>) is 92, so I guess we might as well use that.