Trimble Business Center

Hello,

The flags pane is really appreciated and important.  It would be really helpful if the user of TBC could assign different categories or quality types to the flags.  TBC could come with some stock groupings, or it could leave it up to the end user.  There would be groups that flags could be assigned and added to, like, Reviewed and Acceptable, To be Reviewed, Unresolvable, or what have you.  TBC would then allow the user though a toggle like that is available for layers, to either show or hide various groupings.

Our TBC projects for some projects will span a decade and that is a lot of flags, and to me and my memory 10 or more flags is more than too many.

We end up revising the project settings, back and forth, to make flags disappear or come back.  A good example of this is the Horizontal Tolerance for mean angles.  We normally will double and mean angles using measurements to a target mounted on legs and tribrach.  These measurements have very low residuals, we also do the same at a close distance to a target on a rod.  We end up with MTA H residuals that are all over the board and need to be reviewed sometimes on a case by case basis.  Once the reviewer has determined that the residual is due to real world conditions, and not crew member error or blunder, it would be nice to be able to remove that flag from the overall set of flags.  There is no way to do this.

Having the ability to add quality groups to flags would give the user this ability.

It seems pretty simple to me.  I have seen this asked for before and I have asked before.  I have sent both of my vendors requests and input, way back about 10 years ago and several times in between.  

As I understand it, Trimble works on the stuff that get the most attention (sometimes this is very influential in prioritizing improvements, maybe not always, sure).  So if you are like me and would like to see this added as an improvement, email the idea to your vendor, post here, like subscribe and comment to this post. etc.

Another example is the tilt distance, sometimes there is a really good reason for a tilt that exceeds what would normally be expected.  I want to get rid of that flag so I can focus on the next one that is important.

Or an as staked value of a point.  We end up getting rid of all of our as staked points, because they throw too many flags and there is no way to make a flag go away, even when it isn't a flag any more.

The project setting is great, but it is to global of an approach.  You can't treat real world flags that way.  There are just too many variables to say that end residuals are caused by the same field conditions or techniques.  A human needs to review and determine whether a flag is material or not and once that determination is made the program needs a way to allow for some user input to document that and that doesn't exist.

Thank you for your time.

Clayton.

------------------------------
Clayton Bradshaw
------------------------------

Hello,

The flags pane is really appreciated and important.  It would be really helpful if the user of TBC could assign different categories or quality types to the flags.  TBC could come with some stock groupings, or it could leave it up to the end user.  There would be groups that flags could be assigned and added to, like, Reviewed and Acceptable, To be Reviewed, Unresolvable, or what have you.  TBC would then allow the user though a toggle like that is available for layers, to either show or hide various groupings.

Our TBC projects for some projects will span a decade and that is a lot of flags, and to me and my memory 10 or more flags is more than too many.

We end up revising the project settings, back and forth, to make flags disappear or come back.  A good example of this is the Horizontal Tolerance for mean angles.  We normally will double and mean angles using measurements to a target mounted on legs and tribrach.  These measurements have very low residuals, we also do the same at a close distance to a target on a rod.  We end up with MTA H residuals that are all over the board and need to be reviewed sometimes on a case by case basis.  Once the reviewer has determined that the residual is due to real world conditions, and not crew member error or blunder, it would be nice to be able to remove that flag from the overall set of flags.  There is no way to do this.

Having the ability to add quality groups to flags would give the user this ability.

It seems pretty simple to me.  I have seen this asked for before and I have asked before.  I have sent both of my vendors requests and input, way back about 10 years ago and several times in between.  

As I understand it, Trimble works on the stuff that get the most attention (sometimes this is very influential in prioritizing improvements, maybe not always, sure).  So if you are like me and would like to see this added as an improvement, email the idea to your vendor, post here, like subscribe and comment to this post. etc.

Another example is the tilt distance, sometimes there is a really good reason for a tilt that exceeds what would normally be expected.  I want to get rid of that flag so I can focus on the next one that is important.

Or an as staked value of a point.  We end up getting rid of all of our as staked points, because they throw too many flags and there is no way to make a flag go away, even when it isn't a flag any more.

The project setting is great, but it is to global of an approach.  You can't treat real world flags that way.  There are just too many variables to say that end residuals are caused by the same field conditions or techniques.  A human needs to review and determine whether a flag is material or not and once that determination is made the program needs a way to allow for some user input to document that and that doesn't exist.

Thank you for your time.

Clayton.

------------------------------
Clayton Bradshaw
------------------------------

Totally agree. MTA flags on short shots very often are just a few thousandths and mean nothing. It would be really nice to have a reviewed or acceptable function that lets you switch them off after you determine there is no issue. Agree on the tilt error as well. Most of the time it's fence shots where the tilt is on purpose.

------------------------------
Mark Macfarlane

Original Message:
Sent: 01-08-2025 11:00
From: Clayton Bradshaw
Subject: Wish List - Flags Pane

Hello,

The flags pane is really appreciated and important.  It would be really helpful if the user of TBC could assign different categories or quality types to the flags.  TBC could come with some stock groupings, or it could leave it up to the end user.  There would be groups that flags could be assigned and added to, like, Reviewed and Acceptable, To be Reviewed, Unresolvable, or what have you.  TBC would then allow the user though a toggle like that is available for layers, to either show or hide various groupings.

Our TBC projects for some projects will span a decade and that is a lot of flags, and to me and my memory 10 or more flags is more than too many.

We end up revising the project settings, back and forth, to make flags disappear or come back.  A good example of this is the Horizontal Tolerance for mean angles.  We normally will double and mean angles using measurements to a target mounted on legs and tribrach.  These measurements have very low residuals, we also do the same at a close distance to a target on a rod.  We end up with MTA H residuals that are all over the board and need to be reviewed sometimes on a case by case basis.  Once the reviewer has determined that the residual is due to real world conditions, and not crew member error or blunder, it would be nice to be able to remove that flag from the overall set of flags.  There is no way to do this.

Having the ability to add quality groups to flags would give the user this ability.

It seems pretty simple to me.  I have seen this asked for before and I have asked before.  I have sent both of my vendors requests and input, way back about 10 years ago and several times in between.  

As I understand it, Trimble works on the stuff that get the most attention (sometimes this is very influential in prioritizing improvements, maybe not always, sure).  So if you are like me and would like to see this added as an improvement, email the idea to your vendor, post here, like subscribe and comment to this post. etc.

Another example is the tilt distance, sometimes there is a really good reason for a tilt that exceeds what would normally be expected.  I want to get rid of that flag so I can focus on the next one that is important.

Or an as staked value of a point.  We end up getting rid of all of our as staked points, because they throw too many flags and there is no way to make a flag go away, even when it isn't a flag any more.

The project setting is great, but it is to global of an approach.  You can't treat real world flags that way.  There are just too many variables to say that end residuals are caused by the same field conditions or techniques.  A human needs to review and determine whether a flag is material or not and once that determination is made the program needs a way to allow for some user input to document that and that doesn't exist.

Thank you for your time.

Clayton.

------------------------------
Clayton Bradshaw
------------------------------

Hello,

The flags pane is really appreciated and important.  It would be really helpful if the user of TBC could assign different categories or quality types to the flags.  TBC could come with some stock groupings, or it could leave it up to the end user.  There would be groups that flags could be assigned and added to, like, Reviewed and Acceptable, To be Reviewed, Unresolvable, or what have you.  TBC would then allow the user though a toggle like that is available for layers, to either show or hide various groupings.

Our TBC projects for some projects will span a decade and that is a lot of flags, and to me and my memory 10 or more flags is more than too many.

We end up revising the project settings, back and forth, to make flags disappear or come back.  A good example of this is the Horizontal Tolerance for mean angles.  We normally will double and mean angles using measurements to a target mounted on legs and tribrach.  These measurements have very low residuals, we also do the same at a close distance to a target on a rod.  We end up with MTA H residuals that are all over the board and need to be reviewed sometimes on a case by case basis.  Once the reviewer has determined that the residual is due to real world conditions, and not crew member error or blunder, it would be nice to be able to remove that flag from the overall set of flags.  There is no way to do this.

Having the ability to add quality groups to flags would give the user this ability.

It seems pretty simple to me.  I have seen this asked for before and I have asked before.  I have sent both of my vendors requests and input, way back about 10 years ago and several times in between.  

As I understand it, Trimble works on the stuff that get the most attention (sometimes this is very influential in prioritizing improvements, maybe not always, sure).  So if you are like me and would like to see this added as an improvement, email the idea to your vendor, post here, like subscribe and comment to this post. etc.

Another example is the tilt distance, sometimes there is a really good reason for a tilt that exceeds what would normally be expected.  I want to get rid of that flag so I can focus on the next one that is important.

Or an as staked value of a point.  We end up getting rid of all of our as staked points, because they throw too many flags and there is no way to make a flag go away, even when it isn't a flag any more.

The project setting is great, but it is to global of an approach.  You can't treat real world flags that way.  There are just too many variables to say that end residuals are caused by the same field conditions or techniques.  A human needs to review and determine whether a flag is material or not and once that determination is made the program needs a way to allow for some user input to document that and that doesn't exist.

Thank you for your time.

Clayton.

100% in support of all this. I found the post when I was searching for a resolution to a couple 100 tilt warnings. Definitely some operator error and a training opportunity on this one, but the points are in a farmers field. They are still useful, and I don't want to set the tilt tolerance to 0.1m just to make the flags go away.

Hello,

The flags pane is really appreciated and important.  It would be really helpful if the user of TBC could assign different categories or quality types to the flags.  TBC could come with some stock groupings, or it could leave it up to the end user.  There would be groups that flags could be assigned and added to, like, Reviewed and Acceptable, To be Reviewed, Unresolvable, or what have you.  TBC would then allow the user though a toggle like that is available for layers, to either show or hide various groupings.

Our TBC projects for some projects will span a decade and that is a lot of flags, and to me and my memory 10 or more flags is more than too many.

We end up revising the project settings, back and forth, to make flags disappear or come back.  A good example of this is the Horizontal Tolerance for mean angles.  We normally will double and mean angles using measurements to a target mounted on legs and tribrach.  These measurements have very low residuals, we also do the same at a close distance to a target on a rod.  We end up with MTA H residuals that are all over the board and need to be reviewed sometimes on a case by case basis.  Once the reviewer has determined that the residual is due to real world conditions, and not crew member error or blunder, it would be nice to be able to remove that flag from the overall set of flags.  There is no way to do this.

Having the ability to add quality groups to flags would give the user this ability.

It seems pretty simple to me.  I have seen this asked for before and I have asked before.  I have sent both of my vendors requests and input, way back about 10 years ago and several times in between.  

As I understand it, Trimble works on the stuff that get the most attention (sometimes this is very influential in prioritizing improvements, maybe not always, sure).  So if you are like me and would like to see this added as an improvement, email the idea to your vendor, post here, like subscribe and comment to this post. etc.

Another example is the tilt distance, sometimes there is a really good reason for a tilt that exceeds what would normally be expected.  I want to get rid of that flag so I can focus on the next one that is important.

Or an as staked value of a point.  We end up getting rid of all of our as staked points, because they throw too many flags and there is no way to make a flag go away, even when it isn't a flag any more.

The project setting is great, but it is to global of an approach.  You can't treat real world flags that way.  There are just too many variables to say that end residuals are caused by the same field conditions or techniques.  A human needs to review and determine whether a flag is material or not and once that determination is made the program needs a way to allow for some user input to document that and that doesn't exist.

Thank you for your time.

Clayton.