• Industries
  • Products
  • Buy
  • Services & Support
  • Communities
  • Discussion Groups

    AutoCAD Civil 3D

    Reply
    Active Contributor jle
    Active Contributor
    Posts: 31
    Registered: ‎09-09-2009

    PointClouds Classification problem between C3D 2012 & 2013

    250 Views, 3 Replies
    05-07-2012 12:51 PM

    Hi, when I index a LIDAR *.LAS file in C3D 2012 to an Ambercore *.ISD database I get good classification and can extract all Ground Classification points. See C3D2012 attachments.

     

    Then after opening a DWG containing the PointCloud OR attaching the same *.ISD database in C3D 2013 I get NO Classification at all?? See attached C3D2013.

     

    I also checked in native Map 3D 2013 and here the problem is the same. There is classification there but it defaults to the first classification 0, never classified.

     

    Seems the new 2013 versions cannot handle LIDAR classifications?

     

    Edit> forgot to mention that INDEXING from C3D OR M3D 2013 also doesn't give Classification! 

    Please use plain text.
    Active Contributor jle
    Active Contributor
    Posts: 31
    Registered: ‎09-09-2009

    Re: PointClouds Classification problem between C3D 2012 & 2013

    06-05-2012 01:22 AM in reply to: jle

    Autodesk Support, can you confirm this issue or not?

    Please use plain text.
    *Expert Elite*
    Posts: 6,474
    Registered: ‎06-29-2007

    Re: PointClouds Classification problem between C3D 2012 & 2013

    06-05-2012 01:38 AM in reply to: jle

    Hi,

     

    seems to be quite similar to >>>this thread<<<.

     

    - alfred -

    -------------------------------------------------------------------------
    Alfred NESWADBA
    Ingenieur Studio HOLLAUS ... www.hollaus.at
    -------------------------------------------------------------------------
    Please use plain text.
    Active Contributor jle
    Active Contributor
    Posts: 31
    Registered: ‎09-09-2009

    Re: PointClouds Classification problem between C3D 2012 & 2013

    06-05-2012 01:55 AM in reply to: alfred.neswadba

    This about sums it up in that other thread:

     

    This is a known issue and the development team is investigating...

    Please use plain text.