@norman-oklahoma I prefer the cross section approach rather than walking the same lines back and forth. ?ÿNo extra keyboarding.
And there's minimal keyboarding required if you set up your DC with a grid of one-touch buttons to store points:
One of the most under-utilized functions in my opinion. 3-5 minutes of setup and I don't have to do anything but tap the appropriate button as I cross-section. Back of walk, top of curb, flowline, lane stripe, crown, stripe, flow, top, back....pace 25 feet down the corridor, repeat.
Tap + to advance to next linestring, if I need to replace a grid button, tap and hold, enter code, accept, go back to surveying.
?ÿ
Years ago I worked for a large company that had a President who would spout thinking outside the box, but never actually made it possible for us to do that because of his rigid thinking. In short, he repeated the latest buzz words but was otherwise clueless. Everything had to be done the traditional way with the traditional hierarchy.?ÿ
When I went out on my own I knew a path to success was high tech and a solo practice, and after 20 years I can confirm that was the best choice, using my own COGO and my own F2F optimized for maximum efficiency. I made money, a lot of money.
I happened to meet him in a local coffee shop and he asked if I was still surveying. I said I was, still working solo. His reply was, "Oh, well, the important thing is you are happy." Still rigidly clueless.
Bottom line: F2F properly used is maximum efficiency. Collect everything, dump it in the computer, and there is the drawing in seconds.
Time to sit out front with a glass of wine and watch the sunset.
The BEST option (IMHO) is not using "end"
If you simply start the line with a unique identifier each time, then there is no need for either.
?ÿ
EC1
EC2
EC3
And Carlson SurvCE (etc) will automatically use the next available identifier, if you set it to do so
Works with ACAD database import as well.
And if you aren't solo, it may be even more important. If the crew can draw the data on the screen and it makes sense, then the drafter (who has never seen the site) has a much better chance of actually making an accurate drawing.
For cross sections I label lines on my left odd numbers and lines on my right even numbers.
There are definitely more special codes that can be used.?ÿ I was just trying to give the OP the basics for getting going.?ÿ
Another good one is using PT for a curve more than 3 points.?ÿ
I find that closing figures and doing offsets in the office goes pretty quick, so I don't bother with a lot of those in the field.?ÿ And I'd rather take another shot than using the JPN to connect to a prior shot point.?ÿ
You just need to try it out, and find out what works for you.
I use sequences for repetitive pickup and you don't have to make any coding changes between shots and you can still shoot a pole or mh in the middle of it all. The only drawback is you need to have the exact number of shots on every section, one extra or too few and it'll mess them all up. So for example code X9 could be a rural road section (BS, DL SH EP CL EP1 SH1 DL1 BS1) . . all with one code.
Yes, but how many numbered strings do you need to use??ÿ
I mean, once you're done with a section of road, you can go back to using?ÿ
BS TS TC EP CL EP1 TC1 TS1 BS1
you can use those same codes again.?ÿ So you don't have to keep increasing numbers, unless you have more than 2 EP's in a cross section.?ÿ You only need to use numbers if you're collecting similar features at the same time.
If after doing a cross section of road you need to locate a parking lot, you can go back to using just EP for the code.?ÿ You don't have to be at EP21 or anything.
?ÿ
There are definitely more special codes that can be used.?ÿ I was just trying to give the OP the basics for getting going.?ÿ
Another good one is using PT for a curve more than 3 points.?ÿ
I find that closing figures and doing offsets in the office goes pretty quick, so I don't bother with a lot of those in the field.?ÿ And I'd rather take another shot than using the JPN to connect to a prior shot point.?ÿ
You just need to try it out, and find out what works for you.
I find the JPN code very useful for shooting a guywire and having it connect it to the previous PP shot. This minimizes time in the office trying to figure out which PP the guy goes to if you have several in a small area.?ÿ
I also use the odds and evens method.?ÿ It's an enjoyable challenge to string together codes.?ÿ I've found that double coding is a clean way to avoid crossing breaklines for features such as driveway aprons.?ÿ bc PT E ec B then ec E bc PC B.?ÿ End the the back of curb at the PC and start the edge of concrete then on the next shot, end the edge of concrete and start the back of curb at the PC.
I had a road profile that allowed me to carry fourn lines.?ÿ bkl11 bkl9 bkl7 bkl5 bkl3 bkl1 ep1 bkl ep2 bkl2 bkl4 bkl6 bkl8 bkl10 bkl12.?ÿ Gotta love JPN and CIR too.
?ÿ
Nevertheless, for a person just starting out, my recommendation is to run lines one at a time. Once the user is comfortable with that he can decide if he wants to get fancier. In the words of Mr. Miagi "must walk before can run."
I've been doing F2f consistently since 1993, and I usually run one line at a time. The exception is when, for one reason or another, moving from point to point is somewhat restricted.?ÿ But I almost never have more than 3 lines going at once.
I'll step off cross sections before I begin and put a paint spot on CL or both curbs to keep me on section.?ÿ
Running streets cross section style means walking back and forth across a street many times while your full attention is divided. There is a safety element to this.?ÿ Even quiet streets have some traffic.
When I had yet to figure out the linework in Magnet field and I had a helper that day, I walked the lines out and had him spray a tiny paint mark at each spot so I would get the cross section right. That and watched on the screen to see if I was next to the nearest shot I took.?ÿ
Now that I have figured out linework and it's pretty quick I'll probably do cross sections.?ÿ
Understood.?ÿ Granted, crossing the street can be hazardous so you could set up the sequence(s) to do each side of the road separately and then finally walk the c/l. I wouldn't classify sequences as "fancy", they save both time and effort and with just one code they're so easy to implement.?ÿ
One other special code I haven't seen mentioned in this thread is "smo" that's useful for a snaky line. It'll generate a smoothed out polyline and if you need a surface, plot it as 3dpoly and it'll interpolate the elevations too and that can generate a more realistic looking tin model.
Hmmm, not sure what a bkl is.?ÿ Breakline?
Your example above looks like you're running 15 lines in a cross section.?ÿ That, makes my head hurt
One other special code I haven't seen mentioned in this thread is "smo" that's useful for a snaky line. It'll generate a smoothed out polyline and if you need a surface, plot it as 3dpoly and it'll interpolate the elevations too and that can generate a more realistic looking tin model.
I do this by coding the initial shot PC then take as many shots along ?ÿthe winding curve needed then end it with PT.
A good example of a site that will benefit from these methods:
@jph?ÿ I've found it's pretty common to have multiple tops and toes or even ECs from detached sidewalks or utility pads.
I have eliminated top and toe codes from my list and substituted a single breakline (BL) code. Also gone are codes for bottom of ditch or CL creek, etc. The contours tell me if a line is a top or a toe. Google earth identifies waterways for what they are.
I've also eliminated separate codes for top of concrete, top of asphalt, top of gravel, etc. in favor of a single code for spot elevation.?ÿ
Before anyone get all up on their hind legs - I made this change several years ago, I've done plenty of topos this way, some quite extensive, and it has never been a problem.
For those using Civil3d, you have geospatially correct aerials available at the touch of a button if your survey is on a NSRS grid coordinate system.?ÿ?ÿ