AU Classes on the View, MEP and Link APIs

Wednesday was my first normal and full AU day, after completing the developer conference and DevLab activities.
I was able to attend two interesting classes held by Revit API developers Steven Mycynek and Arnošt Löbel, and present my own Revit MEP API one.
Here they are in chronological order:

I am including the class materials below, both for your and my own convenience, and also to ensure that all this juicy stuff really is picked up and returned by Internet search engines.

Schedule and View APIs

Revit 2013 includes a major expansion of the Schedule and View APIs.
This class introduces the API for Schedule and Elevation views as well as many methods and properties that apply to all views.
Learn how to create and modify these views to help document and display your Revit model.

This class should really resolve all those recurring questions associated with the creation of different views once and for all!
Take a special deep look at Steve’s multitude of useful utility classes in the sample code.

Revit MEP Programming

This class shows how to work programmatically with Revit MEP models.
It provides an overview of the entire Revit MEP API with specific focus on the major enhancements in Revit 2013.
The most important 2013 feature is the routing preference functionality.
An overview of the available samples is provided.
All MEP domains including HVAC, electrical, and plumbing are addressed.
It shows how to analyse existing systems and create new MEP models from scratch; covers mechanical and electrical system traversal; display of system hierarchies in a tree view; components such as circuits, ducts, pipes, fittings, connectors, cable trays, and conduits; and automatic calculation and sizing based on room and space requirements.

Managing Revit Links

This class explains common pitfalls working with links and how to avoid them.
It details the creation of Revit link types and instances, and recommends how to easily check or modify the parameters of links.
Material describing ways to inquire for data about the various types of external files, including Revit links, is included.
It concludes with an overview of a larger Revit link API application – the eTransmit add-in, which enables users to move an entire package of Revit files while maintaining relationships with all linked files.

Implementing a BIM Business Transformation

Unrelated to any direct programming topic, here is a white paper on
implementing a BIM business transformation that
is of interest to visionaries and decision makers and neatly complements the recently released

BIM for Infrastructure
one.


Comments

2 responses to “AU Classes on the View, MEP and Link APIs”

  1. M. Vallée Avatar
    M. Vallée

    Hi Jeremy,
    First of all thanks a lot for writing this fantastic blog ! it is just a wonderful place to find answers and pieces of code for people who start developing with the Revit API.
    I’m writing a command that automatically generates schedules then places them on sheets (3 schedules by sheet). My trouble is it seems impossible to change the font size within schedules, so the 3 schedules take too much place for the sheet (I am forced to use a specific titleblock – A3 format).
    I see in Steven Mycynek’s PPT that shedules “appearance” is not changeable today… would you know a workaround ?
    Or must I have to create 3 “template schedules” (one by element category) with the good font size, then make duplicates ?
    Thanks in advance for your help !
    M. Vallée

  2. Dear M. Vallée,
    Thank you for your appreciation!
    It is indeed currently not possible to set the font for individual schedule cells. Sorry about that. We are working on it. Revit 2013 provided the first release of the schedule API, and cell formatting would be a pretty obvious next step, as you noticed.
    Yes, a workaround using template schedules sounds like a good idea. Good luck!
    Cheers, Jeremy.

Leave a Reply to Jeremy TammikCancel reply

Discover more from Autodesk Developer Blog

Subscribe now to keep reading and get access to the full archive.

Continue reading