<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">On 22/10/2015 11:18, Colin Smale wrote:<br>
</div>
<blockquote cite="mid:3a99151e396385d85545b41550c610c1@xs4all.nl"
type="cite">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<p> </p>
<div> </div>
<p>On 2015-10-22 11:27, Andy Townsend wrote:</p>
<blockquote type="cite" style="padding: 0 0.4em; border-left:
#1010ff 2px solid; margin: 0">
<div class="pre" style="margin: 0; padding: 0; font-family:
monospace"><span style="white-space: nowrap;"></span><br>
I'd agree with that. I can think of more than a few examples
of "the road/path used to go here, but now it doesn't", and
even if the imagery gets updated, underlying GPS traces won't.</div>
<div class="pre" style="margin: 0; padding: 0; font-family:
monospace"> </div>
</blockquote>
<div class="pre" style="margin: 0; padding: 0; font-family:
monospace">Has anyone thought of a way of limiting returned GPS
traces to a certain date range? So you can look at traces since
or before a certain change in the road layout?</div>
<br>
</blockquote>
<br>
It's tricky, since the traces involved aren't just the OSM ones -
they also include Strava and potentially others.<br>
<br>
With regard to OSM ones, in JOSM you can get information on some
traces trace-by-trace, but it's a bit clumsy to use regularly.
Traces in P2 and iD's "GPS traces tiles" such as
<a class="moz-txt-link-freetext" href="http://gps-b.tile.openstreetmap.org/lines/15/16256/10660.png">http://gps-b.tile.openstreetmap.org/lines/15/16256/10660.png</a> via
<a class="moz-txt-link-freetext" href="https://github.com/ericfischer/gpx-updater">https://github.com/ericfischer/gpx-updater</a> are one-way I believe -
GPS traces go in, but never come out.<br>
<br>
Cheers,<br>
<br>
Andy<br>
<br>
</body>
</html>