AU Class
AU Class
class - AU

Site Grading with Corridors in AutoCAD Civil 3D 2018: Everything Has Changed!

このクラスを共有
ビデオ、プレゼンテーション スライド、配布資料のキーワードを検索する:

説明

Site grading with AutoCAD Civil 3D software has traditionally fallen short of what we think of as true 3D modeling. We typically generate a finished grade surface, but we're not truly modeling our site, including curb, sidewalk, ponds, subgrade, and so on. Well, all this changes with AutoCAD Civil 3D 2018 software and the new features that finally make site design with Corridors a realistic option. New features, such as Corridor Baselines from Feature Lines and "bow-tie" cleanup, enable much more-dynamic and more-stable site models then previously found with traditional Feature Line-only and Grading Object workflows. This class will walk through how to set up a truly dynamic Corridor site model, showing realistic application of new and long-hidden features in AutoCAD Civil 3D. We'll then show how you can harness this data-rich model, including Quantity Takeoff (QTO) in both AutoCAD Civil 3D and Navisworks software, as well as site creation in Revit software. Come join us and learn how site grading just got a whole lot better!

主な学習内容

  • Understand how to build dynamic and stable Corridor site models with AutoCAD Civil 3D 2018 new features
  • Learn how to create truly 3D models of your site, including curb, subgrade, sidewalks, and so on
  • Learn how to extract data-rich AutoCAD Solids from your Corridor for use in Revit and Navisworks
  • Learn how to make your project architect happy with detailed 3D model exports, eliminating virtually all rework typically required in Revit

スピーカー

  • Brian Levendowski
    As a Civil Engineer, Brian Levendowski, PE is the Civil Product Manager for CTC Software. He spends his time developing custom applications and plugins for Civil 3D, AutoCAD and the Infrastructure industry. He is a highly-rated and seasoned Autodesk University Speaker, specializing in serving the civil infrastructure industry. He has lead many advanced implementations of BIM software, including Civil 3D. He speaks regularly at regional and local events, conferences, and professional association meetings. With a practical background as an airport design engineer and inspector, as well as a land surveyor, he has valuable real-world experience, and truly understands the application of Autodesk software in the civil engineering industry.
Video Player is loading.
Current Time 0:00
Duration 1:22:57
Loaded: 0.20%
Stream Type LIVE
Remaining Time 1:22:57
 
1x
  • Chapters
  • descriptions off, selected
  • en (Main), selected
Transcript

BRIAN LEVENDOWSKI: I am Brian Levendowski with CTC out of Minneapolis, Minnesota. This class is site grading with corridors in Civil 3D, everything has changed. Not literally, but a lot of things have changed.

My background, I'm a civil engineer, I worked in aviation design for about 10 years, did a lot of surveying. And I've been with CTC for about the last eight years. I'm a consultant to folks like you guys, and I spend my time figuring out how to make this software work. So hopefully I've got something for everyone here today.

I do want to mention one thing. The handout was not on the website, I apologize for that. I sent a message to everyone, hopefully you got it.

I made some changes to the processes here and I didn't have time to change the handout. So I will have that in the next few days. Might be in the next week, but I'll get it to everyone. It'll be a detailed handout so don't worry about taking rigorous, detailed notes. Just watch what I'm doing, understand it, and the details will come in the form of a handout.

So let's start with why, why corridors for site grading? It's more dynamic than feature lines, right? How many of us do most of our site grading with just feature lines as brake lines on a surface, right? I mean, that's the tried and true way, it's simple enough, but it's not very dynamic.

You're basically managing all these points and these slopes, and it gets to be a lot of stuff. Why corridors? They're more stable than grading objects. Grading objects are kind of cool, they can give me a daylight, they can do these different things. But then if I look at them wrong, they just disappear. So corridors are a little more stable than grading objects.

And this is some of the big stuff here, it's richer model data. I mean, when we grade sites, for the most part, we're grading the finished grade, right? Well, I care about a datum surface, I care about how many materials I have, all sorts of things like this. And so with a corridor, we have assemblies and sub assemblies, we get a lot richer data out of it.

In y corridors now for site grading, why not four years ago, five years ago? Because there's some new features in '17 and '18 that really kind of make this all possible. To me, we've just kind of hit this threshold now, where we can use corridors. And the Autodesk team has really done some work with this aim, us being able to use corridors for site grading.

So some of the old methods here, grading with only feature lines, these are some of the assumptions here, the prerequisites, is that we know how to do at least that. We know how to throw feature lines on a surface and grade in that way. Why don't we want to do that anymore? It's tedious, it's not dynamic, there's no subgrade. Feature lines and gradient objects, really buggy, no subgrade or model.

So let's understand some of these new features here. How many people are using 2018? OK, just a small, small group. How many people are using '17? OK, and '16? OK. So everyone needs to get to '18--

[LAUGHTER]

--if you want to do this stuff. So hopefully I'm your motivation to roll out '18s to your offices.

Here's a couple of the items that I'll showcase here today. Feature lines as corridor baselines. Just like this, your baseline option. And create corridor now has the feature line option. We can link feature lines to surfaces.

So in that wonderful elevation editor that we all know so well, you have a relative to surface option there. The default is absolute, where you're just managing that vertex elevation. But we can make it relative to surface.

And then there is what's called corner cleanup, or bow-tie cleanup, where we can have concentric back of curb to a flow line. Like when you ran a corridor before '18 around a 90 degree corner, it wouldn't make nice, concentric lines. It will now do this magical stuff for us. So that's a big plus.

So corridor site grading, what we're after, what we're going to do today is make this model. Using all corridors, but we're using alignments, profiles, feature lines, a number of assemblies and sub assemblies. And we're after this because, again, of all this data we can get out of it. Surfaces at multiple levels, data we can pull out of it, we can push this into Navisworks, into Revit. And it's not just a finished grade 10, it's an actual model. We can pull solids out, we can pull a variety of different things out of here.

So some of you might look at this and go, yikes, we're going to click through all of this. I'm not going to click through all of it. I've got key steps, stages I'm going to bring you guys through, through nine different drawings, kind of show you the step, the process, here's the key way to do it here. And we're going to leap from one drawing to the next.

Unless-- I mean, we can hang out for five hours if you guys want.

[LAUGHTER]

I can't, in 90 minutes, not pre-bake some things here. But the point is, I'll communicate these strategies, these workflows, and then when you kind of get it, we'll jump to the next drawing and we'll kind of run with it from there.

So the process, the workflow we're going to go through here, we're going to start with grading out our parking lot. Oftentimes that's the most complex part of a site, of a building site. That's our example here.

And what this parking lot drainage surfaces is, is to be creating a simple surface with just feature lines. We all know how to do this, throw feature lines on a surface. This concept, making this surface like this, this isn't new. But I'm using this process, this concept of a drainage surface in conjunction with corridors to give us a much more dynamic model in the end.

So all these steps here, I'm going to walk us through in the software. We're then going to create alignment and surface profiles from the drainage surface. So that surface we just made right here with these yellow feature lines, we're going to then make alignments and surface profiles cut from that surface.

So this concept stems from the idea that-- what is parking lot grading vertically? It's a fairly simple design. I just want sheet drainage this direction, like I've got swales and ridges. And it's not that complex vertically, but it tends to be complex horizontally. I've got all these little curb islands, I've got curves, and all these little things.

But vertically, it's fairly simple. So this concept is where we separate the vertical design from the horizontal design. The vertical design is accomplished through a basic surface of yellow feature lines that you see here. And we can very easily use some of the basic feature line tools to edit this and start to control the drainage pattern of our site.

And then, what is a surface profile? It slices wherever that surface is at any time, that path. So these magenta dash lines here are going to represent our flow line of our curb lines.

How many people does this concept kind of ring a bell, where you make a drainage surface or a drainage scheme surface? OK, so we're still using this. But what's going to be new is, we're going to stack corridors on all this stuff.

So we're not just doing grading objects and feature lines attached to that, we're going to put corridors on them. So with those curb alignments, they're going to attach corridors using fairly simple assemblies like this. And then we're going to target out to a series of feature lines, and we're going to introduce a second set of feature lines here.

So I've got a drainage surface made from those yellow feature lines. And then I'm going to draw other feature lines that are relative, or stuck to, or draped to the drainage surface. And that's going to allow me to basically parcel up my parking lot, my drainage pattern in ways that might vary from the actual drainage surface feature lines themselves.

We're going to use things like relative to surface, and we're going to use a feature that's been here for a long time, which is feature line style hierarchy. How many people know about this? Yeah, it's this hidden thing, it's been here a long time.

So two feature lines cross, I have to assume the same elevations if they're in the same site. And then there's this rule about like, well the last one edited is what controls it. Then you forget how it works, and it does some weird things, right?

If you assign one set of styles to one set of feature lines and another set of styles to the other set, you can control the hierarchy of those styles. Meaning the one you want to always control, put that style at the top. And then every feature line with that style will always control. So we're going to basically drape target feature lines on the drainage surface.

So this little screenshot here, this might look familiar. Maybe some guys have gone through this, graded parking lots with corridors. We could do this years ago, this has been here for a long time. It's those little things that just didn't make it worth it. In my opinion, it's the lack of these features right-- where did I go-- right here. The corners, they look like crap, right?

I couldn't link these feature lines. It became really tedious to manage all this data. And while we'll use alignments and profiles for a lot of the curb lines, we're also going to use feature lines for some things.

All right, so moving along. Next thing we'll grade, we'll have a pond adjacent to our parking lot. And we'll talk about, how do you join those two together? And I don't mean, just draw feature lines and throw them into a surface. We always want things dynamic, I want to be able to move my pond up or down, move it around, change the size of it and have it always stick to or grade to the back of the parking lot.

So we're going to define a common feature line in here that is partially relative to our existing grade, but then also something we can use to just massage the contours and the surface in that area. And we're going to look at some miscellaneous building grading here. This is going to be a separate corridor, just like the pond. And it's just to be grading around our building.

So I know every site has got some unique feature to it. I'm not going to be able to cover how to address every scenario here. But some key ideas I want you guys to take away from this, and then you can run with it from there.

All right, we are starting in this site. I've got a preliminary horizontal design here. I've got some polylines, we've got a building outline, and somewhere over here I'm going to put a pond. We're going to start with grading this parking lot, then we're going to grade the pond, and then around the building. And again, I'm going to step through some of these drawings because you guys don't want to see me click through 1,000 different screens.

So if I'm missing something, please raise your hand, interrupt me. There's a lot of stuff to go through here, so please interrupt. So first things first, we need a drainage surface. I need to dictate how this thing is going to drain. And I've cheated a little bit here, I have some polylines ready to go with this kind of stuff.

What you want to do to make a drainage surface, you want to think about how your site is going to drain overall. And you want to use a set of feature lines that's as simple as you can make it. I'm saying I've got an entrance up here, I need to drain away from here, I need to meet ADA requirements. I've got to tie into existing here, and over here. Existing grade itself falls back this way. I have all these considerations, right?

What we want to do is create feature lines from all of these. And here's where this feature line style starts to come into play. I've got a grid feature line style, and I'm going to throw it in site one. All my feature lines are going to go in that site one.

I'm a big fan of using feature lines styles with layer zero in them and then letting them use the selected entity layer. Oftentimes you might be drawing some geometry, polylines, and you just throw it on a given layer. You can let that layer continue to control, just strip the layers out your feature line styles.

I'm not going to assign elevations right now because I have some elevations on their. We want to then take these and throw them into a surface. I'm going to make a new surface here, we will call it grid.

My add breaklines dialogue box. If you guys don't know what this is, how often does it triangulate along a segment? If I've got two vertices that are 100 feet apart, how often does it 10 along those lines? If I put this at 10, it says triangles are no more than 10 feet apart. It helps you get better triangulation, better contours. This is how it triangulates along curves.

A fairly basic surface here. And what I recommend is to be using-- build some basic line or curve labels that-- let me turn on my layers here-- that label slope and spot elevations. So these are just basic line and curve labels, can build these things.

Then as you work with this, you throw these labels on here, I need to kind of roughly, preliminarily design my site. How is this thing going to drain? Well, I've got all these little callouts on here.

I can use Quick Elevation Editor. If you're not using this tool, you need to start using it. If you're stuck on Elevation Editor, that's great if you're mass editing a whole bunch of points at once. I really recommend using Quick Elevation Edit.

Because I can do things like, well, 816, yup, that's where the entrance is. Let's grade down along the face of the building at a negative 1. Make sure my surface is on rebuild automatic. And it's this really interactive way you can grade your site.

This look familiar to people, doing this kind of thing? Right. This is a really tough place to work. Point by point, don't do it here, do a Quick Elevation Edit.

So I don't want to spend a ton of time on grading this, designing this out. I have some preliminary grades in here. I'm going to move on to the next step.

One thing I want to do though, is point out, we need to tie into existing here too. So we also need to have created a few feature lines-- if I turn them on here-- right along the existing where we match in. Those are thrown into that surface as well. So I have this whole grid, this pattern that basically is the drainage pattern of my parking lot.

What we want to do from here then, is to be-- let me freeze a few of these. We need to start building our corridor. And we need to think about how this thing is going to build. So the standard rule is, we build assemblies where we have the flow line right along the alignment, or along the baseline here.

So if I go-- I've got some assemblies ready to go here and they're fairly simple. And this curb island right here, I want to run a curb around it and I want to target out from that. But I've got curb over here. If I run this and then I target this way, how do I target back?

You have to start thinking of breaking up your parking lot into panels. That's the best term I can come up for it. And this works really well with this whole feature line relative to a surface option we have.

So I've got a polyline here. OK, this would be pretty straightforward. If I take this and then I just target this thing, the lane is just going to shoot out around it. So here's where we introduce these secondary target feature lines.

So let me show how this is going to work. First we'll build-- let's call that left curb island. We're going to make a surface profile and we're going to cut from that grid surface. And I don't even need a profile view, I just need the data to slice from there.

OK, now we know that that elevation is dynamic to this. That's what we're after here. So as I continue to build out my corridor here, everything is still controlled by this. So I'm never editing the profiles in my corridor, I'm only editing these yellow feature lines.

Let's build our corridor. It's like parking lot. I'm going to build it from alignment and profile, the left curb island, and the surface profile I created there. And then the assembly, we want one with pavement on the right and curb on the left, this one right here. OK, fairly straightforward.

There's no target surface and we're going to turn off the baseline options there. Now that builds my corridor fairly simply, but now I need to take this and I need to target out to this thing right here. So let's create a feature line from this.

I'll give it a name. Feature line style hierarchy comes into play now. What if I give this the same style as those yellow ones? Now they're kind of fighting over which one controls.

I don't want to touch this feature line. All I want is for something to be something that I can target with my corridor. But its vertical elevations need to just stick to the gradient surface.

So if I set-- I've got a style in here just called targets-- and assign elevations, and elevations are going to come from the grid surface and they're going to be relative to the grid surface. That's dynamic, it sticks to the surface. So feature line hierarchy, where does that come into play?

Go to your site, you right click on the feature lines category and go to Properties. Right in here is your feature line style hierarchy. If grid is on the top, the grid feature lines will always control. This has been here for years, but to me there's never been a great place for it until some of these other new features came along.

It's got a nice 3D view here. Gonna turn off my existing as well. So all I'm after right here is to have that connect out there, simple targeting. I like to do all of this through the ribbon. Use your corridor region editing up here, edit your targets through here, and I just use the layering option.

So set this stuff up ahead of time. Understand what layers things go on. So I've got curb island left targets, it pulls that feature line in, and I want to target it for both with an offset as well as elevation and slope. OK?

One of things we're after is a dynamic model. Not just a datum surface and a full model, but I want a dynamic model. I want everything to stick to my drainage surface. That's just exactly what we've done. I've got a surface profile right here, and I've a feature line that I'm targeting that sticks to the grading surface.

So let's just make a change of sorts here. Pick this feature line, this one right here. So edit that. If we look over here in 3D, there's my target feature line, I see that just went up with it. Rebuild your corridor and the corridor updates within.

This is the basic concept here. I've got a grid surface, keep it as simple as I can, as detailed as I need for my drainage pattern. I've got target feature lines, and then I have alignments and surface profiles.

Some of you might be asking-- and this is actually why the handout isn't ready-- why don't we make a feature line for this? If I can build corridor baselines from feature lines, why don't we just make the curb island and all the other curb a feature line? Turns out, it gets really unstable when you have a feature line relative to a surface and then a corridor stuck on top of that.

It was really unstable, lots of crashing. And you get a similar thing with alignments and surface profiles, it's dynamic to the grid surface. So we're all good to go.

Can build a basic surface in here. And at this point, I'm going to turn off this surface. So we've got different areas to deal with.

I've got another area I can make a panel out of over here. So the curb islands in the middle, it works to make these panels. The panels don't necessarily have to run on your grid surface feature lines. I can make this shape anything I want.

This rectangle I drew around here for a target, it could have gone wider than this. But what happens when you do that? Well, if I target from here to a line over here, it wouldn't pick up the ridge or the swale here. So you kind of have to follow your grid lines.

But here's the kind of general rule, is draw targets wherever you need them. Make them secondary in terms of the hierarchy and just drape them to the surface. Right in the middle here, this is fairly straightforward. I've got an assembly running along this feature line right here, I target the feature line over there. Easy peasy, right?

Questions so far, is everyone with me? Is this making sense? Yeah?

AUDIENCE: In order to target the feature line that you created, does each feature line that you're targeting have to be [INAUDIBLE]?

BRIAN LEVENDOWSKI: It doesn't. I just like grabbing targets with layers. It seemed a little pointless here, but when we come down here, I'm going to have five, six targets. I don't want to go and pick them all, so I pull them in with layers.

And for some reason, the prompt to go select in drawing-- I don't know if you guys get this. Those of you who are using '18, to go select a feature line target in the drawing, is there this big delay for you?

AUDIENCE: In '17 too.

BRIAN LEVENDOWSKI: '17 too? Yeah. I thought it was just because I had a Mac or something. So for the purpose of this demonstration, I use layers.

So let's move on to one of these regions here. So I've got an alignment up here, same concept. I cut a surface profile for my drainage surface.

And now I'm going to break this up a little bit. Instead of running my lane and then targeting out from there and then having my curb on the other side, that starts to fall apart when we want to take advantage of the corner cleanup, this is the new feature in there. In order for my curb to run around this 90 degree corner, all the sub-assemblies as I understand it need to have constant widths in them in order to get a concentric corner on here.

So it's not a big deal, we'll just make two baselines. On one side I'll build the curb, on the other side I'll build the lane. So let's go ahead and turn on some line work that we're going to use for targets.

So here's my outside, my perimeter curb here. From here I'm going to be targeting this feature line. I'm going to target this. I'm coming all the way around here, targeting right along here.

And then I'm going to get in this situation where the corridor starts overlapping itself. So let's first build this, and you'll kind of see what I mean here. And we're just going to use this basic sub-assembly right here, just a simple lane sub-assembly on it.

So I'm going to pick my corridor, need to add a baseline, and it is going to be my north curb. I get a big delay right here too, just select my profile. And it's going to be that grid surface profile. So I'm adding a baseline.

How many of you guys use the ribbon here for adding baselines, adding regions? I mean, compared to corridor properties and the parameters tab, I mean, when you get a lot of stuff going in your corridor, I think it's a lot easier. Because you work region by region for the most part. This panel right here is really nice.

All right, add a region. It highlights for me. And now I can just say F for fill, which means, go the full length of it.

And I want right pavement. So zero station is here, I want the pavement on the right, hit OK. And if I ignore the targets for a moment, you'll see what we get here. And now I need to run some targets.

And here's where the layering really comes in handy, because I've got a number of feature lines that I haven't made yet. Let's create those. So these are all my target objects. Again, what do we do with these? We make them relative to the grid surface.

And I give them a style so that they're dependent on the grid surface. So assign elevations from the grid surface. You can make it relative, like it could go 1/2 a foot above. There's all kinds of ways we could be doing this.

If we didn't do the corridor, I could make my back a curb and my flow line, they could both be relative to a grid surface. If I just decided no corridors at all, but I want to do the grid surface option. Lots of ways to think about this.

All right, I've got some feature lines, they're draped again, stuck to the grid surface. I simply grab my corridor and I've got a layer setup that will grab all of those targets. You guys use this layering option?

Conditional sub-assemblies, if you guys use those. Like big projects, you could have like 20 targets. You don't want to go pick that stuff. Or maybe you get paid by the hour and you do want to do that.

[LAUGHTER]

Yes. Here's some of these extra feature lines I drew. Because what's going to happen? It's going to start crossing over itself.

The corner cleanup in 2018, kind of sort of handles this. I don't think it does a great job, and that's why I just draw some extra feature lines in here to target this and manage this area in here. You do get one odd thing where it won't target right there. And there's a setting in frequency that says, pick up my offset target geometry points.

Well as much as I can understand it, this station right here, it's closer to that point than this station is. So that functionality only works over here. I don't know, it won't pick it up. I sweared at it all day one day and it just wouldn't do it. So you go and you add the manual thing here. Not a big deal, you can do it after the fact.

So what about the outside now? I've got to put my curb around here, and I want a nice looking curb. I want a concentric corner here. And this is where one of those new features, the corner cleanup come into play.

And so what we're going to do is add a new baseline. I can't run an assembly along the same baseline, along the same station. You can't have regions just overlap each other on the same baseline. Not a big deal, at baseline it's just a reference to an alignment and profile. I still have that one single alignment and profile.

So add a baseline, it's going be the north curb. We'll call the baseline north back curb. And we're going to grab that same surface profile if it lets us.

I get this on my computer. I think it's worse on mine. This is a four-year-old MacBook, a small computer. But do other people get this, that amount of lag? OK, so not many, it's just me.

So adding a baseline-- I really think it is just my computer. I had a baseline and then I do add region. And now my little Tooltip there say, hey, you've got multiple baselines. I'll pick the north back curb, that's the one I just did.

And what I want to do, I want to fill the entire baseline. Zero station is here, I've got curb on the left. There's no targets in there so it just builds.

And here's how this works, everyone knows how to rebuild a corridor, right? It just does it. This is one of the new features that, to me, make it worthwhile to be using corridors for a number of reasons.

I need to stake this. If it doesn't give me my nice back of curb and that's what I'm staking, I've got to do a bunch of manual work for it. It looks weird. I can't sleep at night when that doesn't look like that, it's like all these key requirements.

So the rule with it though, it's a limitation. Autodesk has done some really cool programming to make this happen. You can't have other sub-assemblies in this assembly that have varying widths. So what does that mean? I can't have a daylight sub-assembly, I can't have the lane sub-assembly that I'd be targeting and varying the width. I don't know what the algorithms do. That's the ways way it works though.

But what we do have as well, this is another kind of hidden feature new to Civil 3D, I can extract a dynamic feature line from this, and then I can build a baseline on that dynamic feature line, which means it basically sticks to and it's all connected. All right, so let's do that. Pick this back of curb and I just want the back of curb point code.

Extract, and I get this dynamic feature line. Calls it an auto corridor feature line. And so we'll name this thing North Back. I can add a baseline, it'll be a feature line, and it will be the north back feature line.

One thing to note here, I don't have in a site. This is a new feature as well, you can have feature lines not in a site. I don't want this thing interacting with my grid surfaces at all. This thing is attached to my corridor, I want it to stick at back of curb. It's just along for the ride with my flowline alignment and profile. So leave that outside of a site.

So I've got that baseline, now I do Add a Region. I'm going to fill the whole region, and I've got left daylight. Brings up my corridor mapping, EG, and it daylights.

Does it round the corners really nicely like grading objects? No, it doesn't. You can get crazy with it and do some targeting. But I can sleep at night with this, I'm good with that.

AUDIENCE: I've got a quick question.

BRIAN LEVENDOWSKI: Yeah, go ahead.

AUDIENCE: Is this all part of the same corridor?

BRIAN LEVENDOWSKI: So far it is, yeah.

AUDIENCE: You can have more than one baseline in a corridor?

BRIAN LEVENDOWSKI: Absolutely. You should have more than one baseline in a corridor, yeah. You know, as a general rule, parking lot sites, roadways, whatever, I like to put as much as I can in one corridor until it's too much in one drawing, it just slows down or is too much to manage. A number of reasons, but one of the main reasons is the corridor surface.

Like an intersection, there's so much going on in there. If you have that all in one corridor, your corridor surface, it's just one surface and it just does it for you. When I think of corridor surfaces, I don't really want to be touching those things. If my corridor isn't generating my surface properly, I'm not building my corridor properly.

The focus is on the source object, the corridor. So my rule for when I break a corridor, say there's a gap between my project, and I've got a road project and there's a bridge I'm connecting, an existing bridge, I'd separate those. Because the surface boundary thing falls apart when you have gaps between your regions. And then separate it when it's just too big, there's too much in one drawing, you could put it in another drawing for example. Other questions? Yeah?

AUDIENCE: Is there any advantage to doing the two separate baselines for one for the daylight, one for the curb assembly rather than making daylight the target first?

BRIAN LEVENDOWSKI: Yeah, yeah. So the question is, is there an advantage to doing the two separate baselines? And I assume you're talking about right here at the flowline where on one side we had the pavement and on the other side we had the curb?

AUDIENCE: No, [INAUDIBLE]

BRIAN LEVENDOWSKI: Or right up here?

AUDIENCE: --one for the daylight and one for the curb.

BRIAN LEVENDOWSKI: Yeah. So the same rule applies here. Why did we make a separate baseline here and why didn't we just put the daylight sub-assembly on the curb?

AUDIENCE: Right.

BRIAN LEVENDOWSKI: The curb won't do this. If I have-- so that's the rule, the little limitation, is that it won't do this thing, make a concentric corner if I have a varying width sub-assembly in my corridor region.

AUDIENCE: OK.

AUDIENCE: So you put the same environment in as two baselines--

BRIAN LEVENDOWSKI: Yeah.

AUDIENCE: --and just renamed the baseline?

BRIAN LEVENDOWSKI: I just gave it a different name. It would have given it a different name anyway. But yeah, you can have infinite number of baselines in your corridor with the same alignments and profiles.

It's not a good practice in a conventional corridor. But in this case, we want to take advantage of this corner cleanup thing so I got to jump through the hoops and make the second baseline. It's worth it though, because it's all coming from the same source. I'm not duplicating stuff, I don't have all this redundant stuff. Everything here is still stuck to the gradient surface.

Other questions? We'll move on if there aren't. Yeah?

AUDIENCE: You said that you would [INAUDIBLE] into different drawings if it got to [INAUDIBLE] just driving me nuts. So would you utilize your data shortcuts, and can you connect those two surfaces together?

BRIAN LEVENDOWSKI: Yeah. So the question is, you've got a big site, a big project, how do you break it up into multiple drawings and then bring that stuff back together? You can data shortcut in newer versions of Civil 3D, your corridor. So multiple corridors can go anywhere. If you're after a composite finished grade surface, data shortcut those surfaces and make a composite overall finish grade or datum surfacer, any number of them.

It's not great. Like, I wish we could just put an entire city in a drawing. But it won't handle it. But yeah, corridors, they are in 2018. I think that was '17. Yeah, they came out in '17. You can data shortcut them now.

All right, let's move along. This region down here, this is pretty similar now, right? I can run this along here, I can target along here. So I've got a set of targets along the south end. These green ones right here, these are my target feature lines, they drape to the grid surface, and I just target.

The hardest part of this process is not putting your targets on layers. It's not, remember to build the second baseline. It's, look at your site and come up with a plan. Because everyone's looking at this going, I never did a parking lot like that, mine always have the thing with the deal and the-- right? It's being creative and figuring out how you're going to build this corridor for your parking lot that sticks to your grid surface. That's the challenge, that's the hard part.

So this builds in a similar way. We're going to jump to-- look at that, it's done.

[LAUGHTER]

I built this in the same, same way as this way here. These areas where I've got inside 90s, I put a feature line there and I target. Again, you can do some of this with the bowtie cleanup. Let's actually do it right here. We're going to experiment.

That's what would happen, right? That looks like crap. There's clear corridor bowties. This mostly is great and like a curb return area where the daylight lines are crossing over each other. It can work here and there in this situation.

And so you have to tell it, specify a baseline. Well, I'm looking right here. Specify the starting subentity, that's right there, the ending subentity right there. Where I want to clean this thing up, well, it's basically right in here. Let's see if it does it.

What it does is it makes the sub-assemblies project at non-perpendicular direction.

[LAUGHTER]

See why I say to use the feature lines?

[LAUGHTER]

I shouldn't have done it. OK, it works sometimes. Mondays and Fridays, but nothing in the middle of the week. Luckily we have this feature here, Task Manager.

[LAUGHTER]

It allows us to wake up Civl 3D. You guys know about that one?

[LAUGHTER]

It's new in 2018 and you only get it if you buy the productivity pack add-on.

[LAUGHTER]

I think we left off about here. Any questions while I'm loading some of these drawings again? Yeah?

AUDIENCE: You mentioned earlier, there's only one corridor. So to clarify, the corridor with the little island and the [INAUDIBLE]

BRIAN LEVENDOWSKI: Yeah. The question is, I said, only use one corridor. Yes, only use one corridor so that we can just turn on our surface and it triangulates everywhere. This is all one corridor, it's multiple baselines. That's the distinction here.

A corridor is not a single alignment and profile. In fact, a corridor of any complexity, you've got to be moving to multiple baselines.

AUDIENCE: Quick question.

BRIAN LEVENDOWSKI: Yeah?

AUDIENCE: The only downside of having everything in one corridor is, if you had a dynamic feature line created and it's targeted within another baseline in there, [INAUDIBLE] confused.

BRIAN LEVENDOWSKI: Yeah.

AUDIENCE: And that's the only downside. That's why I try not to. Is that different for 2018?

BRIAN LEVENDOWSKI: Yeah. So the question is, if you have everything in one corridor-- I'm not sure I fully understood it. Like, you can create some continuous loops, right? Depending on what you're targeting, yeah.

I mean, if I targeted those yellow feature lines and those yellow feature lines were making the grid surface, then my alignment and profile were based on the grid surface then I built a corridor on that alignment and profile, that's the circular loop. Yeah. I tried this a lot of different ways where I was targeting these yellow feature lines and it got really unstable, and I think it was for that reason. Is that what you're talking about, or was there something else?

AUDIENCE: It's like when you do a corridor and you create a dynamic feature line into that corridor, and then you have another baseline that comes in that's targeting that dynamic feature line, that's when it doesn't work [INAUDIBLE].

BRIAN LEVENDOWSKI: Right, right, OK. So he was bringing up the situation-- If I had a dynamic feature line like we created here, and then I had another baseline, whatever the project might be, and I targeted that all within the same corridor, yeah, that gets unstable. So that's another reason for a second corridor, you kind of have a primary and a secondary. I do this with a large intersection where it just doesn't make sense to do it all in one corridor.

You've got a primary road, and then along those edges of travel way or something you target that dynamic feature line from the side roads that are coming up to it. All right, let's move along here. We have a similar situation that we've created over here. But I'm not going to do just the daylight here, because I've got ponds, and I've got a building to tie into, and a variety of things here.

So let's look at grading this pond. That's what every pond looks like, right? I'm not going to get into detailed pond grading here. You can do this with all kinds of benches and everything. My point here is to show you how to deal with a corridor and how to have it tie in dynamically to a parking lot next to it.

Let's make a feature line out of this. So alignment and profile, I'm not going to bother with this. This isn't a grid surface scenario. The grid surfaces is-- it's all about parking lots, because we can separate the vertical design from the horizontal design.

A pond, I don't think we need to do that. I can define some baseline or multiple baselines and I can start targeting and building regions and assemblies on those. And that's what I'm going to do here.

I've got an assembly over here I'm going to use. This is going to be my baseline. And this will be the inside of the pond. And I've just got it set so it's just going to meet right in the center there. But we could do all kinds of targeting, and benches, and all kinds of things. That's fairly straightforward corridor modeling.

Then on the outside, what I want to do, I want daylight out here to existing, and then I want it to just magically connect to my parking lot. We're going to introduce some more line work here. I'm going to use that in a second.

First thing, I'm just going to build my corridor. And I'm going to make a second corridor here. It could go in one, this is kind of take your pick. But I'm going to do a second one just because I can.

And we're going to do a feature line, and we're going to do-- let me name this thing. Feature line from base line. There's my pond feature line.

The assembly is going to be this one over here, the pond assembly. The target surfaces is going to be existing grade. I'm not going to bother with my baseline and region parameters, it's just going to go around the whole baseline. So I hit OK and there it is.

Now how do I make this dynamic? I can put a feature line in here and I can just have each corridor targeted, which is what we're going to do, but I want it to be more dynamic. I don't want to have to build one region where it targets this, and another region where it daylights, right? I want it to just know when it's supposed to match in and know when it's supposed to just daylight. So I want to either target this or match into existing.

Enter conditional sub-assemblies. Conditionals work based on targets. How many people know conditional sub-assemblies? So less than half the room, so let me explain them a little bit.

Conditional sub-assemblies don't build anything in your corridor. They're basically used as a pair. They're like an if statement in your corridor. If I find a target, do this thing, meaning what else is connected to me. If I don't find the target, do the other thing.

Common use of these is driveways. I want the curb to keep going from full curb to flat curb, and back and forth. You can use conditionals to have one region that'll just flip curb back and forth on both sides of the road. You might have 50 regions otherwise. You can do it in one region with some conditionals.

We don't have a lot of driveways here, but I want a dynamic relationship so that when I move my pond around, it'll respond. So how does this work? We need to take these, need to create feature lines out of this. And I'm also going to make a feature line out of a similar one right up here.

And we're going to use this to know when it's next to the building, we're going to use this conditional. So I've got a conditional that is either daylight or target something. This is just a link width. It's a custom one made in Sub-assembly Composer, it's basically the generic link with some depth to it.

So let's come up here, select Similar. We're going to make feature lines out of these. And here's some of the stuff I want to do. This end of this feature line is a tie in point to existing. So I want to make this relative to existing, but I only want to do it at the endpoints.

So those points are going to tie into existing no matter what. And the middle points, I can kind of fudge that around, massage the grading between my pond and between my parking lot. So it looks like this. Come in here, edit our targets. OK.

The all caps ones are the conditional sub-assemblies. The lower case ones are the actual sub-assemblies that build geometry. The daylight one, that's when it doesn't find the red line. So I need to assign that red line as a target to the daylight conditional sub-assembly.

What it means is, this builds when it doesn't find that target. In the driveway scenario, it's when it's the typical section. If I have a polyline drawn where my driveway is, when this does find that polyline as a target, then it doesn't do the daylight, or it doesn't do the full curve, it would do the flat curve.

The turf, I'm calling the turf area this area where we're just matching in. I don't want to daylight, I just have a target here. And that's going to be the same set of targets. In fact, it's the same set of targets for all of these.

So the pond one, that's the one right in the middle here. The turf, this is the sub-assembly right here. I just want to target this red feature line, that's where I want to match in. And so all of these get the same feature lines.

It's pulling three in, includes this one, but it's also the one over here. Again, I just used the layering so I don't have to pick and fuss, it just grabs them for me. So this will be easier to understand once I show you what this looks like.

What's this thing doing? It's daylighting to this, meaning this thing is just targeting-- excuse me, not daylighting this, it's targeting this feature line when the target is found. That's the conditional sub-assembly. When it's not found, that's this condition, it just does a 3 to 1 or 4 to 1 daylight to existing.

We want things dynamic, right? I can take this feature line, I move it around. Anywhere I stick this thing, it attaches to the existing surface. So it's 816.36, put it out there, it just finds the existing grade, I rebuild my corridor, that's basically the switch right there between daylight and just targeting the feature line.

Conditionals, like I said, they're all about, you have a scenario going back and forth, back and forth. To me, they're also about making a dynamic corridor. Like if I had two separate regions here and I just want to fudge where I'm daylighting, then I've got to move the regions and all that stuff. If you just use the conditionals, set up your targets, it just kind of does it for you. Is that making sense to people? OK.

We're going to do the same thing on the other side. I'm going to run a daylight from my back of curb, but I don't want to daylight in this area, I want to target that feature line. I want to daylight, daylight, daylight. Here I don't want to daylight, I want to match into great at the face of the building, whatever that is, whatever I define that to be.

And that's what this feature line is up here, it's the red one I turned on. And it's a target feature line, which means it's relative to the grid surface. Yeah?

AUDIENCE: How would you do it if you have [INAUDIBLE] section? You're basically trying to say, [INAUDIBLE]

BRIAN LEVENDOWSKI: So a scenario was just explained, I'm not sure I fully understood it. Let's talk after class on it.

AUDIENCE: OK.

BRIAN LEVENDOWSKI: Yeah. Yeah, there's about 100 other scenarios here we're not going to be able to cover. But if you follow some of these rules and just get creative with conditionals, the grid surface, and so on, you can be after this.

And in case you forgot, again, the reason we're doing all this is because we want to create a model not a surface. And out of a model, I can get quantities, I can get datum surfaces, I can get corridor solids, I can get you name it, right? That's why we're going to this fuss.

And along long way, because corridors are cool, we also make a model that's really dynamic. So let's build this region out here. And I'm going to freeze this stuff right now.

I've got another conditional assembly over here, use of conditional sub-assemblies. I have three scenarios. I have daylight to existing, I have match into pond, I have match into building, which are kind of the same thing. It's just turf target to a feature line.

But right here, I have another scenario. I have pavement, I have my entrance. Or maybe I have three entrances, I don't care. It's something different and I want to model this thing.

So I've got a different sub-assembly with what, four inches of concrete, right? And that's six inches of top soil. We want to model this, not just get a finished grade surface. So I've got three scenarios here. And then after the building, it's going to wrap around here, and I just want a daylight into existing again.

So some of the conditional stuff, it's certainly confusing if you haven't done it before. If you haven't been using them, it's time to get on board. All right, let's build this last region here.

I already have my dynamic feature line extracted from my back of curb. I need to make that a region. That feature line is named south back. Add a region along here, and again, we're just going to do fill.

So you've noticed, every single baseline I've made in here, just fill the whole baseline. I haven't once divided my baseline into multiple regions. When you do that, it's super dynamic. Everything's still just stuck to the grid surface for the parking lot. So fill, and I want to use this right daylight turf and entrance, that was this conditional down here.

Let's just hit OK for right now and let it just do that. All right. My condition for daylighting is the targets are not found. Let's go in and let's do this. First time in the corridor properties. Set all targets, set this to existing. Then we'll get this daylighting to show up here. So right in here, it's daylighting.

Now, that's the default because there's no targets assigned yet to these right here. So come back here, Edit Targets for that region. The turf is going to be this area here and between the building. So I want to go grab those same three feature lines again.

The turf, the lowercase one is the actual one that just daylights to the edge of the pond and to the face of the building. Same set of feature lines. The daylight one is this conditional, so the all caps is conditional. The daylight one, I need that to not daylight when it finds the target. So I have to tell it, here's the target so you know when to not build, and it's the same targets.

The entrance, that's that little 20 foot piece in front of the building there. It needs to know when to build. Well, it builds when it finds the entrance target. And then I need to daylight to that feature line, that actual entrance feature line.

What about back here, the daylight conditional? Don't I also need it to not daylight when it finds the entrance? So I need to add the entrance feature lines here as well.

And then for the turf, that's again, between here and between the building. I simply need to target this sub-assembly to those feature lines. It's basically the same feature lines for every one of these.

So what's it doing right here? It's following this feature line. This region right here knows to switch when it finds this feature line. So again, I bring it out here, it's attached to existing. If I rebuild both of these, it responds to that change. That's my daylight line right there. This is dynamic modeling, this is what we're after. Because we make like one or two changes during the project, so got to be able to respond to those.

This area right along here, I kind of glossed over it. But right in there, we could have put flat curb in for the entrance. I just have full curb running through there, if we take a look at the surface. Actually no, I did. That's the magic of jumping from one drawing to the next,

[LAUGHTER]

Amazing, someone did it for me, what do you know? Here's my flat curb and I'm daylighting into the face of the building there. And that's right at finish floor.

Put your slope arrows on here, put your analysis on. Are you under your 2% there? Do all that. And if you're not, turn on your good feature lines and start manipulating your model.

Does anyone not get the concept where we're attaching everything to the grid surface here, is that clear? That's kind of like the secret connection. I mean, yeah, we're doing it all with corridors instead of feature lines and grading objects now, but one of the key parts to make this really dynamic is the use of that grid surface, that drainage surface of some [? time. ?]

And I know some of you are looking at it and going, yeah whatever, I can't get away with nine feature lines. Fine, use 20 of them, but make a grid of some sort. It doesn't have to be rectangular, you can have it triangular. You got weird areas you need to kind of fudge in? Fine, draw more feature lines.

But that grid surface is really simple. You throw labels on there, you can do edits with a Quick Elevation Editor. It's really simple. Is there a question? Yeah?

AUDIENCE: Yeah. I get the concept, but I had a question. [INAUDIBLE] Townships for example, in the areas of that corner, especially when you have pavement and also when you're in [INAUDIBLE] the middle parking lot when it actually occurs, the [INAUDIBLE] occurs. In reality, you need a flat pane. I mean, sometimes with townships, they don't like to see that. How can you actually clean that up, if there is a way to actually [INAUDIBLE]?

BRIAN LEVENDOWSKI: So the question was, if I understand it, around these corners and curves, how do I get pretty contours, right? My first question is for you, how pretty do they need to be?

[LAUGHTER]

AUDIENCE: I draw this type of design using a feature line [INAUDIBLE]?

BRIAN LEVENDOWSKI: Yeah.

AUDIENCE: Figure out a way to actually clean that up.

BRIAN LEVENDOWSKI: Yeah. So around corners like this, this sort of thing, grading objects do--

AUDIENCE: No, not that--

BRIAN LEVENDOWSKI: Oh, not that area?

AUDIENCE: Actually on the [INAUDIBLE] Yeah, right there.

BRIAN LEVENDOWSKI: Like in here? Yeah. Some smoothing might clean it up. A frequency, let's adjust the frequency. Yeah. Smoothing might clean it up. Here's the other thing, I've got 0.2 foot contours on here. So there's a ton of contours going on.

But yeah, I mean this the thing about Civil 3D. Yeah, it does it for me, but the contours are ugly. Keep them as ugly as you can, that's all I can say, and then do what you have to do to massage it. And that's just the surface-- there's the surface smoothing, there's throwing in-- there's surface editing to kind of massage a little bit.

There's putting in more-- you know what actually would probably clean it up? Let's go to our grid. Let's turn on our grid surface. I think part of the problem is-- yeah, I mean this is a pretty large area here.

If we had another feature line in here, maybe we dialed the supplementing factor when we added the breaklines, brought that up a little bit. Even just another feature line drawn through right there, you get more triangulation. And if in general your triangles are running perpendicularish to your breaklines, you'll get better contours.

So I guess I would try that route first. Don't do the smoothing and that, that's just kind of a Band-Aid fix. Put more feature lines in your surface.

AUDIENCE: [INAUDIBLE]

BRIAN LEVENDOWSKI: I don't know that--

AUDIENCE: [INAUDIBLE] Would that clean it up a little bit?

BRIAN LEVENDOWSKI: I mean, I don't want any more of that than I need. If I want to add those in there, that's because I have a grade break. If I want more triangulation along my feature line, that's the supplementing factor option, that 10 foot thing. So to get more triangles, supplement and factor. Don't do the elevation because then you're managing like hundreds and hundreds of points. I teach a four year degree on getting smooth contours.

[LAUGHTER]

Yeah, question?

AUDIENCE: So the only alignment [INAUDIBLE] that you created was for the island, right?

BRIAN LEVENDOWSKI: And the perimeter curb. The question was, what alignments did I make? It was for the curb islands and it was for the perimeter curb. And I did that because I found making relative feature lines was really unstable. And we get kind of the same effect. Yeah.

AUDIENCE: Typically when I do grading like this using more feature lines-- which I noticed you did as well-- you did not assign intermediate break points. So it doesn't create all the texture of triangles in there for the new line. But with a-- if you're creating a surface from that alignment, it's going to follow that target surface exactly. Does that cause any issue as far as how smooth the surface is or anything? [INAUDIBLE] different things?

BRIAN LEVENDOWSKI: Right, right. So the question is, if I'm using alignment and surface profile, that profile has a ton of little PVIs in it. Compared to if that was just a feature line draped on the drainage surface, the grid surface, and I did not insert intermediate grade breakpoints, what does that do for the corridor surface, how does that affect it? Well, it's going to be more accurate with a surface profile because that's going to pick up every little thing.

I'd adjust the frequency so it's not picking up every little PVI in the frequency of the region. But I guess the-- if you drape the feature lines there, and you say you're not doing the corridor thing, you're draping the feature lines on the grid surface, so long as you have that feature line style hierarchy worked out where it's bending or kinking wherever those grid feature lines might be, it's going to drape to that surface.

If there's a lot of warping in your surface, yeah, maybe add some intermediate grade breakpoints. But I wouldn't just check that on in there, because then you just get a whole slew of them. So did that can answer your question?

AUDIENCE: Yeah.

BRIAN LEVENDOWSKI: We can chat more after class too. Let me keep moving a little bit. I'll save a little bit of time at the end for questions, but I want to just finish it up around the building here, what this looks like. And there, I'm done.

[LAUGHTER]

It's all concepts we've used before. So let me just show it to you, basically what we did here. Let's turn on some of our targets again. I took a feature line, ran it around the backside. And this isn't based on the grid surface except for right there. Grid surface controls right up to the face there.

So along the backside, I'm just-- you know, what's the grade at the face of the building? And then I run a simple daylight sub-assembly around that. And then these areas in here, I just target that feature line for the inside corner again.

I also put a feature line, a common feature line in between them here that this one targets and that this one targets. So if the frequency was really dialed up here, it's targeting this. This feature line here attaches to grid surface there, and right here attaches to-- I'm sorry, that's not attaching to grid surface, it's just relative to the grid surface. This is relative to existing.

All right, why do we do all this? Surfaces at all different kinds of levels, right? I can make a datum surface.

If I have a corridor, I've got a code set style. And in a code set style, we have pay items. Give me my length of curb, give me my area of pavement.

So the QTO Manager works on a basic CSV file. It's not the best tool set in the software. But for some basic quantity take off of pipe networks, pressure networks, or corridors, it's not so bad. How many people have used this for corridor quantities, QTO Manager?

It's a little weird. I found sometimes, you have to go into the corridor properties parameters when your quantities aren't reading right and basically disable, like turn off your corridor. Turn it off, hit OK, rebuild, come back and turn it on, and then it recalculates the quantities in it. So when you do a takeoff, you can do that.

AUDIENCE: So you're saying, don't trust the quantities the first time?

BRIAN LEVENDOWSKI: Yes, don't trust them the first time. No, no, don't trust them the first time. I mean, draw a true polyline, is that 1,000 feet, or is that-- and so in corridors, they work like this.

You assign in the code set style a pay item right here. So I'm going to assign it to flow line. I could add a pay item. This right here is reference to a CSV. And I come in here and pick them and just assign them in my code set style.

If you haven't used QTO Manager, it's right here on the Analyze tab, QTO Manager. Open pay item file, go grab a CSV, three columns, boom it comes in here. You run a takeoff-- I think I have the pay items assigned correctly-- hit compute, crunches through, counts the stuff up.

If I did an entire drawing like this, I've got pipe networks in there with pay items assigned, it's going to count that stuff, corridors, you name it. 1,300 feet of curb, 5,000 square yards of concrete. That pay item file, the unit types matter. In fact, there's an XSL file in the Civil 3D program files that knows what a square yard is versus a square foot.

Go to my YouTube site, I have a video on how to understand what that is and what is the syntax you need to use in your CSV file so it understands what is square yards versus square feet. It will know the difference. I can get surfaces, I can get pay items out of here, quantities of that nature.

I can also extract all kinds of things for staking, right? We could do that with feature lines too, but we can extract it anywhere, at any level with a corridor. I can also pull solids out of here. Solids can be used to bring into Navisworks, can be brought into Revit, and it's fairly straightforward.

Extract Solids, we'll just say All Regions, and we're going to do the parking lot corridor. And there's all these options about, what color is the solid, and the layering, and all this stuff. I'm not going to get into detail with that. And you can attach attribute data, or more specifically, property set data.

This is new information that's actually been in Civil 3D for a lot of years. And they just released it, or basically opened it up in Civil 3D so that you can access it. Think of it as like block attributes for Civil 3D objects. You can attach any of this data to those solid objects.

You can add this to a new drawing, let's call this Solids 2. Extract the solids, and it throws it into a new drawing and we'll see how it looks. This is where you find out, did I really model this correctly, did I really cover everything?

You can get AutoCAD bodies out of this. Those are kind of an odd object. There's my solids. I messed something up there.

You can push this stuff into Revit. I can pass this onto a Revit user in Architect. I can link a CAD file and go out and grab a solids file. You can do an NWC out from Civil 3D, bring it into Navasworks, you name it, all sorts of places.

All right. That is site grading with corridors in a nutshell. I want to touch on a few things here before I let you go. And we'll have a little time for questions at the end.

If you were in here the whole time going, why, why, why, why, I just throw my feature lines in there all I need is my surface and my contours, don't bother. If you need to do full modeling and you need to get more information out of it, then start thinking about using corridors. And I was kind of showing this as I did this, this second concept, build the model and then design it.

I mean, you have to kind of design it, but I don't need to figure it out on a napkin all my spot elevations and then like-- that's not the idea here. You throw together a grid surface for the parking lot, some kind of preliminary drainage pattern, start building a corridor on it, and then kind of massaging that. In fact, I wouldn't even move to the corridor until you're pretty happy with the drainage of that grid surface. Be it earth work, be it ADA requirements, just play with that grid surface, get that where you want it.

You have to design panels. I can explain 100 scenarios you would run into here in different sites. But you've got to think of little pieces where the targeting makes sense. I mean, the targeting kind of falls apart and it wants to overlap itself, you do these things we did over here where we targeted a diagonal feature line in the middle here.

And think ahead. This grid surface, these grid feature lines, think ahead a little bit. Like, where does the spotter need to get to, all those things. Think about that in the grid surface.

Those target objects, this is easy to make a mess of pretty quickly. I've got grid feature lines, I've got alignments and profiles, and I've got target feature lines, now I've got a corridor. Like, you have classifications of this stuff. I've got my grid feature lines, I've got my target feature lines, then I have my baselines, which are either alignments and profiles or feature lines in the case of the pond.

So if you're doing the grid surface thing I recommend using the alignments and surface profiles. If it's just a pond or something where you don't need the grid surface, just use a feature line. It's easier to work with.

And build things to allow for changes. The little stuff like the conditionals between the pond and the parking lot, it might seem a little ridiculous. But if I keep moving that and I make the pond bigger, and move the pond up and down, and all that kind of stuff, it just responds if I model it correctly. So there's some balance there. Whether you do the conditionals or you just do separate regions, that's fine too.

How dynamic do you need to make it? You guys can answer that. So with that, I thank you a lot for watching. Come check out our booth.

I'm with CTC, we have CT Express Tools, all kinds of plugins for Civil 3D and Revit. I'll be there this evening, and tomorrow and everything. Come say hi and come check us out.

But with that, thanks for listening. I will hang around for questions afterwards. So thank you.

[APPLAUSE]

______
icon-svg-close-thick

Cookieの設定

弊社にとって、お客様のプライバシーを守ることと最適な体験を提供することは、どちらも大変重要です。弊社では、お客様に合わせてカスタマイズした情報を提供し、並びにアプリケーションの開発に役立てることを目的に、本サイトのご利用方法についてのデータを収集しております。

そこで、お客様のデータの収集と使用を許可いただけるかどうかをお答えください。

弊社が利用しているサードパーティのサービスについての説明とプライバシー ステートメントも、併せてご確認ください。

サイト動作に必須:オートデスクのサイトが正常に動作し、お客様へサービスを提供するために必要な機能です

Cookie を有効にすることで、お客様の好みやログイン情報が記録され、このデータに基づき操作に対する応答や、ショッピング カートへの商品追加が最適化されます。

使用感が向上:お客様に最適な情報が表示されます

Cookie を有効にすることで、拡張機能が正常に動作し、サイト表示が個々に合わせてカスタマイズされます。お客様に最適な情報をお届けし、使用感を向上させるためのこうした設定は、オードデスクまたはサードパーティのサービス プロバイダーが行います。 Cookie が無効に設定されている場合、一部またはすべてのサービスをご利用いただけない場合があります。

広告表示をカスタマイズ:お客様に関連する広告が表示されます

Cookie を有効にすることで、サイトのご利用内容やご興味に関するデータが収集され、これに基づきお客様に関連する広告が表示されるなど、効率的な動作が可能になります。また、継続的にデータを収集することで、お客様のご興味にさらに関連する広告を配信することが可能になります。Cookie が無効に設定されている場合、お客様に関連しない広告が表示される可能性があります。

icon-svg-close-thick

サードパーティのサービス

それぞれの情報で弊社が利用しているサードパーティのサービスと、オンラインで収集するお客様のデータの使用方法を詳しく説明いたします。

icon-svg-hide-thick

icon-svg-show-thick

サイト動作に必須:オートデスクのサイトが正常に動作し、お客様へサービスを提供するために必要な機能です

Qualtrics
弊社はQualtricsを利用し、アンケート調査やオンライン フォームを通じてお客様が弊社にフィードバックを提供できるようにしています。アンケートの回答は無作為に選んだお客様にお願いしておりますが、お客様から自発的に弊社にフィードバックを提供することも可能です。データを収集する目的は、アンケートの回答前にお客様がとられた行動を、より正しく理解するためです。収集したデータは、発生していた可能性がある問題のトラブルシューティングに役立てさせていただきます。. Qualtrics プライバシー ポリシー
Akamai mPulse
弊社は、弊社サイトでのお客様の行動に関するデータを収集するために、Akamai mPulseを利用しています。収集する情報には、お客様がアクセスしたページ、ご利用中の体験版、再生したビデオ、購入した製品やサービス、お客様の IP アドレスまたはデバイスの ID、お客様の Autodesk ID が含まれます。このデータを基にサイトのパフォーマンスを測定したり、オンラインでの操作のしやすさを検証して機能強化に役立てています。併せて高度な解析手法を使用し、メールでのお問い合わせやカスタマー サポート、営業へのお問い合わせで、お客様に最適な体験が提供されるようにしています。. Akamai mPulse プライバシー ポリシー
Digital River
弊社は、弊社サイトでのお客様の行動に関するデータを収集するために、Digital Riverを利用しています。収集する情報には、お客様がアクセスしたページ、ご利用中の体験版、再生したビデオ、購入した製品やサービス、お客様の IP アドレスまたはデバイスの ID、お客様の Autodesk ID が含まれます。このデータを基にサイトのパフォーマンスを測定したり、オンラインでの操作のしやすさを検証して機能強化に役立てています。併せて高度な解析手法を使用し、メールでのお問い合わせやカスタマー サポート、営業へのお問い合わせで、お客様に最適な体験が提供されるようにしています。. Digital River プライバシー ポリシー
Dynatrace
弊社は、弊社サイトでのお客様の行動に関するデータを収集するために、Dynatraceを利用しています。収集する情報には、お客様がアクセスしたページ、ご利用中の体験版、再生したビデオ、購入した製品やサービス、お客様の IP アドレスまたはデバイスの ID、お客様の Autodesk ID が含まれます。このデータを基にサイトのパフォーマンスを測定したり、オンラインでの操作のしやすさを検証して機能強化に役立てています。併せて高度な解析手法を使用し、メールでのお問い合わせやカスタマー サポート、営業へのお問い合わせで、お客様に最適な体験が提供されるようにしています。. Dynatrace プライバシー ポリシー
Khoros
弊社は、弊社サイトでのお客様の行動に関するデータを収集するために、Khorosを利用しています。収集する情報には、お客様がアクセスしたページ、ご利用中の体験版、再生したビデオ、購入した製品やサービス、お客様の IP アドレスまたはデバイスの ID、お客様の Autodesk ID が含まれます。このデータを基にサイトのパフォーマンスを測定したり、オンラインでの操作のしやすさを検証して機能強化に役立てています。併せて高度な解析手法を使用し、メールでのお問い合わせやカスタマー サポート、営業へのお問い合わせで、お客様に最適な体験が提供されるようにしています。. Khoros プライバシー ポリシー
Launch Darkly
弊社は、弊社サイトでのお客様の行動に関するデータを収集するために、Launch Darklyを利用しています。収集する情報には、お客様がアクセスしたページ、ご利用中の体験版、再生したビデオ、購入した製品やサービス、お客様の IP アドレスまたはデバイスの ID、お客様の Autodesk ID が含まれます。このデータを基にサイトのパフォーマンスを測定したり、オンラインでの操作のしやすさを検証して機能強化に役立てています。併せて高度な解析手法を使用し、メールでのお問い合わせやカスタマー サポート、営業へのお問い合わせで、お客様に最適な体験が提供されるようにしています。. Launch Darkly プライバシー ポリシー
New Relic
弊社は、弊社サイトでのお客様の行動に関するデータを収集するために、New Relicを利用しています。収集する情報には、お客様がアクセスしたページ、ご利用中の体験版、再生したビデオ、購入した製品やサービス、お客様の IP アドレスまたはデバイスの ID、お客様の Autodesk ID が含まれます。このデータを基にサイトのパフォーマンスを測定したり、オンラインでの操作のしやすさを検証して機能強化に役立てています。併せて高度な解析手法を使用し、メールでのお問い合わせやカスタマー サポート、営業へのお問い合わせで、お客様に最適な体験が提供されるようにしています。. New Relic プライバシー ポリシー
Salesforce Live Agent
弊社は、弊社サイトでのお客様の行動に関するデータを収集するために、Salesforce Live Agentを利用しています。収集する情報には、お客様がアクセスしたページ、ご利用中の体験版、再生したビデオ、購入した製品やサービス、お客様の IP アドレスまたはデバイスの ID、お客様の Autodesk ID が含まれます。このデータを基にサイトのパフォーマンスを測定したり、オンラインでの操作のしやすさを検証して機能強化に役立てています。併せて高度な解析手法を使用し、メールでのお問い合わせやカスタマー サポート、営業へのお問い合わせで、お客様に最適な体験が提供されるようにしています。. Salesforce Live Agent プライバシー ポリシー
Wistia
弊社は、弊社サイトでのお客様の行動に関するデータを収集するために、Wistiaを利用しています。収集する情報には、お客様がアクセスしたページ、ご利用中の体験版、再生したビデオ、購入した製品やサービス、お客様の IP アドレスまたはデバイスの ID、お客様の Autodesk ID が含まれます。このデータを基にサイトのパフォーマンスを測定したり、オンラインでの操作のしやすさを検証して機能強化に役立てています。併せて高度な解析手法を使用し、メールでのお問い合わせやカスタマー サポート、営業へのお問い合わせで、お客様に最適な体験が提供されるようにしています。. Wistia プライバシー ポリシー
Tealium
弊社は、弊社サイトでのお客様の行動に関するデータを収集するために、Tealiumを利用しています。データには、お客様がアクセスしたページ、ご利用中の体験版、再生したビデオ、購入した製品やサービス、お客様の IP アドレスまたはデバイスの ID が含まれます。このデータを基にサイトのパフォーマンスを測定したり、オンラインでの操作のしやすさを検証して機能強化に役立てています。併せて高度な解析手法を使用し、メールでのお問い合わせやカスタマー サポート、営業へのお問い合わせで、お客様に最適な体験が提供されるようにしています。. Tealium プライバシー ポリシー<>
Typepad Stats
弊社は、弊社サイトでのお客様の行動に関するデータを収集するために、Typepad Statsを利用しています。収集する情報には、お客様がアクセスしたページ、ご利用中の体験版、再生したビデオ、購入した製品やサービス、お客様の IP アドレスまたはデバイスの ID、お客様の Autodesk ID が含まれます。このデータを基にサイトのパフォーマンスを測定したり、オンラインでの操作のしやすさを検証して機能強化に役立てています。併せて高度な解析手法を使用し、メールでのお問い合わせやカスタマー サポート、営業へのお問い合わせで、お客様に最適な体験が提供されるようにしています。. Typepad Stats プライバシー ポリシー
Geo Targetly
当社では、Geo Targetly を使用して Web サイトの訪問者を最適な Web ページに誘導し、訪問者のいる場所に応じて調整したコンテンツを提供します。Geo Targetly は、Web サイト訪問者の IP アドレスを使用して、訪問者のデバイスのおおよその位置を特定します。このため、訪問者は (ほとんどの場合) 自分のローカル言語でコンテンツを閲覧できます。Geo Targetly プライバシー ポリシー
SpeedCurve
弊社は、SpeedCurve を使用して、Web ページの読み込み時間と画像、スクリプト、テキストなど後続の要素の応答性を計測することにより、お客様の Web サイト エクスペリエンスのパフォーマンスをモニタリングおよび計測します。SpeedCurve プライバシー ポリシー
Qualified
Qualified is the Autodesk Live Chat agent platform. This platform provides services to allow our customers to communicate in real-time with Autodesk support. We may collect unique ID for specific browser sessions during a chat. Qualified Privacy Policy

icon-svg-hide-thick

icon-svg-show-thick

使用感が向上:お客様に最適な情報が表示されます

Google Optimize
弊社はGoogle Optimizeを利用して、弊社サイトの新機能をテストし、お客様に合わせた方法で機能を使えるようにしています。そのため弊社では、弊社サイトにアクセスしているお客様から、行動に関するデータを収集しています。収集するデータには、お客様がアクセスしたページ、ご利用中の体験版、再生したビデオ、購入した製品やサービス、お客様の IP アドレスまたはデバイスの ID、お客様の Autodesk ID などが含まれます。機能のテストの結果によっては、お客様がご利用のサイトのバージョンが変わったり、サイトにアクセスするユーザの属性に応じて、パーソナライズされたコンテンツが表示されるようになる場合があります。. Google Optimize プライバシー ポリシー
ClickTale
弊社は、弊社サイトをご利用になるお客様が、どこで操作につまづいたかを正しく理解できるよう、ClickTaleを利用しています。弊社ではセッションの記録を基に、ページの要素を含めて、お客様がサイトでどのような操作を行っているかを確認しています。お客様の特定につながる個人情報は非表示にし、収集も行いません。. ClickTale プライバシー ポリシー
OneSignal
弊社は、OneSignalがサポートするサイトに広告を配置するために、OneSignalを利用しています。広告には、OneSignalのデータと、弊社サイトにアクセスしているお客様から弊社が収集する行動に関するデータの両方が使われます。弊社が収集するデータには、お客様がアクセスしたページ、ご利用中の体験版、再生したビデオ、購入した製品やサービス、お客様の IP アドレスまたはデバイスの ID が含まれます。この情報に併せて、OneSignalがお客様から収集したデータを使用する場合があります。OneSignalに提供しているデータを弊社が使用するのは、お客様のデジタル広告体験をより適切にカスタマイズし、関連性の高い広告をお客様に配信するためです。. OneSignal プライバシー ポリシー
Optimizely
弊社はOptimizelyを利用して、弊社サイトの新機能をテストし、お客様に合わせた方法で機能を使えるようにしています。そのため弊社では、弊社サイトにアクセスしているお客様から、行動に関するデータを収集しています。収集するデータには、お客様がアクセスしたページ、ご利用中の体験版、再生したビデオ、購入した製品やサービス、お客様の IP アドレスまたはデバイスの ID、お客様の Autodesk ID などが含まれます。機能のテストの結果によっては、お客様がご利用のサイトのバージョンが変わったり、サイトにアクセスするユーザの属性に応じて、パーソナライズされたコンテンツが表示されるようになる場合があります。. Optimizely プライバシー ポリシー
Amplitude
弊社はAmplitudeを利用して、弊社サイトの新機能をテストし、お客様に合わせた方法で機能を使えるようにしています。そのため弊社では、弊社サイトにアクセスしているお客様から、行動に関するデータを収集しています。収集するデータには、お客様がアクセスしたページ、ご利用中の体験版、再生したビデオ、購入した製品やサービス、お客様の IP アドレスまたはデバイスの ID、お客様の Autodesk ID などが含まれます。機能のテストの結果によっては、お客様がご利用のサイトのバージョンが変わったり、サイトにアクセスするユーザの属性に応じて、パーソナライズされたコンテンツが表示されるようになる場合があります。. Amplitude プライバシー ポリシー
Snowplow
弊社は、弊社サイトでのお客様の行動に関するデータを収集するために、Snowplowを利用しています。収集する情報には、お客様がアクセスしたページ、ご利用中の体験版、再生したビデオ、購入した製品やサービス、お客様の IP アドレスまたはデバイスの ID、お客様の Autodesk ID が含まれます。このデータを基にサイトのパフォーマンスを測定したり、オンラインでの操作のしやすさを検証して機能強化に役立てています。併せて高度な解析手法を使用し、メールでのお問い合わせやカスタマー サポート、営業へのお問い合わせで、お客様に最適な体験が提供されるようにしています。. Snowplow プライバシー ポリシー
UserVoice
弊社は、弊社サイトでのお客様の行動に関するデータを収集するために、UserVoiceを利用しています。収集する情報には、お客様がアクセスしたページ、ご利用中の体験版、再生したビデオ、購入した製品やサービス、お客様の IP アドレスまたはデバイスの ID、お客様の Autodesk ID が含まれます。このデータを基にサイトのパフォーマンスを測定したり、オンラインでの操作のしやすさを検証して機能強化に役立てています。併せて高度な解析手法を使用し、メールでのお問い合わせやカスタマー サポート、営業へのお問い合わせで、お客様に最適な体験が提供されるようにしています。. UserVoice プライバシー ポリシー
Clearbit
Clearbit を使用すると、リアルタイムのデータ強化により、お客様に合わせてパーソナライズされた適切なエクスペリエンスを提供できます。弊社が収集するデータには、お客様がアクセスしたページ、ご利用中の体験版、再生したビデオ、購入した製品やサービス、お客様の IP アドレスまたはデバイスの ID が含まれます。Clearbit プライバシー ポリシー
YouTube
YouTube はビデオ共有プラットフォームで、埋め込まれたビデオを当社のウェブ サイトで表示および共有することができます。YouTube は、視聴者のビデオのパフォーマンスの測定値を提供しています。 YouTube 社のプライバシー ポリシー

icon-svg-hide-thick

icon-svg-show-thick

広告表示をカスタマイズ:お客様に関連する広告が表示されます

Adobe Analytics
弊社は、弊社サイトでのお客様の行動に関するデータを収集するために、Adobe Analyticsを利用しています。収集する情報には、お客様がアクセスしたページ、ご利用中の体験版、再生したビデオ、購入した製品やサービス、お客様の IP アドレスまたはデバイスの ID、お客様の Autodesk ID が含まれます。このデータを基にサイトのパフォーマンスを測定したり、オンラインでの操作のしやすさを検証して機能強化に役立てています。併せて高度な解析手法を使用し、メールでのお問い合わせやカスタマー サポート、営業へのお問い合わせで、お客様に最適な体験が提供されるようにしています。. Adobe Analytics プライバシー ポリシー
Google Analytics (Web Analytics)
弊社は、弊社サイトでのお客様の行動に関するデータを収集するために、Google Analytics (Web Analytics)を利用しています。データには、お客様がアクセスしたページ、ご利用中の体験版、再生したビデオ、購入した製品やサービス、お客様の IP アドレスまたはデバイスの ID が含まれます。このデータを基にサイトのパフォーマンスを測定したり、オンラインでの操作のしやすさを検証して機能強化に役立てています。併せて高度な解析手法を使用し、メールでのお問い合わせやカスタマー サポート、営業へのお問い合わせで、お客様に最適な体験が提供されるようにしています。. Google Analytics (Web Analytics) プライバシー ポリシー<>
Marketo
弊社は、お客様に関連性のあるコンテンツを、適切なタイミングにメールで配信できるよう、Marketoを利用しています。そのため、お客様のオンラインでの行動や、弊社からお送りするメールへの反応について、データを収集しています。収集するデータには、お客様がアクセスしたページ、ご利用中の体験版、再生したビデオ、購入した製品やサービス、お客様の IP アドレスまたはデバイスの ID、メールの開封率、クリックしたリンクなどが含まれます。このデータに、他の収集先から集めたデータを組み合わせ、営業やカスタマー サービスへの満足度を向上させるとともに、高度な解析処理によって、より関連性の高いコンテンツを提供するようにしています。. Marketo プライバシー ポリシー
Doubleclick
弊社は、Doubleclickがサポートするサイトに広告を配置するために、Doubleclickを利用しています。広告には、Doubleclickのデータと、弊社サイトにアクセスしているお客様から弊社が収集する行動に関するデータの両方が使われます。弊社が収集するデータには、お客様がアクセスしたページ、ご利用中の体験版、再生したビデオ、購入した製品やサービス、お客様の IP アドレスまたはデバイスの ID が含まれます。この情報に併せて、Doubleclickがお客様から収集したデータを使用する場合があります。Doubleclickに提供しているデータを弊社が使用するのは、お客様のデジタル広告体験をより適切にカスタマイズし、関連性の高い広告をお客様に配信するためです。. Doubleclick プライバシー ポリシー
HubSpot
弊社は、お客様に関連性のあるコンテンツを、適切なタイミングにメールで配信できるよう、HubSpotを利用しています。そのため、お客様のオンラインでの行動や、弊社からお送りするメールへの反応について、データを収集しています。収集するデータには、お客様がアクセスしたページ、ご利用中の体験版、再生したビデオ、購入した製品やサービス、お客様の IP アドレスまたはデバイスの ID、メールの開封率、クリックしたリンクなどが含まれます。. HubSpot プライバシー ポリシー
Twitter
弊社は、Twitterがサポートするサイトに広告を配置するために、Twitterを利用しています。広告には、Twitterのデータと、弊社サイトにアクセスしているお客様から弊社が収集する行動に関するデータの両方が使われます。弊社が収集するデータには、お客様がアクセスしたページ、ご利用中の体験版、再生したビデオ、購入した製品やサービス、お客様の IP アドレスまたはデバイスの ID が含まれます。この情報に併せて、Twitterがお客様から収集したデータを使用する場合があります。Twitterに提供しているデータを弊社が使用するのは、お客様のデジタル広告体験をより適切にカスタマイズし、関連性の高い広告をお客様に配信するためです。. Twitter プライバシー ポリシー
Facebook
弊社は、Facebookがサポートするサイトに広告を配置するために、Facebookを利用しています。広告には、Facebookのデータと、弊社サイトにアクセスしているお客様から弊社が収集する行動に関するデータの両方が使われます。弊社が収集するデータには、お客様がアクセスしたページ、ご利用中の体験版、再生したビデオ、購入した製品やサービス、お客様の IP アドレスまたはデバイスの ID が含まれます。この情報に併せて、Facebookがお客様から収集したデータを使用する場合があります。Facebookに提供しているデータを弊社が使用するのは、お客様のデジタル広告体験をより適切にカスタマイズし、関連性の高い広告をお客様に配信するためです。. Facebook プライバシー ポリシー
LinkedIn
弊社は、LinkedInがサポートするサイトに広告を配置するために、LinkedInを利用しています。広告には、LinkedInのデータと、弊社サイトにアクセスしているお客様から弊社が収集する行動に関するデータの両方が使われます。弊社が収集するデータには、お客様がアクセスしたページ、ご利用中の体験版、再生したビデオ、購入した製品やサービス、お客様の IP アドレスまたはデバイスの ID が含まれます。この情報に併せて、LinkedInがお客様から収集したデータを使用する場合があります。LinkedInに提供しているデータを弊社が使用するのは、お客様のデジタル広告体験をより適切にカスタマイズし、関連性の高い広告をお客様に配信するためです。. LinkedIn プライバシー ポリシー
Yahoo! Japan
弊社は、Yahoo! Japanがサポートするサイトに広告を配置するために、Yahoo! Japanを利用しています。広告には、Yahoo! Japanのデータと、弊社サイトにアクセスしているお客様から弊社が収集する行動に関するデータの両方が使われます。弊社が収集するデータには、お客様がアクセスしたページ、ご利用中の体験版、再生したビデオ、購入した製品やサービス、お客様の IP アドレスまたはデバイスの ID が含まれます。この情報に併せて、Yahoo! Japanがお客様から収集したデータを使用する場合があります。Yahoo! Japanに提供しているデータを弊社が使用するのは、お客様のデジタル広告体験をより適切にカスタマイズし、関連性の高い広告をお客様に配信するためです。. Yahoo! Japan プライバシー ポリシー
Naver
弊社は、Naverがサポートするサイトに広告を配置するために、Naverを利用しています。広告には、Naverのデータと、弊社サイトにアクセスしているお客様から弊社が収集する行動に関するデータの両方が使われます。弊社が収集するデータには、お客様がアクセスしたページ、ご利用中の体験版、再生したビデオ、購入した製品やサービス、お客様の IP アドレスまたはデバイスの ID が含まれます。この情報に併せて、Naverがお客様から収集したデータを使用する場合があります。Naverに提供しているデータを弊社が使用するのは、お客様のデジタル広告体験をより適切にカスタマイズし、関連性の高い広告をお客様に配信するためです。. Naver プライバシー ポリシー
Quantcast
弊社は、Quantcastがサポートするサイトに広告を配置するために、Quantcastを利用しています。広告には、Quantcastのデータと、弊社サイトにアクセスしているお客様から弊社が収集する行動に関するデータの両方が使われます。弊社が収集するデータには、お客様がアクセスしたページ、ご利用中の体験版、再生したビデオ、購入した製品やサービス、お客様の IP アドレスまたはデバイスの ID が含まれます。この情報に併せて、Quantcastがお客様から収集したデータを使用する場合があります。Quantcastに提供しているデータを弊社が使用するのは、お客様のデジタル広告体験をより適切にカスタマイズし、関連性の高い広告をお客様に配信するためです。. Quantcast プライバシー ポリシー
Call Tracking
弊社は、キャンペーン用にカスタマイズした電話番号を提供するために、Call Trackingを利用しています。カスタマイズした電話番号を使用することで、お客様は弊社の担当者にすぐ連絡できるようになり、弊社はサービスのパフォーマンスをより正確に評価できるようになります。弊社では、提供した電話番号を基に、サイトでのお客様の行動に関するデータを収集する場合があります。. Call Tracking プライバシー ポリシー
Wunderkind
弊社は、Wunderkindがサポートするサイトに広告を配置するために、Wunderkindを利用しています。広告には、Wunderkindのデータと、弊社サイトにアクセスしているお客様から弊社が収集する行動に関するデータの両方が使われます。弊社が収集するデータには、お客様がアクセスしたページ、ご利用中の体験版、再生したビデオ、購入した製品やサービス、お客様の IP アドレスまたはデバイスの ID が含まれます。この情報に併せて、Wunderkindがお客様から収集したデータを使用する場合があります。Wunderkindに提供しているデータを弊社が使用するのは、お客様のデジタル広告体験をより適切にカスタマイズし、関連性の高い広告をお客様に配信するためです。. Wunderkind プライバシー ポリシー
ADC Media
弊社は、ADC Mediaがサポートするサイトに広告を配置するために、ADC Mediaを利用しています。広告には、ADC Mediaのデータと、弊社サイトにアクセスしているお客様から弊社が収集する行動に関するデータの両方が使われます。弊社が収集するデータには、お客様がアクセスしたページ、ご利用中の体験版、再生したビデオ、購入した製品やサービス、お客様の IP アドレスまたはデバイスの ID が含まれます。この情報に併せて、ADC Mediaがお客様から収集したデータを使用する場合があります。ADC Mediaに提供しているデータを弊社が使用するのは、お客様のデジタル広告体験をより適切にカスタマイズし、関連性の高い広告をお客様に配信するためです。. ADC Media プライバシー ポリシー
AgrantSEM
弊社は、AgrantSEMがサポートするサイトに広告を配置するために、AgrantSEMを利用しています。広告には、AgrantSEMのデータと、弊社サイトにアクセスしているお客様から弊社が収集する行動に関するデータの両方が使われます。弊社が収集するデータには、お客様がアクセスしたページ、ご利用中の体験版、再生したビデオ、購入した製品やサービス、お客様の IP アドレスまたはデバイスの ID が含まれます。この情報に併せて、AgrantSEMがお客様から収集したデータを使用する場合があります。AgrantSEMに提供しているデータを弊社が使用するのは、お客様のデジタル広告体験をより適切にカスタマイズし、関連性の高い広告をお客様に配信するためです。. AgrantSEM プライバシー ポリシー
Bidtellect
弊社は、Bidtellectがサポートするサイトに広告を配置するために、Bidtellectを利用しています。広告には、Bidtellectのデータと、弊社サイトにアクセスしているお客様から弊社が収集する行動に関するデータの両方が使われます。弊社が収集するデータには、お客様がアクセスしたページ、ご利用中の体験版、再生したビデオ、購入した製品やサービス、お客様の IP アドレスまたはデバイスの ID が含まれます。この情報に併せて、Bidtellectがお客様から収集したデータを使用する場合があります。Bidtellectに提供しているデータを弊社が使用するのは、お客様のデジタル広告体験をより適切にカスタマイズし、関連性の高い広告をお客様に配信するためです。. Bidtellect プライバシー ポリシー
Bing
弊社は、Bingがサポートするサイトに広告を配置するために、Bingを利用しています。広告には、Bingのデータと、弊社サイトにアクセスしているお客様から弊社が収集する行動に関するデータの両方が使われます。弊社が収集するデータには、お客様がアクセスしたページ、ご利用中の体験版、再生したビデオ、購入した製品やサービス、お客様の IP アドレスまたはデバイスの ID が含まれます。この情報に併せて、Bingがお客様から収集したデータを使用する場合があります。Bingに提供しているデータを弊社が使用するのは、お客様のデジタル広告体験をより適切にカスタマイズし、関連性の高い広告をお客様に配信するためです。. Bing プライバシー ポリシー
G2Crowd
弊社は、G2Crowdがサポートするサイトに広告を配置するために、G2Crowdを利用しています。広告には、G2Crowdのデータと、弊社サイトにアクセスしているお客様から弊社が収集する行動に関するデータの両方が使われます。弊社が収集するデータには、お客様がアクセスしたページ、ご利用中の体験版、再生したビデオ、購入した製品やサービス、お客様の IP アドレスまたはデバイスの ID が含まれます。この情報に併せて、G2Crowdがお客様から収集したデータを使用する場合があります。G2Crowdに提供しているデータを弊社が使用するのは、お客様のデジタル広告体験をより適切にカスタマイズし、関連性の高い広告をお客様に配信するためです。. G2Crowd プライバシー ポリシー
NMPI Display
弊社は、NMPI Displayがサポートするサイトに広告を配置するために、NMPI Displayを利用しています。広告には、NMPI Displayのデータと、弊社サイトにアクセスしているお客様から弊社が収集する行動に関するデータの両方が使われます。弊社が収集するデータには、お客様がアクセスしたページ、ご利用中の体験版、再生したビデオ、購入した製品やサービス、お客様の IP アドレスまたはデバイスの ID が含まれます。この情報に併せて、NMPI Displayがお客様から収集したデータを使用する場合があります。NMPI Displayに提供しているデータを弊社が使用するのは、お客様のデジタル広告体験をより適切にカスタマイズし、関連性の高い広告をお客様に配信するためです。. NMPI Display プライバシー ポリシー
VK
弊社は、VKがサポートするサイトに広告を配置するために、VKを利用しています。広告には、VKのデータと、弊社サイトにアクセスしているお客様から弊社が収集する行動に関するデータの両方が使われます。弊社が収集するデータには、お客様がアクセスしたページ、ご利用中の体験版、再生したビデオ、購入した製品やサービス、お客様の IP アドレスまたはデバイスの ID が含まれます。この情報に併せて、VKがお客様から収集したデータを使用する場合があります。VKに提供しているデータを弊社が使用するのは、お客様のデジタル広告体験をより適切にカスタマイズし、関連性の高い広告をお客様に配信するためです。. VK プライバシー ポリシー
Adobe Target
弊社はAdobe Targetを利用して、弊社サイトの新機能をテストし、お客様に合わせた方法で機能を使えるようにしています。そのため弊社では、弊社サイトにアクセスしているお客様から、行動に関するデータを収集しています。収集するデータには、お客様がアクセスしたページ、ご利用中の体験版、再生したビデオ、購入した製品やサービス、お客様の IP アドレスまたはデバイスの ID、お客様の Autodesk ID などが含まれます。機能のテストの結果によっては、お客様がご利用のサイトのバージョンが変わったり、サイトにアクセスするユーザの属性に応じて、パーソナライズされたコンテンツが表示されるようになる場合があります。. Adobe Target プライバシー ポリシー
Google Analytics (Advertising)
弊社は、Google Analytics (Advertising)がサポートするサイトに広告を配置するために、Google Analytics (Advertising)を利用しています。広告には、Google Analytics (Advertising)のデータと、弊社サイトにアクセスしているお客様から弊社が収集する行動に関するデータの両方が使われます。弊社が収集するデータには、お客様がアクセスしたページ、ご利用中の体験版、再生したビデオ、購入した製品やサービス、お客様の IP アドレスまたはデバイスの ID が含まれます。この情報に併せて、Google Analytics (Advertising)がお客様から収集したデータを使用する場合があります。Google Analytics (Advertising)に提供しているデータを弊社が使用するのは、お客様のデジタル広告体験をより適切にカスタマイズし、関連性の高い広告をお客様に配信するためです。. Google Analytics (Advertising) プライバシー ポリシー
Trendkite
弊社は、Trendkiteがサポートするサイトに広告を配置するために、Trendkiteを利用しています。広告には、Trendkiteのデータと、弊社サイトにアクセスしているお客様から弊社が収集する行動に関するデータの両方が使われます。弊社が収集するデータには、お客様がアクセスしたページ、ご利用中の体験版、再生したビデオ、購入した製品やサービス、お客様の IP アドレスまたはデバイスの ID が含まれます。この情報に併せて、Trendkiteがお客様から収集したデータを使用する場合があります。Trendkiteに提供しているデータを弊社が使用するのは、お客様のデジタル広告体験をより適切にカスタマイズし、関連性の高い広告をお客様に配信するためです。. Trendkite プライバシー ポリシー
Hotjar
弊社は、Hotjarがサポートするサイトに広告を配置するために、Hotjarを利用しています。広告には、Hotjarのデータと、弊社サイトにアクセスしているお客様から弊社が収集する行動に関するデータの両方が使われます。弊社が収集するデータには、お客様がアクセスしたページ、ご利用中の体験版、再生したビデオ、購入した製品やサービス、お客様の IP アドレスまたはデバイスの ID が含まれます。この情報に併せて、Hotjarがお客様から収集したデータを使用する場合があります。Hotjarに提供しているデータを弊社が使用するのは、お客様のデジタル広告体験をより適切にカスタマイズし、関連性の高い広告をお客様に配信するためです。. Hotjar プライバシー ポリシー
6 Sense
弊社は、6 Senseがサポートするサイトに広告を配置するために、6 Senseを利用しています。広告には、6 Senseのデータと、弊社サイトにアクセスしているお客様から弊社が収集する行動に関するデータの両方が使われます。弊社が収集するデータには、お客様がアクセスしたページ、ご利用中の体験版、再生したビデオ、購入した製品やサービス、お客様の IP アドレスまたはデバイスの ID が含まれます。この情報に併せて、6 Senseがお客様から収集したデータを使用する場合があります。6 Senseに提供しているデータを弊社が使用するのは、お客様のデジタル広告体験をより適切にカスタマイズし、関連性の高い広告をお客様に配信するためです。. 6 Sense プライバシー ポリシー
Terminus
弊社は、Terminusがサポートするサイトに広告を配置するために、Terminusを利用しています。広告には、Terminusのデータと、弊社サイトにアクセスしているお客様から弊社が収集する行動に関するデータの両方が使われます。弊社が収集するデータには、お客様がアクセスしたページ、ご利用中の体験版、再生したビデオ、購入した製品やサービス、お客様の IP アドレスまたはデバイスの ID が含まれます。この情報に併せて、Terminusがお客様から収集したデータを使用する場合があります。Terminusに提供しているデータを弊社が使用するのは、お客様のデジタル広告体験をより適切にカスタマイズし、関連性の高い広告をお客様に配信するためです。. Terminus プライバシー ポリシー
StackAdapt
弊社は、StackAdaptがサポートするサイトに広告を配置するために、StackAdaptを利用しています。広告には、StackAdaptのデータと、弊社サイトにアクセスしているお客様から弊社が収集する行動に関するデータの両方が使われます。弊社が収集するデータには、お客様がアクセスしたページ、ご利用中の体験版、再生したビデオ、購入した製品やサービス、お客様の IP アドレスまたはデバイスの ID が含まれます。この情報に併せて、StackAdaptがお客様から収集したデータを使用する場合があります。StackAdaptに提供しているデータを弊社が使用するのは、お客様のデジタル広告体験をより適切にカスタマイズし、関連性の高い広告をお客様に配信するためです。. StackAdapt プライバシー ポリシー
The Trade Desk
弊社は、The Trade Deskがサポートするサイトに広告を配置するために、The Trade Deskを利用しています。広告には、The Trade Deskのデータと、弊社サイトにアクセスしているお客様から弊社が収集する行動に関するデータの両方が使われます。弊社が収集するデータには、お客様がアクセスしたページ、ご利用中の体験版、再生したビデオ、購入した製品やサービス、お客様の IP アドレスまたはデバイスの ID が含まれます。この情報に併せて、The Trade Deskがお客様から収集したデータを使用する場合があります。The Trade Deskに提供しているデータを弊社が使用するのは、お客様のデジタル広告体験をより適切にカスタマイズし、関連性の高い広告をお客様に配信するためです。. The Trade Desk プライバシー ポリシー
RollWorks
We use RollWorks to deploy digital advertising on sites supported by RollWorks. Ads are based on both RollWorks data and behavioral data that we collect while you’re on our sites. The data we collect may include pages you’ve visited, trials you’ve initiated, videos you’ve played, purchases you’ve made, and your IP address or device ID. This information may be combined with data that RollWorks has collected from you. We use the data that we provide to RollWorks to better customize your digital advertising experience and present you with more relevant ads. RollWorks Privacy Policy

オンライン体験の品質向上にぜひご協力ください

オートデスクは、弊社の製品やサービスをご利用いただくお客様に、優れた体験を提供することを目指しています。これまでの画面の各項目で[はい]を選択したお客様については、弊社でデータを収集し、カスタマイズされた体験の提供とアプリケーションの品質向上に役立てさせていただきます。この設定は、プライバシー ステートメントにアクセスすると、いつでも変更できます。

お客様の顧客体験は、お客様が自由に決められます。

オートデスクはお客様のプライバシーを尊重します。オートデスクでは収集したデータを基に、お客様が弊社製品をどのように利用されているのか、お客様が関心を示しそうな情報は何か、オートデスクとの関係をより価値あるものにするには、どのような改善が可能かを理解するよう務めています。

そこで、お客様一人ひとりに合わせた体験を提供するために、お客様のデータを収集し、使用することを許可いただけるかどうかお答えください。

体験をカスタマイズすることのメリットにつきましては、本サイトのプライバシー設定の管理でご確認いただけます。弊社のプライバシー ステートメントでも、選択肢について詳しく説明しております。