On Sun, Jan 30, 2011 at 12:16 PM, Samuel Longiaru <[email protected]> wrote: > G'morning Everyone, > > Thanks to all who responded to my request for advice and guidance. As a > result I received some excellent instruction as how how to import CanVec > data. I've since been able to upload two adjacent files to the database... > both from a remote area SW of Kamloops. One had no existing OSM data at all > and the other had only a small section of an unpaved road. The import has > led to several questions regarding stitching data at boundaries, but I > should probably best pursue those problems off-list.
Or here! If we "import," we should "maintain" as well. After all we're not just dumping and running, or "throwing data over the wall." ;-) So what are some good questions and answers regarding responsible imports? Stitching the road network seems like a high-priority. Is stitching wooded areas important, or is it better to keep manageable relation sizes with arbitrary rectilinear breaks? etc. Regarding your specific import Sam, could you link to it for us? I see the wooded areas on the border, but that sounds a little further than away from Kamloops than you. Share! ;-) Were these full size NTS tiles or sub tiles? Are they of a "manageable" size for stitching. How long did it take? Should we make a group effort of stitching before moving on the the next import? Many open questions. :-) Best regards, Richard _______________________________________________ Talk-ca mailing list [email protected] http://lists.openstreetmap.org/listinfo/talk-ca
