I have a job that is a good ways from where I live. I have to go and tie into some Roads (With curves), and fences, and calc the job, to give one parcel 3.01 acres, and another at 4.01 acres. The client owns in all directions, except across the road. I want to go and tie a pile of stuff, then calc the acreage. Now, I know, I can down load it into a laptop, and calc it there.... however, I can also do this on my TDS as is. It is not as nice as on a laptop. But, I'm looking to know a few details about cogo.
Where this question is coming from is I often do field work, then office work, (generating search coords) and return to the field. Tie more stuff, and then sometimes totally re calc the job, based on the found monuments. It's just what I do.
Fast and easy cogo is valuable.
How much is in the LS?
Is is simple?
Or is it strictly a box that gets good lat longs, where it then gets exported (projected) to a plane, then stuff is generated, and sent back to the LS for staking?
Thank you,
Nate
Just (maybe not quite) enough?
Parallel area calculations are supported in J-Field (Javad's data collection software for the Triumph-LS), but currently polygons with curves are not supported in parallel area. Areas with curves can be calculated - including area at the grid or ground (or ellipsoid for that matter). The height of the polygon can be manually entered (useful if you are calculating areas from points with zero elevation - such as calculation points).
There are a lot of CoGo features in J-Field and new features are added all the time. There are intersections, inverse (expressed in any flavor you want - grid, ground, ellipsoid, mark to mark), inverse to lines, area, averaging points and calculating offsets, create points from direct (bearing and distance) or traverse (turned angle).
One recent addition is the ability to store a rotation angle in a memory cell (such as the rotation you might have between a deed call and your own bearing relation between two surveyed points). You can enter the deed calls, and then add, or subtract the rotation when calculating points ahead.
Some CoGo can be done in the map environment (similar to CAD).
I would rather calculate in CAD any day of the week over a data collector, so you have to figure for yourself what makes the most sense for calculations, what you are most comfortable with, what you are most efficient with. Generally when traveling for over an hour to a job (in hopes of completing it in one trip), we take a lot of redundant equipment. We'll take the laptop, just in case we run into something that requires more computing power.
I think there's a lot of cogo in the box, but I'm finding the user interface to be so different from TDS or SurvCE that I'm still struggling to do any cogo efficiently. It might be me, it might be the box, it might be both. I'm hopeful, though, on all counts!
