TDS raw data missing grade, elevation fields in stake-to-line and offset staking

Did you mean to occupy #1007 ??ÿ Just looks like some 10'-20' shots nearby, did you set up on #1007 or stay on #1006 ?

Hi R.J.,

Yep, I just didn't cut/paste the setups, they're all part of the same control survey and they're all correct in the raw data, WITH elevations.

?ÿ

Posted by: @rj-schneider

Did you mean to occupy #1007 ??ÿ Just looks like some 10'-20' shots nearby, did you set up on #1007 or stay on #1006 ?

Thought you might have somehow accidentally set your occupied point the same as your backsight.

Most dc software nowadays will warn you when you do that.?ÿ Not sure if that was the problem, really just guessing.

Most of those shots were relatively close to the instrument, couldn't see why you'd change setups.

anyways.

Were the actual shots outside the beginning or end of the line? In the example "bad" record, I see a station value of zero. Maybe the rod was just barely outside the beginning of the alignment.

Did you see cuts and fills onscreen in the field?

I suspect our routine is similar to yours, we'll always use the field values to write on the lath, then run a custom cutsheet report like yours and check the written values after staking is complete. But I've never seen it show cut/fill data in realtime then not store it in the raw data.

In the past I have had survey pro miss raw data for a few shots with no explanation. Maybe a 100 shots taken all from the same set up with no changes but shots 43 thru 49 have no raw data. Never did figure out the cause.

Posted by: @lurker

In the past I have had survey pro miss raw data for a few shots with no explanation. Maybe a 100 shots taken all from the same set up with no changes but shots 43 thru 49 have no raw data. Never did figure out the cause.

Weird, I used SP for ~2 years a while back, didn't see that occur.

Or (more likely) it did happen and I missed some shots during that time?ÿ ?????ÿ

@rover83 It was so infrequent we thought maybe it was a bad sector on the hard disk that wouldn't store any data. So whenever data was being written to that sector there was a gap of missing raw data. Still have no idea whether it was hardware or software, but we are almost positive it wasn't caused by the operator.

DOH. Nevermind. It's operating as intended, I suppose. The design points didn't have elevations, so it didn't record the grades either.

You know, with Survey Pro, you can open the raw/rw5 in notepad or wordpad and do a search/replace for SK, and change to SS, and you can get your elevations when you process through Carlson, C3D, etc.?ÿ Just make sure to delete all of your SP lines, or do a search/replace for SP, to --SP,

Hi JPH, thanks, this was always just about getting the grade and elevation from the raw data to a cut sheet programagically; we can always get the elevation from the stored coordinate and add the grade manually.?ÿ

It's not an issue anymore, since I realized that it only happens when the design point has no elevation when the SK shot is stored. It CAN be imported from a .csv file with NO elevation, but it shouldn't be. We now insure that imported points have an elevation, even if it's 0.0. and the program works every time.

Cheers!