Trimble Business Center

 View Only
Expand all | Collapse all

Why does feature linework not draw in point number order?

  • 1.  Why does feature linework not draw in point number order?

    Posted 03-26-2019 10:27

    When we combine multiple jobs files and send out a single job file with all the points the linework jumps.

    Example:

    point 31101 (edge of asphalt)

    1549 ea      Inverse between 31101 & 1549 = 3629ft

    1550 ea      

    1551 ea      Inverse between 1551 & 1550 = 17ft

    31107 ea     Inverse between 1151 & 31107 = 3589ft --- 31101 & 31107 = 61ft

    1552 ea       Inverse between 31107 & 1552 = 3601ft --- 1551 & 1552 = 12ft

     

    This makes no sense. These codes should link up due to point order or distance. My only thoughts is it wants to process it like it is a text file due to the order it was created, but why would TBC order the points that way? If you expand the job in the Project Explorer tree under imports you can see that when TBC exported these points it placed them in this order so the linework is processed in the random order also.

     

    Why on earth would the export do this, and that the feature processing isn't done in point number order?



  • 2.  Re: Why does feature linework not draw in point number order?

    Posted 07-18-2019 05:26

    Can you give more information? In which format are you exporting out of TBC? Which program are you using the exported file in?



  • 3.  Re: Why does feature linework not draw in point number order?

    Posted 07-18-2019 11:32

    This isn't exported out of TBC this is in TBC, so an export format is irrelevant. 



  • 4.  Re: Why does feature linework not draw in point number order?

    Posted 07-19-2019 05:06

    You did state export, which is why I asked. In which format are you bringing in data into TBC?  Importing the JOB file or a point file?



  • 5.  Re: Why does feature linework not draw in point number order?

    Posted 08-06-2019 16:40

    Hi James, 

    I've seen this before and still don't know why. Underneath the point ID, there are some point serial numbers to control the behavior. But the workaround here is to add line control codes so TBC knows they should be two lines instead of one. Add Start to P31101 and P1549, and add End to P31107 and P1552, the line will break into two.

    Another workaround is to use EA1 for all P311xx and EA2 for all P15xx, no line control codes.

     

    Hope this helps. Thank you.

    Rui