field to finish

We have been using field to finish for years and it does save alot of time in the field and drafting as well. I do not think it slows me down any to hit the Beg, PC, PT or Clo command after I enter in the point code. Our field guys are really into it as well, they have the line work on the data collector so they can see and check the line work as they are taking the shots, and can correct it then or on the drive home.

Sometimes when I have alot of the same line open and cant remember if I was on BC16 or BC17 I will just jump a few numbers to BC19 however if you end each line code you can keep using BC1.

I think it just depends on your business model and the type of work you do; it doesn't really make sense for us in most cases.

I've been doing F2F since 1997. I field code the points and the conversion/drawing happens on import to AutoCAD. I've used Carlson Survey to do it, I've used Land Desktop, and I've used a proprietary LISP written by a coworker. I even tried out C&G Survey System's F2F. Now I'm using Civil3d and it really works well for that.

I have been shown how to create linework at the data collector directly, but haven't found that very satisfactory, particularly because it involves dealing with lines on a 3" screen in the sunshine. So I don't do that.

I'm a big believer in F2F. IMO it is worth the time. But the speed is not the only reason. It's the quality control. I encourage my surveyor friends to use it and my competitors to avoid it.

I came late to the F2F party, having started in 2011 it so, but I use it on every topo I do now. It saves a ton of time both in the field (I rarely have to sketch anything anymore) and in the office (no more scratching my head trying to remember how to connect the points).

I'm mostly Microsurvey, but have always, since early mid 90's appreciated FTF.
Initially using appropriate coding, but later with Field Genius and straight codes.
Not sure I'd want to not use it for any topo over 200 (?) points.
Be extremely time consuming and like Jim said a lot of head scratching otherwise.
Adds a measure of quality assurance IMO, knowing line work is generated in the field not later.

Well worth effort to get up to speed I'd suggest.

Richard, post: 393050, member: 833 wrote: I'm mostly Microsurvey, but have always, since early mid 90's appreciated FTF.
Initially using appropriate coding, but later with Field Genius and straight codes.
Not sure I'd want to not use it for any topo over 200 (?) points.
Be extremely time consuming and like Jim said a lot of head scratching otherwise.
Adds a measure of quality assurance IMO, knowing line work is generated in the field not later.

Well worth effort to get up to speed I'd suggest.

Field to finish for everything I do. I don't want to be sitting behind the computer drafting what the f2f can accomplish in the field.

Mark Mayer, post: 393036, member: 424 wrote: I've been doing F2F since 1997. I field code the points and the conversion/drawing happens on import to AutoCAD. I've used Carlson Survey to do it, I've used Land Desktop, and I've used a proprietary LISP written by a coworker. I even tried out C&G Survey System's F2F. Now I'm using Civil3d and it really works well for that.

I have been shown how to create linework at the data collector directly, but haven't found that very satisfactory, particularly because it involves dealing with lines on a 3" screen in the sunshine. So I don't do that.

I'm a big believer in F2F. IMO it is worth the time. But the speed is not the only reason. It's the quality control. I encourage my surveyor friends to use it and my competitors to avoid it.

So the way you currently do it the lines are not visible in the field? I kind of like being able to check them as I go to see if I made a mistake, and also to see if I'm missing anything.

I haven't played around much with linework in the field, but base on my experience with simple tasks like looking at points on that tiny little screen, I'm thinking that I wouldn't use it much, if at all. Just viewing points is a real pain.

Dan Patterson, post: 393063, member: 1179 wrote: So the way you currently do it the lines are not visible in the field?

True. Frankly, if I miss any lines I'm not likely to pick that up on a 3" screen in the sunshine. I can view the points, of course.

To a certain point the line work can be a pain. But one can immediately see crossing lines and know something is a miss.
Heading up the road and forget to change from bitumen edge (linework) to verge (linework) one immediately sees a wrong entry.
As said that's Field Genius and my method.
Basically being comfortable with your software is No 1.

I love it. I started using it about 4 years ago and want go back to the "old way" of topo. Seeing it draw right in front of you eliminates a lot of user error and allows you to immediately fix mistakes in the field. When data arrives to the office, it's right and the thinking part is over with.

For the guys who have a hard time seeing in sunshine, you can turn your map background black in survce.

Sent from my SAMSUNG-SM-N920A using Tapatalk

Being fairly new to f2f. I understand he concept, but my problem is trying to remember what bc, top, toe,eg,ea line # im on.

John. Birner, post: 393555, member: 12084 wrote: ...my problem is trying to remember what ...... line # I'm on.

For just that reason I usually run a whole line, then run the next one on the way back. That makes for more walking I suppose but so what. A small white paint dot, keel mark, or boot scuff in the dirt helps me get the shots at corresponding places where needs be, as with gutter line and top of curb.

John. Birner, post: 393555, member: 12084 wrote: Being fairly new to f2f. I understand he concept, but my problem is trying to remember what bc, top, toe,eg,ea line # im on.

If you're using survce, you can check an option in the job settings to use unique linework IDs.
So that way if you come up to a new line, you can just press the begin line button and it will automatically insert the next number for that specific code. Here's an excerpt from the manual.
ST & END: Start and End Line. Some users prefer codes such as BL for Begin Line and EL for End Line, and ".." is another example of an "end line" code. You only need either to start or end lines to get new lines. You don't need to use both the start and end line coding. If you code 3 EP points as EP ST, EP, EP then the nexst new line can be EP ST again. Or you could just end the line as in EP, EP, EP END, then start again with EP. Another separate technique to generate unique lines is to add a number to the code, as in EP1, EP1, EP1. Then if you code EP2, EP2, EP2 a separate line will be drawn. In this case, you don't even need to use the start or end special codes. This allows you to mix the codes up as in EP1, EP2, EP2, EP1. In this case, the EP1 codes will connect and the EP2 codes will connect. See also the discussion below on "Auto-Detect Code Pattern" for techniques of cross-sectioning roads and other linear features. Within Configure, the option "Use Unique IDs for Linework" makes use of the EP1, EP2, EP3 concept by incrementing the appended number each time a new line is started using the line start code (eg. ST) or the line start icon. With "Use Unique" on, the EP code becomes EP1 when you start a line, and if you use EP again and start another line, the code becomes EP2, etc. In this case, the ST code is retained (redundant but harmless) as in EP2 ST, EP2, EP2.

Sent from my SAMSUNG-SM-N920A using Tapatalk

arctan(x), post: 393583, member: 6795 wrote: use unique linework IDs.

I interpreted John's remark to mean that the problem isn't the ability to generate unique IDs, but rather to remember which line he's shooting. Mark's solution is the simplest, but it involves extra walking. I usually try to keep no more than 3 lines going at the same time, as I have a hard time keeping any more than that straight in my mind. I usually end up editing a line or two in the office despite my best efforts in the field, but that's okay -- F2F still saves me a ton of time.

Jim Frame, post: 393586, member: 10 wrote: I interpreted John's remark to mean that the problem isn't the ability to generate unique IDs, but rather to remember which line he's shooting. Mark's solution is the simplest, but it involves extra walking. I usually try to keep no more than 3 lines going at the same time, as I have a hard time keeping any more than that straight in my mind. I usually end up editing a line or two in the office despite my best efforts in the field, but that's okay -- F2F still saves me a ton of time.

My solution if I forget which I'm line I'm on is to type in the code and press the begin line button to get the next line # and then backspace the new # and subtract 1.
Another nifty thing survce can do is the auto-detect code pattern for linework. Works really well when shooting a road or multiple parallel features since it auto populates the next code for you.

Sent from my SAMSUNG-SM-N920A using Tapatalk

Then there's always a field book to keep track ...

I run TDs with C3D...any videos out there y'all can point me to to see if F2F would work for me?