Hi Jeremy,
The new API calls in 2015 look interesting. I'll have to investigate further.
The origin of this request came from the need to generate non-standard spot coordinates. Rather than placing spot coordinates showing Easting and Northing data on the leader line, I needed spot coordinates to show a integer (an index to a row in an accompanying schedule) and to enclose this integer with a black circular border. Because these coordinates needed to be generated as part of an automated pipeline, I needed a way to customize the spot coordinate text and style within the API. Based on the available API documentation (http://revitapisearch.com/html/5d70c697-396a-cc67-2caf-5608f556a456.htm), it looked as thought it *might* be possible to manipulate the style and content of a SpotDimension after creation, but I couldn't find a precedent example, and a tight deadline led me to seek an alternative implementation. This led me to try manipulating User Keynotes. This gave the appearance/style I needed, but the approach was stopped in its tracks when I found I couldn't change the type of a newly generated keynote to my modified keynote family. In the end, I wrote some routines to fake the appearance by adding additional detail annotations on top of pregenerated text tags.
Two lessons came out of this efforts:
- Keynote type changes in the Revit API appeared, as of 2014, to be limited, and the whole effort to use keynote tags for custom spot coordinates was probably a red herring from the start.
- Flexible, custom SpotDimensions are what I really needed, but the constraints of deliverable schedules didn't afford the time to discover the "right" way to match requirements.
Thanks for your assistance.