Trimble Business Center

So I imported my JXL into TBC and now I can't edit the feature codes, it's greyed out. Any ideas on what's happening?

------------------------------
Donnie Hughes
------------------------------

Unusual, what code did you give them in the field? Anything specific in the feature code library?

You may have to convert them to normal points. Select them, right click and "convert As-Staked point".

What TBC and Access version do you use?

It's probably a localization thing UK vs US, on all TBC versions that I have it's called "As-Set Out" not "As-Staked".

------------------------------
Ronny Schneider
------------------------------

there is a toggle in the setting to allow the modification/editing feature codes but this is specifically for feature code processing, so I'm not sure. Are you certain that you have full rights and have plenty of space on the drive where that file resides?

------------------------------
Zach Edwards
------------------------------

"As Staked" points can't be edited or adjusted. They're intended as a record. If want to use them in some other way you'll have "Convert as staked" which creates a copy as a topo measure point.

------------------------------
Andrew Haukaas
------------------------------

i sure wish that tbc would let you change ALL greyed out values. sure, show a pop up that warns that you are changing a 'record' but most of the purpose of the processing stage of a project is to fix field records missed when out in the harsh realities of the world. 

further to this as staked points AND coordinates should be 'linked' to the field data and have an option to allow them to move with network adjustments, again show a pop up warning what is going to happen. there are more days than not that we are on a project and use stakeout and then run a network adjustment. so many days that we ALWAYS convert as staked points and delete them. 

------------------------------
ian bissonnette
------------------------------

Our SOP is that NOTHING is saved as a staked point unless you're actually putting something in the ground for construction stakeout. It's good that the saved shots taken on hubs don't convert to different coordinates with transformations and coordinate changes.  This could, and would often, result in erroneous reporting of the laid out coordinates. My opinion, no one should be post-processing construction layout coordinates. IMO

------------------------------
Andrew Haukaas
------------------------------

Original Message:
Sent: 02-02-2025 10:15
From: ian bissonnette
Subject: Can' Edit feature codes in TBC after importing JXL

i sure wish that tbc would let you change ALL greyed out values. sure, show a pop up that warns that you are changing a 'record' but most of the purpose of the processing stage of a project is to fix field records missed when out in the harsh realities of the world. 

further to this as staked points AND coordinates should be 'linked' to the field data and have an option to allow them to move with network adjustments, again show a pop up warning what is going to happen. there are more days than not that we are on a project and use stakeout and then run a network adjustment. so many days that we ALWAYS convert as staked points and delete them. 

------------------------------
ian bissonnette
------------------------------

@Andrew, how do you do a shutter alignment check or pavement check? They're always "staked points". In case of shutter check I need to see the offset values while I do the pickup, and in worst case stop have it rectified and redo/continue. And for pavement it's common practice to pick up at certain station intervals along a line and you have to make sure to pick up and check if it is wide enough. I'm nearly 100 % of my time in stake mode. 

And I haven't seen the above shown greyed out feature code yet. That's one of the things you should be able to change, it's basically just like a comment.

So far, I was always able to do that since I tend to change feature codes easily with polygon select and the 3D view in TBC than changing it all the time manually while in stake mode. Changing feature code is rather cumbersome while in stake mode, a hybrid of measure codes and stake mode would be good.

------------------------------
Ronny Schneider
------------------------------

Original Message:
Sent: 02-02-2025 11:16
From: Andrew Haukaas
Subject: Can' Edit feature codes in TBC after importing JXL

Our SOP is that NOTHING is saved as a staked point unless you're actually putting something in the ground for construction stakeout. It's good that the saved shots taken on hubs don't convert to different coordinates with transformations and coordinate changes.  This could, and would often, result in erroneous reporting of the laid out coordinates. My opinion, no one should be post-processing construction layout coordinates. IMO

------------------------------
Andrew Haukaas
------------------------------


Original Message:
Sent: 02-02-2025 10:15
From: ian bissonnette
Subject: Can' Edit feature codes in TBC after importing JXL

i sure wish that tbc would let you change ALL greyed out values. sure, show a pop up that warns that you are changing a 'record' but most of the purpose of the processing stage of a project is to fix field records missed when out in the harsh realities of the world. 

further to this as staked points AND coordinates should be 'linked' to the field data and have an option to allow them to move with network adjustments, again show a pop up warning what is going to happen. there are more days than not that we are on a project and use stakeout and then run a network adjustment. so many days that we ALWAYS convert as staked points and delete them. 

------------------------------
ian bissonnette

i get your point andrew, and i think we both have similar goals, correct work and correct records of the work done. i also agree that in theory it would be great if all stakeout was done from an adjusted control network, but i think there are many scenarios where that is not possible without a second trip to site which ends up costing the client.
maybe we are the exception (not sure), we often start projects from an autonomous base station setup and complete the job in one day. typically the reason it happens is that we are laying out something that needs to be relatively correct but not necessarily absolutely correct until the deliverables are produced. examples: stakeout of property lines relatively correct to found property corners, layout of a building to property setbacks, layout of power pole inline with two other poles and/or calc deflections and anchors, layout of power line wire sag in relation to attachment points, i m sure there are others…
you are using the software how it is designed to be used, so that is great, i am asking to keep this workflow, but offer the option to link ‘coordinates’ / staked point to the observations. in our workflow we are trying to purge the data collector of all possible transformations/manipulations that the field crew might have done and only keep the reduced raw angles/distances, vectors…so having the software hold the asstake coordinate over the observation does not work well and removes the value of the as staked function.
hope that makes sense.


Original Message:
Sent: 2/2/2025 1:16:00 PM
From: Andrew Haukaas
Subject: RE: Can' Edit feature codes in TBC after importing JXL

Our SOP is that NOTHING is saved as a staked point unless you're actually putting something in the ground for construction stakeout. It's good that the saved shots taken on hubs don't convert to different coordinates with transformations and coordinate changes.  This could, and would often, result in erroneous reporting of the laid out coordinates. My opinion, no one should be post-processing construction layout coordinates. IMO

------------------------------
Andrew Haukaas
------------------------------