Thomas Wood wrote:
[updating way when node moved]
However, I think potlatch does work in this way..
It does in 0.5 but won't in 0.6.
This does make it a bit more difficult in 0.6 for Potlatch's way revert tool
('H') to figure out what the revision dates were, which is what I'm working
on at
On Jan 12, 2009, at 13:45, Nevel Gandish wrote:
And can I be sure that when moving a node caused a new history entry
for the node and the way that both have the exact timestamp or might
they differ by a few seconds?
Just moving a node doesn't create a new history entry for the way, I
think.
2009/1/13 Robert Vollmert rvollmert-li...@gmx.net:
On Jan 12, 2009, at 13:45, Nevel Gandish wrote:
And can I be sure that when moving a node caused a new history entry
for the node and the way that both have the exact timestamp or might
they differ by a few seconds?
Just moving a node
2009/1/13 Nevel Gandish koanti...@googlemail.com:
2009/1/13 Robert Vollmert rvollmert-li...@gmx.net:
On Jan 12, 2009, at 13:45, Nevel Gandish wrote:
And can I be sure that when moving a node caused a new history entry
for the node and the way that both have the exact timestamp or might
they
Hello!
I currently try to reconstruct ways from the history. Retrieving the
ways is no problem. Retrieving nodes from the history isn't too.
But how to put them together? Not every node has a entry for every
entry in a ways history.
Is figuring out by comparing the timestamps the right method or
Hi,
Nevel Gandish wrote:
I currently try to reconstruct ways from the history. Retrieving the
ways is no problem. Retrieving nodes from the history isn't too.
But how to put them together? Not every node has a entry for every
entry in a ways history.
Is figuring out by comparing the
6 matches
Mail list logo
