WorksOS

 View Only

WorksOS Point Data 

12-15-2022 16:39

Not sure if this is the right place to post..

When exporting data from WorksOS, can I get some clarification on the point data I am seeing.
Are the points we extract for say (lowest pass) the centre of the bucket, the left / right side / both positions?


(If I look at the attached screen grab) there are a number of points from the excavators lowest pass. 
The bucket on the excavator has a width to it, but we don't get a dual point location output. Therefore I assume we get a cleaned output based on the filter, and a background coded clearout of extraneous data?

i.e. in some trenching operations, I have seen a single point lowest pass location. (This effectively gives me a width of zero. I know that the bucket was 600mm wide, 900mm wide, etc, so any outputs from that single point aren't a true reflection on the bucket width) and hence overall volume would be reduced.

If anyone can shed some light on this it would be appreciated.

Kind Regards,
Julius

Foundation solution and overdig via WorksOS output records (view from underneath carpark).

Statistics
0 Favorited
43 Views
1 Files
0 Shares
6 Downloads
Attachment(s)
jpeg file
Screenshot 2022-12-16 103340.jpg   914 KB   1 version
Uploaded - 12-15-2022

Comments

12-19-2022 17:28

Whenever you export the data either from a .ttm surface or from something like machine passes or a grid report there is similar logic working based on how the data is stored. 

In WorksOS what you are seeing in all of these cases is the impact of the grid model. The data is placed within an artificial grid that is 34cm x 34cm and oriented North and South. 

The resolution of the data and the edges of something like an excavator bucket are indeed lost in the precision of the specific left and right edges as the data is only recorded when the bucket intersects with the center of a grid. 

12-19-2022 01:33

Answered as per below.

Dan / Trimble mentioned (and it's logical), that this will be related to what the bucket position is at the time of recording.

So, when processing, (and depending on the size of work / project, it's critical to know what you are outputting as the asbuilt (and associated notes / volumes / positions) need to reflect what you are actually showing in your data.

Thanks,
Julius

Related Entries and Links

No Related Resource entered.