<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 TRANSITIONAL//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; CHARSET=UTF-8">
<META NAME="GENERATOR" CONTENT="GtkHTML/3.30.3">
</HEAD>
<BODY>
Good morning Everyone...<BR>
<BR>
Thanks for the tips on the mid-line handles and how to merge points in JOSM. Very handy. <BR>
<BR>
I spent some time editing four CanVec files I imported this weekend and ran into a problem that I hadn't seen before. I must have done something procedurally that I should stay away from as I eventually just wound up abandoning about an hour's work. No biggie. But maybe someone can clue me in on what may have happened and how I might avoid it in the future.<BR>
<BR>
Last night, I did a merge of CanVec and existing OSM data, trying to make sure first to remove from the CanVec data layer anything that was already in the OSM data. The upload went fine with some warnings... which I was going to address today with some edits. Anyway, this morning, after doing some editing, checking the Validator and so on... the upload of the edits failed with the error that I was trying to upload a node (and only one node was listed) that was older than a node currently existing. I was trying to replace a Version 2 node of mine with a Version 1 node. JOSM asked if I wanted to synchronize and I said YES. Tried to upload again and it failed with more errors. Something was definitely wrong with my edit and so to avoid corrupting the existing database, I bailed at that point.<BR>
<BR>
Here's where I think I may have messed up. While editing, one of the warnings was that there were duplicate nodes. Apparently there was a short section of road that I had originally missed removing from the CanVec data before merging. While sorting out which way to remove, I got a message that said that the selected way extended into an area that had not been downloaded and asked whether I wanted to download additional data. YES. Then I made sure to select only the duplicate from the CanVec data and deleted that, leaving the old OSM road intact. I would have thought that was the way to go. I merged some corner nodes and so forth... but nothing else was really out of the usual edit routine. <BR>
<BR>
So did I screw up by downloading additional data during an edit? Is that to be avoided? The database thing is rather mysterious and magical anyway so I don't have a real grasp as to what is actually going on behind the scenes. Or is there something else that I did that could trigger this "writing older-over-newer" kind of error?<BR>
<BR>
Thanks,<BR>
<BR>
Sam<BR>
Kamloops, BC <BR>
<BR>
</BODY>
</HTML>