TBC Convert As-Staked points

Having the same issue.

Maybe your dongle has come unseated?

Not a dongle issue, It seems to only happen when I get files from a specific DC.

Firmware is my guess. Keep everything current, everything always works (always may not be totally accurate I guess... but generally)

Not the firmware, all DC's use the same version and share the control file for this particular project.

Maybe they didn't store the point as an as-staked point and shot in regular mode. I've had this happen before also and can't remember what the deal was.

makerofmaps, post: 346833, member: 9079 wrote: Maybe they didn't store the point as an as-staked point and shot in regular mode. I've had this happen before also and can't remember what the deal was.

Did you figure out a way to De-flag them?

Jayme, post: 346856, member: 10812 wrote: Did you figure out a way to De-flag them?

Seems like you can disable one of the points through properties or turn off the flags in view filter.

Turning off the flags does not eliminate the flags. It's kinda like sticking your head in the sand to avoid predators.

Any solution?

I had this happen and i could not select any and export either. ?ÿWhat I ended up doing was deleting the jxl or job files that they came in with recompute the project then re import the same jxl or job file and for whatever reason it worked for me. It has happened a couple times now just randomly. I have a tbc project that is several months old and ever so often it does something goofy with as staked points. ?ÿThey are there but not there. Kinda thing.?ÿ

@olemanriver?ÿ

My PM has also had another issue with staked and stored points I shot, where they came in across a different lot in an entirely different location then where I stored them. It only happened on this one job last week and another done by a different crew several months ago (different tsc7 and version of access with that crew).?ÿ

?ÿ

My PM has also had another issue with staked and stored points I shot, where they came in across a different lot in an entirely different location then where I stored them.

?ÿ

Are they being flagged with large deltas i.e., they are obviously in the "wrong" place?

?ÿ

Were their point numbers duplicates?

Do the project coordinate system settings in TBC match the job coordinate settings on the DC on import? e.g., Local vs State Plane or vice versa.

?ÿ

?ÿ

@rover83?ÿ

I'm not sure about any flags on his end but they were staked out within 0.009m on my end with no warnings or anything. He eventually got it to work but still had no idea why it happened.?ÿ

The only unusual thing was I had to set up on a point that was linked from another job and the other job had calcs for the house in a different position (house was shifted back on the lot). Not sure if that has anything to do with it or not.?ÿ

I'm on holidays until Monday so I won't likely be looking into it until then.?ÿ

From what I have seen, the ability to not convert points comes from an inconsistent coordinate system, usually the geoid model being used.?ÿ ?ÿ

@fairleywell?ÿ

I will check that with my PM when I'm back.?ÿ

@350rocketmike lol this just happened to one of my crews. ?ÿHere is what I assume happened. He had a job he started and imported points from a csv fiI gave him. Instead of linking it like I requested. ?ÿWhen he imported them he had a rental dc. The values were in usft. His dc job was default to meters. So the dc thought they were meters. He realized something was wrong. Called me i had just been in a meeting about the usft to international foot thing so i asked him to ck it was meters. I told him just start a new job set it up right and move forward he did. But instead of linking to the csv file he linked to the other job. On ground everything was correct he cked into old stakes all good. When I brought it in it shifted everything and i was like what in the world. ?ÿI had him unlink the job file re send me same exact jxl. And it plotted correctly. Probably some glitch. Linking to a datum job from a scale only job can cause issues sometimes as well.