On 7/21/2011 12:48 PM, John Smith wrote: > On 21 July 2011 21:41, Andrew Ayre <[email protected]> wrote: >> Yes, changes are applied sequentially, i.e. one set every 24 hours in my >> case as that is how frequently I run Osmosis to perform the change merge. > > So what is it you want to do exactly, the state file saved to the hdd > is the last one successfully applied, if osmosis is interupted it goes > back to that. > > The only alternative I can think of is the one I suggested before > about osmosis dumping the contents of memory to hdd so it could pickup > where it left off from that point in time.
I guess you don't realize that there are two planet files involved when applying changes - the old one and the new one. Fredrick, Brett and Andy immediately understood my issue and gave me the answer I needed regarding how to call Osmosis. That left me with one remaining issue which Brett immediately identified - namely switching from the new planet file to the old one in a recoverable manner, which I currently perform by creating a symbolic link (as I mentioned). This will have to be solved in a script that wraps the update process as my suggestion to perform it as part of the Osmosis call is flawed. Many thanks again to Fredrick, Brett and Andy for their invaluable help! Andy -- Andy PGP Key ID: 0xDC1B5864 _______________________________________________ dev mailing list [email protected] http://lists.openstreetmap.org/listinfo/dev
