InfraWorks, AutoCAD Civil 3D, and Revit 2018 Working Together for Master Plan Design

ENRIQUE GALICIA: My name is Enrique Galicia, Enrique Galicia Duval. I'm an architect, and--

AUDIENCE: [INAUDIBLE]

ENRIQUE GALICIA: Sorry?

AUDIENCE: [INAUDIBLE]

ENRIQUE GALICIA: As well?

AUDIENCE: [INAUDIBLE]

[LAUGHTER]

ENRIQUE GALICIA: No, it's all right. I like being an architect. I'm also a programmer. So I have the things in common, which is good.

Then I have been working with Revit for more than eight years. I'm a BIM consultant of Mexico and Saudi Arabia, so I jump between here and there on giving courses, training, developing things. I'm also have participated in over 70 projects regarding hospitals, waterdemps, urban roads, offices, housing, commercial, touristic complexes.

I'm author of several Revit add-ins, [INAUDIBLE] all of them in-house for different types of companies. I'm quite familiar with the Revit API. I gave a lecture on 2011 Revit API for construction builders in NIU, but I haven't gone since then to this forum.

Also, I know some JavaScript and Dynamo workflows. I have over 22 courses on Udemy, some of them in English. I have start putting everything on English from last October until now, and I have another one in Spanish, focusing things on functionality for a scope, so it's like having an open forum. And if there's some flow that I'm researching, it can be helpful to find out solutions or other types of things for that.

I'm also a professor for more than five years at the Tecnologico de Monterrey in Mexico City. Well, you can contact me for any courses, training, implementation, research, development if it's BIM, or even if it's not. There's my contact. It's on, also, the outlines and on the presentation.

You can follow me on PracticalBIM. My LinkedIn profile is still there, so it's having everything up in the table. Udemy profile, my email, so it's a lot of information. [INAUDIBLE] you can, just hey, I know where you live.

AUDIENCE: [INAUDIBLE]

ENRIQUE GALICIA: Yeah, yeah, I haven't put my address on. It's going to be all right.

AUDIENCE: [INAUDIBLE]

ENRIQUE GALICIA: So-- [LAUGHING] no bank account, no credit card, no, it's all right. So I have another lecture tomorrow called Dynamo Studio Modeling Information Analysis for Construction Builders. It's at 1 o'clock, and-- yeah, it's 1 o'clock to 2 o'clock.

And before I [INAUDIBLE] the presentation, I wasn't able to download the-- upload the additional files. They're already on the site for downloading. For everything we're going to see, there's going to be the files. There are the files already in there, so you can download it and practice how the workflows goes.

So let's review the outline for today's lecture. It's to be we're going to work on creating workflows from AutoCAD Civil 3D and InfraWorks. We will start from that scratch. How do we get from InfraWorks, transferring information to Civil 3D, and going back?

We will review some bullet points of what can be done easily on InfraWorks and what can be done easily in Civil 3D, so you can have a fluent workflow between those two. Then we will learn how to get quantities from Civil 3D and export it in and out. And then we will mix those two with the Revit 2018, exporting files from Civil, then getting in Revit, and Revit back again to InfraWorks.

So introduction, just going to check. This is our beginner course for Infra-- to use InfraWorks, Civil 3D, and Revit. So we're focusing on workflows, how do I send files from one side or another one, and what will help me to improve things, whatever I'm doing?

So we will start from scratch reviewing, so I am going to ask some questions. Does everybody is familiar with InfraWorks have try it? Yes?

OK, with Civil 3D? Most. And from Revit? OK, so we are most, even. So it will be quite good.

So it's not a beginner course. I'm not focusing on each individual, but I will just grasp at what we need to focus on how we can get those workflows running. So it's recommended as general overview, and that's all right. And [INAUDIBLE] will be using.

So the main idea is that we have InfraWorks, and InfraWorks is highly set for presentations. It will help us to show how elements get together and how a big scope of a project is not limited to the scope Revit has. Can have several elements, and also, we can change the sizing of those, and it has a high value on quality graphics and communication. We can share it. We can place it on web services, and that can help us bring the things and see how we can improve, make some changes on the go.

But the problem is that, with InfraWorks, we like precise information. If we want to have the points exactly in one location, either we do it with scripting, or we get it from Civil 3D. Otherwise, they won't have the same positioning system. So it may be a road in this area, but not actually the road we want to show.

So without Civil 3D, we will set-- we will use the millimetric precision of surface geometries, so we can export that back to InfraWorks [INAUDIBLE]. And then if we want to model elements in BIM, we can do it with Revit.

And Revit 3-- Revit 2018 is mainly about BIM models with-- without the high-end scope of the master plans needs. So we cannot have a huge master plan complete on Revit file because it's going to be too heavy to process. So if we order the key points of this trifecta, we can set the workflows for master plan's design.

So I'm going to start with the first one. The first one is learn how to create workflows between Civil 3D and InfraWorks. How do we get from InfraWorks and Civil 3D together?

So just a general review. That's the interface for InfraWorks. We have many components or many things that we can do there is we set coverage areas, land areas, and we can set up roads just to have a general idea, because if we're just clicking in the screen, they may look like, but they don't have any precision on a technical aspect of how to show the project.

So we can also have this tool that is the profile settings, that is really helpful when checking that the geometry is going through the profile surface, and to [INAUDIBLE] slope is good enough for bringing those together. Also, InfraWorks is really useful for that analysis. It can show up really quickly how to get slopes, how to get elevation elements.

So we can review. We're trying to get the road-- yeah, we're trying to get our road here, or we're trying to get it somewhere here. We need to space those elements in these parts, just to jump around.

So the starting point here is we have a tool called a Model Builder. Model Builder is actually-- [INAUDIBLE]. Yeah, the Model Builder is there. It's next to the models, and it has Model Builder New or Open.

And with the Model Builder, we're seeking how is our space being placed. So for this example, I'm using one that is a project done in [INAUDIBLE] on the Conejos Bay. So for [INAUDIBLE], they needed to be taking the topography, and they needed to be changed within the real topography done by the station.

So with the Model Builder was good to get topography, but it will lack of complete precision it needs to get the real thing. So you just select an area, and you have these four options that are selecting it from the screen, getting a selection [INAUDIBLE] square, rectangle, polygon, or just to set the other elements. The maximum is 200 square kilometers, and then you just save it as a new file, and it will be on cloud. It will depend on how you configure group settings or other elements to know where your file is.

Let me see. It keeps-- yeah. And then the first thing we need to get really clear is where our model is sitting. How does the ends of that model will be placed?

So we have a tool called Model Properties. We will see how to get there, and that will give us these two points that are the minimum and maximum. It's the starting point and the ending point of that reference. Just going to go do that.

So that window is actually at the end when it says the settings, and in the settings, it has one that says Model Properties. Just going to wait for my other [INAUDIBLE]. Yes, [INAUDIBLE]. And then we have the lower end and the upper end using a system of latitude, longitude, and degrees, and those two that we need to have it because we will use it for Revit to get the location system, so it has the same weather station close by. And we will use it for other purposes.

So from there, then we're going to export as EMX because we want that to be linked with our Civil 3D. The EMX format will be the one that will help us doing that. What it will actually do is just to get all the surface together.

It will get the roads as well. The roads are picked from the imagery that that space on the Model Builder was, so they won't be accurate but still will give us an idea of how are the main roads being placed. I'm just going to say, yes, save it already, and we're going to go for the Civil 3D part.

Next, we open Civil 3D as-- I'm just going to give you a little hint on Civil 3D before we go that, because otherwise, it may be complicated. So just-- so for those who aren't familiar with Civil 3D, we have these settings on the left-hand. There are the settings for elements. Most important ones are from the surface alignments and points because we cannot great points in Revit, and we cannot create points as points on InfraWorks. But we can do it in Civil, so we can have those reference being placed, and we can use it for importing back.

We have those three elements that will behave as elements with information. So for any of those, we can set it through our property span, similar to the one we have in Revit. Not quite, but still, I'll just [INAUDIBLE]-- yeah, Revit, which will be the Surfaces tile. The Surfaces tile will affect the type properties of how the surface is being placed, and those will help us to get the information of a surface or a point or an alignment.

So with that really, really easy, just really basic scratch of Civil 3D, we can continue with our workflow. So I'm just going to continue here. And then what we're going to do is we can import that one on Civil 3D. We have one that it says InfraWorks settings. It's using an EMX file.

That file will pick it, and it will request this element, so you can have the same coordinate system. So it will pick the one that we have already in Civil, and because we started from a brand new file on Civil 3D, it will configure all layers. So it will get properties for different types of-- I just forgot the--

AUDIENCE: [INAUDIBLE]

ENRIQUE GALICIA: The [INAUDIBLE]?

AUDIENCE: [INAUDIBLE]

ENRIQUE GALICIA: Yeah, OK. Yeah, the surface. Sorry. Sorry about that. Just think I need some water, would be good.

So once we import it, we will have these type of elements. In this case, it's importing services and the alignments. So the good thing here is, because it's attached to the surface and how it goes, when it's having a point of movement, it will get that coordinate connecting with the surface it's been placed. So that can help us for roads, for having some elements being checked up. And as well, we will have the surface.

The surface itself, because it's not set only by-- OK, it's just-- I'm just-- [INAUDIBLE]. The service itself, because it's not set, we can change it. We can change the number of the borderlines, how they go. So in this case, I'm just going to-- here.

So for example, in this case, we have the complete area with the borderlines, but we can change it with the surface's style. So if it's a huge model, and we want to import it to Revit, it may not work quite well because we will have a lot of points in between. It will depend on how is the level of detail we want to get.

So it's important to know that because it will affect how we import files from Civil 3D back to InfraWorks and from Civil 3D to Revit. So in that example, what I'm doing is just getting the properties for the elements having them. We know this plane, and what I will do is it let me delete the alignments. I don't want to have that information at this point because I want to coordinate it with the other model.

And I will always have, when I export a file from InfraWorks, these two surfaces that are the existing ground and existing transportation. When I get line work, it will have another one that is proposed ground. But if I want to get comparisons or check it with the topography I will have from my station, what I need to do is actually create a new one that have both.

So in that example, I turn both off, but I'm pasting one over the other one, so I can have this view of how the road is getting. But because of the nature of the files, we will need to get some audit, so it's always recommended that, if you're getting [INAUDIBLE] file, just review it so it doesn't have any gaps in between because one of those topographies is just where you have a road, and the other one doesn't have roads. So you want them to get mixed.

[INAUDIBLE], so we don't have any polygon errors. And then what we can do is create a border on the reference. So it becomes a boundary that will show on the topography, and it will have those openings. You see here, we have a problem of opening. If we try to run it like that, it will create problems when we're trying to get quantities, so compare one with another one, how they work together, so I'm just creating a border and having [INAUDIBLE].

I will upload this video as well, because if you wanted to see it slow pace, and I'm just rushing everything. But I just wanted to get the clear picture, and I will have uploaded, as well, the reference of those videos. I know it's not-- even though you're not with a computer, not paying attention is [INAUDIBLE], you're not [INAUDIBLE] like that. So just reviewing-- I'm just going to make a post when we finish this workflow, and we can have a little questions. And we go for the next ones.

So once we have it, we can export it as an EMX file. Just scoping the route, so I'm having that exporting the same position. And what it will do is that, if I'm using the topography, and I have already my real topography being set, I can place those services under the same process, matching the first ground with the other one.

So I passed over it, the real one. Just review the edges, that we don't have too much difference. And now that the surface is saved, we can turn it back to InfraWorks, so we will have the real topography to work with.

So just review key points-- we have here the surface properties, and we have here the number of contours that were-- that wasn't what I was looking contours for. So in this case, we're using it one to five, so that will be [INAUDIBLE]. Doing it in InfraWorks, maybe we want Revit. If it's a bigger space, we will need to have it lowered down, let's say five to 10, or something around that.

And then what we can do is, from that, we have a tool on the top that it says data sets. With the data set, we can select our file, and it will pull the elements that it has-- for example roads, water, and surfaces. It's showing me just surfaces because I choose that once.

We can configure, and it will say which one do you want to import. In the order I'm placing each surface, it will go with the last one. So it's important here to notice that InfraWorks works as a database. So each time you pull up something new, it will take some amount of space, and if you continue the leading placing, maybe you will need to refresh it after a few elements.

AUDIENCE: You said [INAUDIBLE].

ENRIQUE GALICIA: Yeah, yeah, yeah. What will happen is, in this case, it has a terrain elevation. So when we're importing, the other one this is-- oh, what is [INAUDIBLE]? So when actually we're importing an element, what it will do is it will get with a new one.

So you get one file. You get another one, and we will go over it. So if he doesn't have the complete surface, it will just make some patches, whatever it is placed. So that can be helpful in some areas, if you have it on a split design, and maybe you have a master plan with several elements, and you want to go for different zoning spots.

Because it's already set on the same coordinates where you use the import and export, it will remain in the same position. So everything we placed on the Civil file will have the same coordinate system. So I'm just going to go with the next one.

So now, next thing we want to do is we want to have precision using elements in AutoCAD, but then we wanted to export into InfraWorks 3D, so we can know this land area-- it's in a good space, it looks better, we need to change rating, or things like that. So the easiest way to do it is using the SDF files. The SDF files will be just the single lines. It will be the lower level of having that geometry, and it will be quite easy.

We can use the advantage that Civil 3D has on AutoCAD base elements, so we can draw rectangles. We can have polylines using those references to create elements. And then the only thing we need to do for those-- just waiting a little-- is to set up here. We're changing elevation elements, so we need-- we see where that platform is being placed, how is the proposal being set up.

For example, in that case, it's been 12 because this [INAUDIBLE] level, so it's just 12 meters up. And the common we will be using-- it's called Map Export. The Map Export-- what we'll do is we'll pick just elements that are single, polylines or other type elements, and it will save it us an SDF file. So just select Manually, click it on that one, and now on our database set, we can just import as SDF file.

So as we can see, it's now feature type. It doesn't have a last name, so we can change it and modify it. We have two different types. We have land areas or coverage areas, with the benefits of flattened surface or if it will end up as a zoning element.

And when it's getting import, we don't need to place the location system because it's already been taken from the Civil 3D. So in that spot, it's already been placed, and that's our surface. Because we didn't give a grading or another type of element, it's just picking it up with the-- with a default type. We can change that, or we can set up a different type of manual grading.

And an important fixture there, it's the source draping tape. So if we want the element platform to be on a particular level, we don't want it to drape, so it will go on a straight position. And it will adapt with the gradings. And if we wanted to adapt to the surface, we will use it with no drape.

AUDIENCE: [INAUDIBLE]

ENRIQUE GALICIA: In that case, because it doesn't have really a real topography, it may be just in whatever it picks. But if its topography is set onto the lower level, it will go however the surface is placed. For example, in that case, it's already with a grading of [INAUDIBLE] of 0.1. It's 0.1, and the other one is 321, so it will adapt when it's having the [INAUDIBLE]. But when it cuts, it's almost a straight.

In that case, it was a land area. The land area will work as a platform, but we can use it as well as a coverage. A coverage will be useful if we're doing some master planning and settings. This will be zoned for residential, industrial, or other elements.

What we can do with that is just, instead of placing it as a land area, we will use coverage. We can set up the rules style. Yeah, the rules style. And for example, getting a commercial one just being placed, so in that case, is with draping, a drape, so it will goes however the surface goes in the terrain.

Also, you can set it up to be without closing polylines, and that will help you just to have borderlines to [INAUDIBLE], all the elements. So as you can see, it will be really easy, and instead of trying to draw it in InfraWorks, drawing it on Civil 3D, have [INAUDIBLE] view imported, and then change proposals to review one with another one. And if you tried to do it on InfraWorks, it will take a long time. It's really, really take a long time. I didn't even-- do not do it on a flythrough on InfraWorks because it will take the complete class just to show up that.

So I'm just going to almost go to the first stop because I think I will have been talking a lot. Just want to see some insight. For this first section, what I want to pull up is what we have for bullet points of Civil 3D. Civil 3D will give us accurate typography.

We'll have all the points, all the elements, and they can draft having all the boundaries. Then we have surface analysis up to millimeter. We have rows and alignments set to center profile, so we can use that one being pulled up on the surface and then draw it by certain type of profile. And the gradings can be properly developed.

On the InfraWorks, it will looks better because it will be easier to move. Will show up the elements how they are being placed. The analysis models will be much more easier because, if you want to do the same type of analysis, you get an InfraWorks for colors, you need to change surfaces tiles on the elements in Civil 3D, and that may not-- may take a little time, so you can have different schedules and change them. Roads can be optimized for each set. Gradings can be visualized or changed between the different types of elements, and models from other platforms can be inserted in InfraWorks.

So before passing to the other one, I just want to have maybe two minutes set to questions for this part. Or just breathe a little because I have been just pulling it up. Questions?

AUDIENCE: [INAUDIBLE]

ENRIQUE GALICIA: Sorry?

AUDIENCE: [INAUDIBLE]

ENRIQUE GALICIA: Yeah, yeah, for example, I use it those-- I have been use it for projects. So what it does is it gets the information from topography, gets coordinated, pull it in through InfraWorks, and you're jumping just around from one to another one because there are things that you cannot do in InfraWorks or Civil 3D. So I'm going to show you some examples at the end of how everything gets pulled together once you have the complete circle from the three of them. But so far, we have just jump InfraWorks, Civil 3D.

Question? Somebody else? Ah, you have your-- yes. I bring some candies, so just-- just to put it up.

AUDIENCE: [INAUDIBLE]

ENRIQUE GALICIA: Yeah, it's good. Yeah. So see if somebody else-- questions? It's good, because they'll get feedback, and then I get out of [INAUDIBLE].

AUDIENCE: [INAUDIBLE]

ENRIQUE GALICIA: Was difficult to get the bowl.

AUDIENCE: [INAUDIBLE]

ENRIQUE GALICIA: Yeah, yeah, yeah.

AUDIENCE: [INAUDIBLE]

ENRIQUE GALICIA: Yeah, yeah. Well, no, it's not from Google Map. We have it for Bing service, I believe. It's from--

AUDIENCE: [INAUDIBLE]

ENRIQUE GALICIA: What it will do is, from the Model Builder, it will pick those two from a server. So if you go-- for example, this is going to pick at that one really quickly. For example, if you go from here on the data sets-- the data sets-- [INAUDIBLE].

What it actually does, for example, in this case, is connecting to-- [INAUDIBLE]. That's not [INAUDIBLE]. It's a SQL Server. Where's-- just [INAUDIBLE], yeah, that's it.

Yeah, [INAUDIBLE] so here, a big map, and then we get the imaginary off your surface. So actually, the topography you have there won't be accurate because what it's doing is just having a difference on how the image goes. So we actually will vary almost up to 10 meters height, so it's not good for a project in any other way.

But you to have a real typography element in place and then be linked, but if you're just hanging around checking how the surface goes and placing some elements to have a general idea, we'll be fine. Anymore-- [INAUDIBLE]. Hope you like it from [INAUDIBLE], Anymore questions?

AUDIENCE: [INAUDIBLE]

ENRIQUE GALICIA: Yeah, just [INAUDIBLE]. Yeah, for example, in this case, just-- [INAUDIBLE]. Does everybody here [INAUDIBLE]?

So for example, in this case, we have the surface. Just going to hide it on this real quick view. Just pulling its [INAUDIBLE].

So for example, in this case, it works [INAUDIBLE] like that because it's going to break the boundary lines when we export it to Revit. We have a lot of lines, so we can change it from the style, from example of 525-- we didn't [INAUDIBLE] too much. That's because [INAUDIBLE].

I just-- yeah, sorry, sorry. It's-- we need to turn this one off. There you go. And existing ground-- we can change it so it was-- yeah.

For example, if you doing like that, it will be easier because it has less points, less elements. So if you're using that for a general setting in Revit, will be fine. If you go to the details, you may need to split it up into small sections, and you can go up through there to the level of project and then import it back.

For the case of InfraWorks, it won't really matter because it will pick the surface as [INAUDIBLE]. I cannot give you [INAUDIBLE] because it's-- OK, but as you can-- [INAUDIBLE]. So OK, let's continue. So far so good? Great.

So now we-- how do we get that information on Revit 2018? Well actually, 2018 is not too much of a difference, so I'm just going to open it. And in Revit, the advantage we have is that we have, here, the topography. We can set up the elements to have a volume from the [INAUDIBLE] face. So if we're moving and pulling out, we have that decision making, and it's different volume.

And also if we connect it with Dynamo, we can set up a value for having different mixes on landscape and all those other elements. Not to [INAUDIBLE], we're-- I'm not going to touch too much Dynamo in this class. It's-- we'll be fine. So you can get the building paths, and all of those elements will have their own properties their own ID, so we can use it for scheduling, for moving, for changing, for having the material's elements pull in and out. So without really, really easy--

AUDIENCE: I'm sorry.

ENRIQUE GALICIA: Yeah?

AUDIENCE: [INAUDIBLE]

ENRIQUE GALICIA: In that case, I believe it's whatever the InfraWorks picked from the picture.

AUDIENCE: [INAUDIBLE]. I mean, how can we-- how do we confirm that this is the [INAUDIBLE]-- the actual [INAUDIBLE]?

ENRIQUE GALICIA: No, we need to change it from the topography one. I mean, the one that [INAUDIBLE] really brings with InfraWorks won't be good enough for making some design. And it just will be helpful for having a general idea, but quite vague. It won't-- because--

AUDIENCE: [INAUDIBLE]

ENRIQUE GALICIA: Yeah. Yeah, because if the picture gets the [INAUDIBLE], and the other one doesn't have, it would make something like this. So that's why I'm talking to you about having a 10 meters difference, maybe more. It depends on how big you InfraWorks file is. So it can be used for proposal, but if you get the topography, the real topography in it, now you can trust it. It would make a problem.

So let's continue. Question? No, OK.

So we need to coordinate both files, so the first thing we need to get is this coordinated. The end of coordinate, because as we can recall, we get it from the model properties. They meet the minimum and the maximum elements, and we want to make it on the same grid.

When we pick it up on AutoCAD Civil 3D, what it will go is from the 0 origin to that point with this reference that says x, y, and the z value is picking up on height. So we will use those references because, with those, whatever we do on Revit using the same origin point, it will export exactly on the same position. And that will help us to create and see how everything is filling up.

So next one goes-- this is not [INAUDIBLE]. So for doing that purpose, what we'll pick is the lower end. It's the same one we got from the InfraWorks model. We will check up the properties to see how it goes from x, y, and z values.

We will save those, as well as the other ones. [INAUDIBLE] give me too much time to pick those [INAUDIBLE]. Good.

Actually, it wasn't quite accurate. It needs to be-- OK. Just going to [INAUDIBLE].

So once we have those values, what we're going to do is, in a Revit-- a Revit fire, we need to check units are properly set. Units need to be on the same-- we're using it. And we need to check for the origin point.

The location settings, we're going to place there. Instead of using the location by a pin, we will use it on the false city. And with that, we can place here, on latitude and longitude, the ones we got from our InfraWorks file at the beginning, the ones that we get from the model properties on the mean setting. We can use those, so they're going to have the same behavior on weather conditions. [INAUDIBLE]

[LAUGHTER]

Well, if you-- if you have a question, it's really, really fun. Yeah, it's excellent.

AUDIENCE: [INAUDIBLE]

ENRIQUE GALICIA: Yeah, just-- OK. So just-- yeah, sorry, I just get-- yeah. We have the line. That's it.

And we need to see, for this site, the break base point. The break base point, even though we need to place it-- even though it will be always 000 for all the elements in the project, we get geometry analysis or we get the coordinates positions for an element. It will be reflected to that 0, 0. We need to change it there.

So if we're coordinating multiple projects, they will have the same belonging within the areas we're setting. So we can use [INAUDIBLE] origin to origin with those elements, and then we'll get together connected. So we can cut, set, and make separate sets of surfaces. So I'm using those.

The coordinates I'm using there are the ones we get from the Civil 3D from the starting point to the endpoint. So all the files can go from InfraWorks to Civil 3D. Civil 3D will set up the bunch of images and services. And with that, it link Revit file with Revit file. It will have the same coordinate system, so it will be in the same position.

So once it's moved, what we need to do is we need to copy. Finish-- [INAUDIBLE]. I-- I'm not [INAUDIBLE]. Just-- that was out of-- [INAUDIBLE] copy.

So we have it there. We have change, and we have the [INAUDIBLE] address here with the coordinates from InfraWorks, and we have here with the coordinates on Civil 3D. And then we need to make a copy of this AutoCAD file so we can move from that origin to the 0, 0 and import it like that so it will make it a clean reference for our Revit file. I'm just going to [INAUDIBLE] little that.

Yeah, so we will move that topography to the 0, 0, and that is where we need to check how our boundaries will be changed from being just in a state of one and five, five and 25. But it will depend how big the [INAUDIBLE], and how much we are going to work at the same time on the Revit model. So I'm just placing it there.

Once we have it, we can save it, and we will explode it. So we will have just the lines, and then import it to Revit, to have the same settings. Just [INAUDIBLE], so it doesn't have anything else. We're reviewing if we have the lines, and move a little. There.

And with that, we can use it as a reference to create a [INAUDIBLE] on site. We'll make a topo surface from a link. Then we have all the layers that the Civil 3D file has. We are the only ones who will use that topo major and minor.

That will set enough points, so we can use those as references for building [INAUDIBLE] and how we plan to mix elements together, just seeking under three dimensional. We have all the points. Just to look at shaded, and we fine. I'm just going to jump a little. OK.

So we have the [INAUDIBLE] Revit, and the good thing with that is that we can now create building paths or other types of elements. And the reference we will get is when it has the point, or the starting point, we will have that level. We can also set it up to be the same height in level 0 or to set it up at proper level for the surface. So when it's changing the height, we have that one set on the base break point, but the levels can be [INAUDIBLE] to a local origin. So I'm just going to [INAUDIBLE] a little from here.

So with the building parts or all the elements in Revit, now we have it there. We can use it, export it as an FPX file or a EFC file. It will depend on how we're getting on performance or in look. We do it with FPX file, it will might be bigger, a lot of elements from the materials. If we do it from a mere EFC file, it will [INAUDIBLE], but it will be good for analysis on how the elements are being placed.

Then I'm just placing there some floors and some walls, hiding the topography. And with that, we can configure that to be a building element. The building element needs to have an x, y, and z, so we already have those because we have our model [INAUDIBLE], and we have our height. So it will use the same latitude and longitude elements from the xy because we're using 84, and with that, it will place the elements in the same position.

So I'm just going to jump like that. So in this case, it's just plane concrete, so it won't look too much. But just already have it there will be good because you have that-- you share it with whoever is doing the project. They have it on Civil 3D, and they just upload the new file of every x, and you have the coordinates. Everything's set so you can review how it has the changes.

AUDIENCE: When you said FPX was going [INAUDIBLE]?

ENRIQUE GALICIA: No, EFC will be lighter. It will have no performance issues, but it won't have materials, too much materials. It will be just blank. It's for analysis. It will be lighter.

If you use FPX, you will be charging the materials elements, so you have a lot of polygons, and it will looks better. But it may help you. It may not help you as you want it. So just a quick overview on that because we're-- OK.

So we have Revit uses parametric objects. Constructs by links, so you can have several multiple elements or projects within Revit. And those can be linked together, so you won't have a problem with how link those elements. Detail elements integrate in topography.

You can use Dynamo tools for setting everything together, and you have sustainability analysis features on Revit. Also, with Revit, you're just Massing and Site tools. You have Dynamo tools for complex elements and building parts for quantity analysis. Just going to get to quantities.

So if we see, for quantities, we have that the InfraWorks is not-- you can have the distance and elements, but not actually to get the volumes there because it will affect on how the surface is being placed, and you need to have a collaboration between both. So I don't recommend you to do it that way because it would-- it can be different values than what you actually get. The best way to do it is using quantities from Civil 3D.

In that case, what we can do is just export the resulting movement that we get from the SDF files, or whatever we get from the Revit, and then compare them to create a surface of difference between those two. In that case, we have on the left one, one that shows how much is being excavated and how much is it getting filled. Just going to go from here. And then in Revit as well, we need to use this process that it's for having a surface, so it gives us the right elements.

So what you do actually is, once you have that surface, you need to have two faces being placed. The original one will need to go on an existing surface, and then with that, you can change the view, so it goes on New Construction. You create the building paths however you need it with different settings, so however.

This is the footprint of the building. For example, like that. But it won't tell you the volume on-- OK, I'm just going to--

[LAUGHTER]

Come on. Hey, come on. OK, OK, OK. Well, at least, everybody will [INAUDIBLE] smile in the [INAUDIBLE].

And then we use a graded region. Graded region is this option that will create another topo surface within the new one. That will give you these volumes-- the cut, the net cut field, the field and the cut. So actually, now, if you're moving the topo surface that-- if you're moving the building path, that topo surface is getting you the new quantities and how things are getting built together.

AUDIENCE: [INAUDIBLE]

ENRIQUE GALICIA: Hm?

AUDIENCE: [INAUDIBLE]

ENRIQUE GALICIA: Yeah, in that case, the only way you can do the fill, if you want to have it-- because the building paths will only give you something that is a square. It's completely plain, and if it gets completed, you will need to have that setting. The only thing you can do is to work it in with Dynamo. So there will be [INAUDIBLE], because otherwise you will need to create some mass or create some lines of borders, and Revit won't do it as itself.

So I have some examples of that if you want to. I will-- I have shared some of the courses for that. As well, you can ask me, and I can tell you how you get those scripts for having from one side to the other one, and it connects to the topo surface. And I will help you to do those in-fills because otherwise, it won't be possible. It's not possible.

So we have seen quantities from Revit, and then we have [INAUDIBLE] back. The only thing that it's missing here to complete the circle is how do we get those building parts surfaces into the InfraWorks? Because we decided where it goes, but if we just export the model, it will make the holes because we need to change the surface. The surface needs to have a new land area, so it goes down.

So the workflow set here is using Dynamo, just a simple script. And with Flux-- somebody has heard about Flux? No, [INAUDIBLE]? OK.

And with Dynamo, what it will do is just to get us the polygons of where are the building parts are set, so we can have those polygons. And with Flux, we will export back to AutoCAD. So just a general review-- well, I'm just going to skip this one. Won't make too much-- just going to quickly because we're almost done. [INAUDIBLE]

So Flux-- it's a really good product. What it will do is just-- it adds plugins from Dynamo, and it will just export row data, simple data. So you're actually not having a new file and having it because, as you have seen through the complete lecture, for each of these, you have a file that is from InfraWorks [INAUDIBLE] to Civil, back [INAUDIBLE]. So for the case of this, if you have it for different types of elements, you can have just key elements, and that will help you to export. So for example, I'm using here a mix between Dynamo and Revit. It's just a single script.

Not going to go too deep in this, but what it will do is just graph a face-- that is, these faces that we want to get, the ones that are on the lower part. Those two. Once we have it-- just need to coordinate better with myself.

Once we have it, we will get the perimeter curves. Then it will transform them into a poly curve, and that poly curve will be pulled for AutoCAD using Flux. So it gets a line of two lines elements, just connects a project. Send it to Flux through a key setting.

And if we connect on the other part-- this is on our own Civil 3D. We just connected the Flux there. What it will do is it can receive whatever data we have.

Let's call it. It's loading it, and we will have it on our CAD file. So we just need to put it out to the origin, and we can export that in an SDF file and [INAUDIBLE]. It will go down. So with that, we can complete the circle on having, now, our project on Revit, changing the surface, and then place it again into InfraWorks.

So just going to jump to the other one. You see, those are the two elements being pulled from Flux that the surfaces that were in Revit could save us an SDF file. It opens up in InfraWorks, and you have those two surfaces in the same area. So once you explore it, again, your project from Revit, you will have it on this spot, and it will have the excavation and settings. So you have it there.

So we're going to go for the [INAUDIBLE] examples, where it's-- yeah, OK. That's it. So from [INAUDIBLE] examples, we have this one that Huatulco, and the thing he was-- it was just that 72,000 square meters was not possible just to handle it in Revit. So he wants to split it four different types of models.

[INAUDIBLE] InfraWorks and Civil 3D topography coordinated, and it had a lot of reviews between roads, excavations, and elements because it wasn't a really hard soil. So the problem there was, if they didn't take too much attention on how much to excavate, would be a high cost project. So that would be the direction of all of them.

So that's phase one. It's one setting here, that it's also on the mountain. It's all these elements and all these land areas were pulled from Revit. Mix it with the Civil 3D, and you have the other one as well. So it's mixing up a lot of landing, and it looks quite easier than just showing it on-- well, you cannot show that on Civil 3D with those six elements.