<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=Content-Type content="text/html; charset=us-ascii">
<meta name=Generator content="Microsoft Word 12 (filtered medium)">
<style>
<!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.E-MailFormatvorlage17
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;}
@page Section1
{size:612.0pt 792.0pt;
margin:70.85pt 70.85pt 2.0cm 70.85pt;}
div.Section1
{page:Section1;}
-->
</style>
<!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=DE-CH link=blue vlink=purple>
<div class=Section1>
<p class=MsoNormal>> Am I the only one that cares about this?<o:p></o:p></p>
<p class=MsoNormal>No, I'm interested in this too.<o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>If I wanted to know the primitive which was valid at
the certain point in time, currently I would have to query the whole history
with<o:p></o:p></p>
<p class=MsoNormal> /api/0.6/<type>/#id/history<o:p></o:p></p>
<p class=MsoNormal>find out the version from the timestamps in the history and
then retrieve the primitive with this version using<o:p></o:p></p>
<p class=MsoNormal> /api/0.6/<type>/#id/#version<o:p></o:p></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>The API could be extended with <o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>
/api/0.6/<type>/#id/versions?from=date&until=date<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'> which would reply all primitive versions in the specified
range.<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Is there any reason why we can query changesets in ceratain
timerange, but not primitive versions?<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>-- Karl <o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm'>
<p class=MsoNormal><b><span lang=DE style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>Von:</span></b><span
lang=DE style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>
dev-bounces@openstreetmap.org [mailto:dev-bounces@openstreetmap.org] <b>Im
Auftrag von </b>Ian Dees<br>
<b>Gesendet:</b> Dienstag, 15. September 2009 20:30<br>
<b>An:</b> Tom Hughes<br>
<b>Cc:</b> dev<br>
<b>Betreff:</b> Re: [OSM-dev] "Deep History" App<o:p></o:p></span></p>
</div>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal style='margin-bottom:12.0pt'><o:p> </o:p></p>
<div>
<p class=MsoNormal>On Tue, Sep 15, 2009 at 1:22 PM, Tom Hughes <<a
href="mailto:tom@compton.nu">tom@compton.nu</a>> wrote:<o:p></o:p></p>
<div>
<p class=MsoNormal style='margin-bottom:12.0pt'>On 15/09/09 19:05, Ian Dees
wrote:<o:p></o:p></p>
<p class=MsoNormal>Ok, next question: is there a way to fetch full history for
more than<br>
one node at a time? I'd prefer to not have to either (a) download and<br>
parse the full planet or (b) make tons of node/history queries to the<br>
main API server.<o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
</div>
<p class=MsoNormal>Planet won't help as it doesn't have history, and if you do
try scraping the history from the api you will find yourself blocked<br>
as soon as I notice...<o:p></o:p></p>
<div>
<p class=MsoNormal><br>
When someone changes a way by moving/deleting/adding nodes there's no way to
see what it looked like beforehand?<br>
<br>
That's disappointing. Am I the only one that cares about this? With permission
I'd be happy to try and write something for the <a
href="http://openstreetmap.org">openstreetmap.org</a> site to make this
feasible and not kill the API frontend servers.<o:p></o:p></p>
</div>
</div>
</div>
</body>
</html>