Author Topic: Code Styles?  (Read 3070 times)

0 Members and 1 Guest are viewing this topic.

therock003

  • Guest
Code Styles?
« on: June 01, 2009, 10:42:15 AM »
In order for me to stay organized and improve F-2-F functionality of my Total Station i need to set some help setting up my code style sets.

What might you suggest i add/define in order to improve my field work, and become more efficient?

Bakerman

  • Guest
Re: Code Styles?
« Reply #1 on: June 01, 2009, 11:31:38 AM »



Several state DOTs have very good survey manuals that you might draw from. Here is a link to the California one.


http://www.dot.ca.gov/hq/row/landsurveys/SurveysManual/Manual_TOC.html


mjfarrell

  • Seagull
  • Posts: 14444
  • Every Student their own Lesson
Re: Code Styles?
« Reply #2 on: June 01, 2009, 09:20:26 PM »
Be your Best


Michael Farrell
http://primeservicesglobal.com/

Bakerman

  • Guest
Re: Code Styles?
« Reply #3 on: June 02, 2009, 01:01:53 PM »
:-o :lol:  and where in all of that are the code styles? 


I noticed that there were no code styles but I figured it would give a search direction......sounds like there may be a need for more than code styles.  :-D


mjfarrell

  • Seagull
  • Posts: 14444
  • Every Student their own Lesson
Re: Code Styles?
« Reply #4 on: June 02, 2009, 02:51:41 PM »
......sounds like there may be a need for more than code styles.  :-D



and I so want to fill those needs... I see them quite a bit in ol' rockies posts....
Be your Best


Michael Farrell
http://primeservicesglobal.com/

therock003

  • Guest
Re: Code Styles?
« Reply #5 on: June 05, 2009, 05:08:51 PM »
Yes i'm a puzzled young lad all right!  :-)

Although i'm searching this specific task so i can achieve better field-2-finish with my total station.

It allows you to create code set, where eachcode is linked to each own layer style and point style and has certain properties.

Sofor example youcan survey the boundaries of a parcel and codethem as boundary and have the set for the layer style andfor the linework to be completed upon surveying each point.

So not only do the points appear onthe drawing but the linework is ready as well.

This helps out a lot and if you take the time to organize and manage your projects efficient you may beable to get a lot more done with less sweat!

And that's what i'm asking for here.

Suggestions for this coding scheme.

The parcel boundary is the most obvious example. What others are most frequently used?

jugglerbri

  • Guest
Re: Code Styles?
« Reply #6 on: June 06, 2009, 11:51:43 PM »
It allows you to create code set, where eachcode is linked to each own layer style and point style and has certain properties.
Well, to accomplish this, you need to set up your description keys.  Description keys will filter your points as you bring them into your drawing and modify some of their properties such as style, label style, layer, convert a raw description to a full description.
So not only do the points appear onthe drawing but the linework is ready as well.
For the linework, you'll need to set up a figure prefix database and then process the linework.  You can use a fieldbook file or the new linework code sets to automate the creation of the linework.

mjfarrell

  • Seagull
  • Posts: 14444
  • Every Student their own Lesson
Re: Code Styles?
« Reply #7 on: June 08, 2009, 09:37:29 AM »
You will like to watch the following tutorial to set these up more easily: http://primeservicesglobal.com/tutorials/Points.zip

These are covered in more depth in the Pirated3D series of videos as well.
Be your Best


Michael Farrell
http://primeservicesglobal.com/

Dent Cermak

  • Guest
Re: Code Styles?
« Reply #8 on: June 08, 2009, 01:36:47 PM »
Descriptor keys and figures are probably the most important tools for the surveyor in AutoCad, yet I am told that 90%-97% of the people out there do not use them. I cannot speak for AutoCad C3D 2010, but all the way up to 2008, they were very simple to set up.The loggerhead came in trying to get the field people to use them. Eventually they will come around and the days of "connect the dots" will be over. BUT, you must think out your setup, pre-plan it and make it as easy to use in the field as possible. Our descriptor key list is 9 pages long. It's mainly 2 or 3 key stroke descriptors. You MUST Keep It Simple for it to work.
You will also need to look at what codes your data collector supplies. These codes added to the descriptor keys are what can make it all happen with maximum ease.

mjfarrell

  • Seagull
  • Posts: 14444
  • Every Student their own Lesson
Re: Code Styles?
« Reply #9 on: June 08, 2009, 07:47:50 PM »
What I have found works the best, is to set up your Field codes, based as closely as possible on what they are already using to describe features. 

Then explain the theory, of how the line coding works to the field crew and why you want them to use it.

Then have them go outside and survey around your build, and parking lot and some of the street. Applying the line codes and theory.

Import the data (FBK) or the new ASCII line coding and have them witness the results of their coding.  When it works, or not they will be able to A) see that the line codes work, and or B) learn what doesn't work and revise their process as required.

From that point forward you will find they are more apt to use them.

Until they make the connection between what and how they do in the field relates to what happens in the office, you are unlikely to get them to play along.
Be your Best


Michael Farrell
http://primeservicesglobal.com/