Wednesday, 14 June 2017

LandXML & Civil 3D tips, clarifications and important matters to remind me while programming

LandXML angular direction :
Unit is always Decimal Degrees
Positive values only, counter clockwise, zero to East

LandXML horizontal alignment elements :
Are set in CoordGeom
Common to Civil 3D are Line, Curve and Spiral (others are Irregular line and Feature ?)

LandXML horizontal alignment element Spiral :
Civil 3D supports only Spiral.SPItype=Clothoid

LandXML horizontal alignment element Curve (Civil 3D Arc) :
Civil 3D supports only crvType=arc

Civil 3D api can be viewed only using Chrome. IE does not show side window elements !?
http://docs.autodesk.com/CIV3D/2018/ENU/API_Reference_Guide/

Civil 3D alignment simple type entities are subentities of more complex ones like SCCS etc.

LandXML theta angle :
is Pi-SpiralIncludedAngle in degrees and is always positive and less than Pi.
Spiral Included Angle is the angle between Short and Long tangents and is always positive and less than Pi.

Friday, 2 June 2017

Leica Infrastructure Link - Civil 3D corridor export : failure - Autocad JIT error message "Enumeration has either not started or has already finished"

Searching for a workaround for the previous post i tried exporting the corridor with all baselines checked.
And i got the following message.


More serious bug reports to come...

Leica Infrastructure Link - Civil 3D corridor export : bug - Layer centerline set to wrong baseline alignment

I had a corridor with multiple baselines attached to multiple alignments.
I unchecked all of them except one of them which it was the only one i wanted to export.
I used Leica Infrastructure Link to export it.
Finally i used the MS XML editor to view the exported HeXML file.

The alignment of the checked baseline was not exported.
Instead of it, the alignment of the first (and unchecked) baseline was exported !
The correct feature lines were exported.
Finally the wrong exported alignment was attached to the layer as a centerline.



 

TPS1200 RoadRunner cannot be used for checking tunnel sections

I had a Civil 3D corridor with a tunnel.
I exported it as LandXML file.
I used the Layer check option of RoadRunner.
Unfortunately it only references the cross section vertically. Not perpendicular to it.
It gets the plumb point to the cross section and the ref lines among it are used for further calculations.
I could not find a perpendicular option for the layer check.
I guess this is, among others, a major difference between RoadRunner Road and Tunnel modules.

 
 
 
 

Leica Infrastructure Link - Civil 3D export corridor : failure - Autocad JIT error message "This operation on featureline-based baseline is invalid"

One of the top rated in the wish list about Civil 3D was the option to create a corridor using feature line baseline type. Civil 3D 2017 was the first version to support it.

Leica X-Change no longer exists since this C3D version.
Its successor Leica Infrastructure Link freeware must be used instead.

Running this addon pressing the "Read Civil Objects" button user sees the following message.
The program stucks at this point.



OR

After reading civil objects when trying to save "Export HeXML" user sees the following message

Well at least it is multithreaded. So in either cases user can press Continue and then the OK button and end this addon. But no export takes place.
Same thing happens even if baselines feature line based are unchecked when rebuilding the corridor.
Only solution is to revert to the previous baseline type method of alignment/profile.


Well. It is obvious that Leica developers did not examine the changes between v2016 and v2107.
In v2017 baselines types can differ. Developer should examine if it is "IsFeaturelineBased" or else the above exception is thrown. At least there should exist a user notification.

Leica developers should have seen this link
https://knowledge.autodesk.com/support/autocad-civil-3d/learn-explore/caas/CloudHelp/cloudhelp/2017/ENU/Civil3D-DevGuide/files/GUID-6D41D043-4958-40B7-9C7E-45A6D780955B-htm.html

Thursday, 27 April 2017

Civil 3D 2017 : corridor endless out of date status finally missing after saving drawing

https://forums.autodesk.com/t5/autocad-civil-3d-forum/corridor-out-of-date/td-p/2923316

"

My problem was even worse not just Rebuild status always on.
 
Immediatelly after saving dwg...
 
...an alignment, some feature lines and the corridor that is built on them were lost. Just not existing anymore in prospector and screen !
Undoing resurrected them !
 
OR
...the above mentioned alignment was visible but not existing in the prospector ! I could right click on it and handle it although it was a...ghost ! Corridor reported it as its baseline !
If my next action was...
...moving it siteless the object became visible to prospector and everything became normal !
...saving dwg again, alignment became invisible and corridor reported that had no baselines ! Totally lost. Single undo does nothing. Second undo ressurects corridor object and the graph but not the alignment object to the prospector.
 
Had to find a solution since saving and loosing them was not an option and ofcourse keeping it open until a solution was found in the future is impossimble (on the way to madness and what could i say to my supervisors expecting from me to finish just a simple job)
 
I was lucky enough to find out that setting the alignment to whatever site, new or existing with whatever name is the caution to loose it and the corridor that is attached to it and also the feature lines.
 
Moving to site none (siteless) , rebuilt status clears after rebuilding and saving works fine !
 
I attach the dwg. First import in an empty dwg the also zipped subassemblies and then open the dwg.
The objects i mentioned above are...
alignment named...EDL002B240_TKV
corridor named...EDL002B240_TKV
feature lines...both siteless
Try move them to existing site or a new one and then rebuild. Rebuild status remains on whatever i do.
Finally try saving dwg twice.

"

Monday, 3 April 2017

Visual studio 2017, autoCAD 2017, edit & continue

I am so happy !
Just realised that installing Service Pack 1 to autoCAD or Civil 3D 2017, it is possible to use full Edit & Continue with MS Visual studio 2017 community edition !!!

FULL Edit & Continue !!! By its exact meaning !!!
No workarounds, no Visual Studio extra settings.
Not just view variables.
Allowed to hit new breakpoints while running.
Allowed to change code.
Autocad loading and running absolutely fine.
Must be dreaming !!!

https://forums.autodesk.com/t5/net/edit-and-continue/td-p/6910483

http://adndevblog.typepad.com/autocad/2016/07/autocad-2017-sp1-and-net-debugging.html