AU Class
AU Class
class - AU

Innovating with the Advanced Turnout Catalog Implementation in Civil 3D

Share this class

Description

Join us as we explore the heart of rail alignment design. Turnouts are not just critical components of heavy rail; they also form the backbone of all rail projects, including light rail, metro, and high-speed rail systems. Our session is designed to empower you with the necessary skills to create your configuration file for turnout creation in Civil 3D software. Moreover, we'll guide you through the process of translating your geometrical requirements into a comprehensive turnout catalog. This presentation is your ticket to mastering the dynamics of rail alignment design, challenging conventions, and setting new standards in railway infrastructure.

Key Learnings

  • Learn about the diverse components that constitute the turnout catalog.
  • Master the essential elements required for modifying or creating various catalogs.
  • Gain proficiency in establishing different rules pertaining to the turnout catalog.

Speaker

  • Avatar for Heidi Castellanos Leyra
    Heidi Castellanos Leyra
    Heidi is a seasoned railway engineer with over 15 years of experience in the infrastructure industry. She spent more than a decade with the French National Railways (SNCF), focusing on alignment track design across a variety of projects. Her work ranged from routine maintenance to the development of new lines, high-speed rails, and heavy rail systems, all while contributing to national alignment specifications. At SNCF, Heidi played a significant role in the BIM strategic program, working to implement innovative new workflows for alignment, track, earthworks, and drainage. Her commitment to advancement in the industry led her to join the Building Smart group for IFC RAIL in 2019. A year ago, Heidi joined Autodesk as an implementation consultant. In this role, she collaborates with a diverse range of clients, implementing solutions that enhance their day-to-day workflows. Her efforts have brought efficiency and effectiveness to their operations, illustrating her proficiency in workflow optimization. In this class, Heidi will share her knowledge and practical experience of the Autodesk (ADSK) turnout tools to implement and configure new turnout catalogs.
Video Player is loading.
Current Time 0:00
Duration 44:31
Loaded: 0.37%
Stream Type LIVE
Remaining Time 44:31
 
1x
  • Chapters
  • descriptions off, selected
  • en (Main), selected
Transcript

HEIDI CASTELLANOS LEYRA: Hi, everyone. So today we are here to talk about how to innovate with the advanced turnout catalog implementation for Civil 3D. First of all, we are going to do a quick safe harbor statement. Please remember that everything that is presented in this current is in the current state of tools and that it may evolve with new releases. So please do not make any purchase based on the statements that we are going to make today. So about me, I'm Heidi Castellanos Leyra. I'm an implementation consultant in Autodesk. I'm based in Paris, France, and I'm have more or less 15 years of infrastructure experience with design, construction, and maintenance and mainly 10 years in rail in the French railway company.

So for the class summary, what we're going to see today, we are going to start with the 3D supported geometry and catalogs that we have in the new tool for turnouts, the configuration files content, what it's in there, the basics, so you can define your own configuration file, and a quick guide on parameters needed in your catalog file. And we are going to do-- this all will be based in one practical example. So at the end you can get the files that we are going to work on and then you can modify and play with them.

Well, two of the main objectives of the learning of the class today will be acquire knowledge about the diverse components that will constitute this turnout catalog that we are going to need in the tool and mastering the essential elements required to creating this catalog, like all the basics that you need to know. So we're going to go ahead and start with Y turnouts.

I guess most of you are in the rail industry, so you are already aware that turnouts are a core component in the rail design. They are present in all types of metro, all types of rail projects, in heavy rail, high speed metro, tram, high speed lines. So no railway can be operational without the turnouts. So that's why it's important to have a tool that allows us to go ahead and use this element in the track design.

And one other thing that you may also be aware of is that there are multiple and different standards around the globe. So unfortunately, we don't have one international standard. So the Civil 3D tool, what it's aiming to be, it's versatile enough to integrate these different kind of models and different types of turnouts. And it's aiming this by being flexible enough to integrate different construction rules and different behavior rules.

C3D right now, what it's going to be supporting is five different types of turnouts, right? So we're going to have simple switches, symmetrical, doubled turnout or three tracks turnout, crossing, that can be also classical, simple, and double, and combined crossing. So these are basically the five that we are supporting right now, that the product is supporting.

And we are going to do-- we are going to center ourselves today in the simple switch. Why? Because I think it's the easiest one to do in the catalog, and also because once you master the easiest one, it will be easier for you to configure the other type of models. And also because I think it's the most current one used in the rail industry, so it will cover most of the use cases.

So the type of insulation that we support in Civil 3D will be a straight and bend. And we will have different track geometries supported. So your track geometry, your diverted track geometry can be composed of lines, of radius, or transition curves. We do not support for the moment the installation for the main track in transition curve, so only in diverted line.

So we'll go ahead and have a small overview of the tool, where to access it and where to upload these configuration files. So actually this is a ribbon of rail in Civil 3D. You can access here in create turnout and create your crossover, the main tool of creating a turnout.

But what you need to do first before that is loading your turnout catalog. And this is the whole point of this class. We are going to learn how to configure this files that you need. The tool will ask you to upload first a new catalog and then you will be searching for a JSON file. This JSON file is the one that you have to upload.

So right now the tool has different catalogs in the out of the box products. As you can see in the right, you will have French catalog, a generic catalog that you can use as a base, and US catalog. So it's possible for you guys to copy and to modify one of these catalogs if one of them is near to what you are using right now to your standards.

For that, it will be interesting for you to know, first of all, what's the content between the JSON file and the JSON expression. As you can see in the slide before, they always come by pairs. Like you have a JSON and you have a JSON expression file for one catalog. So why? Why do we need both?

So the first one will be the JSON file. This file will contains the catalog library and the geometrical parameters of each model. And then you will have the JSON expression file. The JSON expression file will be the one that defines how your turnouts behave, how your turnout is constructed, how your diverted line is built. And actually you will have parameters in common between the two files. So be aware of it and be super careful with spelling because it's spelling sensitive.

So to open these files, you can use visual studio code or Notepad. I recommend something that can syntax highlight because it will be easier for you to modify the files. And you can save these two files wherever you want. Like normally, if it's a standard for the whole company, you should stock it in a shared location. If not, you can just put it in your drive to work on it just before sharing.

But you always have to use the same naming for both of the files and put it in the same location, both. Just remember that. So right now, what we are going to do is, I'm going to show you some semantics that we are using in this configuration files. For some of you, if you already try to read these files, you are going to see that we don't use the common or standard naming for the critical points. We are using some French standards because we first did the French catalog.

So we are keeping this naming. Don't worry. This naming is-- you can completely customize this naming. It's just if you want to understand the files that are by default in the product, I would like you to know what's the semantic that it's being used. So we're going to start with the GP. It's the vocabulary for the critical points. The GP will be the stock rail joint. The [INAUDIBLE] will be the point of the switch. CM will be the point of intersection between the two tangents. JT will be the heel of the front of the turnout, and Cut A will be the last long tie and Cut B will be the small tie.

So for the content of the files, here I'm going to give a brief overview of the content. And then in the second part of the presentation, we will start going along the files to see what do you have to modify in each file. So for the JSON configuration file, we have the parameters node. That is going to be a list basically of parameters with the naming and the units that you are using. You are just creating the parameters. You are not going to put any numerical value on it, it's just creation of the parameters.

Then you have something called public parameters that are the parameters that you want to be able to see and visualize in the user interface. And then you will have critical points saying you are going to name it only. You are creating the critical points. This when you can change the semantics use. Like instead of GP for example, you can use P3, 0.1, 0.2, whatever you want.

And then you have the node of turnout types. This node defines all types and the list of parameters for type. So yes, basically right now in this class, we will only do the single type, the simple switch. But it's normally made so you can list the different types you want to configure. For example, simple, symmetric, tree tracks, and then lists for each type the parameters needed to build your turnouts. So as you know, each type will have different list of parameters.

And then finally the models node. This node will define the value of each parameter. So this will be more specific to the model of the turnout. You will recall the list of parameters and then you will put a numerical value in front of it.

The second file is the JSON expression file. This file can be built as ever you think it's better, you can change it. It really depends on the person who is building the file. But I will give you the basic parts that I thought it was useful to build this way the file. So we're going to start with the first part, where we are going to define basic variables that are going to be used along the file.

The second part will define your points, your critical points. The third part will define the inverted line geometry, the inverted line geometry, sorry, how it behaves in a straight pose and in a band pose. For example, the fourth part will be the exit geometry after your heel, like what's happening for the long ties or the small ties. And finally the creation of the theoretical angle or the boundary for Civil 3D visualization.

So first of all, here, we're going to start like with small tips that are going to help you building these configuration files. The first thing I will advise you to is before even thinking about touching the files, like take a look and design your sketch with your basic turnout components. You have to be able to understand how your turnout is going to behave if you want to configure that in the files.

So just take a step back, design the sketch with a basic turnout components. Then, as the theoretical triangle, then think about, do you want to represent the theoretical triangle in the center line of the tracks or there are some countries where they prefer representing this triangle in the exterior rail of the tracks. So that's what you need to be thinking about like in the representation that you want to see.

Then, exactly the same for the end of crossing. What do you want to see after the hill of the turnout? Do you want to see all the last long ties? Do you want to see the small ties? What do you want to see, how they are-- do you have the standards for the distance for this last ties? Check out the types of diverted land geometry that you want to have. Like, even if it's a simple switch that we will be working with, we all know that not all the models have the same type of diverted line.

So in your standard, you may have, I don't know, simple switches that have only a curve as a diverted line, simple switch that have a line and a curve, simple switch that have a transition curve. So define all the types of different geometry because you will need to configure the configuration file for each type of geometry you have. You want to be able to construct everything in Civil 3D. So you have to know what type of line geometry your catalog has.

And then with the list, also identify the critical points in which are based your turnouts. For example, here I identify the stock rail, the rail switchblade, the pointed intersection, my hills, and my last long ties. And as I say, we're going to use a simple example. Like this example is going to come with us along the whole hour. We are going to be recalling some of these concepts.

So take note that we will be working with a simple switch example. It will have five critical points. They are named 0.3, 0.4, 0.0, 0.1, 0.2. We will have a diverted line. That will be a diverted line that will be composed for one line, one arc, and a second line.

Note that this first line is not going to be tangent to the center, to the center line. And this second line, it's going to be tangent to the hill. And we will have three end of crossing possibilities. So we will have a straight curve, curve, and reverse curve. And we also have to define, I want to see in Civil my cut A, my last long tie point.

So just for you to basic concepts for expression files, language that you're going to see, you have to know that the points definition in expression file, it's not only the naming of this point. What you have to see is that each point has to be defined with its own coordinates. For example, here, P3, it's defined with X and Y in 0. Why in 0? Because I want that P3 to be my base point, right? So that's why it's my origin of my turnout.

And then P1, for example, has to be defined also with its coordinates and with the directions of P1. It's kind of-- yeah, it's hard to get it at first, but you will get used to. Like P1 is going to be defined from P3 with the distance from P3. So I will say, P1 in x, it's defined by the distance between P3 and P0 and the distance between P0 and P1. That's why you have the addition here.

And the coordinate in Y it's 0 because it doesn't move in Y. And for the directions are the same as I'm moving in x, it's x that is going to be 1. And my direction in Y it's going to be 0 because I'm not moving in Y. So for the geometrical elements, it's exactly the same. Like you will have constraints. You will have to put some inputs to build these geometrical elements.

So a geometrical element will be built from the start point, the direction in X and Y of this point. The end point, the direction in X and Y of this point, the length of the arc, the radius of the arc, and the direction. Is it clockwise or counterclockwise? So keep in mind this information.

And also I advise you to think about the bend behavior that you are going to-- that you want to see in the turnouts. Not every catalog and not every country bends their turnouts. But if you are bending, take a moment to think. Do all your turnouts like bend the same way? I know in France particularly, we bend two different ways.

So understand the behaviors that you want to see, to understand what you want to put in your expression file. So first of all, identify if the length of the turnout will be kept in the center line. But here, for example, here is the length in my [INAUDIBLE]. Is it the same length that I want to keep in my central line of the track? Or is it going to be calculated with a length in the exterior rail?

And also how the bending is going to affect-- sorry, my bend geometry of the diverted line. How is it going to affect the radius? How is it going to affect the length? Do you have a standards that specify how to recalculate these values and how your end of crossings are going to be calculated.

Also, what's the behavior in your standard? Are you keeping the distance between the two tracks? Are you keeping the radius at the end? Are you affecting the radius by the bend radius? How is it going to work? All of these questions you have to answer before going deep into your expression file.

And then for this example in particular, we are going to state that the length of the turnout will be kept in the center line and the geometry of the diverted will be defined as following. So as you can see, there are some formulas here that I got from our royal standard. This is the formula that will help me recalculate my new radius when my turnout is bend. So it's going to help me calculate my diverted line affected by my main track bending, and the same for the length of these elements.

So, after the basic statements, we are going to start configuring the JSON files. So here you can find you're going to have this. You can have the list of the API functions that are working in the expression file. Don't worry, I'm not going to read each one. The basic thing that you have to know is that you have different APIs functions for different goals.

So you have geometry functions that are going to help you calculate points, for example, calculate distance, calculate rotation points, this kind of things. You will have also line functions. This line functions are to create and to calculate lines from a start point or from an endpoint. Depending on the information that you have, these are going to help you build this geometry, the geometry that you have, the line.

Then you are going to have the same kind of functions, but to calculate arcs. And then you have also functions to calculate-- sorry, to query the element. So imagine you just calculated a line from the start point and you want to know what's the endpoint. So you query this line that you just created. These functions are going to be super helpful too.

And then finally, you have the functions for expression to bound to the turnout context. So everything you are going to create in expression file, you are going to calculate elements, you are going to calculate points, but they are not going to be added automatically to the turnout in Civil 3D. You have to just use these functions on function add turnout so you can add geometrical elements, so you can add critical points. So remember that. Keep that in mind.

We're going to start with expansion file directly. First of all, what I advise you is to start by defining the type of turnout that you are going to work with. Like this conditions are going to help you filtering the configuration for all your types of turnouts. So in this case, everything that I'm going to write after this condition, it's only going to work if my turnout is defined as single.

Other thing that you can see in the slide, like everything that I highlight in yellow, it's a parameter that needs to be mapped into the JSON file. Remember I told you like there are parameters that are going to be shared between the two, so they have to be spelled the same way. And then I'm going to [? call ?] them from the expression file, but they are going to be defined in the JSON file.

So define your turnout type as single. And after that, define general variables that you may recall later. So is your turnout bend? Yes, no. Define the direction of your turnout. Define some variables. Here you can see them in the expression file for those ones who haven't still built a configuration file or a JSON file. You can create variables.

What this means is that you are creating a variable. You are identifying a value next to it, and then you can record that variable, a longer expression file. Then, after defining basic variables, start defining your critical points. As I said before, your critical points need to be defined with coordinates and with directions.

So please just be aware that here in the first part you can see everything is in 0. It's because I'm just creating. the container, right. I'm just creating the variable. Even if it's empty, I will calculate the value afterwards. Then I define a function turnout entry as default. So now that I created a turnout entry, I can start defining critical points and I can start defining diverted line geometry.

As you can see here, just after I just created a turnout critical point named P3. So this P3, it's going to be located in 00, because as I said before in this example, what I want to see is my P3 to be the base or the origin, like local coordinates, I'm going to say, for my turnout. Then, add another condition to build separately the content for bend post and straight post for the single switch.

So we are going to start with the easier. That it's the straight post. What you can do is recall every point that you just created. Like I'm recalling P0, P1, P2, and I'm defining them. So how am I going to define them?

As I said before, here, for example, I'm defining P0, so I will be defining it from P3. So I'm going to be defining it with the distance between P3 and P0. And it will be the same for P1. It will be defined in X from the distance from P3 to P1. So I add this expression, right?

And for P2, what I'm doing, is creating a point that will start from P0 with the length of P0 to P2, but it's going to be created here first and then I will rotate it with the angle. The angle, as you can see, is already a variable that I created in the first part of my expression file.

And then I will define this variable, that it's kind of useful depending on your type of turnouts on the diversity of your diverted line geometry. I decided to start creating, I start straight. This will be the point where my diverted geometry will start. And in this specific case, for this example, it will be the same as before. But it's not always the case.

Like in this practical case, I'm starting my only geometry that we are going to define from before. But you can start your geometry. Maybe there are models that start from P3 or for a theoretical point before P3. I don't know. So this is a way that you can change it

Then, yes, then we will start defining geometry for the diverted line. So first of all, where do we start? So remember, my practical case was with three geometrical elements, line, curve, line. And I told you this line is tangent to P2. This line is not tangent to anything well, only to this arc. But we don't have this arc.

So I will advise you to start with the element that it's easier to calculate. So in this case will be line two. So you can use an API function and recall the length of the line 2 from the JSON file. Again, this is in yellow because it will be defined in the JSON file also.

So you have an endpoint that it's P2. You have the direction for P2. You have the length of line 2. So now you can use the API function. You see here, it's a function that it's calling-- it's creating a line from the endpoint with the length. And you have all these variables. So you can create it from P2 with the coordinates, with the direction of P2 that you just defined in the step before and the length of line 2.

So this will create your line. This will calculate your line. But it's not adding it to the turnout. So you need to use another function to add it to the turnout. Just, you are saying-- here, you are saying just add to the turnout, the line two that I just calculated. And then as you have your line, what do you need after that? You will need to define this start point.

This start point, you don't know it. You don't know the coordinates, but you will need it because it's the base of this arc. Because this start point is the endpoint for the arc. So in order to be able to use the functions to create this arc, you have to find out these points.

So this point, you are going to find out how you are going to query the line. That's why I say those functions about query are important. So you can see them here, function dash curve, start point, line two. So give me the start point of this line. And you are going to do the same for the other line. You are going to create your arc. You're going to add it to the turnout, and then you're going to create the last line.

The next step will be creating the arc. As you can see put you create variables to the radius and the length that are defined in the JSON file. And you do exactly the same. With the API function, with the start point. Here, you will create the arc and then the line. And that will create your diverted line geometry for a straight post.

Now we're going to repeat the same process, but for bending. There are some-- basically it's the same. You just have to integrate the impacts of the main radius of the main track bend in the diverted line geometry. So how are we going to do that? We are going to define some variables here same.

What I'm doing first of all, the most important one for me, it's before, because I'm going to be defining the point where my diverted line geometry is going to start. So, same, use the API functions. They are the same functions that I showed you before. And I'm going to start from 0, like from my P3 with my instant radius, with my length that I know from P3 to before. And I'm going to use the central line in the direction of my central line.

And I'm going to add these critical points before. Then what I'm going to do is create this variable that is also important. It's the length. Remember, my length was going to be kept in the center line. So what I'm saying is creating this variable, it's going to be the length between P3 and P1. And I'm going to use it to create the main arc in the main track. I'm going to create this arc.

Just theoretically, I'm not going to put it in Civil 3D because in Civil 3D, it already exists because it's an alignment, right? But I have to calculate so I can be able to calculate P1 here. So what I'm doing is calculating this arc from P3 with the length that I know because the length is this one that I just calculated and with the instant radius that is calling. Instant radius here, this variable, is calling the instant radius of my alignment in 3D.

And then I will be able to calculate my P1. Like, I'm going to query this arc and I'm going to tell the expression file, give me the endpoint of this arc. And then I'm going to be able to calculate P1 as I say here. I already calculated the center line. So I have the center line. Please give me the endpoint of the center line. And please give me the end direction so I can have the coordinates and the direction of this point.

And I'm going to do the same from here. I'm going to calculate P0 because P0, I can calculate with P0 distance that I have in my JSON file. So I'm going to do exactly the same thing, like more or less the same thing. I'm going to use the API functions. And I'm going to ask him, draw a line, calculate a line that comes from P1 with this direction that I just got with this length. And I'm going to be able to calculate P0.

And from P0, I can calculate P2 with the P0, P2 distance. Now you have your critical points for a band pose. Now we're going to pass to create the diverted line geometry when it's bent, how your turnout is going to behave. How am I going to do that? If you remember, like my geometry of the diverted line in this example, I started with my line 2 because it was the easiest one. So this line 2, what is going to happen when I bend?

This line 2 will become a radius because you are bending, right? It's going to be affected by the main radius. And the arc that we are going to [? call ?] with the radius of the diverted line, it's going to be another radius. It's going to be affected. It's not going to be the same value because you are bending the geometry.

So I go to my standards. I found out the rules for calculating this radius. So, here in this particular case, I'm using these formulas when it's external to my radius and these formulas when it's internal, right? So there will be a condition there.

And then I will have 3-- I will have my line 2, my line 1, sorry, that is going to become also a radius. OK, so let's continue with the diverted line geometry for bend. It's as you can see, the same structure as the straight post. The basic thing that I'm going to change is that the definition of length and radius, because this is what's affected by the bending, right?

So for my line 2, what I'm going to do is integrate this condition about if it's inside the radius or outside the radius. So I can use this external, internal. If it's internal, I'm telling him, use these formulas. If it's external, use this expression. So I'm just transcribing this expression into here.

As you can see, instant radius will be the main track radius. Line 2 length-- sorry, I'm with length so it's these formulas like, in the bottom. So go fetch the parameter that is in my JSON file, and then apply the formula. It's exactly-- I'm just doing a parallel between what's in my [? civil ?] and my formulas. For example, here, [? ARC ?] is going to be the main track radius, so it's instant radius. My [? land ?] 2 [? land ?] is my land in a straight post. And then you're going to get with this formula the new length of the geometrical element.

Once you do this condition, what you are going to do here when you are creating the line, be attentive. Like this line before we just, we use a function calculating a line. As I say, we are going to keep the name so it makes sense. But it's not longer a line. It will be an arc, because it will be bent.

So you have here, calculate an arc with the endpoint that will be P2 with its direction, with the main radius, with the line that you just calculated with this expression, and the direction clockwise or counter-clockwise, and then add it to the turnout. So you are going to do the same. You are going to query for the start point. And then for the arc, you are going to do exactly the same thing that you did for a line. But we are going to do it also for the radius, because the value of the radius will be different.

So you are going to go do the same thing, use API functions, find out query for the start point, and then draw the last line. So now you have your diverted line geometry in both cases, straight and bend. Then you also define along the way, P3 and P4. So now you can define your other critical points, P0, P1, P2. These ones in the expression file will be just function set to turn on critical points with the naming and with the coordinates.

It's going to be simple because you already defined the coordinates in the different cases. So these expressions are just going to go fetch the good definition in your expression file. So they are already defined in the file. Here I'm just adding and I'm just going, fetching the good coordinates.

And then we are going to go through the definition of the exit curves. You have three, reverse, straight, and curve. So you will go ahead. It's the same process. Part one, define some variables, new variables. Then we are going to do the exit curve for the straight post. So if you can see here, you're using-- I'm creating this variable that is called exit curve index that I'm recalling here.

So the only thing you are going to do is create another arc, another arc, yes, another arc here with starting from P2 that you already have the coordinates. So you can start from P2. You have the direction. You have the radius because it will be the same radius as the main track. So you will put [INAUDIBLE] radius. You're going to [? call ?] for a parameter in the JSON that will give you the length. And that's it for bending.

And for straight, it's not an arc. It's a line. So you are just going to create a line from P2 with the length that you are going to [? call ?] from the JSON file. And then for the curve type, remember we had a straight curve and reverse curve. So we are just going to do the curve.

Right away, what we do is create a condition, also a variable with a condition, to say, to integrate the same formulas. If it's internal, if it's external, choose your-- we are telling them, we are telling Civil3D to choose between the two conditions. And then we are going to create this curve radius.

Why am I creating another Variable It's because it doesn't matter if it's a straight or bent. The curve type that I'm looking for, it's always going to be a curve. So what I'm telling Civil here is if it's bend, use this new value that it's called bend curve. If it's not bend, just use the radius that I'm putting in the JSON file.

And then we are just going to create with the functions, a curve that are going to begin from P2 with the directions that I'm going to use curve radius because he's the one who's going to do the choice with the condition. And then use the exit curve length that I put in the JSON file. So that's it. That's our exit curves.

And then what I'm doing, is-- what we are doing is querying for knowing the endpoint in this curve. I want to know the endpoint, because the endpoint in this curve will be my cut, my point that is going to be called cote A, cote A diverted, cote A main. So basically, I'm telling it, please let me know the point at the end of exit curve.

I'm going to put here the variable, the line that I want to use. I'm going to put 1 because I want to know the endpoint. And then I'm telling, please set a critical point that is going to be called cote A diverted at the end of this variable. OK? Yeah. And that's it.

For the main line, yeah sorry, for the main line, I'm going to do the same. It's just that I'm going to add the choice-- the-- sorry, the-- yeah, they chose a condition, sorry. And if it's bent, or if it's in a straight line. So I'm just going to do the same. But I'm going to add a condition.

And then for the JSON file, the JSON file, it will be-- it's much more simpler. Like as I say, we have five principal nodes that we're going to go through. The first node will be parameters. Well, you can put comments and everything, and then you have some parameters. Here in the parameters, you have to define every distance, like every distance that you are going to use. In the expression file, you have to define it.

You have to define also the geometrical characteristics that you are [? calling ?] from the expression file. And you have to define also some other parameters, like angle of the turnouts or the length of the end of crossing. You are just creating. You are not giving numerical values, you're just creating. Then you have the node critical points and it will be naming the critical point and add some kind of description. And these are the same trigger points that you can find in your expression. So be aware of the spelling.

And then the turnout [? starts. ?] But note, it's going to be what I was telling you a couple of minutes ago. You are going to list for this type of turnout, single, using these parameters. Like so just be careful to use-- to list every parameter that you are going to be using, that you are going to need in your expression file.

And then the last node. It's model. Here is where I'm adding the description, like the values, the real values of my turnout. So I call this turnout tangent 11. It's a single. I have a layout type and I put all the dimensions here.

So for example, take a look, a good look of arc radius. It's 214 and the length of the line, 177. So we're going to check out in Civil afterwards after integrating my catalog, if I found a good values. Just take these two as an example. And then, we're going to check in Civil here. If it's-- yeah, I'm going to check it here.

Yeah, so here, you see, in Civil, I just did a rail, a basic rail alignment. I have a straight line, I have a curve. And then I'm going to upload my turnout catalog in the ribbon. I'm going to add a new catalog. I use my JSON file only the JSON. The expression is going to run in the background.

JSON file, I'm going to open it. I'm going to say, OK. And then I'm going to create a turnout. You're going to see the UI open here. You can find my catalog, its name, Autodesk metric. I only have the symbol that we just created with only the model 11 that I showed you before.

It's the only thing that I have in this file I'm going to create. And I have my turnout, right? So it has an [? alert ?] because remember, the first line is not tangent. As you can see in the geometry editor, I ask you to remember the geometry of the diverted line. You can find the same values as your expression.

So you will have the small line of 177 and the radius of 214. And what's going to happen is you are going to move it-- if you want to move your turnout, yeah, you have also the end of crossing that we define. And when we move it, your geometry of the diverted line is automatically going to change. And if you see the values, they are not longer, the same values because they are affected by the expressions that we put in the expression file. And it's automatically calculating your diverted line geometry. OK?

So, as a conclusion, the important things to keep in mind is identify your turnout components. Start simple. Get familiar first on the language using the files and remember to keep coherence between the two of the files. And I hope this was helpful for you guys. Thank you very much. Yeah, thank you very much. That's it.

______
icon-svg-close-thick

Cookie preferences

Your privacy is important to us and so is an optimal experience. To help us customize information and build applications, we collect data about your use of this site.

May we collect and use your data?

Learn more about the Third Party Services we use and our Privacy Statement.

Strictly necessary – required for our site to work and to provide services to you

These cookies allow us to record your preferences or login information, respond to your requests or fulfill items in your shopping cart.

Improve your experience – allows us to show you what is relevant to you

These cookies enable us to provide enhanced functionality and personalization. They may be set by us or by third party providers whose services we use to deliver information and experiences tailored to you. If you do not allow these cookies, some or all of these services may not be available for you.

Customize your advertising – permits us to offer targeted advertising to you

These cookies collect data about you based on your activities and interests in order to show you relevant ads and to track effectiveness. By collecting this data, the ads you see will be more tailored to your interests. If you do not allow these cookies, you will experience less targeted advertising.

icon-svg-close-thick

THIRD PARTY SERVICES

Learn more about the Third-Party Services we use in each category, and how we use the data we collect from you online.

icon-svg-hide-thick

icon-svg-show-thick

Strictly necessary – required for our site to work and to provide services to you

Qualtrics
We use Qualtrics to let you give us feedback via surveys or online forms. You may be randomly selected to participate in a survey, or you can actively decide to give us feedback. We collect data to better understand what actions you took before filling out a survey. This helps us troubleshoot issues you may have experienced. Qualtrics Privacy Policy
Akamai mPulse
We use Akamai mPulse to collect data about your behavior on our sites. This may include pages you’ve visited, trials you’ve initiated, videos you’ve played, purchases you’ve made, your IP address or device ID, and your Autodesk ID. We use this data to measure our site performance and evaluate the ease of your online experience, so we can enhance our features. We also use advanced analytics methods to optimize your experience with email, customer support, and sales. Akamai mPulse Privacy Policy
Digital River
We use Digital River to collect data about your behavior on our sites. This may include pages you’ve visited, trials you’ve initiated, videos you’ve played, purchases you’ve made, your IP address or device ID, and your Autodesk ID. We use this data to measure our site performance and evaluate the ease of your online experience, so we can enhance our features. We also use advanced analytics methods to optimize your experience with email, customer support, and sales. Digital River Privacy Policy
Dynatrace
We use Dynatrace to collect data about your behavior on our sites. This may include pages you’ve visited, trials you’ve initiated, videos you’ve played, purchases you’ve made, your IP address or device ID, and your Autodesk ID. We use this data to measure our site performance and evaluate the ease of your online experience, so we can enhance our features. We also use advanced analytics methods to optimize your experience with email, customer support, and sales. Dynatrace Privacy Policy
Khoros
We use Khoros to collect data about your behavior on our sites. This may include pages you’ve visited, trials you’ve initiated, videos you’ve played, purchases you’ve made, your IP address or device ID, and your Autodesk ID. We use this data to measure our site performance and evaluate the ease of your online experience, so we can enhance our features. We also use advanced analytics methods to optimize your experience with email, customer support, and sales. Khoros Privacy Policy
Launch Darkly
We use Launch Darkly to collect data about your behavior on our sites. This may include pages you’ve visited, trials you’ve initiated, videos you’ve played, purchases you’ve made, your IP address or device ID, and your Autodesk ID. We use this data to measure our site performance and evaluate the ease of your online experience, so we can enhance our features. We also use advanced analytics methods to optimize your experience with email, customer support, and sales. Launch Darkly Privacy Policy
New Relic
We use New Relic to collect data about your behavior on our sites. This may include pages you’ve visited, trials you’ve initiated, videos you’ve played, purchases you’ve made, your IP address or device ID, and your Autodesk ID. We use this data to measure our site performance and evaluate the ease of your online experience, so we can enhance our features. We also use advanced analytics methods to optimize your experience with email, customer support, and sales. New Relic Privacy Policy
Salesforce Live Agent
We use Salesforce Live Agent to collect data about your behavior on our sites. This may include pages you’ve visited, trials you’ve initiated, videos you’ve played, purchases you’ve made, your IP address or device ID, and your Autodesk ID. We use this data to measure our site performance and evaluate the ease of your online experience, so we can enhance our features. We also use advanced analytics methods to optimize your experience with email, customer support, and sales. Salesforce Live Agent Privacy Policy
Wistia
We use Wistia to collect data about your behavior on our sites. This may include pages you’ve visited, trials you’ve initiated, videos you’ve played, purchases you’ve made, your IP address or device ID, and your Autodesk ID. We use this data to measure our site performance and evaluate the ease of your online experience, so we can enhance our features. We also use advanced analytics methods to optimize your experience with email, customer support, and sales. Wistia Privacy Policy
Tealium
We use Tealium to collect data about your behavior on our sites. This 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. We use this data to measure our site performance and evaluate the ease of your online experience, so we can enhance our features. We also use advanced analytics methods to optimize your experience with email, customer support, and sales. Tealium Privacy Policy
Upsellit
We use Upsellit to collect data about your behavior on our sites. This 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. We use this data to measure our site performance and evaluate the ease of your online experience, so we can enhance our features. We also use advanced analytics methods to optimize your experience with email, customer support, and sales. Upsellit Privacy Policy
CJ Affiliates
We use CJ Affiliates to collect data about your behavior on our sites. This 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. We use this data to measure our site performance and evaluate the ease of your online experience, so we can enhance our features. We also use advanced analytics methods to optimize your experience with email, customer support, and sales. CJ Affiliates Privacy Policy
Commission Factory
We use Commission Factory to collect data about your behavior on our sites. This 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. We use this data to measure our site performance and evaluate the ease of your online experience, so we can enhance our features. We also use advanced analytics methods to optimize your experience with email, customer support, and sales. Commission Factory Privacy Policy
Google Analytics (Strictly Necessary)
We use Google Analytics (Strictly Necessary) to collect data about your behavior on our sites. This may include pages you’ve visited, trials you’ve initiated, videos you’ve played, purchases you’ve made, your IP address or device ID, and your Autodesk ID. We use this data to measure our site performance and evaluate the ease of your online experience, so we can enhance our features. We also use advanced analytics methods to optimize your experience with email, customer support, and sales. Google Analytics (Strictly Necessary) Privacy Policy
Typepad Stats
We use Typepad Stats to collect data about your behaviour on our sites. This may include pages you’ve visited. We use this data to measure our site performance and evaluate the ease of your online experience, so we can enhance our platform to provide the most relevant content. This allows us to enhance your overall user experience. Typepad Stats Privacy Policy
Geo Targetly
We use Geo Targetly to direct website visitors to the most appropriate web page and/or serve tailored content based on their location. Geo Targetly uses the IP address of a website visitor to determine the approximate location of the visitor’s device. This helps ensure that the visitor views content in their (most likely) local language.Geo Targetly Privacy Policy
SpeedCurve
We use SpeedCurve to monitor and measure the performance of your website experience by measuring web page load times as well as the responsiveness of subsequent elements such as images, scripts, and text.SpeedCurve Privacy Policy
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

Improve your experience – allows us to show you what is relevant to you

Google Optimize
We use Google Optimize to test new features on our sites and customize your experience of these features. To do this, we collect behavioral data while you’re on our sites. This data may include pages you’ve visited, trials you’ve initiated, videos you’ve played, purchases you’ve made, your IP address or device ID, your Autodesk ID, and others. You may experience a different version of our sites based on feature testing, or view personalized content based on your visitor attributes. Google Optimize Privacy Policy
ClickTale
We use ClickTale to better understand where you may encounter difficulties with our sites. We use session recording to help us see how you interact with our sites, including any elements on our pages. Your Personally Identifiable Information is masked and is not collected. ClickTale Privacy Policy
OneSignal
We use OneSignal to deploy digital advertising on sites supported by OneSignal. Ads are based on both OneSignal 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 OneSignal has collected from you. We use the data that we provide to OneSignal to better customize your digital advertising experience and present you with more relevant ads. OneSignal Privacy Policy
Optimizely
We use Optimizely to test new features on our sites and customize your experience of these features. To do this, we collect behavioral data while you’re on our sites. This data may include pages you’ve visited, trials you’ve initiated, videos you’ve played, purchases you’ve made, your IP address or device ID, your Autodesk ID, and others. You may experience a different version of our sites based on feature testing, or view personalized content based on your visitor attributes. Optimizely Privacy Policy
Amplitude
We use Amplitude to test new features on our sites and customize your experience of these features. To do this, we collect behavioral data while you’re on our sites. This data may include pages you’ve visited, trials you’ve initiated, videos you’ve played, purchases you’ve made, your IP address or device ID, your Autodesk ID, and others. You may experience a different version of our sites based on feature testing, or view personalized content based on your visitor attributes. Amplitude Privacy Policy
Snowplow
We use Snowplow to collect data about your behavior on our sites. This may include pages you’ve visited, trials you’ve initiated, videos you’ve played, purchases you’ve made, your IP address or device ID, and your Autodesk ID. We use this data to measure our site performance and evaluate the ease of your online experience, so we can enhance our features. We also use advanced analytics methods to optimize your experience with email, customer support, and sales. Snowplow Privacy Policy
UserVoice
We use UserVoice to collect data about your behaviour on our sites. This may include pages you’ve visited. We use this data to measure our site performance and evaluate the ease of your online experience, so we can enhance our platform to provide the most relevant content. This allows us to enhance your overall user experience. UserVoice Privacy Policy
Clearbit
Clearbit allows real-time data enrichment to provide a personalized and relevant experience to our customers. 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.Clearbit Privacy Policy
YouTube
YouTube is a video sharing platform which allows users to view and share embedded videos on our websites. YouTube provides viewership metrics on video performance. YouTube Privacy Policy

icon-svg-hide-thick

icon-svg-show-thick

Customize your advertising – permits us to offer targeted advertising to you

Adobe Analytics
We use Adobe Analytics to collect data about your behavior on our sites. This may include pages you’ve visited, trials you’ve initiated, videos you’ve played, purchases you’ve made, your IP address or device ID, and your Autodesk ID. We use this data to measure our site performance and evaluate the ease of your online experience, so we can enhance our features. We also use advanced analytics methods to optimize your experience with email, customer support, and sales. Adobe Analytics Privacy Policy
Google Analytics (Web Analytics)
We use Google Analytics (Web Analytics) to collect data about your behavior on our sites. This 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. We use this data to measure our site performance and evaluate the ease of your online experience, so we can enhance our features. We also use advanced analytics methods to optimize your experience with email, customer support, and sales. Google Analytics (Web Analytics) Privacy Policy
AdWords
We use AdWords to deploy digital advertising on sites supported by AdWords. Ads are based on both AdWords 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 AdWords has collected from you. We use the data that we provide to AdWords to better customize your digital advertising experience and present you with more relevant ads. AdWords Privacy Policy
Marketo
We use Marketo to send you more timely and relevant email content. To do this, we collect data about your online behavior and your interaction with the emails we send. Data collected may include pages you’ve visited, trials you’ve initiated, videos you’ve played, purchases you’ve made, your IP address or device ID, email open rates, links clicked, and others. We may combine this data with data collected from other sources to offer you improved sales or customer service experiences, as well as more relevant content based on advanced analytics processing. Marketo Privacy Policy
Doubleclick
We use Doubleclick to deploy digital advertising on sites supported by Doubleclick. Ads are based on both Doubleclick 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 Doubleclick has collected from you. We use the data that we provide to Doubleclick to better customize your digital advertising experience and present you with more relevant ads. Doubleclick Privacy Policy
HubSpot
We use HubSpot to send you more timely and relevant email content. To do this, we collect data about your online behavior and your interaction with the emails we send. Data collected may include pages you’ve visited, trials you’ve initiated, videos you’ve played, purchases you’ve made, your IP address or device ID, email open rates, links clicked, and others. HubSpot Privacy Policy
Twitter
We use Twitter to deploy digital advertising on sites supported by Twitter. Ads are based on both Twitter 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 Twitter has collected from you. We use the data that we provide to Twitter to better customize your digital advertising experience and present you with more relevant ads. Twitter Privacy Policy
Facebook
We use Facebook to deploy digital advertising on sites supported by Facebook. Ads are based on both Facebook 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 Facebook has collected from you. We use the data that we provide to Facebook to better customize your digital advertising experience and present you with more relevant ads. Facebook Privacy Policy
LinkedIn
We use LinkedIn to deploy digital advertising on sites supported by LinkedIn. Ads are based on both LinkedIn 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 LinkedIn has collected from you. We use the data that we provide to LinkedIn to better customize your digital advertising experience and present you with more relevant ads. LinkedIn Privacy Policy
Yahoo! Japan
We use Yahoo! Japan to deploy digital advertising on sites supported by Yahoo! Japan. Ads are based on both Yahoo! Japan 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 Yahoo! Japan has collected from you. We use the data that we provide to Yahoo! Japan to better customize your digital advertising experience and present you with more relevant ads. Yahoo! Japan Privacy Policy
Naver
We use Naver to deploy digital advertising on sites supported by Naver. Ads are based on both Naver 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 Naver has collected from you. We use the data that we provide to Naver to better customize your digital advertising experience and present you with more relevant ads. Naver Privacy Policy
Quantcast
We use Quantcast to deploy digital advertising on sites supported by Quantcast. Ads are based on both Quantcast 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 Quantcast has collected from you. We use the data that we provide to Quantcast to better customize your digital advertising experience and present you with more relevant ads. Quantcast Privacy Policy
Call Tracking
We use Call Tracking to provide customized phone numbers for our campaigns. This gives you faster access to our agents and helps us more accurately evaluate our performance. We may collect data about your behavior on our sites based on the phone number provided. Call Tracking Privacy Policy
Wunderkind
We use Wunderkind to deploy digital advertising on sites supported by Wunderkind. Ads are based on both Wunderkind 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 Wunderkind has collected from you. We use the data that we provide to Wunderkind to better customize your digital advertising experience and present you with more relevant ads. Wunderkind Privacy Policy
ADC Media
We use ADC Media to deploy digital advertising on sites supported by ADC Media. Ads are based on both ADC Media 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 ADC Media has collected from you. We use the data that we provide to ADC Media to better customize your digital advertising experience and present you with more relevant ads. ADC Media Privacy Policy
AgrantSEM
We use AgrantSEM to deploy digital advertising on sites supported by AgrantSEM. Ads are based on both AgrantSEM 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 AgrantSEM has collected from you. We use the data that we provide to AgrantSEM to better customize your digital advertising experience and present you with more relevant ads. AgrantSEM Privacy Policy
Bidtellect
We use Bidtellect to deploy digital advertising on sites supported by Bidtellect. Ads are based on both Bidtellect 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 Bidtellect has collected from you. We use the data that we provide to Bidtellect to better customize your digital advertising experience and present you with more relevant ads. Bidtellect Privacy Policy
Bing
We use Bing to deploy digital advertising on sites supported by Bing. Ads are based on both Bing 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 Bing has collected from you. We use the data that we provide to Bing to better customize your digital advertising experience and present you with more relevant ads. Bing Privacy Policy
G2Crowd
We use G2Crowd to deploy digital advertising on sites supported by G2Crowd. Ads are based on both G2Crowd 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 G2Crowd has collected from you. We use the data that we provide to G2Crowd to better customize your digital advertising experience and present you with more relevant ads. G2Crowd Privacy Policy
NMPI Display
We use NMPI Display to deploy digital advertising on sites supported by NMPI Display. Ads are based on both NMPI Display 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 NMPI Display has collected from you. We use the data that we provide to NMPI Display to better customize your digital advertising experience and present you with more relevant ads. NMPI Display Privacy Policy
VK
We use VK to deploy digital advertising on sites supported by VK. Ads are based on both VK 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 VK has collected from you. We use the data that we provide to VK to better customize your digital advertising experience and present you with more relevant ads. VK Privacy Policy
Adobe Target
We use Adobe Target to test new features on our sites and customize your experience of these features. To do this, we collect behavioral data while you’re on our sites. This data may include pages you’ve visited, trials you’ve initiated, videos you’ve played, purchases you’ve made, your IP address or device ID, your Autodesk ID, and others. You may experience a different version of our sites based on feature testing, or view personalized content based on your visitor attributes. Adobe Target Privacy Policy
Google Analytics (Advertising)
We use Google Analytics (Advertising) to deploy digital advertising on sites supported by Google Analytics (Advertising). Ads are based on both Google Analytics (Advertising) 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 Google Analytics (Advertising) has collected from you. We use the data that we provide to Google Analytics (Advertising) to better customize your digital advertising experience and present you with more relevant ads. Google Analytics (Advertising) Privacy Policy
Trendkite
We use Trendkite to deploy digital advertising on sites supported by Trendkite. Ads are based on both Trendkite 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 Trendkite has collected from you. We use the data that we provide to Trendkite to better customize your digital advertising experience and present you with more relevant ads. Trendkite Privacy Policy
Hotjar
We use Hotjar to deploy digital advertising on sites supported by Hotjar. Ads are based on both Hotjar 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 Hotjar has collected from you. We use the data that we provide to Hotjar to better customize your digital advertising experience and present you with more relevant ads. Hotjar Privacy Policy
6 Sense
We use 6 Sense to deploy digital advertising on sites supported by 6 Sense. Ads are based on both 6 Sense 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 6 Sense has collected from you. We use the data that we provide to 6 Sense to better customize your digital advertising experience and present you with more relevant ads. 6 Sense Privacy Policy
Terminus
We use Terminus to deploy digital advertising on sites supported by Terminus. Ads are based on both Terminus 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 Terminus has collected from you. We use the data that we provide to Terminus to better customize your digital advertising experience and present you with more relevant ads. Terminus Privacy Policy
StackAdapt
We use StackAdapt to deploy digital advertising on sites supported by StackAdapt. Ads are based on both StackAdapt 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 StackAdapt has collected from you. We use the data that we provide to StackAdapt to better customize your digital advertising experience and present you with more relevant ads. StackAdapt Privacy Policy
The Trade Desk
We use The Trade Desk to deploy digital advertising on sites supported by The Trade Desk. Ads are based on both The Trade Desk 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 The Trade Desk has collected from you. We use the data that we provide to The Trade Desk to better customize your digital advertising experience and present you with more relevant ads. The Trade Desk Privacy Policy
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

Are you sure you want a less customized experience?

We can access your data only if you select "yes" for the categories on the previous screen. This lets us tailor our marketing so that it's more relevant for you. You can change your settings at any time by visiting our privacy statement

Your experience. Your choice.

We care about your privacy. The data we collect helps us understand how you use our products, what information you might be interested in, and what we can improve to make your engagement with Autodesk more rewarding.

May we collect and use your data to tailor your experience?

Explore the benefits of a customized experience by managing your privacy settings for this site or visit our Privacy Statement to learn more about your options.