[GRASSLIST:5974] Re: speeding up v.in.ogr

GRASS GRASS user
,
1

I am on a 1GHz OS X Powerbook with 1GB RAM.

Is it one or few big shapes or many small?

It is the florida coastline, so it should be one large shape, with
plenty of small islands scattered alongside.

The problem is in that shape in OS X version. Some shape files are not
good in grass in OS X.

Open it before with another sw: QGIS, Thuban or Jump and see about
problems (in areas, lines, etc.)

In grass 6
Try:
- v.in.ogr with "Do not clean polygons" selected
then
- v.clean

This is not correct. I have already written that here.
For areas v.in.ogr -c + v.clean != v.in.ogr.

What, then, is the best course of action for importing this shapefile?
Should it be converted to another format first?

2

Chris Fonnesbeck wrote:

I am on a 1GHz OS X Powerbook with 1GB RAM.

Is it one or few big shapes or many small?

It is the florida coastline, so it should be one large shape, with
plenty of small islands scattered alongside.

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.

Radim