Trimble Business Center

Hello,

I am trying to find out what would be the best way to manage large data sets (few years of data collecting, 100's of thousand of points) using Trimble Business Centre.

I would like to be able to maintain all Features Attributes as collected in the field.

I am not so fussy about observations (terrestrial or vectors), regular Easting, Northing and Elevations are good enough for me.

Surely over time we will go thru few different FXL files, as new features will be added.

We will have a team of 6 ppl full time in the field, collecting data, doing set outs etc.

Each and everyone of them will process their data at the end of the day. Import JXL from Access to TBC, Process Feature Codes, draft missing Line Strings, remove unnecessary points and so on and so on.

I'd like data like that to be exported to VCL file and then imported to MASTER PROJECT where all the data will be kept.

That's where my problem starts, as data in VCL is a dependable data. If a point was measured using RTK, VCL will not include RTK Vector, therefore as soon as I will recalculate MASTER PROJECT (F4) I will loose all points that were captured using RTK.

Once Features are processed, I'd like to have all the Points/Lines/Polygons and all their Features Attributes together with their linestyles / colours / weights / blocks / labels "set in stone", permanently fixed.

What is the best way to break all dependencies? To stop new FXL's from reprocessing all the data? But to maintain all "Feature Attributes" collected in the field?

Any help will be much appreciated.

Regards,

Marian

@Ross McAtamney

Hi Marian,

You may want to try the command of Merge Survey Projects. You could find it from the Survey tab. There are some limitations of objects to be merged, and some adjusted data may need to be re-adjusted as well. Should you have any questions, you could hit F1 and refer to the topic Merge Survey Projects for details.

Rui

From 'Project Setting>Feature Code Processing', uncheck the box 'Allow editing of processed feature codes and reprocess feature codes during Compute Project' (note compute project auto occurs on export and save). This will stop edited data reprocessing/reverting.

Save this to your template to make permanent, and don't forget to reset if creating a new template (eg. possibly after a version upgrade).

I believe the theory is that the survey points should be correct, and if not, the correction is made to the survey points, not the processed data.

Regardless, always check deliverables, as we still have issues with data apparently reprocessing for some unknown reason.

Rob