Problem with "Import SHP" component

Hi everybody,

When I use "Import SHP" component to get some Polylines from ArcMap to be represented in Rhino, the total number of curves changes and I don't understand why.

So, I have 3242 building footprints represented as Polylines and their attributes in ArcMap, I exported them as a shapefile (with disabled Z and M coordinates), but after running the "Import SHP" component I get 3268 curves... If I try to extrude these curves based on the attribute table (I use TT Toolbox to get the attributes), the heights of course will not correspond to the correct polyline and the whole thing gets messed up.

I also tried "Boundary Surfaces" after the curves from "Import SHP", but the number decreases to 3235. so I'm never getting the curves right.

I tried converting polylines to polygons in ArcMaps and repeat the procedure, but the results was the same.

Does anyone have any idea how to solve this?

Thanks in advance.

Sara

Replies to This Discussion

Permalink Reply by Sara on April 18, 2016 at 4:57pm

Solved! The plugin Meerkat solved my problem - but I still don't understand what happens with Import SHP...

Permalink Reply by Faith Sa on March 15, 2017 at 11:28pm

The IMPORT SHP component simply imports all the curves without recognising that some of them are actually parts of one building. By ignoring this fact, you always get more shapes when you use this component. As you mentioned, Meerkat or Atit components keep the curves in the correct data tree order. If you connect a Param Viewer to the output of Meerkat or Atit component, you will see that some branches have more than one objects on them which as I said is the correct data grouping.

I believe they have abandoned the IMPORT SHP component to its basic level because it is not a general component to be used; and also because plugins like meerkat or atit are doing the job so well.

RSS