Nate The Surveyor
Well-Known Member
I've always done the same as Darren, above.
It's something of interest.
I've thought of a number of schemes. "Export by base session", where it displays all base sessions, with it's respective sideshots. (like dpos does). And, we havee a check box mechanism, to select the base sessions. I'd like this. With an EXTRA check box "include cogo coords, made during session". And, an extra check box "include all cogo from entire job". This second option, would not be session dependant.
The issues that arise, are the fact that alpha only point names are permitted. If we export numbers 35-70, where does that put the alpha only points?
So, point name can be "pipe". (by accident, or on purpose).
Either way, it involves US the end users, having more power, and ability, than we are used to. So, we must think, consider, and be aware of what we are doing.
It's something of interest.
I've thought of a number of schemes. "Export by base session", where it displays all base sessions, with it's respective sideshots. (like dpos does). And, we havee a check box mechanism, to select the base sessions. I'd like this. With an EXTRA check box "include cogo coords, made during session". And, an extra check box "include all cogo from entire job". This second option, would not be session dependant.
The issues that arise, are the fact that alpha only point names are permitted. If we export numbers 35-70, where does that put the alpha only points?
So, point name can be "pipe". (by accident, or on purpose).
Either way, it involves US the end users, having more power, and ability, than we are used to. So, we must think, consider, and be aware of what we are doing.