Hi, Responding to Alan: > I actually would prefer that the tiger:* tags were removed from those > nodes, since they are indeed not useful, though I suppose I could just do > this myself fairly simply.
910 nodes is something we can always to as a one-off later on. For the automatic run, I would like to have it as simple as possible in order to minimize possible errors. So if you don't object I'd just say we go with the "only work on nodes where source is unset or "tiger_import_dch..." rule. Responding to SteveC: > One thing though - what order is this being done in? There might be > arguments for doing geographic areas or some number ranges, or > something, before others. Definitely - I think the order per se is not important but I hate those giant changesets that span across the whole country, so I would try to always make little batches of nodes close to each other, county-sized at maximum, and most counties will require more than one changeset in order for them not to get too large. Sounds ok? Responding to Adam: > Forgive me for being ignorant of your location, but will the 100 days > of edits be done on or topologically near the DB server to minimize > load else where? How will the edits affect normal api access? The work will be done on the dev server which is in the same LAN as the database server. I will prepare the jobs on my machine and then upload them to dev from where they will be fed to the API. Preliminary tests have shown that this should halve the total time - it would have been more like 200 days if I were to do it by accessing the API from here (=Germany). Bye Frederik -- Frederik Ramm ## eMail [email protected] ## N49°00'09" E008°23'33" _______________________________________________ Talk-us mailing list [email protected] http://lists.openstreetmap.org/listinfo/talk-us
