Spot Coordinates Tagged Info

[jacob.small]

I see three issues here, but am not quite sure what you’re after, so I’ll lay them out with the caveat that I may not be understanding what you’re after…

1. If you’re looking for the point which the spot elevation was associated to, then you’re asking the wrong items for the data you are after. The python script in that thread retrieves the element which the spot coordinate is associated to, not the location of the spot coordinate’s host. By pulling the element and then asking for it’s location, you’re pulling the 0,0,0 or initial placement point of your adaptive component (not really sure which but neither is useful here), and the reference points are returning a null value as they don’t have a location (crazy I know). If you use an Element.Location node immediately after the All View Dependent Family Instances Of Category node (or right after the Flatten node), and you should get XY values that make sense. Z values though…

2. The Z values are all over the place. Create a default 3d view and look at the model which you posted. A lot of these items are all over the place elevation wise. You’ve clearly got some stuff outside of the level which has been tagged. This may have been intentional, but I suggest narrowing the view range before you tag stuff as that would have helped ensure some consistency here. Better yet, isolating the 3d datum families before you tag them. Even better still would be to tag the points programatically (as you noted above), using something like the SpotCoorinate.ByPoint node from the clockwork package. A problem for another day though.

3. Your selection method is grabbing some additional spot coordinates, and I’m not sure why. It may be how you stripped content from the model, it could be something else entirely - no clue really. I’d leverage the Select.ByCategoryAndView node in the Archi-lab package instead. This will grab the spot coordinates in the given view(s), omitting the dependent views which I believe is what the Clockwork node was doing, causing there to be 14 items selected instead of 9 (the total sum of instances in the active view).

This graph should help narrow things down: