That will indeed work, but it's WAY too complicated for my Mississippi rednecks. I employ the KISS system. First of all, a field file shot lineraly is just as accurate as shooting in x-section format. In the x-section format all you have to do is miss a shot and you are screwed.
We set up and shoot the EA.Then come back down line with the next feature, say CL of the road. Up and back, up and back. Move up to next setup. Repeat proceedure using RECALL to tie everything together. Initially it took about 10% longer to do it this way. The office savings offset that initial burp by far. Now a crew that knows the system takes about the same amount of time as shooting x-sectionally.
The Key is STANDARDIZING the codes. My code list is on the lilly pond. Anytime a crew comes up with something new add it to the list. This includes the abbreviations for the line work and the descriptor keys. My descriptors for the descriptor keys are my block file name. My block for a sanitary sewer manhole is named "SSMH" thats also the descriptor code.
Jeff to understand the BEGIN , END and other codes, open my FBK file with notepad or word. You will see the codes in place.Most data collectors have you key in "B EA" and the data collector will enter BEGIN EA. This ,may vary from data collector to data collector. Check the Operator's Manual for more details.
If the drawing is to be done at 1"=30', the crew takes a shot every 30 feet PLUS any breaks or features inbetween the 30 foot shots. I also suggest running a closed loop traverse around the project site and setting any spur points you may need BEFORE doing much more. Keep this in a separate file from your other shpots. DO NOT let them mix the files. This will cause greif.
I can tell you now, get ready for the old "We have never done it that way before" whines. I've been through it with all 3 offices and soon will have to go through it again with more new crews. You have seen what it can do. Let them draw the lines while they are standing there looking at it. A drafter going out for field checks is wasted time. They need to be drawing. You want a field check? Cool send the PM. He's the one that needs to be doing that.
The trick is to come up with a system that you CAN work with and they WILL work with. Keep it simple. Keep it detailed. It works. The job I posted is a very SMALL job. Field time was 6 hours (had a LONG vertical run.) Office time 2 hours (including vicinity map, etc. Would be much faster but I type REAL slow.) The client was REAL happy with the low cost that he was billed. He WILL be back.
The key files are:
linetest.dwg = what you should get after importing the FBK file.
5081Topo.FBK= the fbk file that does all of the work. Open this with word or notepad to see how the code has been keyed in in the field.
MaptechCode.DOC+ these are all of our abbreviations for line work and block insertion.
