Trimble Business Center

 View Only

 Rename As Staked Point Duplicates Doesn't Stick

Clayton Bradshaw's profile image
Clayton Bradshaw posted 07-03-2025 11:10

Hi Everyone,

I had noticed this before, and think I have seen others comment on it.  

Yesterday we had a field crew that went out and using the stake out functions stored several points with point numbers that already existed in the overall project TBC database and job file.  So on import the as staked points come in as -1's.  In the as staked portion of the project explorer it is very easy to catch these and then rename (renumber them), but when you convert them from as staked points to points the all revert back to the original duplicate point number (without the -1).  So it is very difficult to find them, fix them and move on.  You don't get the merge points warning on import of .job file like you do for normal point duplicate step ons.

Anyone have a novel way to clean this up?  

Trimble maybe consider fixing this?  We should have to correct the point name issue in as staked points only to lose those change because of the convert as staked points function.

All help is appreciated.

CB

Gary Kuroski's profile image
Gary Kuroski posted 07-07-2025 05:59

Open a separate project. Import the as-staked points, convert them to points, save, export .csv, renumber your points to your liking, then save .csv file. Then import those points into the project you want them in. 

Francisco Guerrero's profile image
Francisco Guerrero posted 07-08-2025 04:01

one- Dont use the drag and drop function.  Use the actual file import tool.  This will allow you to add a pre-fix, suffix or merge.   Also, have the crew export the CSV file to open in Excel and rename.

Clayton Bradshaw's profile image
Clayton Bradshaw posted 07-08-2025 09:32

Thank you Gary and Francisco.  

We build our TBC database off the raw data, so importing .csv does not work in our workflow, with that said, we could change that.  Prior to TBC we only considered the raw data when an adjustment was needed or when we found errors in prism constant or rod height.  Our point database was a collection of point coordinates based on the resulting location from what was measured in the field.  I.E. it was static not dynamic.  Not that TBC is much more dynamic unless you run an adjustment, it is a bit more, but not totally.  

I will try the import function, instead of drag and drop and see if we have luck there.  I am not sure we will, As Stake Points are different than regular points so you don't see the conflict until after the import.  I will give it a shot though.

Thank you for the contributions.