My second thought was “Transfer project standards after making the source color scheme in a file which you could have automated by Dynamo prior to setting the override…”
But no, that doesn’t work as transfer project standards is also not accessible by API. API functionality is 0/2 for me today. Oh well two more votes for both.
Next thought: Why not skip over caring about the color scheme entirely? Enable any color scheme, and override all fill colors as you were before, but by layering them a over b over c over d. This would enable the same results, and in a manner which is accessible via the API.
I didn’t make the attached with Dynamo, but I think I could have.
In any case this could be thought of as a proof of concept.
egress - faux color scheme.rvt (384 KB)
Dynamo wise you’d have to:
- Programatically enable a color scheme for rooms on the view and don’t care about how it looks at all. Literally set any color scheme at all. Ugly and garis is actually good here as it would highlight a room that fails to catch itself in any filter. I don’t know if this can be done but even if it can’t, the four clicks required to enable it is almost a moot point if every other aspect is done by CPU right?
- Define the combinations of parameters for the filters based on your project standards, but ensure “area over 0” is on that list and apply those parameters to a series of filters.
- Apply those filters into the view or template in the correct order. Note that in the file I uploaded the copied floor plan doesn’t apply the colors correctly as the “area over 0” is the last filter applied (top of the list). This is the “make rooms a neutral base” filter.
- Set your colors and hatches for each filter. As you know, if you’re using this for a building department review you likely want it B&W and easily readable after photocopying it a few times so a hatch and grayscale is likely more ideal.