Alpha-numeric detail numbering

Yes what you showed is the intended use of my script. I am debating the correct numbering for 2 and 3. Since I am determining the view’s location from the top right 2 and 3 come before 4 but if I were to number based on the bottom left 2 and 3 would come after 5 before 6. Easy to change BBox min or max.

Looks like my math worked as well. :smile: I did not want to run it on the project I had open but I was hoping I got it right. Thanks for the proof of concept Amy.

1 Like

@Steven Yep it definitely works! I usually use the sample projects to test stuff like that since its all set up already. The 2 & 3 did throw me off as to how your graph would be adjusted for the alpha-numeric grid format, but the math approach you took was certainly clever and I’m sure it could conform to the alpha-numeric format. (Your firm does indeed number oddly though - however the placement of 2 and 3 would make perfect sense to me if the viewport title ran right to left)

1 Like

Wow you guys are quick… I’ve just had the chance to read the latest posts and am testing @awilliams solution now. I’d like to also test @Steven but most likely won’t get the chance to do it tonight.
I’ll recheck once completed. Thanks again for so much help! :grin:

Mine should only take you 1 minute to check. only need to add a code block and Math.Abs to your graph.

1 Like

well…Detail sheets run right to left. floor plans, section, elevations run left to right :sweat_smile: Its an old method and no one wanted to use the stick to make everyone change over to the CAD standard. I just make the tools however they need to be made.

1 Like

Hi All,
I’m having some trouble with the script … it doesn’t want to work quite as expected. I changed lacing to longest at Geometry nodes which helped but there’s still some disconnect with the script… perhaps how it reads the grid. I can reupload the script if there are no immediate thoughts form anyone.
Again, I’m a bit green so thanks for patience and for help!

Hmm those results are peculiar… are those drafting views? Do the geometry outputs from the Rhythm node Viewport.LocationData (if you swapped that one in) appear to be in the correct location?

By the logic of the graph, I’d think those detail numbers could only happen if there is something off about the viewports locations themselves :face_with_raised_eyebrow: Would you upload a screenshot of the graph with the previews pinned for these nodes (Viewport.LocationData, BoundingBox.MinPoint, Geometry.Transform)

As requested, an image of the graph in it’s entirety with Viewpoint.LocationData, BBox.MinPoint and Geometry.Transform previews pinned.
I took some time investigating other possible alternatives, such as the vector axis, grid geometries and other random testing to satiate my curiosity. The views are a mix of drafting and detail views; you suggest a possible problem with the Revit family?
The original script i used seemed to have no problem, other than it didn’t invert the x-axis. Maybe there’s a solution where i return to that as an option?

Hi @awilliams - I took my own advice and after a lot of messing around last night decided to eliminate a variable, that being the “views” and keeping “viewports.” I swaped Sheet.getviewportsandviews for Sheets.viewports and voula!
Everything seems to be working smoothly now. Thanks so much for all your support @awilliams and @Steven - many thanks.

@AW_Rash glad you got it working! I’m really quite curious about the differing results between the Sheets.Viewports node and Sheet.GetViewportsAndViews. I’m trying to test it but can’t seem to recreate the issue.

@john_pierson any chance you’ve encountered strange results with viewports and their locations? It seems here the Rhythm nodes might have been producing incorrect results in comparison to the Hollandaise viewport nodes :face_with_raised_eyebrow:

@awilliams trying to catch up here. Where did the difference occur?

Sorry I should have clarified better, the image on this part of the thread shows:

The locations appear to be off given that their detail numbers weren’t making sense, and it was resolved by switching the Rhythm nodes out back to the Hollandaise nodes

Switching which nodes to which nodes specifically? Several screenshots above mention different nodes at different times… Makes it incredibly difficult to follow along out of the blue.

Wouldn;t make any sense for the Sheet.GetViewportsAndViews node to be causing problems. I am just returning the elements.

This statement is correct - the inclusion of views together with viewports gave me strange results. Any reason to blame the TitleBlock? Could the issue lie in the use of detail views vs drafting views?

@awilliams is referring to the latest screen shot with the red x through Sheet.GetViewportsAndViews - attached again for reference. Swapping Sheet.Viewports for Sheet.GetViewportsAndViews gave me the correct results. @john_pierson Would it be helpful to send you the .dyn file for you to look at?

image

I think I am following now. Also, Sheet.Viewports is a node from archilab. This was adding to the confusion i think

That wouldn’t make sense to me either, really strange but I can’t recreate it. Apologies for the confusion - I thought it was Hollandaise because that’s what is referenced in the AU workshop handout from Nate Holland that this workflow appears to have followed

@AW_Rash any chance you’d be able to share a stripped down version of your Revit file with just that sheet?

If memory serves I believe that Hollindaise culls nodes from arhi-lab? I could be wrong here…
@awilliams I believe I can get something to you but it might not be until later in the day. Any problem waiting on the request?

Sure no rush at all! I’m honestly just curious to see whats going on

I took a different tack on figuring out the module names.
Rather than using math, I just created two lists. One with the distance from the “origin” of the Sheet, and a matching list with the values.
That should make it a lot more customizable and flexible.
Well, technically, it’s 4 lists. Two for the horizontal, and two for the vertical.

RenumberByZone.dyn (60.2 KB)
Here’s a Zoomed in pic of the lists


The first row delineates where the boundaries are horizontally
Second row is that value to assign between those values
So anything less than 0.0 (left of the sheet edge) gets “0” anything between 0.0 and 7.00 gets “1”.
Vertically, anything between 0 and 4.375 gets “H”
Then the “1” and the “H” are concatenated later.

1 Like