Trimble Business Center

We are currently using TBC 5.90.  I can't say for sure that this behavior didn't exist in TBC 5.81, but I don't recall having this as an issue.

We export a .csv file for each day of work that is associated with an imported Access .job file.  If it matters, this is happening with Access 23.00.  For example, after a day of field work, party chief takes .job from data collector and imports this file into TBC.  The only data in that .job day file is the measurements from that day.  All other prior existing data is linked into the empty .job day file at the start of the day.  Once that day .job file is imported into TBC and QAQC is performed, as staked points are converted, then we use the Export command to generate a Point, Northing, Easting, Elevation, Description comma delimited .csv file.  To capture the points associated with the .job day file we select the .job day file and use the select members options.  We then export to the .csv.

We have been operating this way for years and haven't had this problem until recently.  When we do this routine now, we get all the points as expected, but we also are getting some number of .csv rows that are missing their Point Numbers and Descriptions but are also duplicates of points already in the .csv list.  The coordinate values are identical.  I can't say I know why this would be happening.  I have included a .csv file showing the issue and a screen grab showing the same as an illustrative graphic. 

Please let me know if anyone has experienced this behavior before and what the cause and solution are.

Thank you,

Clayton Bradshaw.

i m curious if it has to do with how some points from linked files get copied to the job when occupied or used in other ways in access. are they control points? is there anything funny associated with the points in tbc, or blank points in tbc?

we don t follow the exact routines you do. but i know we sometimes get oddball points in a csv export. sounds different than you because ours will be a duplicate point number with wrong coordinates!!!!! usually with a blank code. they almost seem like ghost coordinate from previous exports. but i can t be certain. i catch them when importing to cad and i get a duplicate point number warning. does not happen all the time and might also have to do with overriding a previous csv export. 

We are currently using TBC 5.90.  I can't say for sure that this behavior didn't exist in TBC 5.81, but I don't recall having this as an issue.

We export a .csv file for each day of work that is associated with an imported Access .job file.  If it matters, this is happening with Access 23.00.  For example, after a day of field work, party chief takes .job from data collector and imports this file into TBC.  The only data in that .job day file is the measurements from that day.  All other prior existing data is linked into the empty .job day file at the start of the day.  Once that day .job file is imported into TBC and QAQC is performed, as staked points are converted, then we use the Export command to generate a Point, Northing, Easting, Elevation, Description comma delimited .csv file.  To capture the points associated with the .job day file we select the .job day file and use the select members options.  We then export to the .csv.

We have been operating this way for years and haven't had this problem until recently.  When we do this routine now, we get all the points as expected, but we also are getting some number of .csv rows that are missing their Point Numbers and Descriptions but are also duplicates of points already in the .csv list.  The coordinate values are identical.  I can't say I know why this would be happening.  I have included a .csv file showing the issue and a screen grab showing the same as an illustrative graphic. 

Please let me know if anyone has experienced this behavior before and what the cause and solution are.

Thank you,

Clayton Bradshaw.

Hey Ian and group, 

It is definitely related to something in our feature line codes processing instructions.  We haven't been able to figure out what, and we aren't sure this happened before 5.90.  We continue to test and look for the reason.

We also examined what you suggested.  And trust me, we have struggled with the same issues you are noting but have some pretty sound policies now to remove.  If you are ever interested, we could Teams and I could show you how we isolate those coordinate definitions that come in from our day files.

i m curious if it has to do with how some points from linked files get copied to the job when occupied or used in other ways in access. are they control points? is there anything funny associated with the points in tbc, or blank points in tbc?

we don t follow the exact routines you do. but i know we sometimes get oddball points in a csv export. sounds different than you because ours will be a duplicate point number with wrong coordinates!!!!! usually with a blank code. they almost seem like ghost coordinate from previous exports. but i can t be certain. i catch them when importing to cad and i get a duplicate point number warning. does not happen all the time and might also have to do with overriding a previous csv export. 

We are currently using TBC 5.90.  I can't say for sure that this behavior didn't exist in TBC 5.81, but I don't recall having this as an issue.

We export a .csv file for each day of work that is associated with an imported Access .job file.  If it matters, this is happening with Access 23.00.  For example, after a day of field work, party chief takes .job from data collector and imports this file into TBC.  The only data in that .job day file is the measurements from that day.  All other prior existing data is linked into the empty .job day file at the start of the day.  Once that day .job file is imported into TBC and QAQC is performed, as staked points are converted, then we use the Export command to generate a Point, Northing, Easting, Elevation, Description comma delimited .csv file.  To capture the points associated with the .job day file we select the .job day file and use the select members options.  We then export to the .csv.

We have been operating this way for years and haven't had this problem until recently.  When we do this routine now, we get all the points as expected, but we also are getting some number of .csv rows that are missing their Point Numbers and Descriptions but are also duplicates of points already in the .csv list.  The coordinate values are identical.  I can't say I know why this would be happening.  I have included a .csv file showing the issue and a screen grab showing the same as an illustrative graphic. 

Please let me know if anyone has experienced this behavior before and what the cause and solution are.

Thank you,

Clayton Bradshaw.