the only issue is that it is just a data exchange. it does nothing for
making the information look right.
Things that work really well both directions:
1) Points
2) Surfaces
3) Alignments- just note all curves come in contrained, not free.
Things that do not work well when brought into C3D thru LandXML:
1) Parcels- LandXMLed in parcels in C3D have horrible topology and have
destroyed my site geometry more than once. Don't do it.
2) Profiles- they come in as the profile data, not view. Which is OK, but I
find that people aren't really good about defining FG centerlines in LDT,
and it is a little un-user friendly to get this information in my c3d dwg.
3)Pipes- Pipes come in as RUNS not NETWORKS which drives me insane. They
don't reference a surface, they are static as heck, and I'd just rather
redraw. It takes less time to redraw then to wrestle
I tell folks the following:
1) Do a C3D project from scratch before you try migrating once you get the
hang of what works and what doesnt a migration is a snap. I did 4 this
weekend and another two tonight. But it takes some understanding of what
data comes through well and its limitations.
2) Go one direction- once. Bring from LDT to C3D and finish the project in
C3D. Or, do some design in C3D (like your lotting, or a corridor) and
explode/xml back to Land Desktop. But DO NOT go back forth back forth, NOR
have 1/2 the team in C3D and half in LDT.
--
Dana Breig Probert
http://civil3drocks.blogspot.com/
CADapult Ltd
Empowering Design With Innovative Solutions
www.cadapult.net
----------------------------------------------
Thanks.