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
6 matches
Mail list logo
