On 16/09/09 01:54, Peter Körner wrote:
You would basically have to do something like:
- Find that node version in the nodes table
to get the timestamp (or changeset?), right?
Yes, to get the timestamp. Actually you probably need to get the next
version of the node (if any) as well so you
Okay, so how can we go on now.. I'm not a ruby man and I don't have a
possibility to test all this.
Atm. my fallback-plan is to wait until the Wikimedia-Guys finished setup
of their copy of the osm-db (which will contain the history tables!) so
I can fetch my data directly from the db.
I'm
Hi,
Peter Körner wrote:
Atm. my fallback-plan is to wait until the Wikimedia-Guys finished setup
of their copy of the osm-db (which will contain the history tables!)
It might contain the history tables, but it will not contain history
data unless they have access to a dump with full history
On Wed, Sep 16, 2009 at 7:38 AM, Peter Körner osm-li...@mazdermind.dewrote:
Okay, so how can we go on now.. I'm not a ruby man and I don't have a
possibility to test all this.
Atm. my fallback-plan is to wait until the Wikimedia-Guys finished setup
of their copy of the osm-db (which will
On Wed, Sep 16, 2009 at 8:10 AM, Ian Dees ian.d...@gmail.com wrote:
On Wed, Sep 16, 2009 at 7:38 AM, Peter Körner osm-li...@mazdermind.dewrote:
Okay, so how can we go on now.. I'm not a ruby man and I don't have a
possibility to test all this.
Atm. my fallback-plan is to wait until the
Atm. my fallback-plan is to wait until the Wikimedia-Guys finished
setup of their copy of the osm-db (which will contain the history
tables!)
Okay, maybe i was too fast too loud..
It might contain the history tables, but it will not contain history
data unless they have access to a dump
I'm on dev just for about one hour so I didn't get your mail and my
problem is a little different. I'm working an very similar tool than you.
I'm currently building the backend of an app that shows changesets in a
human readable way. On the long run this will become a revert tool. But
please
On 16/09/09 00:49, Peter Körner wrote:
But because Node #50 was deleted after Changeset #5 there is *no* way to
fetch the ways this node was in. Same would happen if Way #10 would get
deleted - the GET /node/#id/ways call just does not spit out any
historic information. What we need would be
2009/9/16 Peter Körner osm-li...@mazdermind.de:
But because Node #50 was deleted after Changeset #5 there is *no* way to
fetch the ways this node was in. Same would happen if Way #10 would get
deleted - the GET /node/#id/ways call just does not spit out any
historic information. What we need
GET /node/#id/#version/ways
But i don't think this can go into the api without a major change..
There is no problem adding new methods to the API at any point in time.
Col thing!
The problem here is that I doubt it is possible to implement such a
method in an efficient way -
10 matches
Mail list logo
