I'm trying to develop a civil cell that should have just two primary references. One is the baseline (with profile) of a roadway, and the other is a line crossing that baseline (a bridge abutment). What I find is that it picks up only a few elements, and it's getting tedious establishing what is wrong here.
First, I discovered on my own that sadly it isn't sufficient to draw a line using keypoints on a primary reference element. From what I can tell, all of its DependsOn ancestors must be included in the of the reference elements. Therefore, if it is just point to point, it won't work. Please correct me if I made the slightest mistake. If I'd known this, I'd have constructed the civil cell differently in the first place.
Having discovered this, I'm still having trouble with my civil cell. I have established that the two DependsOn ancestors are insufficient to pick up all elements that I expect it to pick up; those elements that continue to be dotted have at least one ancestor that has not yet been selected.
1. It would be fabulous if we could access a report on exactly which elements have at least one but not all ancestors in the selection set. This report should tell us, for each child element, which ancestors are not included in the set of primary references.
According to this video, all elements to be included in the civil cell have to be fully constrained. According to this article, you can't use Simple Arc From Element with a common datapoint as it will not be fully constrained.
2. It would be fabulous if we could have a subset of tools and snaps and such that will work in civil cell construction.
From observation, all child elements that are fully constrained are automatically included.
3. It would be nice if we could blacklist certain elements from being included in any given civil cell. Sure, now we know that it has to be fully constrained, so if we unconstrain it, of course that element won't be included. But what if we want it to be included in one civil cell but not another?