fahmi14 / geoda

Automatically exported from code.google.com/p/geoda
GNU General Public License v3.0
0 stars 0 forks source link

Export Boundary bug #66

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
What steps will reproduce the problem?
1. Shape->To Boundary,  open NAT.shp, select 1a, save to boundary file bnd.txt
2. Shape->Polygons from Boundary, open bnd.txt, save to bnd2shp.shp
3. Open  bnd2shp.shp

The newly created bnd2shp.shp can't handle islands.

Islands are treated as one single POLYGON. They should be treated as 
MULTI-POLYGN. 

Original issue reported on code.google.com by lixun...@gmail.com on 22 Jan 2014 at 11:49

GoogleCodeExporter commented 8 years ago
Technically a Shapefile polygon should be able to handle multiple parts and any 
number of nested polygons.  See page 7 of: 
http://www.google.com/url?sa=t&rct=j&q=&esrc=s&source=web&cd=1&cad=rja&ved=0CCkQ
FjAA&url=http%3A%2F%2Fwww.esri.com%2Flibrary%2Fwhitepapers%2Fpdfs%2Fshapefile.pd
f&ei=t1vgUu_uPKrlyQHRs4HYBg&usg=AFQjCNHp9v_VCrbagYu23yPhKgqEO9KX8Q&sig2=Vt5He72A
7svcYJ191GZcCw&bvm=bv.59568121,d.aWc  (Google Shapefile Specification, should 
be first PDF that comes up).

Original comment by mmcc...@gmail.com on 23 Jan 2014 at 12:01

GoogleCodeExporter commented 8 years ago
Yes, I think so too. But current code logic when you "export from shp to 
boundary" & "save boundary to shp" can't handle that.

Original comment by lixun...@gmail.com on 23 Jan 2014 at 12:03

GoogleCodeExporter commented 8 years ago

Original comment by mmcc...@gmail.com on 10 Feb 2014 at 11:56