[GRASSLIST:6378] Re: speeding up v.in.ogr
Chris Fonnesbeck
fonnesbeck at gmail.com
Fri Apr 8 20:56:10 EDT 2005
The same problem occurs on 6.1cvs under OSX. I had to use my Linux
machine to import them, then move the layers over to OSX manually.
On Apr 8, 2005 1:50 PM, Jonathan Greenberg <jgreenberg at arc.nasa.gov> wrote:
> I had a similar experience with v.out.ogr trying to translate a sizable
> (~700mb) grass vector file created from v.mkgrid to a shapefile. It seems
> to completely stall (cpu usage about 0.5%, memory usage high, 500mb, almost
> zero disk usage). I'm using grass6 under OS X.3.8.
>
> --j
>
>
> On 3/3/05 4:53 AM, "Chris Fonnesbeck" <fonnesbeck at gmail.com> wrote:
>
> > On Thu, 3 Mar 2005 15:33:06 +1300, Hamish <hamish_nospam at yahoo.com> wrote:
> >> Chris:
> >>>>> I have been trying to import a detailed shapefile of the florida
> >>>>> coast (about 24M) into grass6.0b2, using v.in.ogr. Unfortunately,
> >>>>> having started 3 days ago, the import has not yet completed. It is
> >>>>> making progress, as the number of intersections is incrementing,
> >>>>> however this surely should not be taking quite this long. Are there
> >>>>> ways of speeding up the process?
> >>>>>
> >>>>> I am on a 1GHz OS X Powerbook with 1GB RAM.
> >>
> >> Radim:
> >>>> Is it one or few big shapes or many small?
> >>
> >> Chris:
> >>> It is the florida coastline, so it should be one large shape, with
> >>> plenty of small islands scattered alongside.
> >>
> >> Radim:
> >>>> Then the problem is that bounding box of that long boundary
> >>>> intersects all the islands and v.in.ogr will try to break those
> >>>> lines which takes long time. It was already discussed here. Try to
> >>>> modify v.in.ogr so that it writes long boundaries in more shorter
> >>>> parts.
> >>
> >> It was discussed off list, correspondence (including patch) follows.
> >>
> >> I only come up against this myself every couple of months so have just
> >> it be slow, but I've got a detailed coastline vector map with the
> >> occasional offshore island .. it is topologically clean, but same long
> >> time to process issues.
> >>
> >> Hamish
> >>
> >
> > It seems that Lorenzo was at least partly correct; there seems to be
> > an OSX issue. Importing the file in Linux completed in just a couple
> > hours.
> >
> > C.
> >
>
> --
> Jonathan A. Greenberg, PhD
> NRC Research Associate
> NASA Ames Research Center
> MS 242-4
> Moffett Field, CA 94035-1000
> 650-604-5896
> AIM: jgrn307
> MSN: jgrn307 at hotmail.com
>
>
More information about the grass-user
mailing list