Hi all,
I have an excel with the coordinates and info off ± 700 pipe supports. I load this into my dynamo and filter for the data i need (x , y) unfortunately my output on the Spotelevation.bypoint node is “null” each time.
i’ve already tried replacing the “null” values (thats the warnings you’re seeing).
Could the issue be that im using linked models instead of modelled geometry? my script worked just fine a couple weeks ago when i made and tested it.
seems like i got some results when i adjusted the Z value. is there a possibility to drop the Z-value so i dont have to enter every possible elevation?
im not entirely sure how SpotElevation.ByPoint is implemented. but i think this could be a linked reference issue which requires some tinkering with stable representation of a link to which the spot elevation is about to be bound.
edit: experimentally, if u bind the link then re-run ur script and everything works fine. then it’s a link reference issue most likely.
Hi @niels.van.hove try spot elevatiion by reference from genius loci, it support link as well
most likely its a link issue since i tried running it at the same Z-value with the linked slab and a slab i copied into my model from the link. when i copied and ran it it did work.
What also was weird is that when i was testing it i had to enter a Z-value greater then the Z-value from the slab. now i had to enter ± the same Z-value to be able to get a result
im gonna try out genuis loci’s node and see what happens
yeah see if it could be better, there is a node there to “convert” link reference
seems you have 13 links…you will need get the refernce from element, surface, etc depends which kind of element you will spot…and for link there is a node for convert, any way guess spot elevation from GL need a dimension type input as well
aaah okay. didnt know what they meant with reference. will try now. thanks
Since there’s like 9 linked models i used BimorphNodes LinkElement.OfCategory. Still something is going wrong. no clue what im doing wrong at this point
[/quote]
for bimorph there is a node to convert "link element (floor) to real elements
i think thats the one i used. just looked through the bimorph options for linkedelement and this is the best option that fits your description
not sure, i dont have bimorph, but there should be a node for convert bimorph link element to real elements , if i remember right, but cant remember the exackly name
mhm okay i’ll look into that. also what i have noticed is that my X and Y values in surface.pointatparameter are crazy high and not what the input should be.
allright that sound as some coordinates problem, does your active doc and link share origin ?
yep!
hmmm then probably becaurse you measure from survey or project base point…not sure, but guess these z points is from origin, but the tag itself have option for reletavi, surveypoint, project base point
i revised my script. since im pulling in an excel i already have my coordinates. so thats my point input.
i think my problem is fetching the references. i used LinkElement.Element to get the element from the linked element like you said. but thats not a valid reference. i googled about references but i dont seem to understand how it works.
yeah reference can be a jungle 
sometimes…hahah, but now it seems you feed in element as ref, try this ref compound node i showed for floors, is it for columns or other they probably have another ref,but seems you have a lot nulll as well, try clean that up, and where does thes points come from , project base point, origin, surveypoint… ?? and i would first try with one link, one element, and when it works scale it up
