Today, we look at accessing and exporting sheet view coordinates, transforms, images and title block data, including the title block geometry and text values:
Here is a lengthy in-depth look at accessing, extracting and exporting title block geometry and text from
the Revit API discussion forum thread
on how to extract the geometry and the texts of the title block in a sheetview,
with several interesting new insights provided once again by
Richard RPThomas108 Thomas,
e.g., the possibility of programmatically exploiting the Revit print to XPS functionality:
Question: I want to extract all visible text and geometry in this image of a sheet view with its title block, including correct placement of all attributes:
To be more precise, I want to recreate an identical representation of the sheet view in my own exportable non-Revit document.
Answer: If you want to access the text and visible geometry to recreate a facsimile outside of Revit, you might be able to access text and geometry separately, e.g., using a filtered element collector for real data and a screen snapshot for the appearance.
Most of the text data can be accessed using built-in parameters.
The Title Block is a Revit family, so its geometry can be accessed by reading it from the family definition.
You can Filter for specific elements and retrieve their parameters, e.g., using:
FilteredElementCollector collector = new FilteredElementCollector( document ); ICollection<Element> lines = collector .OfClass( typeof( FamilyInstance ) ) .OfCategory( BuiltInCategory.OST_Lines ) .ToElements(); ICollection<Element> texts = collector .OfClass( typeof( FamilyInstance ) ) .OfCategory( BuiltInCategory.OST_TextNotes ) .ToElements(); ICollection<Element> filledRegions = collector .OfClass( typeof( FamilyInstance ) ) .OfCategory( BuiltInCategory.OST_FilledRegion ) .ToElements(); //etc.
Please note that the call to ToElements is very often a waste of performance time and memory space.
Avoid it when you can, i.e., mostly.
Response: Yes, I want to create a facsimile outside of Revit.
I managed to extract the content of the views that compose it but at real size and not yet find how to extract the cartridge and its content.
The solution you suggest above does not work, the filtered element collector result lists are empty.
Answer: As always, you can use RevitLookup to analyse the properties and other attributes of the Revit elements you are trying to retrieve with the filtered element collector. That will show you which filters you need to apply to extract the desired elements. If the filter returns no elements, you are applying too restrictive or downright erroneous filters.
Response: On the FamilyInstance of my ViewSheet, it finds neither OST_Lines nor OST_TextNodes (for the extract the Title Block).
Do you have a filter syntax that could find them ?
Answer: The most efficient way to define such a filter is for you to pick the elements you are filtering for and explore their properties using RevitLookup, cf., how to research to find a Revit API solution.
Response: I have already explored the viewsheet and the associated family instance as well as the symbol and the family. None has geometry.
Answer: The family definition document of the title block will contain the geometry. You have to open the family for editing. It may have various nested annotation symbols that also need to be traversed.
Besides that, there is the issue of items such as images and schedules.
It would probably be easier to read the fixed document sequence of a printed xps file, cf.,
XPS or the Open XML Paper Specification.
This is an XML file containing path data represented in a mini language similar to what you get in Xaml and 'Glyphs' entries for text objects with render transforms to give their positions.
It takes a while to print an XPS, but if it is only the title block, it may be quicker.
You would still have to interpret the xml, but, as difficult to impossible tasks go, it is slightly less impossible.
XPS is a zip file; change the extension to Zip and unpack it, or, alternatively, there are namespaces for reading packages for such directly (System.IO.Packaging).
I don't envy your task, I usually just print a pdf when I want a copy of something.
HPGL is another historic plotter vector format that could be easily interpreted.
Response: My project is to export a viewsheet in svg format.
Currently, my code correctly exports all viewports, but I still have the title block (drawing and data) to export.
If I understand correctly, there is no way to export the title block (curve and position of the data)?
Answer: As you've noted, Element.Geometry is null for title blocks.
The only approach I know of with the Revit API would be to open the title block family using Document.EditFamily and extract such lines from the plan view within that. As noted above, however, this family could also contain revision schedule that you can't extract lines from and other nested generic annotation families and images. The parameter text values would not be correct, but from the text strings used in Labels and parameter names you can sometimes infer such a relationship (between text locations in your title block family and positions on your ViewSheet in the project). If label has a preview parameter value (which is often the case), then this can't be done. Also, the placement of multiple parameters with line breaks etc. in the same label add to complexity. You don't get a description of these with the API (which parameters used in which label).
Ideally, this task would be suited to CustomExporter, but I believe from previous discussions that this doesn't support ViewSheets.
XLST could potentially be used to convert the XPS path data previously noted to SVG, although I know of no existing templates for such.
Another potential long winded option would be to export the sheet with only the title block showing to DWG and import that on a drafting view to analyse the geometry. Not sure it is a good option, but could be done. DWG links favour polylines: any lines of the same layer joined together will be grouped into polylines. Text object positions could only be found by exploding the dwg (not sure if there is API function for that).
Response: I confirm that CustomExporter2D does not work on ViewSheets.
I tested the other approach:
// vs = current view (Viewsheet) Element El = doc.GetElement( vs.Id ); FamilyInstance FI = null; foreach( ElementId ElI in El.GetDependentElements( null ) ) { Element El1 = El.Document.GetElement( ElI ); FI = El1 as FamilyInstance; if( FI != null ) break; } FamilySymbol FS = FI.Symbol; Document DocFamily = doc.EditFamily( FS.Family ); FamilyManager famManager = DocFamily.FamilyManager; FamilyTypeSet famTypes = famManager.Types; int nb = famTypes.Size; FilteredElementCollector collector = new FilteredElementCollector( docFamily ); foreach( Element ElF in collector ) { DetailLine line = ElF as DetailLine; if( line != null ) { Curve curve = line.GeometryCurve; Line LI = (Line) curve; if( LI != null ) { double XD = (LI.GetEndPoint( 0 ).X * 25.4 * 12); double YD = (LI.GetEndPoint( 0 ).Y * 25.4 * 12); double XF = (LI.GetEndPoint( 1 ).X * 25.4 * 12); double YF = (LI.GetEndPoint( 1 ).Y * 25.4 * 12); Deb.Write( " <line x1=\"{0}\" y1=\"{1}\" x2=\"{2}\" y2=\"{3}\" style=\"stroke-width:{4}; stroke:rgb({5}, {6}, {7})\" {8}/>\n", XD, V - YD, XF, V - YF, 1, 0, 0, 0, "" ); } } else TaskDialog.Show( "Test", "No Line" ); }
This code extracts only 33 lines and nothing else.
How to have access to the text positions?
Answer: Your code extracts nothing but lines, because that is exactly what you have instructed it to do.
You can expand you code to analyse other elements besides lines.
Alternatively, and probably more effectively, you can analyse your family definition document interactively using RevitLookup to discover what other elements it contains.
Response: This family is internal (A0 metric).
How can I use RevitLookup to explore this family?
Answer: Application > Documents > select the family definition document.
Response: Ok, I found some TextNode, TextElement and ImageInstance elements.
But my filters are not working.
Is there any documentation of element filtering?
My code:
FilteredElementCollector collector = new FilteredElementCollector( DocFamily ); ICollection<Element> lines = collector .OfCategory( BuiltInCategory.OST_Lines ) .ToElements(); ICollection<Element> texts = collector .OfClass( typeof( TextNote ) ) .ToElements();
They return no elements.
Where is the error?
Answer: You really do need to learn to search the Internet.
In this case, for instance, you can just search for Revit API filtered element collector.
Please practice this for a bit before asking the next question.
The specific problem that you ran into was discussed in the note on reinitialising the filtered element collector.
Happily, that seems to have resolved the problem for the moment, with no further response so far.
Richard helped with two other sheet related issues as well.
One is on Getting element coordinates on sheet.
To cut a long story short, here is his final answer:
I think you have just wrongly assumed the other two points of the bounding box, i.e., two points represent more than one unique rectangle. If you get all four points of the bounding box corners on plan without transformation and then transform them you can draw lines between them as below. I think what confused me when I looked at this originally was the double door families. Note however that in the case of the sample file all doors were parallel with the internal coordinate system. If your door instances were rotated (hosted on a non-vertical or non-horizontal directional wall) the bounding box would still be orientated to the internal system not rotated with the door. So, that aspect may add a layer of confusion, you would have to orientate the bounding box using the door instance transform first. This may not be possible actually since original two points circumscribe door with a box parallel to internal system, so when rotated this would be meaningless. In such a circumstance you likely need to build your own bounding box within the new orientation by looking at max/mins you get for the geometry in the new system.
You can't get the rotation of a scope box but if you set a view to one then you can compare 1,0,0 to the right direction of the view to get scope box rotation. This should not be required here because the view right direction is used so transform should already incorporate it. Useful to know however that the orientation of a scope box can be found this way (using one of those transaction rollback workflows). The alternative may be to interrogate the geometry of the scope box to find direction of lines around the scope box bounding box centre (for the top or bottom rectangle of the cube). Although you likely couldn't get a full rotation between 0 and 2Pi for this due to symmetry. Depends on how geometry of cube is constructed in terms of line directions there may be some non-symmetrical pattern of this (looking at all 12 lines etc.).
Dim Dr As Element = Doors(DRi) Dim BB As BoundingBoxXYZ = Dr.BoundingBox(V) Dim BL As New XYZ(BB.Min.X, BB.Min.Y, 0) Dim BR As New XYZ(BB.Max.X, BB.Min.Y, 0) Dim TL As New XYZ(BB.Min.X, BB.Max.Y, 0) Dim TR As New XYZ(BB.Max.X, BB.Max.Y, 0) BL = T.Inverse.OfPoint(BL).Multiply(1 / Scale) + Offset BR = T.Inverse.OfPoint(BR).Multiply(1 / Scale) + Offset TL = T.Inverse.OfPoint(TL).Multiply(1 / Scale) + Offset TR = T.Inverse.OfPoint(TR).Multiply(1 / Scale) + Offset Dim LN_B As Line = Line.CreateBound(BL, BR) Dim LN_R As Line = Line.CreateBound(BR, TR) Dim LN_T As Line = Line.CreateBound(TR, TL) Dim LN_L As Line = Line.CreateBound(TL, BL) doc.Create.NewDetailCurve(AcView, LN_B) doc.Create.NewDetailCurve(AcView, LN_R) doc.Create.NewDetailCurve(AcView, LN_T) doc.Create.NewDetailCurve(AcView, LN_L)
Another interested thread addressed by Richard is on how to export 2D sheets as images with high quality, wrapping up with:
Without the annotation objects visible here are two images of the same view (not from exports); the top is set to 1:1000 and the bottom 1:200.
The line weights are scaled in relation to paper space units, so if you set to 1:1 etc., then your lines end up thinner, which may carry through to images exported if you can temporarily set this before export:
This works fine if you are exporting from a normal view, as changing the scale is not an issue.
However, you can’t change the scale in the case of Sheets, because that will affect the viewport size and location.