Showing posts with label Limitations. Show all posts
Showing posts with label Limitations. Show all posts

Friday, 7 July 2017

Leica Infrastructure Link multiple baseline corridor export

In case a Corridor consists of more than one Baselines based on different Alignments then all Feature Lines checked in whatever Baseline are exported but only the first Baseline Alignment is exported ! All other are ignored ! Finally only one Layer is created for the entire Corridor.
So it is not possible to set the appropriate Centerline when in RoadRunner.

X-Change was capable of producing multiple Layers.

So it is crucial to work only with X-Change and up to Civil 3D 2016
or
create mutiple Corridors, one for each Baseline
or
do multiple HeXML exports having checked only one Baseline per session but it does not work
follow this link https://infrastructuresurveyor.blogspot.gr/2017/06/i-had-corridor-with-multiple-baselines.html

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

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.

 
 
 
 

Monday, 15 February 2016

Civil 3D alignment with profiles export to a Leica or Trimble sensor

When in Civil 3D there might be a case an alignment with a profile (no cross sections) must be exported.



Trimble
There are two ways to export it.

Civil 3D LandXML
This is the quickest way to export. Select the desired profile and export it as LandXML. Not native format as RXL but it works fine.
Multiple alignments can be exported within a single LandXML file but when running Roads on controller user will be prompted to select the desired alignment. I have not tested it for alignment with multiple profiles.

update 2022.04.01
Trimble Access 2017+ does not support staking out directly through a LandXML file. You have to use Trimble Access Define/LandXML to create an RXL file so to use this for the stake out.
The LandXML file can have multiple alignments with multiple profiles and also multiple sets of cross sections  eg asfalt, earth works etc. You can create a single RXL for each set of cross sections.
BUT...if a profile is not created from a layout then this profile is ignored and if it is the only one then also the sections are ignored!
LandXML profile has to be of type <ProfAlign> not <ProfSurf>.
To transform a profile based on surface or file to a layout type follow the links at the end of this post.

Trimble Link
There is no way to directly export an alignment with its profile.
Alignment Export, exports only 2D, not profile.
The only way to export it is through Road Export. BUT, at least a dummy corridor with an assembly with just a MarkPoint must be created.
While exporting a message that no surface exists is shown but the alignment and its profile are exported.
The format of the exported file is the Trimble's native RXL. So only one alignment per file with only one profile, the one that creates the dummy corridor can be exported.
The great (and only one) advantage of Trimble Link (compared to Leica whatever method) is that the supported profile types include profiles made of file, by layout and surface. I have not tested for superimposed or other types.

Update 2016.10.07 : Trimble Link for C3D 2017 supports alignment and profile export.


Leica

Leica X-Change
Multiple alignments with their multiple profiles can be exported in a single Job as multiple layers!!!
But the only supported profile type is Layout!!!
In case there is not a Layout profile no warning message takes place.
In case no profile exists for an alignment then no plus signed button exists by the alignment name.
In case at least one profile exists then this button exists. BUT if the profile is not a Layout type then although the plus signed button exists there are no profiles available for checking!!! This might mislead you that your profile is checked!
Leica X-Change Layer naming
Each alignment is named with a prefix ALx where x=1.... follwed by a space character
If the alignment has no profile then the alignment name itself is used for the rest of the layer's name.
If the alignment is exported with a profile then the rest of the name is the profile's name so beware of Civil 3D profile naming!!!
Also if alignment is exported with multiple profiles each profile is set on a seperate layer with its prefix followed by the profile name.

Leica LandXML import to alignment
Suppose a single file Civil 3D LandXML export with lots of alignments and their profiles.
Simply the worse way to do it.
Only one layer is created.
All alignments are considered as Lines of this layer!
To work with a Line (alignment) user must enter the Road Job, Data, Edit and change the center line to the desired Line.
Multiple profiles are ignored. Only the first Layout type (LandXML ProfAlign type) is imported.
Lines are named by the Alignment names and only.
Things are even worse when an alignment has Sample Line Groups. When importing then all alignments are ignored except from the first alignment that has SLG. The prompt is for the sections this alignment owns. But finally no cross sections are imported. Alignments are exported as a single layer's lines.

Tip
When working with Leicas beware of the Alignment and Profile naming if multiple ones exist. Or else user will not be able to select the desired Layer or Line.
Since Trimble native RXL files include only one Alignment and Profile, naming is not crucial. Just be careful of the file name.
But if a LandXML file is used with Trimble then naming is also crucial.


Turning profile type to Layout
Below is a post mentioning the workaround for turning profiles to Layout type...

https://forums.autodesk.com/t5/autocad-civil-3d-general/any-way-to-change-profile-type/td-p/4330341

https://forums.autodesk.com/t5/autocad-civil-3d-general/create-proposed-profile-from-surface-profile/m-p/2957152#M148418

Thursday, 27 August 2015

SAC : New limitation found. Points entered in Decision branches.

I entered a Decision.
False produced a new Point. True also produced a new point.
None of them was available when i tried to use them in a link at a following flowchart although they were both preview visible for their case to take place.

So Points entered by decision are not available for Links. And i guess that their properties (.x,.y,.offset,.elevation,.isValid) are also not available.