[GRASS-dev] Re: [GRASS GIS] #426: v.in.ogr: split long boundaries

GRASS GIS trac at osgeo.org
Fri Jan 30 17:02:16 EST 2009


#426: v.in.ogr: split long boundaries
--------------------------+-------------------------------------------------
  Reporter:  neteler      |       Owner:  grass-dev at lists.osgeo.org
      Type:  enhancement  |      Status:  new                      
  Priority:  major        |   Milestone:  6.5.0                    
 Component:  Vector       |     Version:  unspecified              
Resolution:               |    Keywords:                           
  Platform:  All          |         Cpu:  All                      
--------------------------+-------------------------------------------------
Comment (by cgsbob):

 Replying to [comment:3 mmetz]:
 > Replying to [comment:2 cgsbob]:
 > > In Ticket #397 I reported that some large holes are being filled after
 going through v.clean.  This seems to happen when this large hole is
 surrounded by a large and complex polygon.  Do you think that your
 v.in.ogr might solve my problem?
 >
 > "My" v.in.ogr is not any different from "your" v.in.ogr in that respect.
 You can use "v.in.ogr min_area=2800", but I don't think it's a good idea
 to export your vector and then re-import it again, you may well loose some
 information on the way.

 I agree, but as you can see in ticket #397, I have not been able to clean
 up my vector.  I was just saying that if I did re-import my vector into
 v.in.ogr w/ boundary splitting and then used v.clean tool=rmarea, I might
 get something better then a filled large hole.

-- 
Ticket URL: <http://trac.osgeo.org/grass/ticket/426#comment:4>
GRASS GIS <http://grass.osgeo.org>


More information about the grass-dev mailing list