Overpass API developpement

[mmd <>]

Am 27.11.2015 um 20:36 schrieb michael spreng:
> On 27/11/15 12:40, mmd wrote:
>>
>> It would be good if Michael could put the exact steps somewhere on a
>> Wiki page.
> Here they are:
> 
> https://wiki.openstreetmap.org/wiki/User:Datendelphin/overpasss-attic
> 

Great, thanks! I can easily reproduce the issue here on my own branch as
well.

~/osm-3s-patch-version/build/bin$ ./osm3s_query --db-dir=/mnt/btrfs/dbs
encoding remark: Please enter your query and terminate it with CTRL+D.
[date:"2008-01-01T00:00:00Z"][out:xml];way[highway];out;
<?xml version="1.0" encoding="UTF-8"?>
<osm version="0.6" generator="Overpass API">
<note>The data included in this document is from www.openstreetmap.org.
The data is made available under ODbL.</note>
<meta osm_base=""/>

runtime error: Way 22701281 cannot be expanded at timestamp
2008-05-03T21:42:14Z: Bad geometry for way 22701281
runtime error: Way 22701281 cannot be expanded at timestamp
2008-05-03T19:54:10Z: Bad geometry for way 22701281
runtime error: Way 22701281 cannot be expanded at timestamp
2008-05-03T19:49:04Z: Bad geometry for way 22701281
runtime error: Way 22701281 cannot be expanded at timestamp
2008-05-03T19:40:48Z: Bad geometry for way 22701281
runtime error: Way 22701281 cannot be expanded at timestamp
2008-04-13T11:06:40Z: Bad geometry for way 22701281
runtime error: Way 22701281 cannot be expanded at timestamp
2008-03-27T13:46:58Z: Bad geometry for way 22701281
runtime error: Way 22701281 cannot be expanded at timestamp
2008-06-17T13:21:43Z: Bad geometry for way 22701281
runtime error: Way 22701281 cannot be expanded at timestamp
2008-06-14T16:10:02Z: Bad geometry for way 22701281
runtime error: Way 22701281 cannot be expanded at timestamp
2008-06-13T18:54:01Z: Bad geometry for way 22701281

</osm>


In the log file there's also a number of interesting messages:

Node 243509609 used in way 22701281 not found.
Node 243509717 used in way 22701281 not found.
Node 243509722 used in way 22701281 not found.
Node 243509723 used in way 22701281 not found.
Node 243509724 used in way 22701281 not found.
Node 243509776 used in way 22701281 not found.
Node 243509780 used in way 22701281 not found.
Node 243509609 used in way 22701281 not found.
Node 243509717 used in way 22701281 not found.
Node 243509722 used in way 22701281 not found.
[...]

They seem to be bogus as for the first node 243509609. This node was
created in Jan 2008 and deleted in Feb 2012. For the way 22701281 in
question, it appears last in version 14 from June 2008. At that time,
that node was still alive.

<create>
        <node id="243509609" lat="47.2111169" lon="8.4443596" version="1"
timestamp="2008-01-26T17:25:48Z" changeset="697293" uid="17975"
user="woody1">
                <tag k="created_by" v="JOSM"/>
        </node>
</create>
<delete>
        <node id="243509609" version="2" timestamp="2012-02-24T22:28:21Z"
changeset="10783325" uid="97547" user="datendelphin"/>
</delete>


To me it looks like the deleted node in Feb 2012 somehow confuses the
update process to think the node is already gone - even for an earlier
point in time.

I cannot really imagine that there's a missing time comparison
somewhere. On the other hand, with minutely diffs being processed in the
'normal' setup, this case may be quite unlikely and may not have turned
up so far.



..