Topography subregion missing

[henry3ZJVJ]

I created a topography subregion and there are regions that don't show.

In the areas where there is a strip there is supposed to be a subregion, on the left side it appears as normal how ever for the right side which is part of a different closed boundary the subregion is missing and there is nothing to click on.

I'm not sure how to fix this, hopefully someone has experience with this.

I have included a screenshot since I can't upload the file. 

[barthbradley]

First of all, when you say "left" and "right" side, I get confused. The region in enveloped by the toposurface; no? If not, you don't have a region, you have a split. Which is it? 

[barthbradley]

I looked at your picture again and notice something very telling...There is no contour lines through the white stripping, indicating to me that it is not a subregion -- not a topography element.   

[henryxT3UBU]

Sorry about the confusing description. The grey strip and and the white strip were created from the same subregion instance. 

What you described is the problem, the part of the topology that belongs there is missing and I'm not sure what causes this error. The subregion just disappears for no apparent reason. 

[barthbradley]

Maybe you merged it. But still, the point I'm making is that the bright white "stripping" on the right side of your picture do not look like a Topo feature. What is it? Perhaps, you can post the file here for us to determine. 

[henryxT3UBU]

I know exactly what you mean, the white strip means there is nothing there and that is what boggles my mind. 

I kind of found a fix for it.

First I copied the sketch so I didn't have to do all that work again. Then I deleted all the build pads and the that subregion from the topography. Then I created a new subregion and pasted the sketch back in and the subregion generates correctly now.

Perhaps there is an issue with adding/modifying subregions while there are build pads in the project.

[barthbradley]

Yah, I don't know about that, but I would have liked to see the problem child.  Did you have warnings in the project there were associated to those elements? That's always a good place to start troubleshooting from. 

[henryxT3UBU]

All right so the problem went away, but now its back since I replaced the building pads. So I'm guessing this problem is related to the building pads.

[barthbradley]

Offer stands. You can post file here. 

...or a step by step workflow to replicate. 

[henryxT3UBU]

Sorry, I can't share the file here. 

I'm not sure what the work flow is/was because I've made changes to the file in the past that may have affected it.

Generally it consists of a topography then multiple subregions (two or more) that share a boarder, and building pad(s).

Now it appears that it doesn't matter if the building pads or subregions come first it seems to produce the same error.

[barthbradley]

---

@henryxT3UBUwrote: the white strip means there is nothing there and that is what boggles my mind. 

---

So you're saying that the "white strip" is actually a HOLE in the Toposurface?  The only way that could happen it if you used Split Surface instead of Subregion tool, and then deleted or phased out the Split Surface.  If a Subregion got accidentally deleted, there would still be a Toposurface there. Subregions are dependent on the Toposurface from which they are created; Split Surfaces are independent Toposurfaces. 

FWIW. 

[henryxT3UBU]

I know it sounds hard to believe but yes, it is a subregion, it is missing, it is a hole. 

It seems to only happen when i have a building pad in the topography as well. Other wise it shows up again. My only guess is building pad splits the topography and then the sub region hosts itself on that split topography.

Try to avoid using splits because I find it a bit destructive unless I need to resize the topography. 

[ToanDN]

It should normally not happen.  Is your sub-region boundary super complex?  Try to split it to a smaller sub-regions maybe.

[barthbradley]

Never mind me. I'm just curious. Actually, I recall reading similar threads as yours in the past.  So, this could quite possible this is a real glitch with the software. I've just never experienced it. 

Good luck. 

[henryxT3UBU]

Yeah my subregion is pretty complex. I actually made multiple subregion from one instance of it.

[ToanDN]

---

@henryxT3UBU wrote:

Yeah my subregion is pretty complex. I actually made multiple subregion from one instance of it.

---

Can you show a picture where the building pad interfacing with the subregions?

[henryxT3UBU]

Sorry I can't. But you can think of this like a road that is flanked with sidewalks on both sides and then the build pad is sharing an edge with the one of the side walk sub region edges. I'm trying to redo the entire model to see if this is a bug within the file or overall bug in Revit.

[barthbradley]

Can you describe the workflow your using to create the sidewalk? 

[henryxT3UBU]

I just remembered the toposurface is two toposurfaces spliced together. There is a site condition and a planned condition where the boundary of the planned topo was cut out of the site topo, deleted, and then merged together. Do you guys this had an affect on it?

Is there a better way to approach what I am trying to do rather than splicing two surfaces together?

[cbcarch]

I suspect a Phasing problem, based on the "merged then deleted toposurfaces" description.

What Phase are the topo surface and pads on?