<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On Sat, May 4, 2013 at 3:31 AM, Michal Migurski <span dir="ltr"><<a href="mailto:mike@teczno.com" target="_blank">mike@teczno.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div><div>On May 3, 2013, at 12:22 PM, Eugene Alvin Villar wrote:<br>
<br>
> On Sat, May 4, 2013 at 2:27 AM, Michal Migurski <<a href="mailto:mike@teczno.com" target="_blank">mike@teczno.com</a>> wrote:<br>
>> Would it be silly to suggest that changesets get their own geometries in PostGIS and an associated spatial index, consisting of every way and node deleted, moved, etc.?<br>
><br>
> Isn't this similar to what Paweł's New History Tab is doing behind the scenes?<br>
<br>
</div></div>Maybe—where would I look to find out?<br>
<br>
<a href="https://github.com/ppawel/openstreetmap-website" target="_blank">https://github.com/ppawel/openstreetmap-website</a> is obviously the starting point, but where then?<br></blockquote></div><br></div><div class="gmail_extra">
The source code is definitely the place where one should look. I think this is the more direct location:<br><br><a href="https://github.com/ppawel/openstreetmap-website/tree/owl-history-tab">https://github.com/ppawel/openstreetmap-website/tree/owl-history-tab</a><br>
<br>Anyway, basing on Paweł's numerous previous emails on the subject since January, I gather that his code processes each changeset and creates vector tiles which record the geometry changes. Vector tiles are obviously spatially indexable.<br>
<br>
</div></div>