On Tue, Sep 9, 2008 at 4:43 PM, Florian Lohoff <[EMAIL PROTECTED]> wrote:
> On Tue, Sep 09, 2008 at 07:32:34AM +1000, Brett Henderson wrote: > > As Jochen mentioned, the --write-pgsql-dump task and subsequent import > using > > COPY statements should be faster. I've looked at getting osmosis to > stream > > data directly into the database but unfortunately jdbc drivers don't > expose > > that kind of functionality. > > Shure - the point is that you cant keep the database up to date with > the write-changes as it throws an exception when you simple drop the > bbox column ... > > I've updated the 0.6 tasks to allow dropping of the bbox column. All pgsql write tasks check for the existence of the bbox column and only populate it if it exists. Not going to be of much use until 0.6 is deployed though ... In the meantime can you import using the COPY files and comment the bbox population sql command out of the load script. The osmosis changeset task will continue to update the column when applying changesets but it shouldn't add too much overhead.
_______________________________________________ dev mailing list dev@openstreetmap.org http://lists.openstreetmap.org/listinfo/dev
