Friday, 8 March 2013

Autodesk Sync Settings

A couple of recent projects have involved using Autodesk Cloud services - both for storage and for online services (AIM 360). One thing that cropped up was how to prevent Autodesk Sync from automatically syncing information to the cloud from certain software.

If you are logged into your Autodesk account in one piece of software and accessing cloud services you are also logged in for any other Autodesk software you have open at the same time. In other words you have one login for all software. So for example I am working in Autodesk Infrastructure Modeller (AIM) and am sharing scenarios to the cloud. At the same time I have Civil 3D open and am working away on a project. I want to stop Civil 3D syncing to the cloud but cannot log out of my Autodesk online account because I am uploading from AIM.

The solution is to prevent C3D from automatically syncing. In C3D type OP at the command line and in the options dialog box, online tab you can untick the boxes in the following screen grab. This will prevent C3D automatically uploading to the cloud.

Thursday, 7 March 2013

Infra. Design Suite Unable to find Licence

I had a tricky tech support issue recently which involved network licences of Infrastructure Design Suite (IDS). The licence file being used contained 2 seats of IDS and a number of Map 3D 2011's.

The two IDS users would rarely get a licence even though the software was only installed on their two PC's and nowhere else. When looking at the status report from the licence server it would report that two of the Map 2011 users had taken an IDS licence leaving 2 Map licences untouched. None of this seemed to make sense. These two users had also borrowed licences which meant the IDS licences were not returned at the end of each session.

According to the Autodesk knowledgbase the Map 3D should look to take a Map 3D licence first and if none are available then look to take the IDS licence but this is not what was happening:

http://usa.autodesk.com/adsk/servlet/ps/dl/item?siteID=123112&id=17150857&linkID=9240697

After a lot of back and forth with the customer and Autodesk (thanks to Inchul Lee at Autodesk tech support for his help) we found the source of the problem.

The IDS licences are on subscription which means that the customer is entitled to run the current version and up to 3 versions back. This means that the customer could run 2011 versions of the IDS software if they wanted. IDS was not available when the 2011 versions came out so to accommodate this in the licence file Autodesk have included single licence codes for the 2010 & 2011 products. See below from the licence file:
This is fine except that the single licence code added to the IDS licences for 2010 and 2011 versions are the same as the single licence codes if they were not part of the suite. This meant that when the users who had Map 3D 2011 only installed started the software on their PC it sent a request to the server for a licence with code 85557MAP_2011_OF.
The way the licence file in the image above is constructed the first two instances of this code it finds are contained in the IDS licence. There was no warning or message on the user end, they just got what they assumed was a Map 3D 2011 licence and off they went. Then when the IDS users went to start their software they would get a message stating that a valid licence could not be found.

The solution to the problem was to open up the licence file in Notepad and rearrange the licences so that the IDS ones were at the bottom and hence the last ones that were searched.
This meant that one of the 8 available Map 3D licences would be pulled down first by the Map 2011 users.  A problem could still arise if 10 users tried to run Map 3D 2011 as it would use the 2 IDS licences as the two extra Map licences required, still with no warning.

I can see why Autodesk have added in the 2010 and 2011 products to the IDS but surely there was a way to flag users who mistakenly took an IDS licence - or use a different licence code.

Tuesday, 5 March 2013

Printing Image Transparency to PDF

If you have raster images attached to a drawing and have transparency set on them this transparency does not print to PDF if you use the Autodesk DWG to PDF.pc3 print driver.



This is a known issue apparrently and is also present in the DWF print drivers. As a workaround you can use a free PDF driver such as BullZip. The transparency will now print.

http://www.bullzip.com/products/pdf/info.php


Thursday, 14 February 2013

Visualisation for Landowner Query Pt2

This post follows on from something I was working on at the end of last year and I decided to create a video showing the workflow and final results.

http://youtu.be/_Z8XygN-6xo

The first five and half minutes of the video explain a bit about what was required for the visualisation and demonstrate the workflow to get from Civil 3D to Autodesk Infrastructure Modeller (AIM). The final results from the AIM model start at 5min 40 sec for those who want to skip...

If you would like more info on how to export from C3D to AIM then read the following posts:

http://civilintentions.blogspot.ie/2013/02/civil-3d-to-aim.html

http://civilintentions.blogspot.ie/2013/02/civil-3d-to-aim-part-2-its-all-in-code.html

Monday, 11 February 2013

Civil 3D to AIM part 2 - It's all in the (Code Set) Style

In the last post we looked at taking the topo survey and areas of interest from C3D into Autodesk Infratsructure Modeller (AIM). In this post we will look at taking the proposed design (C3D corridors) out to AIM.

While you can export surfaces to LandXML from C3D and import into AIM this does not work well for corridor (proposed) surfaces. The reason is that AIM treats LandXML surfaces as Terrain and will drape your aerial imagery onto them - in effect you will end up with a surface that takes on the shape of your proposed design but has the existing aerial imagery draped onto it as below:
The most efficient method of exporting your proposed design from C3D to AIM is to use the IMX file format. As usual there is a couple of things to look out for. The main thing I have learned is that setting a render material to elements of the corridor in C3D first through the corridor code set style will make life a lot easier when you import in AIM.

First we need to identify what elements of the corridor to attach materials to. Hover over the links in your corridor (these are the corridor lines running perpendicular to the baseline) and you will see in the tooltip what the link code is:
Do this for each of the links in your corridor and note the link code being used by each. There will be a different link between each of the corridor featurelines, see below:
Next select your corridor, go to Corridor Properties on the ribbon and on the Codes tab edit the code set style being used (or create a new one).
We need to make sure that the codes set style contains all of the codes being used in the corridor. In the code set style dialog box click on Import Codes...
...navigate to your assembly in the drawing and drag a selection box around it. This will bring in all the codes used in the assembly to your code set style for editing.
Back in the code set style dialog under the links section assign a render material to each of the link codes used in your corridor. Be careful here as the top code will be used by all links so assigning a material to that will be used for all links. It is better to assign separate materials to the codes such as Daylight_Cut, Daylight_Fill, Ditch etc.
Once you have done this select the corridor in your drawing and choose object viewer on the ribbon, set the view style to Realistic. How the corridor looks in realistic view will give a good indication of how it will look in AIM. If there appears to be any part of the corridor that does not have a material assigned then check your link codes and assigned materials before exporting to AIM.
Now in C3D you are ready to export. On the Output tab of the Ribbon click Export IMX:
You can connect direct to this file in AIM. It will bring in Roads and Surface as two separate connections under data sources. As in the previous post right click on each connection separately and select configure and make sure that the coordinates are set correct. Do not drape these connections as we want to use the design level information. The corridor should now appear in AIM using the materials assigned in C3D:
Looking South from T1
 T2 and Compound with T1 in background
T8

Civil 3D to AIM

The following couple of workflows demonstrate taking your design from Civil 3D to Autodesk Infrastructure Modeller (AIM) for visualisation. Next post will cover taking proposed design (corridors) from C3D out to Autodesk Infrastructure Modeller (AIM) for visualisation.

The first thing to be aware of is what format you export your data out of Civil 3D for use in AIM.

Existing Topo:
The best way to get your existing ground surface out of Civil 3D is to export it as a LandXML file and then connect to this in AIM. You can do this a number of ways - right click on your surface in the Toolspace and select Export to LandXML or access the command from thee Output tab of the ribbon - see below:
When you connect to this in AIM it will automatically treat it as terrain. Once connected to in AIM right click on the connection and select Configure to make sure the coordinates are set or you may not see anything in your model. Any aerial imagery will automatically be draped onto this surface.

Areas of Interest:
For any areas of interest on your site that you want to highlight in the AIM model the best format to export them out of Civil 3D is the SDF format. For example in the project (Windfarm site) I am working on there is a CAD drawing which contains all of the site constraints in AutoCAD format. you can isolate CAD objects for each type of constraint and export them as separate SDF files. You can then connect to and control the display of each of these constraints separately in your AIM model. This allows you greater flexibility in controlling the display of the constraints in your AIM model rather than importing them as a CAD drawing underlay or all at once.

One of the constraints in my CAD drawing highlights areas along the proposed internal roads where there is a high risk of peat instability. I want to be able to highlight these in my visualisation.

These are represented by closed polylines in the drawing. In Civil 3D select one of closed polylines, right click and select similar then right click again and Isolate Objects. Once isolated type MAPEXPORT, choose SDF as files of type and give the file a name. In the dialog box that appears choose 'Select Manually' and select the isolated objects from the drawing.
In AIM connect to this file as below:
After connecting to the file, right click on the connection in AIM and select configure. On the Common tab set the 'Type' as Coverage Areas, Set the style.
On the Geo Location tab set the coordinate zone. On the Source tab set the draping options to Drape (since they were just 2D polylines originally they have no level information) tick the box to convert to closed polygons also. Click close and refresh and you should see your areas draped on the 3D model as below:
In my model the red highlights areas along proposed routes where there is high risk of peat instability, blue represents areas of peat greater than 3m in depth and magenta are areas of blanket bog.

Wednesday, 30 January 2013

Sight Distance Check Results

This issue came up back in December but I have had an unusually busy January so haven't had time to post about it. All credit to James Curran at Donegal County Council for identifying the solution to the problem...

The sight distance check in Civil 3D allows you to check the sight distance at intervals along a corridor. You can specify the eye height, target height, minimum sight distance required and also the interval at which to check. The results can be output to report format and will give you the following information at each chainage interval:

  • the actual sight distance achieved
  • the minimum sight distance required
  • whether the minimum sight distance was violated
  • the location of the obstruction point
Below are the the reports from three checks using the same settings along a corridor but checking for different minimum sight distance. The first check was for 60m and it passes, reporting back that there is no violation and we get 60m sight lines at all locations.

Next we checked for 120m. This time we get a violation at a number of chainages. Looking at chainage 1440m we see that the actual sight distance is reported as 49.268m. This doesn't seem to be correct given the previous results.
Next we checked for 160m and got a different actual sight distance (89.956m) value for the same chainage.Again this doesn't seem to make sense given the other results.
So what is happening here? The issue appears to be what the software calculates as the actual sight distance. Taking a not to scale AutoCAD drawing provides an explanation of the results. First the 60m check.
We can see there is no violation - everything ok here.

Next the 120m check.
Here we can see the sight line in red. The actual sight distance as measured by Civil 3D is from the target point to the intersection of the sight line and the ground profile. However the actual sight distance  would be tangential to the ground profile as below in blue and would give a longer actual sight distance value.
Technically the software is correct in how it is calculating but I think calling it 'actual sight distance' is misleading or at the least there should be a better explanation within the command of how and what it is calculating. Maybe it should also give distance at tangent and call it available sight distance.

With what it is calculating at present for the actual sight distance you would need to run the command for increasing or decreasing increments of minimum sight distance and check the report each time to see when you get a violation to properly identify your actual sight distance.