Contents Index
Road Utilities includes necessary routines to convert centerlines, profiles and cross sections from other formats to the formats used by SurvCE. SurvCE uses ASCII file formats for centerlines (“.cl” files), profiles (“.pro” files) and cross sections (“.sct” files). These same formats are used by other Carlson products such as Carlson Civil (formerly SurvCADD), Carlson Survey, Takeoff and Construction.
Road Utilities will also scale up or down centerlines and profiles, usually to convert between metric and English units. In addition, Road Utilities includes a command for entering a superelevation file (“.sup”). This file can serve as an optional input file and react with templates in commands such as Stake Road, Slope Staking and Elevation Difference. Road Utilities has an option for a Template Series file (".tsf" file). This file will transition from one template to another automatically between designated stations, as long as the templates share identical IDs. The Template Series file can be substituted for a standard template file in Slope Staking and Stake Road, wherever design files are applied. Finally, a "Template Grade Table" can be entered in Road Utilities, which designates slopes and offsets that apply left and right of centerline for any road segment, between which a proportional grade and lane width transition is calculated. Template Series files and Template Grade Tables are alternate methods of transitioning roads of variable width or slope and should not be used in combination in the same station range.
File Conversion and LandXML: The LandXML file format is becoming an encouraged standard of many departments of transportation (DOTs). This standard is also recommended by Autodesk, Bentley and Carlson. LandXML files have an “.xml” extension and may contain multiple road design files including centerlines, profiles, and cross sections. The “header” lines within the “.xml” file will indicate what design files are included. In some cases, several files of the same type, such as three or four centerlines or profiles, may appear in the same LandXML file. As more and more software companies offer LandXML file output, this file type may become the preferred form of data exchange. Be aware that each company tends to implement the LandXML format in slightly different ways, much like DXF files for drawing data exchange were sometimes slightly different in format between Autodesk and Microstation, or from release to release. Therefore, if a LandXML file containing centerlines, profiles or cross section files fails to convert, it is recommended that the file be emailed to Carlson Software so changes can be made in SurvCE to enable conversion. LandXML is an evolving format that is likely to solidify in the near future.
Centerline Conversion
This command converts horizontal alignment files to and from the Carlson centerline format (*.CL). Supported file types include:
- ASCII Inroads (.ASC)
- ASCII LDD (.TXT)
- Caice (.KCP)
- CLIP (.PLA)
- Geopak (.OSD)
- ISPOL (.ALI)
- LandXML (.XML)
- Leica (.GSI)
- MOSS (.INP)
- SDMS (.ALI)
- SDR (.SDR)
- SMI Chain (.CH)
- TDS (.RD5)
- Terramodel/Geodimeter (.RLN, .ALN and .ARE formats)
The SurvCE format has a “.CL” extension. These source files can be loaded into SurvCE using Data Transfer, located in the File menu options. When performing the conversion, and selecting a particular format, SurvCE automatically looks for the corresponding file extension.
Report Icon for LandXML Files: If you are importing a LandXML file specifically, you can click the Report icon left of the "Return" icon in the upper right of the dialog, and review the source of the data as shown:
Conversion: Clicking Existing File in the upper right (in the Land XML section) will load the file, and clicking Select New under the CL File section will save the centerline file in the correct format for use in SurvCE. To convert in the opposite direction, select Existing File under the CL section to recall a SurvCE centerline file, and then click New File in the upper left (under LandXML file) to save it back to a LandXML file, for use in other software.
For file types in which both Import and Export options are available, the conversion procedure forms a “criss-cross”: You bring the files into SurvCE by going upper right (“Existing”) to lower left (“Select New”). You send the files back to the “non-SurvCE” format by going lower right (“Select Existing”) to upper left “New”.
When the files have been selected, the appropriate action is highlighted below, "Import to CL" or "Export to <type>". When the process is completed, the program announces “Process Done,” and you are free to move on to the next command. Most formats only convert to SurvCE and not back again, and therefore only have “one-way” dialogs. These include ASCII-Inroads, ASCII-LDD, Geopak, Moss, TDS and Terramodel/Geodimeter.
Importing TDS RD5 Files
Importing TDS RD5 Files: If TDS is selected, centerlines can be converted one-way to SurvCE centerlines (centerline files CANNOT be converted back to TDS files). It is important to note that the TDS RD5 file is a dual centerline and profile file. Because the TDS RD5 file does not display the starting station, an extra dialog will appear requesting starting coordinates (which can be recalled from a point) and a starting station.
Verify the Conversion
It is recommended that after converting centerlines, profiles or cross section files to SurvCE format, you go to the Editor and Draw options for these file types and review the data to verify that the correct file was converted and that the conversion was successful. So, for example, after converting a centerline from Inroads format to SurvCE “.cl” format, go directly to Centerline Editor in the Roads menu and verify the data.
Recognizing File Formats
For reference, portions of four of the file types are shown below, as they might display in a Text Editor. The LandXML, SurvCE and SDR examples all reference the file DOT1.CL. These displays may help you recognize these file types in the future. The new LandXML format, endorsed by many Departments of Transportation in the United States, may soon become the standard in the future for internet transfer of roading and other types of design files.
Centerline Transformation
This routine is designed primarily to convert centerline data from Metric to Survey Feet or from Survey Feet to Metric. The image below shows the dialog and scale factor when converting from Metric to Survey Feet.
Apply scale factor for start station: If this option is enabled then the starting station will be converted using the scale factor. For example, a start station of 1000 would become 3280.833. If disabled, the start station would remain at 1000. If the goal is to change the starting station by a certain amount unrelated to the scale factor, then you must use Input-Edit Centerline and enter a new start station in the initial dialog. This will automatically translate all stations in the centerline by the appropriate amount.
When Apply Scale Factor for start station is enabled, the centerline is adjusted by the scale factor, after a confirming warning screen.
Profile Conversion
This command converts vertical alignments to and from the Carlson profile format (*.PRO). Supported file types include:
- ASCII-LDD (.TXT)
- Caice (.KCP)
- CLIP (.ALZ)
- ISPOL (.RAS)
- LandXML (.XML)
- Leica (.GSI)
- MOSS (.INP)
- SDMS (.PRO)
- SDR (.SDR)
- SMI (.CH)
- TDS (.RD5)
- Terramodel/Geodimeter (.RLN, .ALN and .ARE)
The SurvCE format has a .PRO extension. These source files can be loaded into SurvCE using the Data Transfer feature in the FILE tab. The conversion screen is similar to Centerline Conversion, with the characteristic “criss-cross” logic for 2-way conversion (LandXML and Leica) and one-way import only conversion for the other options.
The SurvCE Profile File Format: It should be noted that of all the SurvCE file types that are ASCII and therefore viewable in standard text editors, the profile (.pro) file has the simplest format. The format is station, elevation, length of vertical curve, and description for road profiles. For example, the Demo.pro file that is typically provided with the software has the following four lines (which can be viewed in Notepad):
0.0000, 997.0000 , 0.0000,
200.0000, 1005.0000 , 200.0000, (200 foot vertical curve length)
308.0000, 1003.9200 , 0.0000,
0.0, 0.0, 0.0 (this is an “end-profile” line)
Profile files can be created from within SurvCE, but are simple enough to be hand-entered using a text editor as well. Unequal vertical curve lengths can be entered in the form 150-50, indicating 150 units to the point of vertical intersection and 50 units to the point of vertical tangency. Other ASCII file types, such as centerlines, can be deciphered, but are generally of a more complicated design and are best created using the editors provided within SurvCE.
Profile Transformation
Like Centerline Transformation, this routine is primarily used to scale a profile up or down to go from Survey Feet to Metric or from Metric to Survey Feet.
Unlike Centerline Transformation, Profile Transformation can directly translate the profile up or down. You can also scale the profile stationing and elevations. If you want to apply a translation to selected stations, tap the Translate button. The Translate option leads to its own dialog of entries, which allows you to translate both the stationing and the elevations, as shown below. In this way, you can make the starting station 1000, or raise the entire profile 15 feet or meters.
By default, the entire range of stations is selected. If you wish to only translate a range, highlight the beginning station, then click End Station and highlight the end station. Next enter the amount to translate in the Change Station box. You may also translate the elevation using the Change Elevation box. Tap OK when you are finished.
Section File Conversion
This command converts section files to and from the Carlson section file format (*.SCT). Supported file types include:
- Caice (.FFF)
- CLIP (.TRV)
- Geopak (.XRS, .XSR, .SOE & .TXT)
- IGRDS (.LIS, .RDS & .TXT)
- Inroads (.TXT)
- ISPOL (.SC1 & .RAS)
- LandXML (.XML)
- Columnar Text (.TXT, CSV & .ASC)
- Terramodel/Geodimeter (.XSC)
The SurvCE format is “.SCT”. Section files are used for Stake Slope, Stake Road and Elevation Difference. Cross Section Survey also has the ability to output section files. TDS will store cross sections in an RD5 format that behave as a series of templates, following "rules" for slopes coming from the design profile grade. You can import TDS-style cross sections using Input-Edit Template Series within Road Utilities, and for "Files of Type", select TDS.
Note that if you select XML Info at the top of the screen, you’ll see some of the “header” information associated with the XML file to be exported or imported.
To export to LandXML, you need to load a LandXML file that already contains a centerline covering all or part of the station range in the SCT cross section file. Otherwise, you will see an error message.
Despite the message, you can add the horizontal alignment portion to the LandXML file after creating the file with sections only. However, if you first create a LandXML file containing one or more alignments, then choose that existing LandXML file to export to, you can select among those centerline alignments when making the cross section file.
Section files in SurvCE can contain descriptions useful for reference in other routines such as Stake Road. If descriptions are found in the source section file, they will be captured by the import process into the “.sct” file for use in SurvCE.
Pipes running longitudinally along horizontal alignments can be imported in the form of cross sections using the Columnar Text form. The example below shows the layout of the pipe format that is recognized by SurvCE.
STA,Offset,FL elev.,Link - ID,Link - Library Item,Type
13+00.00,52.13,22.32,NP-26,18" RCP,T
14+00.00,-47.61,22.08,NP-1,18" CMP,T
14+00.00,49.63,22.02,NP-26,18" RCP,T
15+00.00,-39.58,21.78,NP-1,18" CMP,T
15+00.00,49.15,21.73,NP-27,18" RCP,T
16+00.00,-38.00,20.22,NP-3,24" RCP,T
16+00.00,48.92,21.45,NP-28,18" RCP,T
Within Stake Road, Section Method, the pipes can then be loaded as a cross section file and the pipe inverts can be staked in the same way that road cross section points can be staked. The pipe format is recognized and the pipes display with their correct diameter shown. Note the ability of the program to display the pipe size, captured as the 5th field in the ASCII file (above):
Input-Edit Section File
This routine is a convenient cross section editor. It can be used for entering new sets of cross sections or for editing and reviewing an existing set of cross sections. One nice application is Slope Staking. If you know the left and right “pivot points” on stations to be slope staked, you can enter very simple, two-point cross sections consisting of the left pivot offset and elevation, and the right pivot offset and elevation. Then, without taking a cheat sheet into the field, you can slope stake by cross section method, and the program will seek these pivot points, and even interpolate the correct pivot points between entered cross sections.
A better approach would be to include all break points in the sections from pivot left to pivot right, along with descriptions. Then Slope Staking will report the progressive information to grade each point from the catch all the way into centerline. This “section-based slope staking” is a cross between user-defined (where you need the cheat-sheet!) and design files, where the pivot offsets and elevations are taken from the pivot points in the template as they react with the profile and superelevation files. Sections used in Stake Road should be complete cross section files, with all offsets, to enable precise, interpolated stakeout within the left-to-right range of the sections, on station, or at interpolated stations.
The Input-Edit Section File routine begins by prompting for a cross section file name. If you wish to start a new cross section file, just enter a new name.
If you choose to select an existing cross section file, such as DEMO.sct, after selecting the file, you will see the “Section List” dialog.
From this dialog, you can Add stations, Edit existing stations, Remove stations, Load entire new cross section files, Save As (to save your changes to the current loaded file or to a new cross section file), and Clear the list of stations (not recommended unless you want to start from scratch). Select Edit to review a station.
In this dialog, you can Add, Edit, Remove, Rearrange, or Clear existing offsets and elevations. Note that cross section offsets are negative for left of centerline and positive for right of centerline, and can have descriptions such as SH, EOP, CL, Ditch, 21, 22, 23, etc. These descriptions, where they exist, are potentially useful for description-based interpolation between stations, as applied in Stake Road. If you want to add an offset at -42.867 called RP, click Add. You don’t have to highlight the correct offset to add above — the software will sort and place the new entry appropriately.
When you click OK, your new entry will be in the list.
The Edit box leads to the same entry dialog as Add. Remove will provide a warning and then delete the highlighted offset and elevation. Up and Down should not be used unless a file conversion led to out-of-order listing of offsets and elevations. When you click OK from the station edit dialog, you can save the revised cross section file back in the section list dialog.
Input-Edit Superelevation
Roads can contain one or more curves, and each curve can have its own superelevation data. This data includes start station for super transition, station for full super, percent of full super, station for end full super, and station for ending the super transition back to normal crown. In SurvCE, each superelevation data set for each curve would be entered as a “line” of superelevation data in the “.sup” file.
If we had two curves, both with superelevation, then we would do two Adds using this dialog. Let’s say, for simplicity, that we have a road with a 2% “normal crown” which has one curve to the left followed by one curve to the right, with the following information:
|
|
Curve 1
|
Curve 2
|
|
Start Super Pivot
|
Sta: 100
|
Sta: 2200
|
|
Full Super
|
Sta: 600
|
Sta: 2500
|
|
Full Super %:
|
3% Left
|
4% Right
|
|
End Super:
|
Sta: 1400
|
Sta: 3500
|
|
End Super Pivot:
|
Sta: 1900
|
Sta: 3800
|
The first curve to the left goes through three stages as it pivots into full super: (1) the right side pivots to “flat”, (2) the right side pivots to “reverse crown”, where the slope is the same across the template and (3) both the right and left sides pivot from the hinge point (centerline) into full super. All of these key pivot points are entered in the superelevation dialog.
You enter all these key stations (begin, flat outside lane, reverse crown, full super) both going up to full super and transitioning back down to normal crown. Recognizing that the normal crown of -2% transitions from station 100 through a slope of 5%, the transition is 1% per 100 feet, assuming an even rate of transition. Therefore, a “flat” outside slope occurs at station 300, reverse crown at station 500 and full super at station 600, as shown. You will need to compute these stations in advance. These intermediate stations are entered in the superelevation dialog to allow for different rates of transition from normal crown to flat to reverse crown to full super. Normally, the rates of transition are consistent. Note that super left or right is always entered as a positive percent slope — the road centerline curve direction will control the direction of pivot. You are now ready to click Add and enter in Curve 1.
When you click OK, the first line of the superelevation dialog is filled in. Curve 1 is complete. Next, we enter Curve 2 as follows, using similar logic.
When OK is clicked, the two curves are complete and the summary dialog appears. There is one line (or row) for each curve.
Note: If any of the columns are too narrow to display all the text, you can “grip” the vertical line separating columns, much like in programs such as Excel, and make the column wider.
The superelevation file is one of the optional “roading” or “design” files in Stake Slope, Stake Road and Elevation Difference. After a superelevation file has been entered and saved, it will appear as the default superelevation file in all of these commands, unless removed from the design file list by the user.
Input-Edit Template Series
SurvCE allows for two types of transitioning: (1) a single template can transition by being “acted upon” by template transition files (made in Carlson Roads, Topsite, Leica Site Manager or Carlson Civil) and superelevation files, or (2) a template series file can transition between several templates sharing identical IDs, but having different slopes and widths between ID points within the templates.
You can load an existing TDS template series file, in the RD5 format, by clicking Load, then clicking the down arrow for Type of File, and selecting TDS format. TDS templates always have IDs and the same number of template points per cross section, so once imported, they behave exactly like SurvCE-defined templates. Using the Draw Template option, any particular template in a template series file can be selected and displayed as shown:
The Template Series approach can even be used to transition from normal crown to superelevation, avoiding the need to use superelevation files. The Template Series approach is commonly used to expand the width of a lane to accommodate, for example, a passing lane. Since template IDs must match, if a “special slope” lane “appears” for a certain station range, then the Template Series approach can still be used as long as you add the extra ID point (e.g. EP2) to the normal template, perhaps making that point 0.001 units in dimension initially. In the second, transitional template, the EP2 lane can have the full width of 3.5 meters or 12 feet or whatever applies. If the transition starts at station 500 and ends at station 600, EP2, will be 1.75 meters or 6 feet or exactly half the full dimension at station 550.
Starting with the demo.tpl file, with a 10’ lane to ID “EP” followed by a 6’ shoulder lane to ID “SH”, you can make another template called Road.tpl, with a 12’ lane to “EP” and an 8’ shoulder to “SH”. Note how we have made sure to use the same ID for the road lane (“EP”) and the shoulder lane (“SH”).
If the demo.tpl is used from station 0 to 500, and the Road.tpl is used from 600 to the end of the project at station 1000, then the entry process for a Template Series is as follows:
Click Add and you will obtain the next dialog.
Choose Select File and pick the first template (demo.tpl). Click OK. Back in the main dialog, click Add again and specify the ending station for demo.tpl as station 500. Then click Add again and specify the first station for Road.tpl as station 600. You do not need to specify an end station, as Road.tpl will be used for the remainder of the project.
You then Save the Template Series File. When running Stake Road, Stake Slope or Elevation Difference by Roading Design Files and recalling a template file, you have the option to recall a Template Series File and process a set of transitioning templates.
Input-Edit Template Grade Table
Very complex roads such as exit ramps, with widening and shrinking lane widths and slopes that do not follow a simple superelevation pattern but instead adapt to meet grades of intersecting roads, can be defined using the Template Grade Table feature. Although template series files can be used to model any road, the creation of multiple templates, including all lanes, can be a labor-intensive process compared to entering the precise slope and width for particular template ID points. These slopes and widths are often provided in tabular form in the design documents, so direct entry of the slope/width data, applied to the appropriate template ID or several IDs, is often the most efficient way to handle complex road conditions.
Consider a template that goes from the center of the road to SH and then to SH2. The second segment is always 8 feet dimension at a fixed slope. The first lane, from centerline, is paved and has variable width and slope. The template grade table is applied to the first lane, after which the normal template rules apply. After selecting the command, you name your new (or existing) template grade table, and then the template that it is associated with. This leads to the screen shown below:
The normal slopes of -2% to the edge of pavement (inner edge of shoulder) and -4% to the outer edge of the shoulder would apply if the template behaved normally. But if you click Edit on the right shoulder, for example, you can enter station-based lane widths and slopes as shown below:
In this example, considering first slope, the road begins midway in transition, at slope 1.61% in a curve left, then transitions into a curve right with a slope of -3.9% at station 1180, greater than normal crown, holding this grade through station 1260. Then the road veers again to a curve left of 2% and holds that from station 1418 through 1480, after which it transitions to 4.7% at station 1540, holds that slope through 1754, and transitions back to a uniform cross slope of 2% at station 1814 where it remains through station 2066.86. Note that where no slope entry is entered (eg. at station 1361.11 through 1381.25), the program transitions proportionally between the last actual entries provided (1260 and 1418).
While the slope is following the instructions of the slope column, the road lane width adheres to the distance column. So if the right-side shoulder width is 32.5 feet through station 1361.1, you can enter that distance for all stations in that range, or you could simply bracket the distance by entering 32.50 for station 1085.45 and 1361.11 and leave 1180 and 1260 blank for distance. Either way, it will compute correctly. Then for each station where a distinct distance is given in the plans, a new station entry is made, such as at 1378.61 (30') and 1381.25 (28'). If the road transitions from 28' to 16' between stations 1381.25 and 1608.08, then all stations used for slope in that range can be left blank for distance. For station 1608.08, the distance of 16' needs to be entered, to complete the distance transition, and the slope at 1608.08 can be entered (since it is known) or left blank. Either way, it will calculate correctly, since the 4.7% slope is governed by stations 1540 and 1754. Similarly, for the final stations 1754 through 2066.86, the known distance of 16' can be entered or left blank.
At station 1500, the right-side SHR lane is both in slope and in distance transition. The program will calculate this and you can review the slopes by using the Stake Road command, as shown below:
By clicking on the SHR ID point, the program displays the computed offset (21.718) and the computed slope in (2.901%) and slope out (-4%, per the standard template). A similar page of values was entered for the SHL ID point, leading to the uniform superelevated slope left to right. With the Template Grade Table, applied to as many template ID points as needed, any complex road can be defined. When running Stake Road, Stake Slope or Elevation Difference by Roading Design Files and recalling a template file, you have the option to use a Template Grade Table for precise modeling of complex roads.
Contents Index
The Stake Slope command calculates and stakes out the location of the “catch point” where fill slopes or cut slopes contact the original ground. The command will also set offset stakes to the catch point and will produce a report of the slope stake information. The location of the slope stake is dependent on the position of the “pivot” point where the slope begins and on the slope itself (eg. 2:1, 3:1, 4:1, etc.). Slope stakes are typically used in highway work to locate the top of slope or top of cut. If design file information is available for the road template and profile, then the slope stake routine will calculate distance and offset information for all “break points” on the template from the slope stake itself back to the centerline. This also applies to slope staking conducted by section files, and descriptions associated with the break points on templates and/or sections are identified by name in the slope stake report.
Note: Slope Staking can be conducted within the Stake Slope command from the fixed "pivot point" of the template, the end-points of cross sections, or the centerline points of a horizontal and vertical alignment (as for a ditch). Slope staking, however, can also be conducted directly within the command Stake Road from any picked pivot point on the template or cross section. One of the advantages of the Stake Slope command is the ability to obtain catch point information "real-time" using the "non-interval" method of walking parallel to centerline. Stake Slope will also automatically detect the ditch pivot point in cut scenarios using templates defined by Carlson Civil and Carlson Roads. Plus Stake Slope knows which side of the centerline you are on and slopes stakes automatically to that side. The main advantage of Stake Road is the ability to slope stake from any picked point going either Left or Right as specified, for "staged" or partial roadwork design, or for finding catch points towards the interior of the template (eg. central median). Stake Road also has a cross section view option (within the Helmut Help). All slope staking is improved if the instruction to the user is In-Out from centerline and Forward-Back along the axis of the centerline. For this reason, it is best to set the View Point within FILE, Configure to In-Out and Left-Right, but also click on "Use Centerline for Reference Object".
There are “rules” for slope staking. The slope stake is measured from a pivot point, which is user-entered, or starts at the centerline itself in “point-defined” alignments, or starts at the last template point before the cut or fills when templates are involved, or starts at the left and right end-points of sections when using section files. Note that in the command Stake Road (which works with both sections and templates), slope staking can be initiated from any desired point. This allows for slope staking of interior, central median catch points and slope staking of any side of an eventual divided highway, being built in stages. Slope staking can be interval based, or accomplished based on where you are standing right now, independent of station interval.
Although office plans may predict the position of the catch points, slope staking is necessary to accurately determine the catch points based on actual field conditions. Slope stakes are often set at an offset to the actual catch points, since stakes at the precise top of slope or bottom of fill are likely to be knocked out by earthmoving activity. Furthermore, slope stakes are often marked with information on the slopes and distances in toward centerline or in toward the building pad or other feature. The information on the slope stake is often written in “progressive” form: distance and slope from offset stake to slope stake, distance and slope from slope stake to outside shoulder, distance and slope from outside shoulder to edge of pavement, on into centerline. Thus, the slope stake, placed safely beyond the area of construction, tells the story of the cuts and fills in toward centerline or toward the center of the work.
Catch points for both cut and fill are shown in the typical section graphics below. See these two figures.
Note in the “cut” example above (bottom figure) how the catch point may be closer or farther from the pivot point based on the slope of the original ground. With flat ground at virtually the same elevation as the centerline of the road, the catch is found approximately 15 feet from the pivot point in the base of the ditch. But with ground sloping slightly uphill, it takes a full 30 feet or so to find the catch point. The program helps find the catch quickly by modeling the surface of the ground with each shot taken. Thus, by projecting the ground slope outward, the program advises the user how far to go to find the anticipated catch point. Unless the ground slope changes dramatically, the catch point is usually staked within just a few tries. With GPS, the process is even more automatic, since the ground elevation is being computed continuously as you walk toward the catch point. No “shot” has to be taken until you are positioned right on the catch point itself. This next figure shows a cut condition slope stake in 3D. The “catch” is located at the top of the cut.
Four Methods of Slope Staking
- User-Defined: This is the most commonly used method of slope staking. Here, you simply enter the station, offset and elevation of the pivot point. Do not enter a minus sign for a left offset as in –25, since the program detects whether you are left or right of centerline. The only prerequisite is the selection of a centerline file. Cut and fill slopes are entered in the field.
- Point-Defined Alignments: This method is often used for staking the top of cut for a ditch, particularly a V-ditch. You can select the centerline by any of the three classic methods of centerline file, a picked polyline on the screen, or a sequence of points. The vertical alignment can be derived from any picked 3D polyline or from the elevations on the sequence of points, or you can separately enter a profile. This method is useful for slope staking existing flow lines, where you simply take two shots at either end, create an alignment by point number, then set the slope stakes at the user-entered slope ratio.
- Design Files: This is the most “formal” way of slope staking, but typically only applies to uniform, simple road, drainage ditch or levee projects where the pivot offset positions do not vary from station to station. While all methods require that a centerline be selected, the design file method additionally requires, at a minimum, a template file and a profile (vertical alignment). For more complex roads, superelevation files and template lane width transition files may also be entered. With the exception of the centerline, profiles and simple templates, the other files are usually created at the office using Carlson Civil, Carlson Roads or TakeOff, and then downloaded onto the field computer.
Note: Whenever the Road Design File option is selected, templates can be selected as a single “TPL” file, or as a series of templates organized as a “TSF” file (Template Series File). The TSF file can be entered within Road Utilities. If the left pavement lane of a road expanded from 10’ to 20’ for a passing lane, from station 1100 to 1200, you can create two templates, Road1 with the 10’ lane and Road2 with the 20’ lane. Then if you create the Template Series File shown below, the program will auto-calculate a 15’ left pavement width at station 1150. This same feature can be accomplished by using one template and applying a Template Transition File, which instructs on the changing dimensions of portions of a single template. Unlike the Template Series File, the alternate Template Transition File can only be created at the office using Carlson Civil, Carlson Roads or Carlson TakeOff.
One advantage of the design files method is that since each template point has an “ID”, the slope stake report will include information to locate all ID’d template points from the slope stake back in to the centerline. In this way, the entire road can be built from the information marked on the slope stake, which is placed outside the construction area at a user-specified (eg. 5’) offset to the actual catch point.
A report might appear as follows:
|
|
HDIST
|
VDIST
|
SLOPE
|
|
OFFSET to CATCH
|
5.02
|
-0.17
|
CUT 3.4%, 29.5:1
|
|
CATCH to PIVOT
|
32.20
|
16.10
|
FILL 50.0%, 2.0:1
|
|
PIVOT to SHLDR
|
14.00
|
33
|
FILL 16.7%, 6.0:1
|
|
SHLDR to EOP
|
12.00
|
0.48
|
FILL 4.0%, 25:1
|
|
EOP to CL
|
12.00
|
0.24
|
FILL 2.0%, 50:1
|
Within the program itself, the report might appear as shown here:
Progressive or Total: The above report is sometimes referred to as a “progressive” report, since it lists the incremental information from each break point to the next, going in toward the centerline. In some areas, the stake is referred to as a “story stake” or “progressive story stake”, because it tells the whole story of the gradework. The program is able to identify the names of the break points (eg. “SHLDR” and “EOP”) because the templates used by the program must have pre-defined IDs for all break points. Specifically with office-defined templates where cut conditions can have downslopes for ditches followed by upslopes, the program will auto-detect whether to pivot into fill or to create a cut condition, and pivot from the ditch line. You can also click the "Total" option and get offset distances to all break points as totals measured from the offset stake. In either case, the report is issued only if you stake the offset point to the catch.
- Section Files: Section files can be used to identify the pivot points left and right and minimize fieldwork. Consider the sections shown below.
Shown are stations 0+20 and 0+40, with the pivot points for slope staking identified on station 0+40. For the section approach to work, the left-most point in the cross section must be the left pivot, and similarly, the right-most point in the cross section must be the right pivot point. The section should only be entered from pivot left to pivot right (the “designed” catch points should be dropped). But since the interior section points have no bearing on the slope staking, they can be omitted, too. So in the case of station 0+40, a 2-point cross section could be entered, consisting of pivot left and pivot right. That 2-point section is also shown in the graphic above. It is just as effective for slope staking as a section containing all the break points between pivots. The one exception is if you have entered descriptions for your section points, you can obtain a progressive slope stake report, just as with the templates. Note that if descriptions do not exist, the report leaves them out. Section-based slope staking requires selection of a centerline file and field-entry of the cut and fill slopes.
Section-based slope staking is useful when the pivot points for stakeout vary unpredictably and don’t conform to a fixed template. Section-based slope staking has 2 advantages. First, all sections can be entered in the office as 2-point sections (left and right pivot), minimizing field paperwork and reference material. Secondly, odd stations can be staked out (eg. station 0+27.5), since the pivot points can be straight-line interpolated by the program.
Note: Section files can be used for slope staking within the command Stake Road. In this routine, you can choose sections or templates to stake, and you can pick any point to slope stake from—so any point on the section can become the pivot point. The advantage of slope staking by section file within Stake Road is that you can pick any point (greater flexibility). The advantage of slope staking by section file within the Stake Slope routine is that it automatically uses the left and right end points of the section as pivot points, which means less screen picks are involved (greater speed).
Section files may be entered in Road Utilities, or in an external program such as Carlson Civil, Roads or TakeOff.
Choosing the Slope Staking Method
When Slope Staking is selected, you are presented with a Definition Method screen, where you choose among the 4 methods of Slope Staking: User-Defined, Point-Defined Alignments, Design Files or Section Files. The application of these methods is discussed above.
- Stake Station Interval: When clicked on, your slope stake target is always a fixed point. It is the slope stake at the specified station in the input dialog in all 4 methods. But if clicked off, the slope stake target point moves forward/back station as you move. In User-Defined, the pivot offset and elevation is used regardless of station position. In the other methods, the pivot elevation is recalculated dynamically as you move based on the known information (3D points, profile, sections).
- Round Station: This option applies only if you turn off “Stake Station Interval” and move to “fluid” slope staking. If you “round” to an interval, such as 5, then the elevation to stake from is calculated to the rounded station value, as is the up-down station position for the offset. Rounding only applies to the stored report—the target still moves fluidly as you walk forward or back parallel to the alignment.
- Load Road Net File/Select Road Element: Carlson Civil 2008 and Carlson Roads 2008 have the option to output an "RNF" file, or "Road Net File", from the RoadNet feature. This file contains every centerline, cul-de-sac and road intersection "curve return" treatment for an entire road network. For example, a complete subdivision road system can be output as a single RNF file, and then SurvCE can stakeout any element of the RoadNet file that is loaded. Since the RNF file contains both templates and final sections, the Load RoadNet File option is accessible when slope staking by Design Files and Section Files. If you select, "Load RoadNet File", it merely loads the files, announces "Process Done" and all road files are placed into a temporary directory. You then need to click "Select RoadNet Element" to choose the element of interest. The three choices are centerlines, cul-de-sacs and the curve returns at intersections. For centerlines, the Center ID of the design template (if that method is used) is applied to the horizontal alignment. Keep in mind that for cul-de-sacs and curve-returns, the position of the horizontal alignment is set in RoadNet within Carlson Civil and Carlson Roads, and typically is set to the edge-of-pavement alignment position. Slope staking will therefore use just the outer part of the template, for example, from EP ID outward, to find that pivot point. If you re-load the same RoadNet File, the program warns you that the prior temprorary files will be erased and new ones created. This is done in case you actually modified a profile or other files in the temporary files, in which case you should use SaveAs in the appropriate command to preserve the changes in a new file name. When you Select RoadNet Element after loading an "RNF" file, you can highlight any element to stake, which then appear "dashed" when highlighted:
When you click out of the opening dialog that offers the 4 methods of Slope Staking, you obtain additional input screens.
- User-Entered Dialog: If the User-Entered method is selected, you are first prompted for a centerline, and a dialog appears.
At each station, you can enter a specific pivot offset, pivot elevation and the cut and fill slope ratio that governs. Slope ratios can be entered as percent as well, is "Display As Ratio" is clicked off. Pivot offsets should be entered as positive numbers even left of centerline, since the program will detect which side of centerline you are on from the first total station or GPS reading. The program will take the absolute value of the pivot offset entry, in any case. You can obtain the position to stake from “Read Instrument”, which calculates the station, offset and pivot elevation from a measured position. Or you can enter a point number to obtain a station, offset and pivot elevation.
- Point-Defined Alignment Dialog: The selection of the Point-Defined method leads to the classic alignment selection screen, familiar to users of Offset Stakeout and Stake Centerline.
Though this is the classic use of the Point-Defined option (using points), slope staking can be conducted from a single centerline and single profile or from a picked 3D polyline. Points can be selected by number or picked directly off the screen.
When a new horizontal alignment is selected by 3D polyline or point method, the program will ask if you wish to overwrite any existing vertical alignment selection. The typical answer is yes—you want it for both, and you are ready to stake any station at any interval based on user-entered slopes. Think of points 6 to 7 as the flow line of a ditch with steep side slopes, and the goal is to lay the slopes back at 2:1—a perfect application for Point-Defined Slope Staking.
- Design File Dialog: If you select Design Files, a dialog appears.
Centerlines, profiles and templates can be made using SurvCE. In fact, centerlines and profiles can be imported from a variety of file formats using the commands within Road Utilities. Note that templates can be either single template “.tpl” files or multiple templates with transitions in a Template Series “.tsf” file. If the roads have superelevation, the “super” files can be made in Road Utilities. If template transition files are to be used for lane changes, then this file type must be made using external software such as Carlson Civil or Carlson Roads. Note that “sets” of Roading Files can be saved and loaded using the buttons at the bottom of the screen. The Settings icon at the top of the screen, to the left of the checkmark, allows you to place the profile grade at an offset to centerline, such as at the inside edge-of-pavement for divided highways, as shown below:
- Section File Dialog: If Section Files are selected, a dialog appears.
The Section file (which has an “sct” file extension) can be entered in Road Utilities or imported from the LandXML format using Section File Conversion, also in Road Utilities. Note that for all roading design files, there is no requirement that starting and ending stations (chainage) match. All that is necessary is that they have a station range in common (in the above case, 10+00 through 20+00 is common to all files). Roading File sets (as in the above Boneta files) can also be saved to a named set and then re-loaded later for convenience. With cross sections, the profile is not required, but including the profile will lead to more accurate slope staking between known cross sections, such as at high and low points in the road.
Setting the Station and Interval for Stakeout
The next screen sets the station to stakeout and the interval and will appear in some form in all cases except section and design files slope staking with interval turned off. In effect, there are 8 ways of going into Slope Staking: 4 methods times 2 interval options (on=fixed station/off=fluid, real-time). You also have 3 more methods if you include the Stake Road routine which offers Slope Staking by Section, Template or Sections Cut from DTM, all fixed station.
The station to stake can also be read from the GPS or total station measurement, allowing you to slope stake "where you are". You can also get the station by entering a point number, in which case it projects the point onto the centerline to determine the station. In the non-interval method, the above screen does not appear. You slope stake wherever you are all the time, and are freed of the constraints of staking a specified station.
The User-Defined and Point-Defined Alignment methods have their own pair of “follow-up” screens for the location to stake.
For flow line or V-ditch staking, a 0 pivot offset would be entered from the point-defined alignment. If the ditch were a trapezoidal ditch with a 2 meter bottom width, and the alignment was the centerline, each side of the ditch could be slope staked using a pivot offset of 1 (1/2 of the ditch width from center to pivot point).
Both the Road Design Files and Section Files methods go straight to the navigation (stakeout) screens if no interval is selected (Stake Station Interval turned off). The pivot offset is built into these methods based on the “rules” outlined earlier -- you stake from the pivot to cut or fill in templates, and from the extreme left and right points of cross sections. With interval turned off, slope staking by "User-Entered" method simply asks for the pivot offset and elevation at the current location, and slope staking by point-defined alignment asks only for pivot offset, obtaining the elevation from the vertical alignment.
Slope staking cannot occur outside the station range of the horizontal alignment. If your horizontal alignment runs from station 0 to 308, you can’t stake station -10, either by interval method (naming the station) or by the non-interval, fluid “where-you-are” method.
In live stakeout mode, you will get “Off Centerline” when beyond the range of the horizontal alignment.
All paths lead on to the navigation or stakeout (some call it “set out”) screen.
The Navigation (Stakeout) Screen
When configured for GPS, the navigation screen then appears.
Note that because the GPS reads continuously and models the ground surface, the program calculates immediately where the catch point (the circle with the X) is located. You simply walk right to it. If the ground goes uphill or downhill as you approach the point, then the X will move closer or move away, until you are right on it.
As you get closer to the point (within the stake tolerance distance) the program will present a bullseye screen.
When you are satisfied with the accuracy of the slope stake position, you then touch S for Store (or press Enter to take the shot). In this case, its time to drive the stake.
Interval and Non-Interval Methods Impact Stakeout Screen
The stakeout screens above are for the interval method. In the non-interval, “fluid” slope staking, where you can drive the stake anywhere, the “Forward-Back” portion of the screen becomes vertical “Current Fill” or "Current Cut". In this fluid stake-out mode, you simply move in or out from the centerline to set the slope stake—there is no correct or incorrect forward or back station. So the program instead reports the vertical up to the fill slope above you or down to the cut below you.
If you are moving out to the catch point along the ground, you would get a report of “CrtF 1.25” or some such number, and the “Current Fill” amount to the ground would decrease as you approach the catch. The actual stakeout screen would appear as shown below. Note that some surveyors will watch the lower line (1.6:1 for 3.65) and just keep moving out until they see 2:1 (or the desired slope) and drive the stake. Others will watch the “CrtF” value decrease to 0 and drive the stake, or watch “OUT” decrease to 0.
Storing the Slope Stake and Offset Stake Points
When S for Store is pressed, you may store the actual slope stake point. You can also store a first offset point (since the slope stake itself can be removed by construction). The slope stake information is typically written on the first offset stake. Then you can also stake a second offset point, to obtain “line” to reset the slope stake if it is knocked out. The first and second offset stakes provide a direction back to the slope stake. When the slope stake is set, the program prompts for setting the first offset stake. When the first offset stake is set, the program prompts for setting the second offset stake. Both offset stakes are optional.
The storage of the slope stake points is an option turned on by clicking “Store Point to CRD File”. With this clicked off, you can simply slope stake and avoid storing any points. The Description for the point will default to the station and offset. Slope Staking will not respond to settings in Configure Reading for the Height/Description prompt screen. If you are using a named “Slope Stake File” (set in File, Job Settings, Stake tab, Cutsheets option), you can still control at the point of staking whether you choose to append data to the file by clicking on or off “Store Data to Report File”.
Note that there are two options for the slope stake report: Elevation and Offset. The standard option is the Elevation method. This assumes you were able to survey the actual slope stake point with reasonable accuracy, and it reports the actual stake to pivot point results. If you were staking a 2:1 cut slope, it reports your actual slope (as 1.997:1 in this case), and you can choose to round the result and write "Cut 2:1, 9.25 V, 18.48 H" on the stake. But if at the catch point there are boulders in the way, you can walk out and away from centerline in cut and in toward centerline in fill, and drive the stake where you can. In this case, you would choose the Offset method. In the Offset example above, we had to walk past the catch point about 2 units (from 36.50 to 38.56). We drive the stake, and note that the catch is at 956.03 rather than 955.01, so we measure up 1.02 on the stake, and draw a horizontal line there as the catch point. An extra line appears in the report that tells us to write "Cut 2:1, 10.28 V, 20.56 H" on the stake. In cases of fill where there are obstructions, walk into centerline so when you drive the stake, you can mark where the fill intersects the stake. Note that this same level of reporting occurs with "non-interval" staking, where you get real-time cut and fill at any point, also allowing you to drive the stake to avoid obstructions.
When Enter or OK is pressed, you are prompted for whether to stake the first offset stake.
If you are doing “User-Defined” or “Point-Defined Alignment” methods, you are shown the horizontal distance and vertical fill or cut difference to the pivot point, which can be written on the Slope Stake. Additional break-point information appears if you are using the “Design File” or “Section File” method. If you trust that the Slope Stake will not be knocked out, then you are done—no need to set an offset stake.
Pressing OK leads to the prompt to set the first offset stake. If you choose to set the first offset stake, then you can set the offset distance.
Press OK and then you are in a standard stakeout screen. The offset point is a fixed location and the stakeout procedure is similar to point stakeout. This leads to a report of information that can be written on the Slope Stake. Finally, you will be prompted for staking out a second Slope Stake, to establish “line.” After the first offset stake is set, and before the prompt for the optional second offset stake, a summary screen will appear. If you have used the Road Design File or Section File methods, you will be presented with every break point into centerline.
Finally, you will be prompted for staking out a second Slope Stake, a more rarely used option whose purpose is to establish “line” (the direction) from the first offset stake to the slope stake itself. This permits accurate replacement of the slope stake when it is knocked out by construction activity.
Note: When using Road Design or Section Files in Slope Staking, setting the first offset point is the recommended procedure, as it produces the full report, referenced to cross section and template IDs, for all break points all the way into the centerline point.
Procedure for Slope Staking with Total Stations
The procedure is nearly identical for Total Stations, except that you must press R for Read (or Enter) to take shots and allow the program to begin calculating the Slope Stake position. Unlike the GPS, SurvCE cannot predict the location of the target slope stake point until at least one measurement is taken.
Note: When using either GPS or total stations for slope staking, you can obtain more graphics and less screen information by pressing the down arrow key. It literally has the effect of bringing the graphic screen down (see below). Pressing the up arrow key will pull the screen back up and show the full text. This works in all modes except GPS Simulation, where the up arrow moves the cursor faster, down arrow slower.
The Slope Stake Report and Writing on the Slope Stake
Surveyors doing slope staking have the option to write the information on the stake as each is surveyed, or to come back at a later time, refer to the slope stake report, and write on all the stakes after the surveying is complete. The slope stake report file is a comma-separated “.txt” file, configured in Job Settings, Stake, Cutsheets, which might appear as follows if formatted in Excel or another spreadsheet form:
|
#Des Sta
|
Des Off
|
Des Elv
|
Staked Sta
|
Staked Off
|
Staked Elv
|
Desc
|
|
1+00.000
|
L33.849
|
998.075
|
0+99.966
|
L33.453
|
998.075
|
Catch Point
|
|
1+00.000
|
L38.849
|
------
|
1+00.019
|
L38.866
|
998.15
|
First Offset Point
|
Here is another example as viewed in the Edit mode within Job Settings, Stake, Cutsheets, Edit Slope Stake.
The columns are configurable with the Slope Stake formatting in Job Settings. Shown above is a "total" report (as opposed to "progressive"). No offset stake was set. The template involved was flat from centerline for 12', then had a 2:1 slope for 6' into a ditch point (ID="BD" for "base of ditch). This cut downslope condition was created within an office-entered template using Carlson Civil or Carlson Roads, and SurvCE automatically detected the cut condition and used the ditch points as pivot points, offset 18 with elevations 945.75 at station 6+00 and 946.50 at station 6+50. Some survey teams use one person to set the slope stakes and another to enter data on the stakes, which is easily done using the stored slope stake report above.
Contents Index
This function collects as-built cross sections of roads or other alignments and stores them optionally as points, as cross sections or as an ASCII file organized by station. The station and offset can be stored into the description field of the points. The station itself can be set to automatically round to the nearest 5, 10 or other station interval (eg. a shot at 177+98.23 would round to 180+00 if a rounding of 5 or 10 is used). The information can be stored into a “.txt” ASCII file in addition to the points themselves, if "Store Comma Separated File" is turned on, and if point storage is turned on, you can save a ".not" file of the station and offset. You can save the cross section data to a cross section file in .SCT or RAW/Geodimeter format. Store Sections can also be used simply to verify your current station and offset as you move along a centerline using GPS or taking total station shots.
This routine is often combined with office software to check as-built road cross sections against desired grade and to calculate quantities for payment. The field crew begins by taking shots along each desired cross section, as shown in this figure.
If, for example, four sets of cross sections were taken from station 0+75 to 1+50, the points would appear as shown in the plan view below, and the 3D view shown below that. There is an option to turn off point number storing, in which case the shots can still be stored to a cross section (.sct) file and report file (.txt).
Here, below, we see the 3D view of this area.
The command begins with a screen where you select the method for defining a centerline.
The next screen allows you to choose whether or not to store a file summarizing cross section data. Because the SCT method requires that you choose an alignment, the option for no alignment (“None”) only applies to the Raw/Geodimeter method, in which case a named file is required. Except for this case of option “None”, the Section output file is optional because the information will be stored with the points. When you click Select File, you have two file type options when using a horizontal alignment.
The Raw file format is a design that is compatible with the old Geodimeter section file format, and includes special prompting for job type. It is discussed in detail below (see the discussion of “None” as centerline option). It leads to a different set of screen options than the SCT format.
Unless you are looking for Geodimeter file format compatibility, you should consider storing a section output file in the “.SCT” format, since it can be converted, using Road Utilities, to LandXML form and then imported to several different roading software packages for plotting and computation of volumes. The “.SCT” section files can also be used directly for volume calculations with Carlson Roads, Leica Site Manager, Topcon Topsite and Carlson Civil. You can also set the rounding—here, a rounding of 10 units (feet or meters) has been selected. The station and offset can also be stored as the point description and as a note file, if the lower options are clicked on.
Note that the rounding is fully automatic. If you choose a 5-unit rounding, and are targeting station 0+75, but take a shot at 0+77.93, it will round up to 0+80.
Before collecting the cross sections, it is important to click X-SCT Settings near the top of the dialog, and set the stations you wish to capture. This way, if the station rounds, per the above screen, to a station that doesn’t exist in your list, you are warned before proceeding with storing. This list also includes the left and right “tolerances” for the offsets, which will lead to warnings if you exceed that distance from centerline. If you set a tighter “Station Tolerance” in X-SCT Settings (option Edit) than the “Rounding” Tolerance, you will be warned even though the rounding is correct. In the screen shown below, station 16+70.000 has been added as a special station. Clicking the first line (10+00.000-23+00.000) allows you to set the standard interval, and the additional stations in the list would be for special stations in addition to the standard interval.
The below, smaller dialog appears when you tap Add Odd Stations, shown in the above figure.
With the first line highlighted, selecting Edit leads to the settings options for the full range of stations.
With an interval set of 50, and Start/End Stations turned on, the program will only expect you to capture stations at 50 units intervals starting at 10+00 through to 23+00, but also including 10+11.57 and 16+70 in this case. The Offset from alignment to X-Section option lets you, in effect, use an alternate, parallel centerline at a left (negative) or right offset from the main centerline. Unless the Raw/Geodimeter method is used, a station “warning” screen is used if the rounded station is not in the list or pre-selected stations. A capture of station 1075 would round to 1080, but since 1080 is not in “the list”, you will be warned before storing. A station of 1667 would round to 1670, which is in the list, leading to no warning screen. Since the rounding was set to 10 in this example, data collected at 45 to 55 would round to 50 (station 1053 would not round up to 1055), and therefore only “even 10” stations will be collected to begin with. So the additional “Station Tolerance”, which rounds the collected station data to the listed stations, will not activate.
When OK (green check mark) is clicked from the Store Sections dialog, the program immediately proceeds to a point collection mode, with continuous presentation of station and offset (if running GPS or robotic total stations).
- Storing Points using GPS: There are two methods for storing points in real-time GPS mode: Press the S icon at right (or pick Alt S) or simply press Enter. The “binoculars” icon will bring up the Monitor/Skyplot dialog. You can survey as many cross sections as desired within the command. Unlike in Slope Staking, Store Sections will respond to the setting for Hgt/Description prompt on save, found in Configure Reading, allowing you to arrow key to desired descriptions or change your rod height after taking the shot. Option C goes to the Configure Reading directly from the data gathering screen. When done, simply select the Menu button, and you are returned to the Road menu. When exiting by pressing Menu, if you have opted to store to an SCT file, you will be prompted to store the cross section information in SCT form.
- Storing Points using Total Stations: After confirming the occupied station and backsight, as with all total station work, proceed through the same options above until you reach the store point dialog. In the example below, our centerline is metric, starting at station 0+000.
Here, your options are R for read, followed by S for Store, or simply Enter to Read and Store. The backsight icon can be pressed to set a new occupied point or backsight point. Note that we have a very “busy” screen of points. If you just want to see your setup, backsight and last point that was measured, press Alt F. This produces the screen below. You will stay in this mode until you press Alt F again and toggle back to the presentation of all points.
If a shot is taken that doesn’t round to a station in the list of “approved” cross section stations (X-SCT Settings), then a warning screen appears. In the warning dialog shown below, the tolerance has been exceeded on two accounts. We round to 0+80, which is not in the list, and our offset is 186.891 left, which exceeds our anticipated maximum offsets of 100 left and right.
Points Store with Station/Offset Descriptions, as shown below:
|
29
|
0+125
|
L23.58
|
|
30
|
0+150
|
L33.24
|
|
31
|
0+150
|
L19.39
|
|
32
|
0+150
|
R1.98
|
|
33
|
0+150
|
R18.12
|
The comma-separated file would appear as follows if presented in a tab-delimited form:
|
#Point ID
|
Station
|
Offset
|
Elevation
|
Description
|
|
29
|
0+125
|
Left 23.5759
|
991.2901
|
0+125 L23.58
|
|
30
|
0+150
|
Left 33.2363
|
989.9193
|
0+150 L33.24
|
|
31
|
0+150
|
Left 19.3923
|
996.8921
|
0+150 L19.39
|
|
32
|
0+150
|
Right 1.9816
|
998.2340
|
0+150 R1.98
|
|
33
|
0+150
|
Right 18.1201
|
997.0731
|
0+150 R18.12
|
When you exit the routine by clicking Menu from the data gathering screen, and have Store SCT file turned on, you will be asked if you want to “process” or add the last shots you collected to the named SCT file. You have the choice to “Process” (use the data) or “Discard”.
The program will even keep the section data “on file”, so that if you Cancel the above screen, and re-enter Store Sections, you will be prompted again whether to save (process) or discard the cross section data collected earlier.
Options When Storing in Raw/Geodimeter Format
Different options present themselves when the Raw/Geodimeter Format, or File Type, is chosen.
When Raw/Geodimeter is selected, a distinct set of screens are obtained. This particular format was adapted for highway departments and survey companies that had built cross sectioning practices around the Geodimeter format. This method requires that you enter the station (chainage) being surveyed, and only uses the centerline position to advise you on your station and offset. A horizontal alignment is not required. The program detects the selection of this format, and before proceeding, opens with a starting screen where job-based information is entered.
There are pre-set job categories and tasks, which save into defined number categories in the old Geodimeter raw file format. Whereas the SCT method recognizes the station you are on and automatically rounds to it when you are within tolerance, the Raw/Geodimeter method requires that you click the Station button, and set your target station for collection of cross section data.
Then you proceed from the current location to the target station. In fact, although the points that are stored may contain station and offset descriptions, the data stored to the raw file pays no attention to the centerline information. The station and offset on the screen act only as a check on your current location. The direction of taking the sections, (L to R or R to L), is important and is set by specifying “Chainage Direction”. Unlike with the SCT format method, pressing Menu to exit does not store the data, but instead the data is automatically stored as you go, as a series of 37 (N), 38 (E) and 39 (Z) record types (Geodimeter format), with header line records, as shown below:
50=XSEC1
54=104 North
0=As-Builts 240-300
53=VF
90=2
97=0
51=3-28-2004
56=65.0
74=30.10
55=3
96=2
6=2.100
80=280.000
91=1
37=5105.857
38=5069.091
39=991.905
37=5104.091
38=5074.931
39=990.724
Starting left to right, the data points begin with a 91=1 record. A right to left section would begin with 91=2. When you “cross 0” or are on the centerline or baseline, you click the CL/BL button which sets a 92=1 record for centerline and 92=2 for baseline, and the next shot is the centerline/baseline shot. If you select the “-0.00” button, this indicates whether the next shot is a tie-in (catch) or extension beyond the tie-in. This sets a 93=1 record for the catch and 93=2 for the extension prior to the subsequent coordinate record. In effect, you tell the program where the centerline or baseline is by shooting that point. Then the station and offsets of the shots for that cross section are determined relative to that center-of-alignment shot. It does not use a horizontal alignment combined with rounding to determine the station and offset of the shots (like the SCT method does). You tell it the station, the direction of measurement (left to right or vice versa) and you tell it which one is the center shot. This is why the Raw/Geodimeter method is the only method that works with no centerline (the “None” option). For each section, you tell it the station and center shot, and all other measurements are used to determine the left and right offsets relative to the center shot. If the L to R method was used, shots before the center shot are on the left, for example, and their offset is determined by the inversed distance to the center shot. The centerline file or other form of horizontal alignment, if selected, is academic and only used to advise you on your current station and offset. The CHK button will allow checking into known points to be sure that tight coordinate control is maintained. N moves onto the next station as defined by the interval set using the Sta button.
Note: The .SCT file method is the standard Store Sections method. The RAW/Geodimeter method is a flexible routine designed to adapt to customers who have built their cross section processing systems around the Geodimeter raw file format.
Contents Index
Stake Road is one of four major commands used in highway work. This command is designed to stakeout specific stations and offsets along a centerline. For example, if your goal is to stakeout the break points at station 87+80 on a given road centerline, you would use Stake Road. Stake Road, therefore, is used primarily to lay out road surfaces for construction. Stake Road is typically used to set cut and fill stakes or “blue tops” at specific stations and offsets. The elevation used to determine the cut or fill at each offset is derived from either design files (the template interacting with the profile and centerline) or from cross sections or from sections that are “cut” from alignments. At any specific station, you will be guided to the desired offset and will get a cut or fill. By contrast, if the goal were to simply set random cut and fill stakes along an alignment, at no particular station or offset, then the command Elevation Difference would be used. If the goal is to stake out the “catch” in cut and fill, where cut slopes and fill slopes meet existing ground, then Stake Slope would be used. However, you can also Slope Stake within Stake Road. The fourth, major highway-oriented feature is Store Sections, which is used to gather “as-built” information on a road. In this command, you take cross sections of data points along the road, at random or specific stations. In summary, Stake Slope starts the cut and fill work, Stake Road directs the precise roadbed work and fine grading, Elevation Difference acts as a quick grade check, and Store Sections produces the final confirmation of the as-built road for payment and certification. It is highly recommended for all road stakeout that you set on "Use CL for Reference Object" within Configure, View Point tab.
Defining the Road
The first dialog that comes up when you select Stake Road is where you define the road by selecting one of the following options.
- Design Files: In Carlson SurvCE, design files include templates, centerline, profile and optionally, superelevation and template transition files. If you wish to “clear” a file such as a superelevation file, just click it and choose Cancel. The definitions for each of these files is covered in their own sections of this manual. Design files are recommended for subdivision streets, access roads and simpler highway designs.
- Section Files: Sections are made up of simple offsets and elevations that can have descriptions such as “EOP”, “DL” or “SH” and must be accompanied by a horizontal alignment file (centerline). Every cross section is a “snapshot” of the template at a given station. SurvCE supports using multiple surfaces simultaneously in Stake Road by using multiple section files or by extracting the section for each surface when all surfaces are within a single file. Each surface can exist on its own layer with its own color for easy identification while in the Stake Road dialog. For complex designs, with non-conforming intersections, transition lanes, special ditches, etc., it is recommended to use cross section data if available.
- Cut Section from Alignments: Provides the ability to extract cross sections directly from 3D polylines that exist within SurvCE. The first thing you need to define is the horizontal and vertical alignment files. These form the basis for cutting the sections and determining left and right offsets from the horizontal alignment or centerline. The centerline-defining screen is similar to the screens found in Stakeout Line and other commands.
This just starts the process. With both horizontal and vertical alignments defined, click OK. You will then be asked to define a template point alignment (TPA) file. In this process, you must either pick or identify by point number or file each alignment “pair” (H and V) that define an edge-of-pavement or other feature of the sections. It takes a 3D polyline, or a pair of horizontal and vertical files, or any mixture of points, polylines and files, to define a single offset feature.
Click on Left Surface, for example, then Click Add. This brings up the same screen used to define the centerline. If you have a drawing of 3D polylines (brought in as a DXF file, for example), it is very easy to illustrate this command by the Pick Polyline option. When chosen, you obtain the next screen, where you can pick the EP.
Now click OK, say Yes to Overwrite vertical alignment (if the polyline is 3D), and simply OK the screen (no need to save the file as a named alignment). This brings up the name template ID dialog.
Repeat for the outer polyline (SH, left side), then for the EP on the right side and SH on the right side. You now have a centerline and 4 offset alignments from which to cut sections. When you get the full contingent of alignments defined, click Save As to save the TPA file. Now any design offset at any station will be automatically interpolated, and normal template/section stakeout can proceed.
- Save Roading Files: This button will save the selected set of roading files as an RDF file for recalling later.
- Load Roading Files: This button loads all of the files previously saved to an RDF file. The files must still be present in the original locations.
Interpolation
If descriptions are provided, “intelligent” interpolation is performed between similar descriptions on slope transitions or widening lanes as well as vertical curves for all methods described above.
Stake Road
The next screen is the heart of the program. Here is where you select the station and offset to stake out. You can even launch into a slope stake and then return to stake out other template points.
- Settings: The “Additional Stake Stations” that appear in the List are set in the lower portion of the dialog. The Vertical Scale option will allow for “exaggeration” of the vertical on the template graphic. Though defaulting to 1, we can double the exaggeration by setting this to 2. In fact, an exaggeration of 5 works fine for the “demo.tpl” template file. The “Next Station Method” governs how “N” for next, from the stakeout graphic screen, moves you up. When set to “None”, N for Next will stay put until you change your entries. But if set to “Next Offset (Left to Right)”, Next will stay on the current station and move to the next offset. The “Next” in the dialog below, however, always increments the current station by the next station in the List. Don’t confuse the Next button on this screen, with the N button on the graphic screen to follow, which is influenced by “Settings”, and moves you along after you complete each point stakeout.
- Station: The value of the Station to Stake.
- Interval: The horizontal distance to increment the stationing when using the Next and Previous buttons.
- Play/Pause: This button allows the user to play through the road file like watching a drive-through movie.
- List: Depending on the settings and specified interval, “List” will list the defined stations including intervals and critical stations.
- List Offsets: This dialog allows the user to pick from the known offsets by a list rather than using the graphic screen below. It also allows the user to select an optional second point of "Reference" for reporting cut/fill information while staking. So you could stake the shoulder but also reference cut and fill to the centerline, as an option.With this option, the selected offset and the secondary reference offset will both be reported to.
The resulting plan view in stakeout shows cut and fill to both the reference and the target point.
- Design Offset: Any offset can be entered, even if it is not a “break point” on the template. For example, an offset of Left 5 (-5) or Right 7.23 could be entered. For every design offset point selected, the elevation is calculated and presented. You can select the offset point from the offset list or literally pick it on the screen. The touchscreen is active in the graphic, so you can select the -12 (EP) just by picking it. Picking on the graphic screen will take you to the “Offset List” screen for verification, where you can confirm your pick by pressing Enter or selecting another offset.
- Stk Off(H): Horizontal offset from the design offset. If you enter an stake offset of 2 and the design offset point was at 12, then the stake would go in at offset 14 off of CL, but the cut/fill would refer to the elevation at the design offset location of 12. The stake offset and Off. to CL inter-react. A stake offset entry of 15 with a design offset of 12 left calculates to a setback of 3. If you click the "Stake Off" button, you can choose from a variety of methods to create an offset point, including extend current slope, apply next slope, vertical offset, or user-defined slope.
Your offset is then computed and shown graphically:
Note that you can zoom and pan in the dialog above. Pan using your finger or stylus.
- Stake Off Button: This button allows the user to specify the horizontal and vertical offsets relative to the design offset. Various methods can be used for computing the offsets based on the template or section points and their elevations.
- Off to CL: This is the total distance that the stakeout position is from the defined road centerline.
- Vert. Off (V): Vertical offset from the design elevation.
- Elevation: Elevation to be staked. This value is based on the combined design elevation and vertical offset.
- Run Slope Stake: This feature allows for dynamic slope staking in the middle of the Stake Road routine. This option is very useful for road staging, and also for staking interior catch points like central median ditches. When the slope stake is completed, the program returns to the main Stake Road dialog. Any point in the template or section can be used for running in a slope stake. You are asked to specify the desired cut-and-fill slope ratios. The slope can be auto-defined or user defined as follows:
Define Slope by Next Section Point: This option allows you to select the edge of the road and use the proposed design catch point for auto-determining the slope rate.
Define Slope by Previous Section Point: This option allows you to select the proposed design catch point and then use the next point toward CL for auto-determining the slope rate.
Extend Current Slope: This option will allow you to pick the edge of the road or catch point and use the next point toward CL to end the slope between then away from CL.
User Defined Slope: Allows you to enter the slope ratio by hand for on-the-fly slope changes.
Slopes by Template: This option extracts the slope definitions from the template file itself.
If you click Slope Stake, you can stake by the template slope for the ditch shown on the left side, or you can enter a user-defined slope to override what is in the template.
- Pivot Point: This option allows the user to perform on-the-fly offsets relative to the stakeout position.
Stakeout Views
Stake Road now allows you to navigate to the point in either plan view or cross section view. Select the helmet icon and choose Section to see a section view and choose Plan to return to plan view.
Cutsheets
Stake Road will produce Alignment-style cutsheets that include the option to report station and offset as well as the cut and fill to any point. These are fully described in Stake Line/Arc, Elevation Difference and in Job Settings, Stake Tab. If using Slope Stake within Stake Road, a slope stake report, including "progressive" and "total" distances to all template or section points, can be output.
Contents Index
This chapter describes the use of the MAP screen. The MAP screen commands are available in the pull down menus or at the command prompt. The MAP screen is useful for drawing, COGO, creating points for stakeout, and for the import and export of DXF and shape files. No measurements are taken from the MAP screen.
Contents Index
The MAP screen is accessed by tapping the globe icon in the upper right of the main menu, or by selecting MAP from the Helmet pulldown options. The basic operations of the MAP screen are described here.
Map View Icons
The commands associated with the MAP View Icons are described in the figure below:
Executing commands in Carlson MAP
The MAP screen defaults to a pull down menu format containing approximately 80 additional commands, virtually doubling the number of commands found in the Menu Screens. Many of the commands in MAP offer CAD-like features such as layer freeze and thaw, predetermined area, polyline offsets and even contouring. One of the most important commands is Polyline to Points, which allows you to create points for stakeout (set out) from any selected polyline. The MAP screen also includes a command line format that can be set using Preferences. Several MAP screen pull down menu commands involve “fly out” options, as shown below.
Alternatively, you can enter the command name, or command alias, at the command prompt and press ENTER. In many cases, the user can start a command while using another command. The newly started command is called a "transparent" command. Each command from the left-toolbar menu is a "transparent" command.
Usually, a command does not immediately execute. Carlson MAP either displays a dialog box or displays prompts at the command line requesting more information from the user. Typically, the user can select objects on the screen or enter data on the command line. Many commands consist of a series of options, structured as follows:
Cmd:Command name-Option1/oPtion2/opTion3/.../<default option>
To select one of the options, the user can enter the entire option name or only the capitalized letters, and then press ENTER. If available, the default option always appears in angle brackets (<>). To select the default option, just press ENTER. If no command is active, the user can repeat the previous command by pressing ENTER.
Panning the Screen
The user can move the drawing display (PAN) anytime. To use this command, the user must hold down and slide a finger — or the proper pointing device — on the screen. The drawing display is moved in the same direction as the pointing device. When you release the pointing device, the panning stops. Only the display moves and all objects retain their correct coordinates. Be careful to start the pan by picking in “empty” space. If you hold down on a point, you may obtain the “Point Details” screen, or you may see a list of points to select from (to see Point Details). If you hold down on a line, you may see the "Line Details" screen.
Point Details
Unless you are in the middle of a MAP screen command, you can click on a point and see a Point Details dialog. If you tap near several points, a list of nearby points will appear from which you can select the target point. Otherwise, you will go straight to Point Details, and see a screen that includes the option to delete or edit the point.
If you are in total station mode, and actively surveying (with a setup and backsight specified), clicking on the setup or backsight point will lead to a special graphic, as shown here:
If you have assigned attributes to the points (e.g. Description Pole, Type-Metal, Wires-4, etc.) by use of the Feature Code capabilities, these attributes can be reviewed. The Point Details option works both within the MAP screen (when you are not being prompted for entering points or selecting objects) and in all graphic screens within the Menu options. It is not as transparent and available as the dynamic pan option, but nearly so.
Unless you are in the middle of a Map screen command, you can also click on a line and see Line Details. Clicking the line at the lower edge of the drawing (a blue ditch line) leads to a simple Line Details display:
You have the option to delete the line or change its layer. If the polyline (a line with 2 or more vertices) has different elevations on some of the vertices, then it is designated a "3D Polyline". A more advanced Line Details is provided when using Feature Codes within the Store Points command, allowing extension of lines and new lines from vertices on the polyline. The advanced Line Details is discussed under File, Feature Code List.
Contents Index
DXF File - Import DXF (IDXF)
Similar to the AutoCAD(r) DXFIN command, will bring in polylines from AutoCAD, Microstation, Terramodel and other products that can export data into a DXF file format. Points, text and blocks such as symbols are not imported. However, many software packages such as Carlson Survey and Carlson Civil allow text to be converted into polylines – in which case the text will import for reference.
DXF File - Export DXF (EDXF):
The EDXF command is useful for exporting files to Microstation, Autocad, Intellicad, ESRI and virtually all other CAD drafting programs. It provides controls for displaying points and also for displaying GIS attributes associated with points and linework.
The EDXF command, similar to the AutoCAD(r) DXFOUT command, will export a DXF file. It captures not only 2D and 3D polylines and their layer names but also exports all visible (layer on) points from the CRD file into AutoCAD “Point” entities form (layer PNTS). All points and polylines that are visible (layers on) would be exported, not based on the current screen zoom, but based on the full extent of the drawing.
The EDXF command has many special features for displaying the points in the exported drawing. Consider the source drawing below:
When the Export DXF command is issued and a file name is entered, a dialog appears with options shown below. If you choose "Create block attribute on layer: 0", then all attributes such as point number, elevation and description take on the layer of the node. In this case, all point attributes inherit the fence line layer for the fence points and the utility layer for the catch basin and manhole points. If you do not put the attributes on layer 0, then they have distinct colors and layers for the number, elevation and description. In addition, if you click on "Save GIS Point Feature to Block", then if GIS attribute data is included, this data will appear beneath the description in a vertical, left-justified column (eg. 5.4=depth, 2=number of inlets, Cast Concrete=type).
Other options in the command include drawing the actual point symbols, drawing GIS line feature attributes and drawing in 2D (at zero elevation). If "Save GIS Line Feature to Block (Center)" is clicked on, then attributes associated with a polyline will draw in the middle of the longest segment of the polyline. If "Save GIS Line Feature to Block" is clicked on, but the "Center" option is not clicked on, then the GIS attributes of the polyline draw on the second point of the line, below the other "standard" point attributes such as elevaiton and description. Shown below is the combination of normal point attributes (not placed on layer 0) and linework GIS feater plotting, shown associated with the second point in the polyline.
DWG File - Import .dwg (IDWG)
The IDWG command directly loads a ".dwg" file into SurvCE and all layer names are retained. No hatching, points or blocks are imported. Only polylines or text that has been converted to polylines will appear in SurvCE.
DWG File - Export .dwg (EDWG)
The EDWG will export to ".dwg" format all linework appearing in the SurvCE Map screen, regardless of origin (imported, drawn in the MAP screen, created by Field Codes). Layers and even line thickness (as created by field codes) will be retained in the exported drawing. The controls for exporting DWG files are similar to those of exporting DXF files described above, with the added option to designated the DWG format as shown below:
LandXML - CRD from Land XML (XML2CRD):
This command allows you to import points from LandXML format to SurvCE.
LandXML - CRD to Land XML (CRD2XML):
This command allows you to export points from SurvCE to LandXML format.
LandXML - Export Chain File to LandXML (CHAINXML):
This command allows you to export all the polylines from the current drawing created using Feature Codes, as LandXML chain objects into a LandXML file. For example, if you made strictly 3D polylines for break lines using descriptions such as EP for edge-of-pavement or DL for ditch line, then the 3D polylines can be exported as a LandXML chain file and used as break lines for contouring in other CAD programs. The combination of points and break lines can lead to optimal contouring. Most CAD packages will import linework using the DXF file approach, but many now recognize linework in LandXML “Chain” file format.
SHP File - Import Shape File (ISHP) (e.g. from ESRI):
This command allows you to import entities and also the associated attributes values from a SHP file. The routine displays "Import from SHP" dialog box. If the SHP file has POINT or POINTZ type, the entities will be stored into a CRD file. In the cases of an ARC, ARCZ, POLYGON or POLYGONZ SHP type, the entities will be stored into the current drawing. The attribute values will be stored into a *.vtt file. The routine requires a feature code name from the user, which will be used to store the name and the type of the attributes from the SHP file.
SHP File - Quick Import SHP (QISHP):
This command allows you to import entities from SHP files (used by most programs produced by ESRI). The routine displays the Import from SHP dialog shown below. POINT or POINTZ type entities will be stored in a CRD file. ARC, ARCZ, POLYGON, or POLYGONZ entities will be stored in the current drawing as POLYLINES.
Current SHP: Displays the name of the SHP file that will be imported when this command is completed. Read-only, you must use the Select SHP button to specify the file name.
Select SHP: Tap this button to select a SHP file name.
Current Job: Available when importing coordinate data. Specify whether to Overwrite Exiting Point Numbers or Use New Point Numbers.
Attribute used to fill Description: Available when importing coordinate data. Lists the attributes in the currently selected SHP file. Select which attribute to use to fill out the Description field in the CRD file.
Layer used to store new entities: Available when importing geometry. Select the layer to store the new entities.
Process: Tap the green checkmark to begin the import process. When complete, it will display, "Process done". Then click the orange back arrow to exit. If you are importing a large file, a progress bar at the bottom of the dialog will indicate the progress of the import.
SHP File - Export SHP File (ESHP):
This command allows you to export entities from the current drawing and also the associated attributes values, into a SHP file (or more accurately, multiple shape files). The routine will allow the user to select which entities will be exported, based on entity type and also based on the feature code name. The routine displays "Export to SHP" dialog box.
Click on Export All and include special attributes and optionally the Z coordinates. If you have point, arcs (non-closed polylines in ESRI terminology) and polygons (closed polylines), all with one attribute, you will obtain up to nine files as shown below:
Ascot1_11.dbf
Ascot1_11.shp
Ascot1_11.shx
Ascot1_13.dbf
Ascot1_13.shp
Ascot1_13.shx
Ascot1_15.dbf
Ascot1_15.shp
Ascot1_15.shx
The selection of the Z coordinate places the 1 after the underline character. Otherwise, the file form would be, for example, Ascot1_1.shx (special attributes only). The “1” group represent points, the “3” group represent arcs (unclosed polylines) and the “5” group represent polygons (closed polylines). Within Export Shape file, the field name in the dbf file is expanded to handle up to 254 characters.
SHP File - Quick Export SHP (QESHP):
This command allows you to export polylines and/or points to an SHP file. When first entering the command, you may be prompted for a "projection file", a .prj file, that allows the export to overlay on grid coordinates. The ".prj" file itself is made within ESRI products. You can choose to use the current ".prj" file, use another, or cancel any use of a projection file, as shown below:
Then proceed to a dialog that displays the following options:
Current SHP: Displays the name of the SHP file that will be created when this command is completed. Read-only, you must use the Select new SHP button to specify the file name.
Select new SHP: Tap this button to select a SHP file name.
Do not export points: When this option is checked, only polylines are exported to the SHP file.
Export entities from selected Layers: Lists the layers in the current map. You may select certain layers for export.
Select All: Selects all layers in the list.
Clear All: Clears all selected layers in the list.
Remove Arcs (offset cutoff): Specifies the maximum distance that a vertex on a polyline segment will deviate from the original arc.
Include Z Coordinates: When this option is checked, elevation data (or Z coordinates) will be included in the SHP file.
Slope if 3D Line: If distinct, different vertice elevations are detected, you have the option to retain the starting elevation for all vertices or export the vertices with their distinct elevations.
Process: Tap the green checkmark to begin the export process. When complete, it displays, "Process Done". Then tap the orange back arrow to exit. If you are exporting a large file, a progress bar at the bottom of the dialog will indicate the progress of the export.
Export ASCII w/GIS:
Allows exporting of points with attribute data in the form Pt ID, Northing, Easting, Elevation, Description, Attribute1, Attribute2, etc.
DTM Import - DTM from DXF (TDXF):
Allows you to import 3DFACE entities from a DXF File and save them as a triangulation (TIN) file and also draw them as 3D faces.
DTM Import - DTM from Land XML (TXML):
Allows you to import 3DFACE entities from an XML File and save them as a triangulation (TIN) file and also draw them as 3D faces.
The DTM file is stored in SurvCE as a TIN file and can be used for commands such as Elevation Difference (obtaining cut/fill by comparing field measurements to the DTM).
The 3DFaces are placed on a layer (TRI_FACE by default), and that layer can be turned off and removed from view. If you choose E for Erase, you can pick the 3D Face entities and erase them on command. There is no particular value to seeing the 3D Faces, so it is not recommended that they be drawn. The main value is to capture the TIN (triangulation) file for use in Elevation Difference.
DTM Import - DTM from Ispol:
Allows you to import a TIN file from the Ispol format, commonly used in Spain.
Preferences (SETT):
This allows the user to turn on/off the pull-down MAP menus. The graphic screen style of normal or reverse (solid dark) background is set here.
Command Aliases (AL):
Brings up a list of commands in the MAP mode for which the user can substitute an alias. If you would prefer to type A for Area rather than AR, you can substitute “A” as an alias for AR. Three commands will not accept substitutes: Inverse, Traverse and Sideshot (I, T and S). In addition to commands, you can toggle over to the “Linework special code” option, and substitute aliases codes for the default special codes such as PC, PT and END (used to control linework using feature codes). As an example, you could choose the “X” or “..” to End a line, or use “CS” for curve start instead of PC. A sampling of commands is shown below:
Quick Save (QS):
Saves the current DXF file without prompting for the file name.
Save As(CRD):
Saves the current coordinate file to the location you choose as a backup copy.
Draw MOSS File (DMOSS):
This will import and draw a MOSS ".inp" file.
Exit (X):
This exits the MAP and CAD session and brings you back to the Menu screen.
Help (H):
Launches the interactive Help screen describing various MAP screen commands. Scroll up and down to review. With wireless on, includes access to Internet Explorer, by tapping the icon at the top of the Help screen.
Contents Index
The View menu is found next to the File menu in MAP view. Below you will find each feature described.
Zoom (Z):
Increase or decrease the apparent size of polylines and distances between points, in drawing area. The specific options in the command are N (Zoom to Point ID/Number, enter zoom magnification), I (Zoom In), O (Zoom Out), W (Zoom Window), P (Previous) and E (Extents). The Zoom command options can also be accessed using the first 5 buttons from left-toolbar menu. The order of buttons, starting with the first top button, is: Extents, In, Out, Window, Previous. Zoom Previous will "nest" which means that if you Zoom In or Zoom Window 3 times, each Zoom Previoius takes you back one step and 3 Zoom Previous commands would return to your original view.
Layer (LA):
This command manages layers and layer properties.
To add a new layer: Type in a new name into the New Layer edit box. The New button will appear at the bottom. Tap this button. If you type in a new layer name and the New button does not appear, then the layer name you entered contains invalid characters.
To set a layer current: Highlight the layer name in the list and then tap the Set button. You cannot set a layer current if that layer is turned Off. Turn the layer On first and then set it current.
To delete a layer: Highlight the layer name in the list and tap the Delete button. You cannot delete layers that contain objects. If you select a layer and the Delete button is not visible, then this layer contains objects.
To turn a layer On/Off: Highlight the layer name and tap the On/Off button. Objects on layers that are On will be visible, objects on layers that are Off are not visible.
On all: This button will turn all layers on
Off all: This button will turn all layers except the current layer off.
Color: Clicking on the color bar will bring up the color palette allowing you to set or change the layer color of the highlighted layer.
One of the main purposes of the Layer command is to permit the import, by DXF, of a drawing containing all possible polyline work to stake out (set out). Then you can reduce clutter on the drawing by turning layers off, leaving only the layers you want. You can stake any endpoint, intersection, or other location on the polylines using "snaps" without creating point numbers. You can also do the MAP command Cogo, Interpolate Points, Polylines to Points and make point numbers out of all vertices (corners) of polylines where you need to set stakes. Then proceed with Stakeout by Points.
View Options (VO):
This command controls the appearance of point objects on screen. This is exactly the same as touching the lower left graphic icon. The routine displays the View Point Options dialog. Pt#, Description and Elevation toggles control whether these attributes are labeled with the points. If Freeze All is on, the points are placed on the map, without attributes. Available point symbols are: ".", "+", "x". The “Decimal is point location” toggle determines if the decimal point used in the display of elevations represents simultaneously the point location and symbol. This slightly reduces screen clutter. Turning on the WCS Icon and Scale Bar would show the north direction and graphic scale at all time in the MAP view. Turning them off also reduces screen clutter.
Small and Large toggles determine the size of font used to display the point object on screen. Set Color Attributes brings up the color palette (available only on color CE devices). This lets you choose the color of the point symbol, elevation and description text. Traverse Defaults is found under the Data tab, which also includes the "Intelligent Zoom" toggle (on setting recommended). The Traverse Defaults button brings up a dialog that has the settings for prompting each time for instrument and rod height and the vertical angle. This applies to the T for Traverse and SS for Sideshot commands that allow point calculation within the MAP Screen. For Cogo work, turn off Instrument/Rod Height and Vertical Angle prompting. For manual entry of actual field measurements, turn them back on.
Isolate Points (ISO):
This is another useful command to reduce screen clutter. If you have 500 points on the screen, you can isolate to only those points you wish to see, by entering a distinct point range, in the form 1-10, 22, 25-30, or a certain description. This would isolate to points 1 through 10, point 22 and points 25 to 30, and other points are “frozen”. You can also isolate to descriptions (D for Descriptions) by entering a description such as "EG" for Existing Ground or a wildcard description using an "*" such as "IP*" for any description beginning with IP (IP, IPF, IPS, etc.). Repeat the ISO command and enter the full point file range (or “all”) to restore all points.
Isolate Layer (IL):
Select any polyline layer and isolate it to keep that layer. Other polyline layers are turned off (frozen), but point layers are retained. Use the Layer command to turn layers back on as needed (On All).
Aperture (AP):
Controls the size of the rectangle area used to select points or polylines from screen. Initially, the size in pixels is 20 units for points selection and 10 units for polylines selection. You can change it as shown. The routine displays the Aperture size dialog.
UCS (UCS) User Coordinate System Indicator:
This toggles the visibility of the UCS icon shown in the MAP screen.
Find Point (FND):
This command allows you to find a point on the MAP screen. Enter the point you want to find and a zoom height. If you enter a point that is not on the map, the dialog will warn you and allow you to enter another point number.
Click Find and the SurvCE zooms to the selected point at the entered scale.
Scale Bar (SB):
This toggles the visibility of scale bar on or off. The scale bar is normally shown at the bottom of the MAP screen.
List (LI):
Applying to linework entities only, this lists the layer, 2D or 3D status, Closed or Open status, perimeter (length), and area or projected area (if not closed). If the polyline is 3D, the coordinates of the polyline are shown:
Contents Index
The Draw menu is found next to the View menu in MAP view. Below you will find each feature described.
2D Polyline (PL) (AutoCAD style):
This command allows you to pick points from the screen or type in point numbers or snap to line segments. The snaps appear as icons (see below) and include, in order, left to right: "Endpoint," "Midpoint," ""Center of Arc or Radius Point," "Intersection," "Nearest," "Perpendicular," and "Tangent to Arc." The "Nearest" snap will simply pick a point on any line or arc you select, at the nearest point to where you pick. First, pick your starting point then you have several options on the command line. You can also draw by point number and even use ranges, as in 8-10,37 which would draw sequentially from 8 through 10 then to 37, as shown below.
Points can be entered or picked from the screen. The default option is to keep picking points and the other options are described below.
Cmd:Polyline-Arc/Close/Undo/<End>
A: Starts an arc segment. See below for details.
C: Closes the polyline (you must have at least two polyline segments drawn before you can close)
U: Will undo the last segment drawn (you can Undo again and remove multiple segments)
E: Will end the Polyline command.
Constructing an arc segment
After choosing A, the command line will change to:
Cmd: Polyline-Arc CEn/Len/Sec/<Rad>
You have various options for constructing an arc as part of your polyline.
CEn: Allows you to specify the center point (or radius point) for the arc. After picking the center point, you must specify the arc end point and then the arc direction.
LEn: Allows you to specify the arc length. First you pick the arc end point and then you can enter the arc length. The minimum arc length is given to you.
SEc: Allows you to specify the second point and end point to define the arc.
Rad: Allows you to specify a radius length. First you pick the arc end point and then you can enter the radius length. The minimum radius length is given to you.
2D Polyline (Road) :
This command allows you to draw a 2D Polyline. You can draw by point number, with ranges as in 8-12, or by picking on the screen using snaps or picked points. This command is similar to the polyline command described above with the following additions:
+/-: The +/- options activate an additional prompt that allows you to plot line segments at a 90 degree deflection angle from the last line. [+] is a right deflection and [–] is a left deflection.
Len: This option prompts you for the length of a line segment. Enter the length and a line segment will be drawn that length using the same bearing as the previous line segment. If the previous segment is an arc, then the new segment will be tangent to that arc.
3D Polyline (3DP):
The 3D Polyline command is similar to the 2D polyline command. It will even draw arcs, but will create a polyline on the screen with many vertices at different Z elevations which are linearly interpolated around the arc. If the start of the arc is point 17 at elevation 842.246 and the end of the arc is point 9 at elevation 839, then using View, List, you would see intermediate vertices (note that the segment length between vertices is about 0.12 units).
Using the snaps to draw lines can accomplish advanced coordinate geometry calculations. For example, if you offset two polylines and wanted to determine the point where the offset lines intersect as well as the corner of the driveway, you could draw a line from intersect to endpoint and do the command Polylines to Points (COGO, Create Points), which would create points 50 and 51. Polylines to Points will not find intersects, so it is more direct to simply do Draw Locate Points and use the intersect snap to create point 50 (COGO, Create Points). These procedures avoid complicated COGO involving curve-line intersects at offset. If your goal is to stake out points, you do not even need to create Point IDs, since the comand Stake Points will locate points by snap, directly from the drawing.
Circle (CR):
This command draws a circle entity, based on diameter defined by two points or based on a center point and a radius.
Erase (E):
Erases all selected polylines. It will not erase points. Note that you can erase an entire area by selecting a Window through the polylines (picking first a lower left point in “blank space”, then picking an upper right point). If you even contact or enclose any polylines with this window selection, they will be erased. So the “window” erase procedure mimics the “crossing” selection method of AutoCAD (r). If you enter "All" at the Cmd prompt, you will erase all linework. There is no Undo, so this would be permanent for that Job. However, you can redraw any linework created by Feature Codes, using MAP, Tools, Field to Finish.
Delete Layer (DL):
Select from a list one or more layers, then the routine will delete all the polylines on those layers.
Change Layer (CHG):
This changes the layer of the selected polylines. One form of selection is to type L and press Enter in order to select last created polyline from the drawing. The routine displays the "Change entities to layer" dialog box. When the dialog appears on the screen, the selection in the layer list will be set to the current layer. Clicking the color bar (where it shows "bylayer") brings up the color palette, letting you change the color by picking or ByLayer.
Extend - By Edge (XBYEDGE): First select the line to extend to, then the line you wish to lengthen and extend. In the example below, pick the line at left first, then the short line to extend second, and you obtain the result:
Extend - By Distance (XBYDIST): This powerful command allows you to create figures such as buildings, walls and other linear features that can then be staked out or used simply as a graphical reference or for additional CAD operations like offsets. If the distance from 99 to 100 is 7.07 feet, and you wish to make an L-shaped building that continues past point 100 for a total distance of 10 feet then goes 15' right, 20' right, 10' right, 10' right and closes, this is done with the following entries:
XBYDisT-Last/Points/<Select Polyline>: Press Enter to Select a Polyline and then pick, towards point 100, the starting line segment. The arrow will appear towards the picked end. If you get Point Details, you have not pressed Enter to "Select Polyline".
Then enter T for Total Distance, then 10 (the additional 2.93 feet is drawn), then R for Right. The arrow then turns to the right. Then enter 15 then R, then 20, R, 10, R, 10, then C to close.
The full list of options are:
L for Left, R for Right (two L's or two R's would reverse the direction of the line)
M for Move: Moves without drawing. Acts like a "pen up". You can then enter left and right distances.
D for Draw: Draws after a Move. Acts like a "pen down". Distances entered will draw.
N for Number: Creates point numbers at the vertices and numbers from the end of the job file.
J for Jog: Turns off point numbering and goes back to simple "jogs" of line segments. This is the default condition.
A for Arc: Draws arcs based on radius point and end point or radius length and end point.
B for Bearing (-aZi/Brg/ToPoint/<Ang>): Entering 45 turns an angle of 45. B for bearing allows bearing entry in all modes accepted by SurvCE, such as N34.15E. You can also draw by azimuth or to a point ID.
C for Close: Used in the example above to close to point 99, the starting point.
E for Extend: Will extend the line to any selected polyline.
O for New Polyline: Starts a new polyline and creates a separate entity, even though the figure will appear continuous.
T for Total Distance
U for Undo
Esc will exit the command at any point.
Offset - 2D (O2):
Mimics the AutoCAD (r) Offset command, and only works with 2D polylines. Enter the offset distance and pick the left or right offset amount. The building pad at left in the graphic associated with Segment Offset was offset 10 units in the outer direction, for example. The 2D and 3D offset commands have the option to fillet the corner (create arcs of radius equal to the offset distance) on exterior offsets based on Offset Settings under the Tools pulldown menu. This exterior offset with arc is sometimes referred to as a "buffer" offset, in that all points on the exterior offset are exactly the same distance from the source polyline. Buffer offsets are sometimes used for easements or GIS applications. Offsets to the interior will not create arc segments.
Offset - 3D (O3):
This offsets 3D polylines both horizontally and vertically. It is great in combination with road/utility centerlines to create offset polylines to stake. It can be used for ditch lines, curbs, walls and many other applications.
Offset - By Segment (OSEG):
This offsets all vertices of each segment of the polyline in a 90 degree offset and will draw line segments or optionally create points at the offsets. This is shown at right (in contrast to the parallel line offset at left) in the graphic below. You begin by entering the offset amount (eg. 10). Then a dialog appears with options to Avoid Duplicates and "Erase All", which removes the line segments and leaves only the points.
For L-shaped buildings or figures with angles, an additional interior offset point is calculated at the intersect of the parallel offset lines based on the entered offset distance, such as 10 (see point 165 below--the lines to 165 are drawn only to illustrate the 10' offset):
Modify - Remove Arcs (RMA):
Pick any polyline with an arc, specify the “offset cutoff” spacing, and turn the arc into chords. Offset cutoff refers to the maximum separation between the chord and the original arc. If you enter a small cutoff distance of 0.1, then at no point do the chord segments differ from the arc than 0.1. Be careful with this command – there is no “Undo” to restore the arcs (though you can immediately start a new job and “re-load” the last, saved DXF file of the drawing). After removing arcs, you can draw a polyline from points on the arc, after creating small chords, using the "endpoint" snap (first snap on the left in the list of snaps).
Modify - Fillet (F):
Similar to AutoCAD’s Fillet command. It prompts: Cmd: Fillet -Ra/Pl/eXit/First seg 25.00. If you are trying to inscribe a curve at the corner of a polyline, you enter the desired radius first by selecting R for Radius (at the above prompt). Then you choose the P option. This leads to the prompt, Cmd: Fillet -Ra/Pl/eXit/Select pl 25.00. Select the polyline near the vertex where you want the curve to go. This completes the process. If you wish to change the radius, enter R. If you want to fillet the corner of 2 distinct polylines, then just pick them as prompted (do not do the P for Polyline option). This command will only work with 2D polylines, completed with the command 2DP, or imported from a DXF file as 2D polylines, or converted from 3D using the command C2D which changes the vertice elevations to zero.
See the above two figures. Because in the top figure, from 1 to 2 to 3 was one continuous polyline, after the radius was set at 15, P was entered to set up the one-pick approach for polylines, leading to the completed fillet command and the result as shown in the bottom figure. Now you can do Cogo, Interpolate Points, Polylines to Points (P2P) and solve for the points for the beginning of the arc, radius and end of arc, for purposes of stakeout (set out).
Modify - Join (JN):
This command allows you to join polylines. Enter D to specify a new maximum separation distance, then select the polylines on the MAP screen. If you use 0 for Distance, then the polyline to join must be separate polylines connecting to common points. The advantage of joining polylines is that they can then be offset as a unit, and the vertices of the offset polylines can be turned into points for stake out. The offset command, in effect, does all the complicated bearing-bearing intersects for you. For example, if the resulting polyline were a pipeline with a 20 meter total right-of-way, then to stake the right-of-way points, you would offset the polyline 10 units left, then 10 units right, then turn both offset polylines into points.
Modify - Trim (TM):
This allows you to trim polylines to the edge of other polylines just like in AutoCAD (r). Then the command Polyline to Points (P2P) will turn all vertices, including the trimmed end points, into points for stakeout.
Modify - Reverse Polyline (RV):
When you turn a polyline into points, it will start the point numbering at the beginning of the polyline. Thus it may be useful to control the direction of the polylines. This is done with the command Reverse Polyline. Each time you pick a polyline using this command, you reverse its direction, and little temporary arrows are displayed along the polyline indicating the current direction. If it is not the direction you want, reverse again.
Place (Draw) GRID (DG):
This command toggles a horizontal and verticle grid display over your drawing, allowing you to set the grid resolution in drawing units. These grid lines are for reference only and are not part of the stored drawing associated with the job. To turn off, repeat the command and enter Off.
Transform: Align Building (AlignB):
This is a building application allowing adjustment of the building pad location in the field. If you import a map of a subdvision or building project containing a building pad, side lot lines and a frontage line, you can reset the building pad to a new, specific offset from the frontage and also force the building pad to be parallel to a selected side lot line, at a specific offset to the lot line. Refer first to the graphic below which shows an existing building on lot 84. Using the I for Inverse command in the MAP screen, you can obtain the distance from the end point of the building and then select the perpendicular snap on the lot line. The distance is 18.7 feet. Similarly, the distance from the building to the arc of the frontage line can be computed at approximately 58 feet.
There are 2 methods of Building Align, which are set under Tools, Align Settings. The first method is to align the buildign parallel to a lot line at a certain offset from the frontage, measured along the lot line. This is the Offset-Distance setting for Building Align. To illustrated this method, assume the goal is to place the building parallel to the side lot line at 20 feet offset, and offset from the frontage at 65 feet as measured along the lot line. Here are the prompts for the Align Building command:
Pick Bldg Segment Near Front Corner: (Pick the same lower left building corner as shown above, but along the side facing the adjoining lot line). This leads to the graphic below. The correct side line is highlighted.
Pick Lot Segment Near Front: Now pick the side lot line near the right-of-way or lot frontage line. The building setback offset will be calculated from the front end of the lot line.
Offset>Crt<18.699>/<10.000>: Enter the desired side line offset (20).
Distance>Crd<57.919>/<10.000>: Enter the desired frontage offset (65), as measured along the selected side line. If the Align Settings under Tools is set to Offset-Offset, then the offset distance applies to the minimum separation distance from the frontage line to the selected building corner. (In our example, the Offset-Offset setting, using the same offsets of 20 and 65, would shift the building slightly closer to the front lot line, since at the 20 offset, the frontage lot line is curving away from the building. Offset-Offset holds the offset distance to the actual building corner, and Offset-Distance measures along the side lot line itself)..
The new building location then draws and the original building remains. If this is correct, use E for Erase to remove the old building. Otherwise, remove the new building and repeat the process.
Transform (MOV, ROT, COP, SCL, MIR):
This command allows you to reposition polylines in the drawing to new locations based on your point geometry. The transformation options are Move, Rotate, Copy, Scale, Mirror. These work much like they do in AutoCAD, with input being the base or source point, and the destination or target point, rotation or scale. In the case of Rotate, the base point is the rotation pivot point and then you enter a rotation angle. The Copy command may be used as a Move command, since it has the advantage of showing the new copy and keeping the original, in case you wish to erase the new version and repeat for better results. The Mirror command includes the option to delete the source or retain the source entities. Note: This command only moves selected linework and does NOT reposition the corresponding points in the drawing.
(Centerline moved from Pt 4 to Pt 8)
Contents Index
The COGO menu is found next to the Draw menu in MAP view. Below you will find each feature described.
Inverse (I):
Inverse command Inverses and presents the bearing and distance between point numbers. It has the added benefit that the previous point inversed becomes the backsight, and the current point inversed becomes the occupied point, allowing you to sequence directly into the Traverse or Sideshot commands. (Use angle code 7 to turn an angle right from the backsight to the foresight.) The "snaps" are available in inverse, so you can calculate the distance from a point to a line by "snapping" to endpoint, intersect, perpendicular or nearest (as shown in Align Building command in Draw).
Traverse (T) (also TR):
Similar to the Sideshot command, the Traverse command will “move up” to the last point traversed, holding the previous occupied points as the backsight. Exit with Esc.
Sideshot (SS) (also S): This allows for sideshots from any point that is “occupied” by use of the inverse command. For example, if you inverse from 126 to 150, you are “on” 150 and backsighting 126. Then at the prompt "Cmd: Inverse – Tr/Ss/Pick point or point No:", you can enter S for Sideshot. The first prompt is the Angle-Bearing Code: Sideshot-eXit/I/Tr/H/Angle-BC(1-7)<7>, which can be any of the following:
1-NE (0 through 90 if degrees, 0 through 100 if gons/grads)
2-SE (same as above)
3-SW (same as above)
4-NW (same as above)
5-Azimuth (360 circle if degrees, 400 circle if gons/grads)
6-Angle Left (degrees or gons)
7-Angle Right (degrees or gons)
Note that at the Angle/Bearing prompt, you can transition back to inverse (from your occupied point) or to traverse, which would move you up to the next traversed point. Code 7 turns angle right. In the standard MAP screen prior to selecting T or SS, if you click the lower left View Options button, and then select the Data tab and choose Traverse Defaults, you can turn on the Zenith Angle or Elevation Difference prompts. Then sideshot and traverse entries can be used for hand-entry of field data. Within Sideshot, you stay on your current point, holding the backsight, and foresighting (calculating) as many points as desired. X returns to the MAP screen as does Esc.
After the angle code, the remaining prompts are the angle itself (as in 85.3522, DDD.MMSS), zenith angle, slope distance, description and point ID. Exit with Esc anytime. In gons/grads, angles are also in decimal form, and angles such as 397.9871 are valid.
Create Points - Draw Locate Points (DrawLP): This command creates points at endpoints and intersections of polylines, based on use of the "snaps". In the example below, point 23 was created at the northeast endpoint 
of the building on lot 88, point 24 was created at the intersect 
of the driveway and the lot frontage line and point 25 was created at the center of the arc 
of the pavement line. The "snaps" from left to right are endpoint, mid-point, arc center, intersection, nearest, perpendicular and tangent.
Create Points - Polyline to Points (P2P):
This command converts any selected polylines into points. It is useful in capturing points for stakeout from polylines created as offsets or brought in from DXF files. This allows you to react to circumstances in the field by creating points from polylines, when and where needed. For example, if you wanted to make point numbers out of the lot corners below on the SW lot, Select Cogo, Create Points, Polylines to Points (or more simply enter P2P at the command line). Then pick each desired polyline. The program will avoid making duplicated points on vertices that already have point IDs.
The new points are shown in “large” format, for emphasis.
Create Points - Divide Along Entity (DVS):
This divides a polyline into the number of segments entered. A dialog will allow you enter in the number of segments. There are settings to prompt for descriptions and elevations and to create points at the end points of the polyline.
The command will create new vertices along the polyline, but can also create point numbers starting at the entered Point ID, and you can elect to be prompted for descriptions and/or elevations at each new point. If a property line were divided into two segments, you would create three new points, if Create Points at Endpoints is clicked on. Otherwise, division of a line into two segments would create only 1 new point ID, in the middle of the line or polyline.
Create Points - Interval Along Entity (DVI):
This divides a polyline by the distance entered. Curves can have a different interval. There are settings to prompt for descriptions and elevations and to create points at the end points of the polyline.
This command is often used for creating points on centerlines. Note the program resets the interval at break points like PI’s and PC’s. Note that you can choose to create more points at a smaller interval going around curves.
Triangle Calculator (TC):
Goes directly from the MAP view to the Triangle calculator. See COGO - Calculator for detail.
Curve Calculator (CC):
Shortcut to the curve calculator, then returns to MAP. See COGO - Calculator for detail.
Area (AR):
This will report the area of any picked polyline. If you pick an unclosed polyline, the program will draw a temporary line for the closing segment and report the area.
Hinged Area (HA):
This command can be used to determine the dimensions of a figure when the area is fixed and three or more sides are known. The figure must be defined by a closed polyline. After executing the command, select the polyline. Next, select the hinge point. The polyline segment clockwise from your hinge point will be the segment to move. SurvCE will then ask you if you want to keep the existing polyline. If you answer Yes, a new polyline with the desired area is created, if you answer No, the polyline you pick is modified. Next, the current area of the polyline is shown. At this point, enter the new area in the units specified under Job Settings. (If your units are set to feet, the area will be specified in square feet). See the top figure below.
Note how the hinged side occurred on the clockwise side of the polygon perimeter (side 57 to 43). If we erase the new polyline, reverse the original polyline (RV) and repeat the command, this time answering “No” to “Keep existing” and again targeting 24000 s.f. area, we get the following:
Sliding Area (SA):
This command adjusts one side of a polyline to meet a specified area. You must specify the new area in the same units as specified under Job Settings. The area to adjust must be a closed polyline. After executing the command, select the polyline. SurvCE will then ask you if you want to keep the existing polyline. If you answer Yes, a new polyline with the desired area is created, if you answer No, the polyline you pick is modified. Next, the current area of the polyline is shown. At this point, enter the new area in the units specified under Job Settings. (If your units are set to feet, the area will be specified in square feet). Let's choose to divide our new parcel into two equal areas of 12,000 square feet each.
Slope Report (SR):
This command reports the horizontal area along with the slope area of a figure defined by a range of points. The command actually executes the TRIANGULATION command to compute the slopes within the defined area. There are options to include breaklines, use a predefined TIN model, and prompt for inclusion/exclusion areas. If you use a TIN model, you should click on "Prompt for Inclusion/Exclusion" and then pick perimeters where the calculation will be applied.
Consider the figure defined by points numbered 570, 97, 569, 584, 585, 75, and back to 570 as shown below. From the COGO AREA command, we see that the horizontal area of the enclosing polygon is 11,653.4122 Sq Ft. Performing the SLOPE REPORT yields the same horizontal results, but also reports the slope area, and the maximum, minimum, and average elevations and the average slope within the area.
Bearing & 3D Distance (3D):
This command reports the horizontal distance, elevation difference, slope distance, vertical angle, percent slope, slope ratio, bearing and azimuth between two 3D points. The user can pick or enter the number of two points, select a polyline segment or pick two points on any polylines from MAP using the "snaps".
Contents Index
The Tools menu is found next to the COGO menu in MAP view. Below you will find each feature described.
Polyline to CL (P2CL):
Converts any polyline into a centerline file for use in the Roading commands and in Centerline, Curve and Offset Stakeout. You will be prompted for starting station and you will obtain a centerline report. Use Reverse Polyline (RV) and repeat the command to change the direction of the stationing. If we choose the existing polyline as shown, we obtain the following CL file report:
CL to Polyline (CL2P):
This command draws a POLYLINE entity using the data from a centerline file. You can practice this command by selecting the file Demo.cl, provided with the program. It draws in the current layer set within the View pulldown, Layer command.
Convert Polylines to 2D (C2D):
Pick any 3D polyline or contour polyline at uniform elevation and convert it to 2D (elevations of vertices are set to 0).
Edit - Polyline (EDP):
Remove vertices, insert vertices and update (alter) the coordinates of any vertex. For example, if we pick the centerline that was used above, we obtain the edit dialog, with options to add or remove segments or arcs, edit curve information, etc. Saving changes updates the graphics on the screen.
Edit - Input-Edit GIS Data (EGIS):
This command allows you to input or edit GIS attributes associated with an entity. Select the entity from the screen or for the case of a closed polyline, pick inside the area defined by that entity.
Only polylines (open or closed) can be selected. This command does not apply to attributes associated with points (use List Points to edit point attributes). Attributes are associated with points, polylines and polygons (closed polylines) either through use of feature codes or by importing shape files. If a polyline is closed, you can use the Pick option and simply pick inside its interior. This “ROAD” description included a “SURFACE MATERIAL” attribute, which now can be edited.
Offset Settings (OF):
This command allows you to set the type of corner that SurvCE should create when offsetting entities.
Align Settings (ABSET):
This command allows you to select between two methods of aligning buildings using the Align Building command under Draw, Transform. The first method (offset-distance) aligns buildings parallel to the sideline based on a sideline offset and a distance offset along the sideline to the front of the building. The second method (offset-offset) holds the building parallel to the sideline but ensures that the frontage offset to the selected corner of the building matches the second offset value.
Traverse Defaults (TD):
This sets the elevation prompting (none, vertical, zenith, elevation difference), within the Traverse and Sideshot commands within the MAP view. Also enables a prompt for Instrument and Rod Height. Default setting is no instrument or rod heights and no vertical angle prompting, so inputs are simplified as angle/bearing code, angle/bearing, distance, description, point number. Traverse and Sideshot entries within the MAP screen are stored to the RW5 file.
Note: 3D MODE must be enabled in Equip/Configure for this dialog to become active. Otherwise, choices are "grayed out."
Triangulate & Contour (TRGC):
Triangulate and Contour can create a final contour map based on user given data: points, polylines. This function has many options which are specified in its dialog box. The routine will prompt also for inclusion and exclusion polylines. You can use exclusion polylines to avoid contouring within buildings, for example. If you have no exclusion polyline (or no inclusion polyline), press Enter to continue. To delete entities drawn with this command, turn off all of the drawing options and reprocess or use the View pulldown menu and isolate to the layers involved then erase all objects.
Volume (VOL):
Volumes can be computed by several methods, using point ranges and/or layers to define existing and final surfaces. Perimeters can be used to further limit the area of the volume calculation.
Referring to the graphic below, which illustrates a stockpile, the “Final” point range could be defined as ALL points, and the “Original” point range could be defined as the base points of the stockpile or points 1-15.
So using the settings above in the Volume routine, you would verify your two point ranges, then click OK. For example, the “Original” surface point range would be set as follows using the “Define” button for “Original” prior to clicking OK.
Clicking OK moves forward to a shrink and swell factor screen. Only if you are set to English units do you get the option for tons based on a density factor. In metric units, the volume is presented in cubic meters. You can create a new surface TIN file that merges the original surface with the final surface within the selected or assumed perimeter. If you do not have an inclusion perimeter, then the largest "convex" figure defined by all final surface points and entities becomes the default perimeter.
Clicking OK continues on to the Volume Report.
The report can be saved to a text file using the “Save to Disk” icon at the top of the screen within “Volume Report”. Click the “Return” arrow to continue back to the Map screen. If you draw a 3D polyline perimeter connecting points with elevation representing the outer limits of the volume calculation (using Draw, Polyline, 3D), then you can click on Inclusion and use the polyline as an inclusion perimeter. You can also use drawn elements on different layers as part of the volume calculation, if they are 3D, by moving them over to the right-colume using the “Define” button. Volumes can also be conducted between “File” surfaces, TIN files made with Triangulate & Contour or within the Volume command itself using the option “Save Surface to File.”
Finally, if you are doing a stockpile and make the effort to put this outer perimeter in the “Perimeter” layer, then you can select the “Stockpile” option within Volume and it goes directly to the shrink/swell factor screen and then to the report, without any other selections by the user. This is because the Perimeter layer will define both the inclusion perimeter and the original surface in this case.
List Elevation (LELV):
This command allows the user to pick on an entity and retrieve the elevation of that point.
Field to Finish (F2F):
This command will redraw the linework created with Feature Codes based on the current coordinates of the points. So if a GPS file was “processed” using a new localization, or a total station survey was adjusted, the existing linework made by use of Feature Codes will erase and redraw by connecting to the adjusted coordinates. In this way, polylines on the MAP screen created by field surveying will be redrawn to recapture their association with the adjusted point coordinates. Note that linework created by Feature Codes will redraw automatically in all graphic screens after coordinate positions or descriptions are edited within File-Points. The F2F command will restore linework to point-based positions after erasing or moving linework on the screen.
Place World Image:
This command will attach an image database to the SurvCE drawing. Image databases are georefenced aerial photography or image maps. These image databases can contain mulitple large images that have been processed for quick display in SurvCE. The boundary for the image-set is shown by a dashed line. Images are inserted in coordinate system and units of the image. Image databases are processed with the Image X-Port utility of Carlson X-Port and take the form of IMD or IDB files. The option to Save Image Boundary Points creates points at the 4 corners of the image, allowing you to zoom to those points. However, Zoom Extents (upper left icon in MAP screen) will zoom to the extents of the image if no points exist in the file.
Contents Index
This chapter contains five tutorials designed to assist you in learning Carlson SurvCE.
Tutorial 1: Calculating a Traverse (By Hand) with SurvCE
To do a hand traverse with SurvCE, go to the MAP screen. To get there, click the icon in the upper right corner of your screen labeled MAP. Once there, you will set your defaults for traversing.
Tutorial 2: Performing Math Functions in SurvCE Input Boxes
Various input boxes in SurvCE allow the user to calculate math functions "on-the-fly". The basic steps for getting started are shown here.
Tutorial 3: Performing a Compass Rule Adjustment
This tutorial shows a compass rule adjustment, with various SurvCE screen captures to guide you.
Tutorial 4: Defining Field Codes, Line/Layer Properties & GIS Prompting
This tutorial will assist users in defining Field Codes in SurvCE. SurvCE can have one pre-defined FCL (Feature Code List) file loaded with the job coordinate CRD file. The Feature Code List file stores pre-defined field codes that define Line/Layer drawing properties and, optionally, GIS prompting. More than one FCL file can exist, but only one can be loaded at a time per job coordinate CRD file. The operator builds this FCL file using option 5 “Feature Code List” in the File main menu.
Tutorial 5: Standard Procedures for Conducting GPS Localizations
This tutorial is intended to assist users with the recommended localization method for SurvCE. Other methods can be used, and it is up to the individual users to determine which is best for them.
Contents Index
In order to do a hand traverse with SurvCE, go to the MAP screen by clicking the icon in the upper right corner labeled MAP. While in the map screen, select the Map Settings icon to set your Traverse Defaults
.
Traverse Steps:
1 To begin, you must key in the command for inverse by typing “I”. This will establish your occupied and backsight points. The command prompt will display the following:
Cmd:Inverse - Tr/Ss/Pick point or point No
2 Key in the backsight point number followed by the [ENTER] key.
3 Key in the occupied point number followed by the [ENTER] key.
4 Key “T” for Traverse or “S” for Sideshot followed by the [ENTER] key.
5 If you keyed in “T” for traverse, the command prompt will be waiting for an angle code by displaying the following:
Cmd:Traverse - eXit/I/Ss/Angle-BC(1-7)<7>
If you keyed in “S” for sideshot, the command prompt will also be waiting for an angle code by displaying the following:
Cmd:Sideshot - eXit/I/Tr/Angle-BC(1-7)<7>
The code choices you can key in are as follows:
1 - Northeast Bearing
2 - Southeast Bearing
3 - Southwest Bearing
4 - Northwest Bearing
5 - Azimuth
6 - Angle Left
7 - Angle Right
6 Key in the angle code of choice followed by the [ENTER] key
7 Key in the angular value in the dd.mmss format followed by the [ENTER] key.
8 If you selected a vertical prompt under Traverse Defaults, then key in the appropriate value followed by the [ENTER] key.
9 Key in the slope distance followed by the [ENTER] key.
10 Key in the point description followed by the [ENTER] key.
11 Press the [ENTER] key to accept the next available point number or key in a new point number followed by the [ENTER] key.
12 If you traversed, then you are now occupying the new point and are backsighting the previous point of occupation. If you sideshot the new point, then you are still at the previous setup and ready to compute the next point.
13 Options at the command prompt when presented with the messages listed in step 5 are as follows:
X - Exit
I - Inverse
S - Sideshot
T - Traverse
Note: in order to establish new occupied and backsight point information, you must use the “I” (Inverse) command and define the backsight point first and the occupied point second.
Contents Index
Many input boxes in SurvCE allow the user to calculate math functions "on-the-fly".
To enter rod heights while in a GPS setup screen that is not in your current units (e.g. you’re using a 2 meter pole but working in U.S. feet), key in the following:
The Rod Height followed by “m” for Meters, “ft” for Feet and “ift” for International Feet followed by the [ENTER] key will convert the measurement into your current units (e.g. 2m = 6.5617).
To compute the azimuth from one point to another to automatically enter in the azimuth while using the Point by Direction option in Point Store, key in the following:
Point ID,Point ID (e.g. "1,2")
To add or subtract a value from the computed azimuth, key in the following:
Point ID,PointID+Angle (e.g. "1,2+90")
Or
Point ID,Point ID-Angle (e.g. "1,2-90")
Contents Index
In the example below, as shown in the next figure, the traverse was performed by occupying point 1 located at the NW corner of the block. The initial backsight was established by azimuth, measured and stored as point 2 shown NW along the hanging leg. Angles and distances were measured in a clockwise direction. Point numbers 6 and 1 are at the same location and point numbers 7 and 2 are at the same location. This method allows for the closing of the angles and the measurement of all traverse legs.
Process Raw File
Select “Process Raw File” from the “COGO” tab, as shown below in this figure.
Select Raw File
The next figure below shows the standard Windows file selection dialog. Select the RW5 file you want to process followed by the “OK” button.
Select “Compass” from the adjustment options dialog box as shown in this figure below.
Reference Closing Point
Key in the initial occupied point number for the “Reference Closing Point #:” and toggle on the “Apply Angle Balance” option, followed by the “OK” button, as shown in the next figure below.
Closed Traverse
In a closed traverse scenario, the reference closing point will always be your initial occupied point name.
Note that you will need two known points, or one point and a known azimuth, for a closed traverse. The angle balance point will be the same location as the original backsight and will not be adjusted.
Open Traverse
In an open traverse scenario, the reference closing point will be a stored point name or coordinates that represents the known values for the last occupied point in the traverse.
Note that you will need two known points, or one point and a known azimuth, at the beginning and at the end of an open traverse; one point at the end will be used to close on and other will be used for angle balance (when Angle Balance is applied). The angle balance point will be the same as the last foresight point in the traverse and will not be adjusted.
Traverse Points
You’ll notice in the Angle Balance Measurement figure below, since you keyed in the data yourself, that the number of traverse points in this survey is 7. Since point 7 was only measured to avoid and record the closing angle balance measurement by hand, in this example the traverse is only from points 1 through 6. Replace the 7 in the “Ending Point Number” input box with a 6, as shown in this next figure immediately below, followed by the “OK” button.
Note that point 6 should be the same location as point number 1 in a closed traverse.
Angle Balance
Select the foresight shot from the last occupied point to the original backsight location. In this example we would select the leg measured from point 6 to point 7, since point 7 was our foresight angle balance shot to point 2. Press the “OK” button. In an open traverse, this would be the measured leg that represents the known azimuth or bearing at the end of the traverse.
Reference Closing Angle
Finally we need to provide the reference closing angle (record). This is the original backsight azimuth. Key in point 1 and point 2, or key in the known azimuth or bearing, followed by the “OK” button.
In an open traverse, key in the stored point numbers that represent the values for the known control points at the end of the traverse, or key in the known azimuth or bearing.
The adjustment report should be presented, and the adjustment should be complete. The angle balance point number 7 will not be adjusted to fit point number 2, and can be discarded.
Contents Index
SurvCE can have one pre-defined FCL (Feature Code List) file loaded with the job coordinate CRD file.
The Feature Code List file stores pre-defined field codes that define Line/Layer drawing properties and optionally GIS prompting. (More than one FCL file can exist but only one can be loaded at a time per job coordinate CRD file.)
The operator builds this FCL file using option 5 “Feature Code List” in the File main menu. See the figure below.
After you select 5 Feature Code List, the following Code List pop-up box is displayed. See the figure below.
FCL (Feature Code List) files can be created, edited or reviewed on a PC using Carlson X-Port or any Carlson Surveying office software. (SurvCE’s FCL file is equivalent to Carlson’s Field-to-Finish FLD Table used in their PC office software. Transfer all PC Field-to-finish FLD table files using SurveyCOM or Carlson Export. Select the Field Code Table option to upload the FLD file to SurvCE as a FLC file.)
Defining Field Code Line/Layer Properties
To define codes with line/layer drawn features and, optionally, GIS prompting, select in the Code List pop-up box “Add” (as shown in the previous figure). The following Add Code pop-up box allows the operator to define Field Code Line/Layer drawing properties.
- Code: Input one-word Field Code
- Layer Name: Defines the layer the linework 2D & 3D will draw in using Store Points
- Full Text: User defined full text description for code
- Polyline On: Yes or No defines to draw or not to draw between similar codes e.g. EP, EP1
- Polyline is 3D: Yes or No - Yes draws in 3D, No in 2D
- New Attributes: This highlights after inputting all the Line/Layer drawing properties
The following EP code has been input in the FCL file. When Surveying using Store Points in the Survey menu, inputting field codes EP, EP1, EP2 and so on will draw 3D Polylines between these similar codes in the EOP layer. A 3D Polyline will be drawn in real-time when collecting data and inputting EP or EP# codes in Surveyed points descriptions.
As mentioned above, “New Attributes” becomes highlighted after inputting all the Line/Layer drawing properties. GIS prompting information can be added for this field code. If no GIS prompting is applicable for this field code, simply pick OK and create another field code, or exit and store the FCL file.
Defining Field Code GIS Prompting
To add GIS prompting to a defined Line/Layer code, select “New Attributes”. This button can be seen in the above figure at the bottom of the dialog. The following GIS Feature pop-up box is displayed. See the next figure below. To define GIS prompting for the EP field code, select “Add” in the Feature dialog shown below. The next pop-up box that appears, titled New attribute, is then displayed (shown below, underneath the Feature dialog). The New attribute dialog creates GIS prompting.
Load will load any existing Field Code GIS prompting for reuse. Edit reviews or revises existing GIS prompting. Add creates individual GIS prompting, as shown in the figure immediately above (New attribute dialog). Remove deletes any highlighted GIS attribute. Up and Down reorders the sequence of GIS attribute prompting. Save stores input or edited GIS prompting and exits to Line/Layer drawing properties.
Defining GIS Prompting
- Feature Code Name: No spaces GIS title for database
- Codes: Special codes, e.g. Date, Time, Lat, Long.
- GIS Prompt: Including spaces full name for GIS
- Default Value: Most common GIS value/default value
- Set: Lets the operator highlight and select the default value if there is a List of attribute Values.
- Type: Offers 4 options CHAR, INT, REAL and Code. Code Type will default to character type corresponding to special Codes. Codes can be Char, Int. or Real automatically.
- Req: Requisite/required entry. Operator cannot leave any GIS prompt empty when this field is set to Yes.
To add GIS attribute prompting for List Values, select the “Add” button within the New attribute dialog, as shown immediately below. The figure below that shows the New value pop-up box. The operator inputs, after selecting Add again, for each possible material (e.g. macadam, concrete, brick, stone cobbles and so on).
The data input for all GIS List Values is shown in following figure below. Note that Macadam is highlighted and will be the default value. If there are more than six attribute List Values, scroll bars will appear. This defines only one GIS entry Material for the EP field code. Each GIS prompt for the field code EP (e.g. Material, Location, Condition, Width, Slope and so on) will require being created using Add in the Feature pop-up box, as shown earlier in this tutorial.
Add, Remove, Up and Down pertain to GIS List Values prompting. Add and Remove create or delete List Values entries. Up or Down reorders the highlighted List Value up or down. OK exits the GIS prompting screen retaining the GIS prompting entries and Cancel exits and discards all new inputs. The completed GIS field code for EP is shown below in the Feature dialog.
With all of the GIS Features input – Material, Location, Condition, Width and Slope – the operator can now select Save to store the GIS prompting for the field code EP. When storing points in the Survey menu in Store Points with EP or EP#, 3D linework when ended will prompt for EP GIS data as defined here. If 2D or 3D linework is created the GIS data will be attached to the linework. Note that Location, Condition and Width are required input GIS fields. Load allows selecting any existing field codes GIS prompting for reuse. Edit reviews or revises existing GIS prompting. Remove deletes highlighted GIS attribute prompting. The Up and Down buttons will reorder GIS attribute prompting. Save stores and exits.
Importing & Exporting GIS Information from SurvCE
SurvCE imports and exports ESRI SHP files. SurvCE solely uses ESRI SHP files to interface with all GIS programs. ESRI SHP files are open architecture and are a widely used and accepted GIS format for most common GIS packages. To import or export GIS data to or from SurvCE, select in MAP – File – SHP File – Import or Export SHP File (Quick Import or Export only reads and writes the drawing entities and doesn’t include the GIS info). There are two figures later in this tutorial that depict this.
SurvCE Creates Three ESRI GIS Drawing Objects: Points, Arcs (Polylines) and Polygons (Closed Polylines)
There are only three types of drawing entries in ESRI SHP files points, arcs (open 2D or 3D Polylines) and polygons (closed 2D or 3D Polylines). The EP field code creates points and arcs and/or polygons. GIS information is stored only to the arcs or polygons and not the EP points. All GIS information for EP will be attached to the 3D Polylines. The second Field Code UP in the FCL job file creates points only with no linework. The UP field code attaches GIS information to the UP points. See the next two figures below.
Save Feature Code List File
With two field codes (EP and UP) with GIS information input and stored, using option 5 “Feature Code List” (in the File main menu), let’s collect some Survey data in Store Points with GIS information. First, Save As these two codes into a Feature Code List file, as shown below.
The Add and Edit buttons create or revise Line/Layer drawing properties and GIS prompting. Remove deletes field codes highlighted. Load unloads the current FCL file and loads another existing FCL Field Code List.
Collecting & Storing GIS information in SurvCE
To demonstrate collecting Survey data with GIS information, SurvCE is set to either Manual Total Station or GPS Simulation.
For Manual Total Station, go to the menu Survey – Store Points (see the next two figures). Follow the figures for Manual Total Station. It is important, in the main menu, that File – Configure Reading – HGT/Desc Prompt on Save is toggled ON!
For GPS Simulation, go to the menu Survey – Store Point (see the next two figures) and follow figures for GPS Simulation.
See these Manual Total Station example screen captures, shown here in the next four figures.
GPS Simulation screen capture examples are shown in these next four figures.
The sequence of shoots started with GPS Simulation storing points 2 and 3 as EP codes. Point 3 was stored as EP END. A 3D Polyline was drawn between 2 to 3 and GIS prompting popped-up after point 3 was stored shown above. Note in the Condition field the operator input data not found in the default settings. Point 4 was stored using manual total station as a UP point code. Point 4’s UP GIS prompting appeared after point 4 was stored. Points 5 through 7 were stored as a closed polygon. This was done by storing point 7 as EP1 CLO to close back to the start point 5 of the EP1 3D Polyline. The GIS prompting appeared for EP1 (not shown) and entered. The last sequence above was to exit Store Points and select MAP.
Editing GIS Information on Arcs and Polygons – Input-Edit GIS Data
To edit existing GIS information stored on Arcs (2D/3D Polylines) or Polygons (closed 2D/3D Polylines) in the MAP pop-up box, select Tools – Edit – Input/Edit GIS Data, and pick any polyline or polygon. There are two figures below. The top figure shows how the closed 3D Polyline between points 5, 6 and 7 was selected using this command. GIS data for the closed 3D Polygon is shown in the second figure.
The above figure displays the next EP code EP2 stored using GPS Simulation. When ended with a END or CLO description after EP2 SurvCE will prompt for EP GIS data to attach to the polyline as defined above.
The figure above displays the ease of reviewing, creating or editing GIS data using Input-Edit GIS Data. From the MAP screen Input-Edit GIS Data was selected and the closed 3D Polyline picked on the screen. The GIS data stored prior was displayed for review or editing. Any data point, polyline or closed polyline could be selected using the Input-Edit GIS Data command in MAP and new GIS attached to this entity or existing GIS data reviewed and edited.
Editing GIS Information on Points using List Points
Input-Edit GIS Data only works creating, reviewing or editing GIS information on Arcs or Polygons. To create, review or edit GIS information on points use List Points shown below under File – 3 List Points.
Highlight point 4 and select Edit (see figure immediately above). Point 4 is the only Surveyed number with GIS data stored to the point. The Edit Point pop-up box appears, and can be seen in the next figure below. To create, review or edit GIS information select Input/Edit Attributes (See Figure 9-32).
Note: At the +UP box on top the down arrow can be selected and one or more GIS field codes could attach GIS data to this same point. Points, Arcs or Polygons can all have one or more GIS field codes attached to these entities.
Exporting SurvCE GIS Data as ESRI SHP files
These final two figures, above, display the exporting of our VA_Beach MAP and GIS data. The ESRI SHP file consists of 9 points, 2 arcs and 1 polygon (closed polyline). Only one point, point 4, has UP GIS data. Two arc polylines and one polygon have EP GIS information attached. Note that Include special attributes is checked. This adds to polyline arcs and closed polygons the polylines length and area to the GIS data automatically. Process with Export All checked stores the VA_Beach three SHP files automatically to a user defined subdirectory and a fourth SHP file with 8 points without GIS data.
Contents Index
This tutorial is intended to assist users with the recommended localization method for SurvCE. Other methods can be used and it is up to the individual users to determine which is best for them.
File Extensions
Localization File: *.dat
Geoid Model File: *.gsf
Coordinate File: *.crd
Raw Data File: *.rw5
Projections
It is essential that the proper plane coordinate projection is selected prior to creating a localization file. This should be the first step performed during the creation of the job file and be performed easily through File à Job Settings à GPS.
Geoid Model
An important item to note is if the user intends to use a geoid model (typical for localizations that contain less that 3 control points), the geoid model must be applied prior to the creation of the localization file.
A local portion of the geoid grid must be extracted from the Carlson Geoid Model using Carlson X-Port, SurvCOM, Survey or Civil/SurvCADD, and the geoid model file must be installed prior to the creation of the local geoid file. It is also highly recommended that the local geoid file grid size does not exceed 100 miles.
Web Link to the Geoid Files
http://update.carlsonsw.com/public/CarlsonGeoidGrids.exe
Transfer or Enter the Known (local) Points
It’s a good idea to simplify the process by transferring the known (local) points to the data collector prior to going to the field. Conversely, the user can keyboard enter the known coordinates for these points into the CRD file, one at a time, using File à List Points à Add. It is not recommended that the user keys in the local coordinates from within the localization process as transpositions can occur easily. However, this can be done as well.
Collect the GPS Locations with Averaging
Using the Survey à Store Points routine, specify your point ID. It is good to use something that will relate to the original known point. Example, if the known point for the first control point is 1, then you may want to collect the measured location as 1001.
Use the average reading icon <A> to collect several epochs of data at each point. Typically when using a 1 Hz receiver, 10 to 30 readings will be collected to ensure that the RTK solution is consistently reporting the same position for 10 to 30 seconds. On a 5 Hz receiver, the user may want to collect 50 or more readings as 50 readings would be 10 seconds.
Create the Localization File
Once the data collector has points that represent the known (local) coordinates and the measured data for these points, the localization file can be created.
Select Equip à Localization à Add to enter each point into the localization file.
Local Point
The first dialog presented to the user will be the Local Point dialog shown below. Enter the known (local) coordinate point ID or coordinates. If the point does not exist in the CRD file and coordinates are entered into this dialog, do not enter a point ID. Select OK when the known (local) position has been defined.
GPS Coordinates
The next dialog presented will be the GPS Coordinates dialog shown below. Since the measured locations for each point has already been recorded, the user will want to use the option From Raw File in this dialog. Select OK to continue.
Surveyed Point
Next, the user will be presented with the Surveyed Point dialog shown below (top image). This dialog allows the user to select or enter the GPS measured point that represents the known (local) point. If the user selects the GPS measured point using the list icon, they should ignore the current coordinates displayed in the List Points dialog shown below (bottom image), as they only reflect the non-localized position at this point. The important thing to remember is that if the local point was 1, and the GPS measured point was 1001, the user must enter 1001 in this dialog.
Save the Localization File
Once all of the points have been added to the localization dialog, save the localization file before exiting using the Save button.
Reprocess Raw File and Update Coordinates
At this point all of the coordinates in the CRD file that represent the measured positions need to be updated to reflect the newly created localization. To do this, select COGO à Process Raw File and process the raw file through the localization file. This will update the previously measured GPS points. Verify that the positions look valid by viewing the points in File à List Points. You should be able to compare the known and measured positions to see if they look right. Depending on the localization method, the measured values may not be exactly the same as the original known positions due to error that may have existed in the original positions.
Additional GPS Measurements
Once the localization is defined, all of the GPS points measured after its creation will be recorded to the CRD file based on this localization.
Changing the Localization
If the user determines that they want to redefine the current localization during a job, they must reprocess the entire raw file after making any changes to the localization file. It may be prudent to simply define a new localization file from scratch, leaving the original intact, and reprocess the raw file through this new localization file. Just remember that the last localization loaded, will be the current localization.
Selecting Projections for use in Localization
Whenever you select a projection or coordinate system, you can place it in a “most used” list of coordinate systems to choose from under the GPS tab in Job Settings. This list can contain one projection system or many different systems the user selects.
This is a special list of either predefined (eg. KY North NAD83) or user-defined coordinates systems. To get the list started or add to the list, select Edit Projection List and click Add Predefined. In the U.S., for example, surveyors might want to keep the UTM (WGS84) system plus the NAD83 and NAD27 “state plane” zones in the list for quick access, covering the region of your work. European and other worldwide zones can be added. When setting up a UTM selection, you can choose your zone, referencing the graphic below for the US:
You can see a map of the UTM zones online at:
http://www.dmap.co.uk/utmworld.htm
To edit the list of saved projections, click on Edit Projection List. Here we select a user-defined UTM system from the list to Delete or Edit.
Choosing Edit will bring you to the screen below:
From this screen, you can select the Projection calculation method as well as calculation parameters. Projections include:
Lambert Conformal_Conic_2SP,
Transverse_Mercator,
Oblique_Sterographic (Double),
Lambert_Conformal_Conic_1SP,
Oblique_Mercator_83,
Stereographic, Oblique_Mercator_27,
Transverse_Mercator_OSTN02,
Oblique_Stereographic_RD2000,
Oblique_Mercator,
Cassini_Soldner,
Transverse_Mercator_27,
Lambert_Conformal_Conic_27,
Transverse_Mercator_Alaska_27
Transverse_Mercator_34.
You may also use the buttons on this screen to edit the existing datum or create a new datum definition.
The Datum definition screen is where you select the ellipsoid and Helmert parameters to apply.
If you select Add User Defined within the Coordinate Projection List screen, you proceed to the screen below:
Here you enter the name of the new system and select the projection type and parameters, or you can “Load File” to load a pre-defined system stored earlier (in the form *.sys or *.csl).
If you select “Add Predefined” to create a new, stored projection system, you will be presented with this screen:
Here you can select the country and then the corresponding system for your area. There is a very extensive list of European and Asian systems including in the list.
The “quick-access” short list of most used projections enhances job efficiency.
Contents Index
Contents Index
The following information describes the various options available for the Geodimeter 600 and Trimble 5600 total stations. It's important to note that firmware 696-03.xx or later is required. To check firmware version, select Menu 5, 4, 1 on the instrument.
Comms
Geodimeter/Trimble default communication settings in SurvCE are 9600,8,None,1. To check these settings on the instrument, do the following:
1. Select MNU, ENT, 4 (Data com), 1 (Select device), 2 (Serial)
2. At prompt “Serial ON?”, select ENT
3. Verify COM=1.8.0.9600 followed by ENT
The software allows you to run the instrument in several modes, depending on the capabilities of the instrument. Selecting a model that says DR informs the software that the instrument is a reflectorless (Direct Reflex) model, and the reflectorless EDM mode will be made available.
Settings/Search (Station)
If the instrument is not robotic or you want to operate it as a standard total station, the Station mode should be used.
- EDM Mode: Allows you to specify the EDM measurement setting as one of the following types:
Standard: Standard EDM mode.
Fast: Fast Standard EDM mode.
Reflectorless: Reflectorless EDM mode (DR Models).
- Turn to point in stakeout: Turns the instrument to the horizontal angle as computed to the stakeout location specified.
- Turn to vert. point in stakeout: Turns the instrument to the vertical angle as computed to the stakeout location specified. This option is not typically used unless a true elevation is known for the stakeout location specified.
Settings/Search/Remote (Direct Robotic)
This mode works exactly as the GeoRadio mode except a cable must be used in lieu of the radio. For this mode,the instrument must be robotic and be operating in the Remote mode with the faceplate removed.
- EDM Mode: This selection allows the user to specify the EDM measurement setting as one of the following types:
Standard: Standard EDM mode.
Fast: Fast Standard EDM mode.
Reflectorless: Reflectorless EDM mode (DR Models).
- Guide Lights: This sets the track lights to one of the following options:
Off: Turns off the track lights.
Low: Turns on the track lights on low power.
High: Turns of the track lights on high power.
- Allow Weak Signal: This will allow the instrument to return a distance when the signal is weak.
- Always Initialize Compensator: This will reset the compensator every time the instrument is restarted.
- Search on Read: This setting will force the instrument to perform a search before initiating a reading if the instrument is not locked on the prism.
- Diode Backsight: This setting allows the user to specify if the backsight has an active diode prism or not.
- Horizontal/Vertical Range: These input boxes allow the user to specify the range to search for the prism when a search function is initialized.
- Minimum/Maximum Distance: Determines the range by distance that the instrument will search for or track a prism.
- Standard Deviation: Defines the allowable standard deviation of the instrument readings.
- Search When Lost Lock: This setting will force the instrument to begin searching for a prism as soon as lock is lost.
- Turn Off Instrument: Turns off the instrument.
- Initialize Instrument: Turns on the instrument and initializes the instrument.
GeoRadio Settings (Remote)
These settings are accessed by selecting GeoRadio as your communication type and pressing the Configure button. This mode works exactly the same as the Direct Robotic mode, except a GeoRadio must be used in lieu of the cable. The instrument must also be robotic and be operating in the Remote mode with the faceplate removed. The only additional settings are for the GeoRadio itself.
- Channel: Specifices the channel of the GeoRadio.
- Station Address: Specifies the station address of the GeoRadio.
- Remote Address: Specifies the remote address of the instrument's radio.
Putting the 600 in the “Remote Mode”
- # Power the 600 on.
- # Answer the initial questions.
- # If you have not selected the Radio Channels and Address, do the following:
- # Press <Menu>.
- # <1> for Set.
- # <5> for Radio.
- # Select Channel (1-8).
- # Select Station Address (1-99).
- # Select Radio Address (1-99).
- # Press <RPU>.
- # Press <3> for Remote.
- # Press <1> for OK.
- # Press <No> for Sector.
- # Press <No> for Measure Ref Object.
- # Press any key when prompted. You do not have to remove the keyboard as prompted unless you are using the Direct Robotic option instead of GeoRadio. SurvCE will control the total station.
Contents Index
This series covers most of the current Leica total stations such as TPS 100, TPS 300, TPS 700, TPS 700 auto, Builder, TPS 400, TPS 800, TPS 1000 (including TC1010 and TC1610,) TPS 1100,and TPS 1200. For the older 600 and 900, turn off ATR and use the TPS 100/300 configuration. Many of these units include the “motorized” option. Some settings may vary by model.
- Comm Setup: Default settings for these instruments are a baud rate: 19200, none parity, Char Length: 8 and Stop Bits:1
- Instrument Series: Instruments supported are TPS 100, TPS 300, TPS 700, TPS 700 auto, Builder, TPS 400, TPS 800, TPS 1000 (including TC1010 and TC1610,) TPS 1100,and TPS 1200
- Read Method: The available read methods are Fast, Tracking, User-Defined, and Reflectorless. The default setting is Fast. The "Standard" option produces a 3-second reading while the “Fast” setting produces a 1-second reading. One application of Reflectorless is to toggle between a 0 prism offset (shooting a rock face or brick wall) versus shooting a prism with a non-zero prism offset. When set to Reflectorless, the rod height and prism offset automatically change to zero. When returned to Standard, the previous non-zero prism offset is recalled, and the original rod height is restored. Turn to Point for stakeout and PowerSearch are disabled in Reflectorless mode. The Read Method (Std, Fast, Reflectorless) will appear in the upper right of the graphic screen for most types of Leica total stations, in commands such as Store Points, Stakeout Point, etc.
- Foresight/Backsight Prism Offset: Here is the list of standard prism offsets. Note that Leica prisms default zero to equate to -34.4 mm. So a prism offset of 34.4 equals a zero “net” offset. Whenever a prism constant is changed, a note is written to the raw (RW5) file. When you select one of the prisms from the list (Circle, Mini, etc), the value that is shown in parenthesis is the actual value sent to the instrument. i.e. 0.0 for Circular, 17.5 for Mini. If you select "30mm" or "40mm", - 4.4 and 5.6 are sent, respectively (30-34.4 and 40- 34.4). You may also type in any value you choose. In this case, we will send that value exactly, unmodified, to the instrument.
- 23.1 (360): Leica Model
- 4.4 Mini (360)
- 34.4 (0mm)
- 0.0 (circle): Standard Leica round prism.
- 17.5 (mini): Leica mini prism.
- 34.4 (ReflTape): Equates to zero offset (wall, surface).
- 4.4 (30mm): Other manufactures (Sokkia, Seco).
- -5.6 (40mm): Other manufacturers.
- Laser Pointer: Ideal for indoor or dark evening surveying, this feature causes the instrument to emit a red beam. It is often used when doing reflectorless work and makes a red mark on the wall, floor or object being surveyed. This is usefule for confirming the position prior to the shot. The beam should not be directed into someone’s vision or eye.
- Motorized: When this option is disabled, many other options will also not be available. These options are ATR, Power Search, Turn to Point in Stakeout, and Turn to Vertical point in stakeout.
- ATR (Auto Target Recognition): For the TPS 700, TPS 1000 and TPS 1100, this option will find the prism after you point in the approximate direction. It searches over a fixed range of motion and detects all prism types and locks on to the exact center of the prism. Saves “dial in” time.
- Power Search Enabled: The Power Search option can be purchased with all motorized Leica total stations. This option activates the “PowerSearch” button in the “banner line” at the top of the survey and stakeout screens. When Power Search is pressed, the total station will typically find the prism in 10 seconds regardless of the direction it is initially pointed. If it has found one prism and you hit “Power Search” again, it will leave that prism and find the next one. If you have only 2 prisms on the job (foresight and backsight), it will conveniently rotate from the foresight to the backsight and back again each time it is pressed.
- Turn to Point in Stakeout: This option should always be enabled with a motorized total station. In stakeout (with the exception of slope staking), the program knows the angle and distance to turn. When enabled, this feature will automatically rotate to correct horizontal angle for the stake point. When on, the associated "Turn to Vertical Point in Stakeout" option will also be made available. Turn to Point in Stakeout is disabled when in Reflectorless mode, since staking out should require the certainty of a prism placed vertically over the target point.
- Turn to Vertical in Stakeout: When auto-turning to stakeout points, you have the option to turn horizontally but not vertically. If “Turn to Vertical” is disabled, you would need to manually dial in the vertical position of the prism in stakeout. However, if rod heights are unchanging, this feature can be enabled, and will turn the gun to the correct vertical position as well, factoring in the current rod height setting.
For Leica TPS equipment that offers the reflectorless option, screens such as Store Points and Stakeout now have a handy icon which, when toggled, switches from non-reflectorless to reflectorless and back. The button appears in both the graphics and text modes of these screens. Rod heights and prism constants will automatically be adjusted when switching from one mode to the other.
Leica 1200 Robotic
The new Leica robotic total station requires the activation of the “Extended GeoCOM” option before it will allow the use of third party data collection software (i.e. SurvCE or Carlson Field).
- Activation Information: The following information was provided by Leica in document Su11-05G.
TPS1200 Instruments (TCA, TCP, TCRA, TCRP) require a special key code to operate in Robotic mode when using an AllegroCE/RCS running SurvCE Version 1.5. The following table lists the part number for the code:
Product Part Number Description
TPS1200 734754 GeoCOM Robotics License
Note: When ordering a TPS1200 Robotic Instrument, AllegroCE/RCS and SurvCE, you must order part number 734754 – this is a no charge item.
- Procedures for Checking Activation Status: A simple way to determine whether the “Extended GeoCOM” option is activated is to enter the Robotics dialog of SurvCE and attempt a power search. If the instrument communicates, but the power search feature fails, the "Extended GeoCOM" option is not activated. If you suspect that this is the case, you can verify that the feature is on in the instrument using the following steps:
- Power on the instrument.
- Select the “User” button on the keyboard.
- Select the F3 button for “STAT”.
- Select list item number 3 for “System Information”.
- Use the down arrow key to scroll to the bottom of the “Instrument” page.
- Verify that “Extended GeoCOM” is on.
- Defining the Port: The Leica 1200 needs to know that you intend to use the GeoCOM interface through the external port. The following steps will set the Leica to communicate with SurvCE:
- Power on the instrument.
- Select “Config”.
- Select menu item 4 for “Interfaces”.
- Arrow down to “GeoCOM Mode” and select F3 for “Edit”.
- Select F5 for “DEVCE”.
- Select “RS232 Geocom”
- Select F3 for “Edit” and verify the communication settings.
- Baud Rate: 19,200
- Parity: None
- Data Bits: 8
- Stop Bit: 1
- Select F1 for “STORE”.
- Select F1 for “CONT” and verify the following option on the GeoCOM Mode page:
- Use Interface: Yes
- Port: Port 1
- Device: RS232 GeoCOM
- Protocol: RS232 GeoCOM
- Select F1 for “CONT”.
- Verify that the only device active is RS232 GeoCOM and select F1 for “CONT”.
- Prediction Settings: The Leica 1200 has several prediction modes for when the instrument has lost lock. The following are the recommended settings while using SurvCE:
- Select 3 for “Manage”.
- Select 5 for “Configuration Sets”
- Pick New or Edit (Recommend New for First Time)
- New - Input Name, Desc and Creator Initials then F1 Store/Cont
- Select F1 for “CONT” 8 times until the "Automatic Prism Search" screen appears.
- Select the down arrow one time and set "After Prediction Search With:" to "No Search" by tapping the right arrow key one time.
- Select F1 for “CONT”.
- Select F1 for “CONT” 2 more times until the "Interfaces" screen appears.
- Select the down arrow key to highlight GeoCOM mode and press F5 for “Use”. Make sure no other mode is set. To toggle off any other mode highlight and press F5 for “Use” to toggle off.
- Select F1 for “CONT” 5 times to save and exit to the Main Menu.
TC1010/1610
For the Leica TC1010/1610 series instruments, it's important that the following settings are true:
- Communications Settings (SurvCE & Instrument): 9600,7,even,1
- Communication Mode: Make sure you set the instrument to communicate RS232 mode, not module.
SurvCE Settings
- Instrument: Leica TPS Series
- Instrument Series: TPS 1000/1100
Make sure all of the toggles in the settings dialog are off.
Contents Index
This series covers most of the current Leica standard total stations including the TPS 1000, TPS 1100 and TPS 1200 series. For best results, set the instrument to Geocom Online mode. From the Main Menu, go to Configuration/Communication Mode/GeoCom Online Mode.
Comms
The default communication settings are baud rates 19200, Parity None, Char Length 8, and Stop Bits 1.
- Wireless Connection: Using the Juniper Allegro CE/RCS, a built-in radio modem and internal antenna is included which permits wireless communication with the robotic total station when using the RM2410 radio. This wireless connection is through the Leica propriety radio and does not involve Bluetooth per the Comm Setup screen. The Comm port for the internal radio on the Allegro is COM 3. For one-man operation, the pole and prism become “freed” from wire connection and can be placed anywhere for a shot or reading, with the process driven “remotely” by the data collector communicating with the robotic total station.
Settings/Search
- EDM Mode: Available methods are Standard (1.5 to 2 seconds), Fast, and Reflectorless. In all modes of data collection, you are in “Rapid Tracking” mode. Clicking that icon goes to the “No Distance” or “Tracking Only Mode” (no distance measurements). Avoiding taking distance measurements will save battery usage. So the “Dist” button refers to the selectable mode you will “go to,” not the mode you are currently in. In Rapid Tracking mode, the store icon will always take a “Rapid Tracking” shot, and pressing enter will take a Rapid Tracking shot if Enter is configured to Store only (to mimic the store icon). Pressing the read icon will always cause configured reading to be taken, as will Enter when set to Read and Store. The next figure shows the Rapid Tracking mode, which follows the movement of the prism by taking rapid distance measurements, much like RTK GPS.
- Foresight/Backsight Prism Offset: This drop down menu provides a list of standard prism offsets. Note that Leica prisms default zero to equate to -34.4 mm. So a prism offset of 34.4 equals a zero “net” offset. Whenever a prism constant is changed, a note is written to the raw (RW5) file. When you select one of the prisms from the list (Circle, Mini, etc), the value that is shown in parenthesis is the actual value sent to the instrument. i.e. 0.0 for Circular, 17.5 for Mini. If you select "30mm" or "40mm", we send - 4.4 and 5.6 respectively (30-34.4 and 40- 34.4). The user may also type in any value they choose. In this case, we will send that value exactly, unmodified, to the instrument.
- 23.1 (360): Leica Model
- 4.4 Mini (360)
- 34.4 (0mm)
- 0.0 (circle): Standard Leica round prism.
- 17.5 (mini): Leica mini prism.
- 34.4 (ReflTape): Equates to zero offset (wall, surface).
- 4.4 (30mm): Other manufactures (Sokkia, Seco).
- -5.6 (40mm): Other manufacturers.
- Guide Lights: This setting causes the instrument to show flashing lights. This makes it easy to tell when the instrument has turned towards you in tracking mode. Can be set to Off, On, or Auto.
- Laser Pointer: Ideal for indoor or dark evening surveying, this feature causes the instrument to emit a red beam. It is often used when doing reflectorless work and makes a red mark on the wall, floor or object being surveyed. This is usefule for confirming the position prior to the shot. The beam should not be directed into someone’s vision or eye.
- Power Search Enabled: The Power Search option can be purchased with all motorized Leica total stations. This option activates the “PowerSearch” button in the “banner line” at the top of the survey and stakeout screens. When Power Search is pressed, the total station will typically find the prism in 10 seconds regardless of the direction it is initially pointed. If it has found one prism and you hit “Power Search” again, it will leave that prism and find the next one. If you have only two prisms on the job (foresight and backsight), it will conveniently rotate from the foresight to the backsight and back again each time it is pressed.
- Work Area: This will define a limiting area for searching. This can speed up both the standard ATR Search and the PowerSearch. The Work area angle ranges apply to both searches. The Show button will show the two positions of the search window, first by moving immediately to Position 1. You will be prompted to press OK to see Position 2. Having defined a “window” of searching, Center will move that window to a new center position. You will be prompted to “Sight on Centered Position and Press OK”. The Define button prompts you to shoot the lower left and upper right positions, which are then displayed above under “Work Area”. If the Work Area is set to start at 0.0000 horizontal, for example, searching would send the instrument to the backsight point.
- Use ATR: When this feature is enabled, ATR (Auto Target Recognition) will be used when configured to standard or fast reading. When running the robotic in remote mode with ATR turned on, and when performing a “Set Angle and Read” in the backsight screen (a standard measured backsight), the ATR connection will be taken into consideration, so that the angle set is relative to the center of the prism, not necessarily the crosshairs of the instrument. The “Set Angle” and “Check Angle” functions will still be relative to the crosshairs.
Work Area Settings
More settings appear when you press the "Work Area Settings" button from the SEARCH tab.
The upper left of the screen controls the ATR Search, and the upper right controls the PowerSearch. The Work area angle ranges apply to both searches. The Show button will show the two positions of the search window, first by moving immediately to Position 1. You will be prompted to press OK to see Position 2. Having defined a “window” of searching, Center will move that window to a new center position. You will be prompted to “Sight on Centered Position and Press OK”. The Define button prompts you to shoot the lower left and upper right positions, which are then displayed above under “Work Area”. If the Work Area is set to start at 0.0000 horizontal, for example, searching would send the instrument to the backsight point.
Tracking
The instrument can also easily switchin between tracking and non-tracking mode from the store points screen by toggling the icon of the man in the upper right hand corner. In the image below, we are in tracking mode.
Next the icon has been toggled to non-tracking mode, which can be energy saving. No distances are taken in this mode.
- Tracking and Reflectorless: If you switch to reflectorless mode while the instrument is tracking, the instrument will be put in standby mode to allow use of the tangent screws. For all Leica robotic total stations and for the Leica 1200 Direct (TPS Series), the timeout for reflectorless mode is 30 seconds. You always have the option to Cancel from a reflectorless reading and if you do, the measurement will not be automatically re-initialized.
Leica 1200 Robotic
The new Leica robotic total station requires the activation of the “Extended GeoCOM” option before it will allow the use of third party data collection software (i.e. SurvCE or Carlson Field).
- Activation Information: The following information was provided by Leica in document Su11-05G.
TPS1200 Instruments (TCA, TCP, TCRA, TCRP) require a special key code to operate in Robotic mode when using an AllegroCE/RCS running SurvCE Version 1.5.
The following table lists the part number for the code:
Product Part Number Description
TPS1200 734754 GeoCOM Robotics License
Important Note:
When ordering a TPS1200 Robotic Instrument, AllegroCE/RCS and SurvCE, you must order part number 734754 – this is a no charge item.
- Procedures for Checking Activation Status: A simple way to determine whether the “Extended GeoCOM” option is activated is to enter the Robotics dialog of SurvCE and attempt a power search. If the instrument communicates, but the power search feature fails, the "Extended GeoCOM" option is not activated. If you suspect that this is the case, you can verify that the feature is on in the instrument using the following steps:
- Power on the instrument.
- Select the “User” button on the keyboard.
- Select the F3 button for “STAT”.
- Select list item number 3 for “System Information”.
- Use the down arrow key to scroll to the bottom of the “Instrument” page.
- Verify that “Extended GeoCOM” is on.
- Defining the Port: The Leica 1200 needs to know that you intend to use the GeoCOM interface through the external port. The following steps will set the Leica to communicate with SurvCE:
- Power on the instrument.
- Select “Config”.
- Select menu item 4 for “Interfaces”.
- Arrow down to “GeoCOM Mode” and select F3 for “Edit”.
- Select F5 for “DEVCE”.
- Select “RS232 Geocom”
- Select F3 for “Edit” and verify the communication settings.
- Baud Rate: 19,200
- Parity: None
- Data Bits: 8
- Stop Bit: 1
- Select F1 for “STORE”.
- Select F1 for “CONT” and verify the following option on the GeoCOM Mode page:
- Use Interface: Yes
- Port: Port 1
- Device: RS232 GeoCOM
- Protocol: RS232 GeoCOM
- Select F1 for “CONT”.
- Verify that the only device active is RS232 GeoCOM and select F1 for “CONT”.
- Prediction Settings: The Leica 1200 has several prediction modes for when the instrument has lost lock. The following are the recommended settings while using SurvCE:
- Select 3 for “Manage”.
- Select 5 for “Configuration Sets”
- Pick New or Edit (Recommend New for First Time)
- New - Input Name, Desc and Creator Initials then F1 Store/Cont
- Select F1 for “CONT” 8 times until the "Automatic Prism Search" screen appears.
- Select the down arrow one time and set "After Prediction Search With:" to "No Search" by tapping the right arrow key one time.
- Select F1 for “CONT”.
- Select F1 for “CONT” 2 more times until the "Interfaces" screen appears.
- Select the down arrow key to highlight GeoCOM mode and press F5 for “Use”. Make sure no other mode is set. To toggle off any other mode highlight and press F5 for “Use” to toggle off.
- Select F1 for “CONT” 5 times to save and exit to the Main Menu.
Troubleshooting: If your Leica robotic total station has any communication issues, it is typically a matter of verifying firmware and configuration settings. Investigate and note down the firmware version of the various components on your instrument.
Contents Index
Data Collector Model: Many of the older instrument could be set to operate as different models. These include T1000, T1600 and T2000 modes. Set SurvCE to match your instrument. Two different models are available for T1000 with a one-row keyboard, and T1000 with two-row keyboard. Choose the appropriate one.
Contents Index
This configuration covers such instruments as the Nikon 520, 521, 522 and 552.
Although the Nikon total stations have their own configuration, they also can be set to Sokkia emulation. If set to Sokkia emulation, they should be configured as Sokkia Set. In this mode, you can turn on the “2-way” communication mode. This enables the Nikons to “turn to zero” in stakeout (set out) mode. In this setting, when you stake point 10 and the angle right to turn is 75 degrees, 15 minutes, the instrument panel will display 75 degrees, 15 minutes, and as you turn towards the point, the display will count down to zero. So without looking at your data collector, you watch the screen until you obtain zero degrees — this means you are on target. In a sense, the performance of the Nikon total stations is enhanced in Sokkia emulation mode.
Nikon 800 Series
The 800 Series configuration will also apply to the older 700 series. To use that product the user must select SET mode on the instrument and have the connection speed set at 1200 baud then select the Nikon 800.
Trimble TS415
Users who own this instrument can use SurvCE by selecting the Nikon 800 Series configuration.
Contents Index
For Pentax instruments, select the "PTS3" checkbox if you are using a PTS3 series instrument.
PTS3 instruments will first send out the last reading before sending the current reading. For some users, you may wish to choose to record the 3rd reading for the most accuracy.
Pentax ATS Series
The following information outlines the settings for the Pentax ATS Series instruments.
This information was compiled using an ATS-105.
1. Power up the Unit & Level it up.
2. Set the baud rate in the instrument. Hold down the Blue “S” key and press the number 6 key in the upper right. This will open the Configuration Menu for Baud Settings.
3. Set the baud rate in SurvCE by selecting the Equip tab, and then select the Comm Setup button. SurvCE defaults to 1200 / None / 8 / 1. Match the Baud, Parity, Char Length & Stop Bits with whatever the instrument is currently set to.
4. Connect the data collector, hold down the Blue "S" key and press the "F5" button. This puts the Total Station into Remote Mode for use with external data collectors. [RM] blinks in the upper left corner.
NOTE: SurvCE has advanced options for setting the Read Method, Number of Readings & use of the instrument lights. Not all models or firmware support these features. If these options do not work, you might be able to update the firmware, or manually adjust the settings using the instrument.
Contents Index
The following information describes the various options available for the Sokkia Set total stations.
- 1-Way vs 2-Way: The 1-Way option mimics the operation of most total station instruments using SurvCE. The 2-Way option has the one big advantage of sending the angle to turn into the instrument during stakeout, so that looking at the instrument panel, you “turn to zero” to aim at the target point. It is recommended that Nikon instruments be run in Sokkia Set emulation mode, enabling the 2-Way communication.
- EDM Mode: Available methods are rapid and fine.
- Target Offset: Enter the prism offset here.
- Zero Hz Angle to Target: This option specifies whether or not SurvCE will set the horizontal angle of the total station to zero in the direction towards the stakeout point. When stakeout is completed, the horizontal angle is set back to the original value. This option only applies to Sokkia total stations or to total stations such as Nikon which have a “Sokkia emulation” mode.
The driver applies to all current Sokkia total stations, including the 110M when used in manual mode. It also applies to many non-Sokkia instruments which have a Sokkia or “Set” emulation mode, including Nikon, Pentax and Topcon. The advantage of Sokkia emulation is that the Sokkia driver includes a “2-way” setting that will upload configuration settings into the instrument such as units, prism constant and the backsight circle. Most important, for stakeout, the “2-way” setting will upload the angle to turn, so that you turn to zero to get on target. The Sokkia Series 30R is reflectorless.
The “On” key is the upper right, which takes you to the “Measure” screen where it is ready to work with SurvCE. Commands would not be accepted, for example, if you were in the “Config” screen. Use the instrument to activate reflectorless mode, and in SurvCE, be sure to set target height to zero. The gun will control prism offset in non-prism modes
Sokkia Motorized Series
This driver is necessary to utilize the motorized features of the motorized instruments. For example, in stakeout, it will turn to the point automatically. The motorized features will turn to the appropriate horizontal and vertical angle in most commands when the instrument is set to “Remote” mode.
Note that baud rates on motorized instruments must be set to 9600 in remote mode but are typically set to 1200 baud in direct mode. Change on the instrument and in SurvCE, Equip, Com Setup. The Settings options for the motorized instruments are shown below:
Joystick speeds are 1 to 6 (for arrow key response turning gun). For reference 6 is approximately 6 degrees per arrow press. Search types are Sight (field of view of gun, or 1 degree, 30 minutes or 10 meters at 100 meters), H Wide, V Wide and HV Wide. The wide views are 6 times field of view. Auto Search before Read finds the prism center exactly before taking a measurement (useful in Set Collection, for example, and in Stakeout). Run Remotely sets the left and right turning of the gun, referenced from the pole, and not from the instrument. This is distinct from left and right referencing for stakeout which refers to movement of the rod. For the Sokkia instruments with RMC search device, there are 2 buttons in the joystick screen for RC Search: “RC Left” and “RC Right”. Left and right will be determined by the Run Remotely setting.
Contents Index
The following information describes the various options available for the Sokkia Robotic total stations.
The instrument “Measure” screen should be shown on the total station in order to work with SurvCE. Commands will not be accepted, for example, if you were in the “Config” screen.
Note that baud rates on the Sokkia robotic must be set to 9600. The Settings options for the Sokkia robotic are shown below:
Joystick speeds are 1 to 6 (for arrow key response turning gun). For reference 6 is approximately 6 degrees per arrow press. Search types are Sight (field of view of gun, or 1 degree, 30 minutes or 10 meters at 100 meters), H Wide, V Wide and HV Wide. The wide views are 6 times field of view. Auto Search before Read finds the prism center exactly before taking a measurement (useful in Set Collection, for example, and in Stakeout). Run Remotely sets the left and right turning of the gun, referenced from the pole, and not from the instrument. This is distinct from left and right referencing for stakeout which refers to movement of the rod. Use RC Unit will enable the RMC search option in SurvCE.
Contents Index
The following information describes the various options available for the Topcon 800/8000 total stations.
Carlson SurvCE supports the Topcon 800 series (800, 802, 800A, 8000, 8200), when running in direct mode (measurements taken from the instrument, no radio connection to the prism). All 800 series instruments are motorized. The Topcon 8000 is a reflectorless unit. The Topcon 800A is motorized but not fully robotic. The 800AR is motorized and robotic. The Topcon 802 refers to a “2-second” version of the 800 series, for example.
To operate either direct or remote, press the Power button to turn the instrument on. After you level, the instrument will go through a motorized self-test. You obtain a 6-icon menu. To run direct, press F2 for Standard. This puts you in the measure screen. Note that in Direct mode, the Topcon 800 typically expects 1200, E, 7, 1 for communication, but 9600, N, 8, 1 in Remote mode. Note that the Topcon 820 and 8200 are a new series of instruments, where Topcon 822 indicates a “2-second” version of the 820 series. Running Direct, the Topcon robotic instruments that have the reflectorless option offer a handy, one-click reflectorless off-on icon at the top of the screen, as shown above in the discussion of the Leica TPS series where it also applies.
Direct
The following settings are presented by selecting the Topcon 800/8000 Direct instrument.
- EDM Mode: Choose between coarse, tracking, fine and reflectorless.
- Turn to point in stakeout: Turns the instrument to the horizontal angle as computed to the stakeout location specified.
- Turn to vert. point in stakeout: Turns the instrument to the vertical angle as computed to the stakeout location specified. This option is not typically used unless a true elevation is known for the stakeout location specified.
- Use CR/LF: If set, this must match the settings on the instrument.
- Auto Aim: This forces the instrument to lock onto the prism before a configured read. This is particularly useful when turning robotic sets. Auto Aim is not available in reflectorless mode.
Remote
This configuration works for the Topcon 800 series running in remote mode (radio link active, equipment operation driven from the prism). The optional RC unit, mounted on the prism pole, provides a “quick lock” feature for rapidly guiding the instrument to the prism. Additionally, the RC provides an alternative to radios allowing limited remote communication between the data collector and instrument. Be sure that the RC unit is pointed directly at the instrument before executing a “quick lock.”
To operate in remote mode, on the instrument obtain the 6-icon menu, press F1 for Program, F6 for More, then F3 for External Link. Press F2 to verify your currents settings, then hit Escape and press F1 to execute the remote settings.
Type: Topon Remote has two types in addition to the standard Cable, Bluetooth, and Radio options. The two additional types support RC Only communication using either Bluetooth or Cable. If RC Only is selected use the RC tab (described below) to specify which type of RC unit is in use.
- EDM Mode: Choose between Fine 0.1mm, Fine 1mm, Tracking 1mm and Tracking 10mm EDM settings.
- Guide Lights: Turns on and off the guide lights.
- Lock on Read: For the Topcon 800/8000 remote, there is a “Lock on Read” option which behaves similarly to the Auto Aim for direct mode, but is not as precise as Auto Aim.
- Search Pattern: Defines the pattern the instrument will search.
- Joystick Speed: This option defines how fast the instrument will turn when using the arrow keys to steer it.
The RC tab refers to the configuration of the RC unit. This tab allows you to specify which type of RC device is being used and whether there is a connection between SurvCE and the RC unit. If there is a connection please use the configure button to set communication parameters for the RC unit. Note that the RC “quick lock” function has a maximum range of 1500ft, while the two way remote communication is limited to 800ft.
Topcon provides distinct cables for radio communication and RC communication. The “Y” cable is used with radios and RC in combination, but is not required. You can press the yellow button on top of the RC to initiate a “quick lock”. The “Y” cable is not used for RC only communication. The advantages of using both radio and RC are range (works remotely over 800ft), speed (faster reading), and ease of operation.
Within SurvCE, go to Equipment, select Topcon 800 Remote, use default port and baud settings.
The recommended settings are as follows:
- Tracking: 10mm
- Search Pattern: Normal
- Track Sensitivity: High (best with Quick Lock)
- Search Scan Range: Middle (applies to APL1 only)
- Tracking Speed: Middle
- Joystick: Middle (this changes the response of the arrow keys)
- Vertical Range: 10
- Horizontal Range:10
- Wait Time (how soon it starts searching when you lose the link): 3 to 5 seconds (low traffic areas) and 120 (2 minutes, in high traffic areas)
- Guide Lights: User choice
SurvCE will track the prism in the fastest mode (10mm), then switch to configured reading when a shot is taken. Note, configured reading was also set to Tracking 10mm, which will take a nearly instantaneous shot. If configured for Fine (1mm), the shot will take 2-3 seconds. Here we have taken a foresight to point 3 and have moved in tracking mode to a new position, ready for a configured reading on point 4. “Configured Reading” shots are taken with Enter or R for Read. The “S” button will take a “fast read” or Tracking Read, no matter what the Configured Reading mode.
If using RC, Select QuickLock button. Otherwise, use arrow keys to turn the instrument, look for the 2 blinking lights (if track lights are turned on) and then tap Search. Above, we set the vertical and horizontal search ranges to 10 degrees. When you obtain lock, you will get 3 beeps from the RC, and in all cases, SurvCE will say Tracking, meaning you are locked on.
Pressing the Search icon does an RC “quick lock” search if you are configured for RC. Standby let’s the instrument hold its position and stop tracking allowing you, for example, to place the rod on the ground and drive a stake, then get on line again and use Search icon to regain the link.
With robotic total stations, commands such as Turn to Angle, Set Collection (choose “robotic” sets) and Check Backsight will turn robotically.
Set Collection Notes
Set Collection works best with radio linkage (radio alone or radio with RC), but has limited functionality in RC only mode. Robotic sets use BD-FD/FR-BR observation order. Note, “non-robotic” sets can be done with a robotic total station. The “Angle Only in Reverse Face” can be toggled on for faster Face 2 readings. “Auto Turn,” available for all observation orders but Robotic Set, will turn the gun automatically to all known points. An hourglass will appear when Robotic Sets is selected, during which time SurvCE initiates constantly streaming data. When in robotic Set Collection, an option to obtain the Robotic screen (search and joystick features) is available. After all sets are collected, the user is prompted whether to move to a new setup station, collect still more sets, or review the set data. Close this dialog and Set Collection is complete for that backsight and foresight.
Topcon APL1
This is an older Topcon robotic total station with excellent tracking.
It’s a larger instrument often used in construction and machine control applications. It communicates only by radio with the 2ASx type radios. You must set the Com parameters on APL1. You only have to do this once.
- Turn the APL1 on.
- Press <Menu>.
- Press <F1> for Parameters.
- Press <F3> for COM.
- Press <F3> for Terminate.
- Select ETX (ONLY) and press <Ent> to accept.
- Select F2 for Transfer Speed.
- Select 9600 and press <Ent> to accept.
- Select F1 for Bit Format.
- Set to BS, S1, and NONE, Press <ENT> to accept.
Putting the APL1 in the “Remote Mode”:
- Turn the APL1 on.
- Press <Menu>.
- Press <F3> for Remote.
- Press <F1> for Remote.
The total station is now in the Remote Mode.
Contents Index
Most standard Topcon total stations will work configured to Topcon GTS Series. This includes the Topcon 200,300,600,700,2000 and 3000 series instruments, and newer models such as the Topcon 230 (which uses Bluetooth wireless communication). This driver does support the reflectorless capability of the “thousand” series instruments (Topcon 2000 and 3000, for example). Typical baud rates for instruments in this group are 1200, E, 7, 1.
Topcon 200 Series
This is another option that can be tried when the GTS Series or other configuration does not communicate. It uses a different speed and mode of linkage.
Topcon 300/600/700/2000
Similar to the Topcon GTS Series, these drivers offer the reflectorless option. Typical baud rates for instruments such as the Topcon 303 and Topcon 313, for example, are 1200, E, 7, 1.
Topcon GTS 3/3B Series
This driver supports the older Topcon GTS 3 and GTS 3B standard total stations. Some of the GTS Series Topcon instruments offer Reflectorless, and in stakeout routines and Store Points (both graphics and text modes), there is a convenient reflectorless icon at the top of the screen to turn on/off reflectorless and show current status. (See discussion of Leica TPS above.)
Contents Index
The first time into this selection, as with most other setup procedures, the program shows the Comms Setup screen.
There is no Configure Base, Configure Rover or Receiver Utilities for Allen-Osbourne. SurvCE reads the NEMA string characters and all of the setup is done on the instrument itself.
Contents Index
This GPS system is typically used for GIS-type surveys with 1 to 3 meter accuracy. Corrections are obtained from Omnistar, WAAS, U.S. Corps of Engineers beacons, or by RTCM message string from an RTK unit. The rover setup offers the ability to set elevation mask and the DGPS Max Age.
Contents Index
Using DataGrid with SurvCE
DataGrid GPS can be connected using either a bluetooth or cable connection. The GPS switches to bluetooth communications when the cable is disconnected and the receiver is powered on. DataGrid receivers communicate at a baud rate of 115200. DataGrid uses ARWest UHF radios for RTK corrections.
Connecting with Bluetooth
To use DataGrid GPS in bluetooth mode remove data cables prior to powering on the receiver. The GPS will automatically switch over to bluetooth. No PIN is required for bluetooth communications.
Radio Configuration
DataGrid uses ARWest UHF radios for RTK corrections. The base GPS has an external radio connected to a radio port on the receiver and the rover uses a built in radio. DataGrid uses one message type for RTK corrections. RTK message selection in SurvCE will show the default message selection and be greyed out. Radio channel selection displayed on the GPS unit and is selectable on the unit. Setting the radios to channel 0 will set the radio selection to an automatic mode.
Contents Index
Default values in Comm Setup are 9600, Parity None, Char Length 8, Stop Bits 1. These can be set by hitting “Defaults”. For the GX1200 series GPS, the default baud rate is 115200.
ATTENTION:
For Leica 1200 GPS units, only firmware versions 2.12 and higher are supported!
GPS Base
This command opens the Base Configuration dialog.
- Base Antenna: This option allows the user to specify the antenna in use. The most common setting for the base antenna is AT502 Tripod type.
- Antenna Height: Input the base antenna height. The AT501 Tripod, AT502 Tripod, AT503 Tripod and AT504 Tripod settings will all prompt to “Measure to Base of 36cm Height Hook”.
When the height hook is used, the Antenna Height is measured down to the hub and tack elevation from the fixed mounting position of the height hook. The measurement is typically in meters, so if you are configured to units in feet, you can enter the Antenna Height in meters with the “m” suffix, as shown above, and the program will do the conversion automatically. You can omit the “m” suffix if you are configured to metric units.
Other Antenna settings for Leica GPS are AT201, AT202/302, AT202/302GP, AT303, AT501, AT501 Pole, AT502, AT502 Pole, AT503, AT504, SR299/399 Internal, AX1201, AX201 Pole, AX1201 Tripod, AX1202, AX1202 Pillar, AX1202 Pole, AX1202 Tripod and “Other”. In all these cases, the antenna height is measured from the ground elevation to the base of the antenna (the “base” is where it would rest if you removed it and placed it on a table—the “base” is the lowest point).
- Elv Mask: This specifies the cutoff vertical angle above the horizon. Any satellites below this angle will be left out of calculations. An elevation mask of 10 degrees is typical. It is advisable to use some elevation mask between 5 and 15 degrees. Satellites low to the horizon can actually degrade the resolving of the GPS position.
- Log Static Data to PC Card: This option will log static data in binary form to the PC Card in the GPS receiver whether or not you choose to conduct RTK GPS work. The static data can be processed using the Leica SKI-Pro program.
- Use Glonass: This option will only apply for System 1200 instruments that support Glonass.
GPS Rover
This command is used primarily to set the appropriate antenna height and antenna type for the rover. Leica typically offers a 2-meter pole, so for antenna height, the most common entry is 2m or 6.5617 feet. The default antenna is the AT502 Pole.
- Antenna Height: Input the rover antenna height. The AT501 Tripod, AT502 Tripod, AT503 Tripod and AT504 Tripod settings will all prompt to “Measure to Base of 36cm Height Hook”. When the height hook is used, the Antenna Height is measured down to the hub and tack elevation from the fixed mounting position of the height hook. The measurement is typically in meters, so if you are configured to units in feet, you can enter the Antenna Height in meters with the “m” suffix, as shown above, and the program will do the conversion automatically. You can omit the “m” suffix if you are configured to metric units. Other Antenna settings for Leica GPS are AT201, AT202/302, AT202/302GP, AT303, AT501, AT501 Pole, AT502, AT502 Pole, AT503, AT504, SR299/399 Internal, AX1201, AX201 Pole, AX1201 Tripod, AX1202, AX1202 Pillar, AX1202 Pole, AX1202 Tripod and “Other”. In all these cases, the antenna height is measured from the ground elevation to the base of the antenna (the “base” is where it would rest if you removed it and placed it on a table—the “base” is the lowest point).
- Elv Mask: This specifies the cutoff vertical angle above the horizon. Any satellites below this angle will be left out of calculations. An elevation mask of 10 degrees is typical. It is advisable to use some elevation mask between 5 and 15 degrees. Satellites low to the horizon can actually degrade the resolving of the GPS position.
- Log Baseline Data: This option stores raw vector data and Cartesian coordinate data for both the base and the rover and stores to the SurvCE data collector, in the “Data” directory. The file will be Jobname_SKI.ASC, depending on the name of the coordinate file. This vector file can be further processed in the Leica SKI-Pro program.
- Use Glonass: This option will only apply for System 1200 instruments that support Glonass.
- Rover Antenna: This option allows the user to specify the antenna in use. The most common setting for the rover antenna is AT502 Pole type.
- Base Antenna: For best results, specify here the type of antenna used at the base.
Contents Index
The Leica System 50 gets its corrections from the Corps of Engineer’s beacons (free) or you can sign up for an annual subscription and pick up corrections from the Racal satellite at a rate of approximately $800 per year. You would need to order a special part with your GS50 system to read the satellite corrections. Though the Corps beacons are free, they are not available everywhere, and coverage is typically up to about 100 miles from each beacon. There are also line-of-sight issues, and you can “lose” the Corps beacons when in deep valleys, for example. Typical accuracies are 0.3 to 1 meter horizontal and 1 to 2 meters vertical. Configure Base, Configure Rover and Receiver Utilities do not apply, but the Localization command can be used to translate (1-point) or transform (multi-point) from the configured coordinate system to local coordinates. It is still important, under Job Settings, GPS tab, to set the correct Transformation (eg. NAD83) and Zone (eg. KY North) so that the Lat/Longs are converted to coordinates on the local system.
Contents Index
Always connect the data collector to COM1 on the Navcom receiver. The baud rates are searched after selecting Navcom in the Instrument dialog. The receiver model is automatically detected. Models that start with SF are capable of Starfire, but that does not mean that the Starfire license is active. Models that are capable of RTK have “RTK” put after the model name.
Configure Base
GPS Rover
RTK Tab
- Device: This list contains the supported devices that deliver or receive RTK messages, such as a radio or IP modem. If an External Radio is selected, the user will need to specify the Port, Baud, Parity and Stop Bits that the radio manufacturer requires. For internal radios, SurvCE will detect the proper settings.
- Network: This list allows you to configure and connect to various networks (e.g. NTRIP).
- Message Type: You must select the RTK message type that you wish to broadcast and receive. This is the format of the RTK message string that is either sent from the base or received at the rover.
- Base ID: This is typically used to isolate paired devices. The user specifies that the base it ID 1, then the rover should be set to only listen to ID 1 so that other base station that might be in the area do not interfere.
- Send Rover Position to Network: This will output a NMEA GGA message for networks that require it.
Navcom GPS handles “QuickStart”. When QuickStart is used, RMS values in Monitor and elsewhere will be displayed as “0.0” as valid numbers will not be reported from the receiver in this mode.
When configuring the rover -- even if the message “Failed to clear Navcom base position” appears -- the software will continue to configure the rover. This message should not affect the operation of the rover.
There are three sets of three LED's on the front panel of the Navcom receiver. The GPS lights indicate the quality of the receiver's GPS position reading. One or more base lights will be on if the receiver is acting as a base. These lights will also indicate the RTK message type being broadcast. When functioning as a rover, all base lights should be off. The number of link lights indicates the strength of the signal the receiver is getting from a base. Blinking link lights, or no link lights, indicates that a base has not been found. For a full description of the meanings of these LED's, read below and also consult your Navcom User's Manual.
Navcom Receiver LED Lights
NavCom receivers have three groups of LED lights labeled LINK, BASE and GPS. Each group contains a green, amber, and red light. They are very useful for quickly understanding what state the receiver is in.
GPS LED Lights
Whatever GPS LED lights are on, they blink at the rate of position calculation (1Hz, 5Hz, etc.). If the red LED is on then there are not enough satellites to calculate a position. The amber LED blinking by itself indicates that a non-differential position is being calculated. Blinking green and amber means there is a differential position (WAAS, DGPS, Starfire, or RTK Float). If the receiver has Starfire capability, then when the green LED is the only GPS LED blinking, the receiver has a Starfire position. If the receiver does not have Starfire, the single green LED indicates RTK Fixed mode. If the receiver has both Starfire and RTK ability, then a single green LED indicates either Starfire or RTK Fixed mode.
Base LED Lights
The Base LED lights blink at the rate RTK corrections are being sent. If the receiver is configured as a rover, all Base LED lights will be off. Which color of LED is blinking depends on the RTK correction format being sent. Green indicates Navcom proprietary format, amber indicates CMR and red indicates RTCM.
Link LED Lights
Carlson Software programs the behavior of the Link LED lights to depend on whether the receiver is configured as a base or rover and whether using an internal or external radio for RTK corrections. The following table summarizes the possible configurations:
|
|
Base
|
Rover
|
|
Internal Radio
|
LED’s off
|
Signal Strength
|
|
External Radio
|
Sent correction
|
Received correction
|
When using an internal radio on a rover, the LED’s show radio signal strength. Full strength is shown by all Link LED’s being on and not blinking. As signal strength fades, The green LED will start blinking then turn off, then the amber LED will start blinking and turn off, then the red LED will blink when signal is lost.
Every time a correction is sent or received when using an external radio, a Link LED blinks. The color of the Link LED that blinks depends on the RTK correction format. Green indicates Navcom proprietary format, amber indicates CMR and red indicates RTCM.
Troubleshooting
Not able to establish connection to receiver
If the data collector is connected to COM2 and configures COM1 to receive CMR corrections, the receiver will no longer recognize commands on COM1. To correct the problem, connect the data collector to COM2, go to the Configure Rover window, set the correction type to Navcom and press OK. Now connect to COM1, go to the Comm Setup window and press OK. It will then search through the baud rates to find the right one.
Unable to update Navcom firmware
A common problem people have when updating the firmware on the Navcom is they connect the computer to COM1 on the Navcom instead of COM2. They must connect to COM2 to update the firmware. The transfer will go faster if they set COM2 to run at 115200 baud before starting the firmware update utility.
Contents Index
This GPS configuration is typically used to pick up the standard, commonly output NMEA string from a variety of receivers, including Ashtech MobileMapper CE, the Sokkia GPS01 Toughbook and some brands of Trimble equipment.
ASHTECH MobileMapper CE
To use the internal GPS of the MobileMapper CE unit from Ashtech, set the following:
Instrument
NMEA GPS Receiver
Communications
Port Number: COM2
Baud Rate: 57600
Parity: None
Char Length: 8
Stop Bits: 1
Configure Reading
Make sure that you toggle off the option to Store Fixed Only.
Sokkia GPS01
The Sokkia GPS01 Toughbook, for example, has an integrate L1 GPS receiver using WAAS for corrections and has accuracies of 1 to 2 meters. That same unit can be connected to real-time GPS or total stations and therefore functions as a dual-use device, locating on-the-ground positions (Lat/Long, state plane, UTM) and permitting standard precision surveying. The GPS receiver is powered on whenever the Toughbook 01 is on, and uses COM3 as the GPS port. Note the “stabilizer bar” which effectively secures the com port connection for use in the field.
Some low-accuracy (10 to 50 meter) GPS outputs NMEA Lat/Long data by default and has no accurate “setting” or method. Alternately, certain accurate RTK brands of GPS, if setup with their proprietary equipment to run RTK, will transmit the NMEA string and allow GIS-CE to pick up the message from the rover receiver. For this reason, NMEA has no Configure Base, Configure Rover or Receiver Utilities option. It is a “plug and play” method, which will pull from the receiver whatever position it is outputting. That Lat/Long position will respond to the transformation defined in Job Settings, GPS and will also respond to any localization file to transform it further to local coordinates.
Contents Index
This is the driver for the original Sokkia Radian “real-time” GPS with centimeter accuracy. Sokkia Radian GPS, like all real-time, high-accuracy GPS requires a base receiver sending corrections to a rover receiver. Most commonly used GPS antenna types include the SK600 and SK502. All Sokkia GPS receivers will accept and transmit RTCM, RTCA and CMR message strings.
Contents Index
Using Septentrio with SurvCE
Septentrio PolarRx2 GPS is a 48-channel dual-frequency GNSS receiver. There are several variants for this GPS line supporting different features including SBAS, DGPS and GLONASS. SurvCE supports the general GPS functions of this unit.
Contents Index
The following information describes the various options available for Ashtech GPS.
SurvCE works with the following high precision, centimeter accurate RTK GPS equipment produced by Ashtech: Z12/Sensor, ZSurveyor, GG24, Z-Xtreme and Z-Max. SurvCE also works with the Ashtech Reliance USCG/DGPS RTCM sub-meter RTK GPS receivers.
Shown below is the front panel view of the Ashtech Z-Xtreme, as it appears in the top of the backpack.
Shown in the next photo is the cabling for the Z-Xtreme, looking at the back panel.
Configure Base or Rover
- Current tab - Model: You must specify the model of Ashtech equipment to be used.
- Receiver tab - Antenna Type: A pull down list that includes approximately 50 different antenna types. Shown in the below photo is the Geodetic 4 antenna.
- Receiver tab - Antenna Height: This is entered as a "vertical" or "slant" height in the current job units. The slant height is the distance from the base of the pole or from the “hub and tack” up to a mark or defined slant measurement point on the edge of the antenna (See NGS for more details). The vertical height is measured plumb, straight down from the base of the antenna (where it screws into the antenna).
- Receiver tab - Elevation Mask: This specifies the cutoff vertical angle above the horizon. Any satellites below this angle will be left out of calculations.
- Receiver tab - Log OBEN Data for Averaged RTK Readings: This setting specifies that the software will log the standard Thales OBEN file as specified by Thales during averaged readings.
- Ports tab - RTK Port: You must select the data port on the GPS receiver that is connected to the radio modem. The default setting is A. Changing this setting will change the internal setting of the receiver.
- Ports tab - Radio Type: This allows the user to specify the various supported radios.
- Ports tab - Message Type: You must specify the message type. For high precision centimeter RTK GPS, set this to Ashtech (CPD). For USCG/RTCM DGPS sub-meter accuracy, set this to RTCM.
- Ports tab - Baud: This setting allows you to change Pacific Crest radio baud settings through the receiver. The default baud rate is 9600. (Note: If there are communication problems with either port A or B on the Ashtech ZSurveyor receiver, turn off receiver and turn it back on with both keys depressed to reset receiver to factory defaults.)
For more information on this tab, see "Connecting GPS"
Configure Rover (Parameters)
- Multipath Type: You must specify this setting in order to filter out interference in the satellite signals caused by nearby objects.
- Dynamics: This setting is applied to all Thales equipment types with the exception of the Z-Max. Here you may specify the dynamics setting. Static is selected only when the Rover receiver is stationary. The default is Walking. When set to Static, the HRMS and VRMS values (measurements of accuracy) will fall to very low numbers (high accuracy), but lock will not hold unless the antenna is motionless. Static is recommended when the antenna and pole are secured by a tripod or bipod.
- Ambiguity Fixing Parameter: This controls the confidence level of fixed positions. The default is 99.0. At a lower confidence interval the system solves much faster. If the system incorrectly solves the position, then the position error will be much greater than the reported RMS value.
- Fast CPD: This option specifies whether or not the program will allow approximating the rover’s position if your position is lost briefly. Off is the default. Fast CPD is generally toggled on when Dynamics is set to Automobile.
Contents Index
Sokkia GSR 2700 IS - What do I do when I get the Bluetooth pass key prompt?
This receiver does not require a pass key. If you are prompted for one, do a factory reset on the receiver by holding the power key down until the message displayed is Factory Reset. Then turn the device off and back on again. In Carlson SurvCE, clear the receiver from the Bluetooth connections list and add it back in.
Sokkia Radian
This is the driver for the original Sokkia Radian “real-time” GPS with centimeter accuracy. Sokkia Radian GPS, like all real-time, high-accuracy GPS requires a base receiver sending corrections to a rover receiver. Most commonly used GPS antenna types include the SK600 and SK502. All Sokkia GPS receivers will accept and transmit RTCM, RTCA and CMR message strings.
Sokkia Radian IS
The Radian IS is an “integrated” GPS receiver with a fixed antenna type, the SK600. Antenna height on the integrated Radian IS with built-in SK600 antenna is measured to the base of the rubber bumper around the antenna. Sokkia provides a measuring tape that connects to the rectangular indentations for precise height measurement. A diagram of the phase center offset (antenna height) is included on the receiver. Similar “hook points” exist on all Sokkia antennas.
Sokkia GSR2600 GPS
The GSR2600 is a modular version of the Radian IS, with a variety of antenna types available. The Log Static Data routine in SurvCE will initialize the storing of raw data to the receiver. This raw data can be post-processed in Sokkia Spectrum Survey.
Sokkia Axis/Axis 3 GPS
The Sokkia Axis 3 is the current GIS-level GPS product from Sokkia and obtains corrections from Coast Guard beacons, WAAS and OmniStar. There is no subscription fee for beacons or WAAS, but there is for OmniStar. The subscription can be by month or year or any other time period (even “weekend” use). Accuracy varies on correction method used, but is typically sub-meter to 3 meters. For example, 0.5 meter accuracy (1.5 feet) is common with beacon corrections when located within 60 miles of a Coast Guard beacon. The Axis 3 is designed for GIS and environmental applications, which are effectively addressed by SurvCE through use of attributing on feature codes and through ESRI import and export features.
Contents Index
This configuration covers all Topcon GPS receiver types. Some of these receivers utilize Glonass satellites as well as the standard U.S. satellites. In the Configure Base routine for Topcon GPS, the firmware version of the receiver will be checked and the correct message for setting the base position will be sent according to the firmware version in use.
Note: Glonass refers to the Russian satellite constellation (Global Navigation Satellite System). There are approximately 24 U.S. satellites active (more will launch over time) and there are approximately 10 Glonass satellites currently active. A full “24 satellite constellation” is anticipated by 2006 for the Glonass satellites. With a minimum of 2 Glonass satellites available or “seen” by the base and rover receivers, satellite coverage is improved, and work is sometimes possible in canopy, urban or deep pit environments where non-Glonass receivers do not have coverage. All Topcon GPS receivers have a "stat" light on the front panel that flashes green indicating number of U.S. satellites and orange indicating the number of Russian satellites.
Comm Setup
- Port Number: This drop list allows the user to select the communications port of the data collector.
- This is a Bluetooth Port: This toggle allows the user to specify that the selected port number is in fact the communications port that the Bluetooth device in the data collector is assigned to.
- Find Bluetooth Port: This button will auto-detect the Bluetooth port number in most devices.
- Bluetooth Type: Select the manufacturer of the Bluetooth device if known. Typically, Socket will be the preferred brand and often the installed brand, but if the brand is not known, select Other.
- Baud Rate: Set this value to match the data baud rate of the GPS serial port. Typically this will be 115200 but may also be 9600 or 38400.
- Character Length: Set this value to match the data Character Length of the GPS serial port. Typically this will be 8.
- Parity: Set this value to match the data Parity of the GPS serial port. Typically this will be None.
- Stop Bits: Set this value to match the data Stop Bits of the GPS serial port. Typically this will be 1.
Bluetooth
In addition to the discussion of Bluetooth (wireless) connection found under the help subject Equip - Comm Setup, there are additional trouble-shooting considerations with Topcon Bluetooth.
- Note that the PIN for all Topcon devices is 11111.
- If the OAF file is not current the Bluetooth will not work. An OAF file is used by Topcon for the firmware of their receivers. With an expired OAF file, many features (including Bluetooth) will not work.
- Normally the Bluetooth port (usually B) must be enabled in the OAF file for the Bluetooth to work.
- It is possible to set the Bluetooth port baud rate. Normally it is 9600, 38400 or 115200. This can be checked from the “A” com port using GRIL (command manual for Topcon receivers) commands. The baud rate in the Com Setup should be the same.
Configure Base Station
- Receiver Type: You must select the receiver type (e.g. Hiper Lite).
- Antenna Type: You must select the Antenna Type (e.g. Hiper Lite). See the figure below.
- Antenna Height: This is entered as a vertical or “slant” height in the job units. The Vertical option is measured from the tip of the pole to the unit's ARP (For the Hiper series GPS units, this is the bottom of the unit where the pole screws in). Vertical is typically used for fixed height poles and tripods. For the Hiper series, the Slant option is measured from the point on the ground to the bottom edge of the square housing. This point is approximately 30.50mm higher than the ARP and is located at the bottom edge of the receiver's metal housing and is marked by a small arrow. For detailed information on antenna heights, please see http://www.ngs.noaa.gov/ANTCAL/.
- Elevation Mask: This value establishes the cutoff value above the horizon in degrees where satellites will not be considered.
Configure Base Radio
- Radio Type: There are two options available, PDL or Spread Spectrum. When using PDL, you must define the radio port, baud and RTK message type. When using Spread Spectrum, you only have to define the RTK message type. Most of the modern Hiper series units come with Spread Spectrum radios. When using PacCrest radios, a “TX” light blinks about every second indicating the radio is transmitting. The “RX” light would blink if you were getting interference.
- Radio Port: You must select the radio port. This setting on the TOPCON base and rover receiver is usually C. Data Port is always A when using a cable and B when using Bluetooth. When using Pacific Crest radios, TOPCON recommends the new PDL Pacific Crest radios. These must be set to 38,400 baud rate. TOPCON can also use Spread Spectrum radios, which work at 115,200 baud rate. The HiperLite GPS uses Spread Spectrum radios running at 57,600 baud. The standard Hiper uses Pacific Crest PDL.
- Radio Baud: This defines the over-the-air baud rate that the radio will use. In many cases, the user must know what the radio expects this setting to be based on the radio's firmware or pre-programming.
- RTK Message Type: You must select the RTK message type that you wish to broadcast.
Configure Rover Station
- Receiver Type: You must select the receiver type (e.g. Hiper Lite).
- Antenna Type: You must select the Antenna Type (e.g. Hiper Lite).
- Antenna Height: This is entered as a vertical or “slant” height in the job units. The Vertical option is measured from the tip of the pole to the unit's ARP (For the Hiper series GPS units, this is the bottom of the unit where the pole screws in). Vertical is typically used for fixed height poles and tripods. For the Hiper series, the Slant option is measured from the point on the ground to the bottom edge of the square housing. This point is approximately 30.50mm higher than the ARP and is located at the bottom edge of the receiver's metal housing and is marked by a small arrow. For detailed information on antenna heights, please see http://www.ngs.noaa.gov/ANTCAL/.
- Elevation Mask: This value establishes the cutoff value above the horizon in degrees where satellites will not be considered.
Configure Rover Radio
- Radio Type: There are two options available, PDL or Spread Spectrum. When using PDL, you must define the radio port, baud and RTK message type. When using Spread Spectrum, you only have to define the RTK message type. Most of the modern Hiper series units come with Spread Spectrum radios. When using PacCrest radios, a “TX” light blinks about every second indicating the radio is transmitting. The “RX” light would blink if you were getting interference.
- Radio Port: You must select the radio port. This setting on the TOPCON base and rover receiver is usually C. Data Port is always A when using a cable and B when using Bluetooth. When using Pacific Crest radios, TOPCON recommends the new PDL Pacific Crest radios. These must be set to 38,400 baud rate. TOPCON can also use Spread Spectrum radios, which work at 115,200 baud rate. The HiperLite GPS uses Spread Spectrum radios running at 57,600 baud. The standard Hiper uses Pacific Crest PDL.
- Radio Baud: This defines the over-the-air baud rate that the radio will receive. In many cases, the user must know what the radio expects this setting to be based on the radio's firmware or pre-programming.
- RTK Message Type: You must select the RTK message type that you wish to receive.
Configure Rover Parameters
- Position Update Rate: In Configure Rover, the RTK Calculation Mode should be set to Delay, which forces a fresh reading, as opposed to Extrapolate, which will project the next reading by your direction of movement, and may apply to difficult shots in tree lines.
- Ambiguity Fixing Parameter: This determines how tight the ambiguities of the RTK solution must be before a fixed position is achieved. It is recommended that High be used for greater accuracy.
- RTK Calculation Mode: In Configure Rover, the RTK Calculation Mode should be set to Delay, which forces a fresh reading, as opposed to Extrapolate which will project the next reading by your direction of movement. Extrapolate may apply to difficult shots near obstructions such as trees or buildings.
Receiver Utilities
- Power Cycle Receiver: Use this button to power cycle the receiver. At times this may help if communications fail and cannot be restarted by Configure Base or Rover.
- Restore Factory Defaults: Use this button to re-boot the receiver back to factory default settings.
- Clear Non-Volatile Memory: Use this option to clear the unit's non-volatile memory.
- Send Command to Receiver: This button allow the user to send command directly to the receiver if necessary.
- Set Base/Rover Radio: Use Set Base Radio and Set Rover Radio to be sure that both radios are on the same channel. Recommended settings are base on low “digisquelch” (low sensitivity) and rover on medium or high digisquelch.
- Set Satellite Status: This command enables you to “turn off” particular satellites, both U.S. and Russian. In SurvCE's Monitor/SkyPlot command, located on the Equip tab, the Sat Info screen displays the Russian satellites numbered 45 and up and the U.S. satellites numbered from 1 to 24.
- Initialize to Known Point: Use this option to speed up the initialization process.
Post-Processing
All Topcon GPS receivers can be used for post processing and will store raw GPS data on the on-board RAM in the receiver. The post-processing can be activated by the Log Static Data command found in the Survey menu of SurvCE. On every receiver, you can also activate logging purely through hardware by holding down the FN key, watch the light turn orange to green, then release. To turn off by hardware, press FN until the light turns off. Since SurvCE will prompt for antenna height, type and other parameters, it is recommended that software be used to initiate logging. Topcon logging files typically start off with the word “Log” followed by the date, and are post-processed using Topcon Tools. Topcon Tools will output a Rinex ASCII file of the logging data for use with programs such as NGS’s OPUS.
Contents Index
The Trimble GPS 4000 is an older series of GPS receiver. The panel on the receiver itself can be used on the Trimble 4000 to configure for RTK. There is no Configure Base or Configure Rover in SurvCE for the Trimble 4000.
Trimble GPS General (4700, 5700 and 5800)
This configuration is used for most current brands of Trimble GPS, including the Trimble 5700 and Trimble 5800. The Trimble 5700 is often used as a base in conjunction with the Trimble 5800, which has the wireless “Bluetooth” communication feature. To use the Bluetooth feature, the Trimble TSCe is outfitted with an adapter on one of its serial ports which includes the internal radio. For use with SurvCE, the standard serial cable is recommended. To use the cable, disable “Bluetooth”.
The Trimble 5800 with Zephyr antenna has a panel that includes an On-Off button at right.
There are three LCD lights. From left, the first round light is yellow and flashes or pulses at 1 per second when sufficient satellites have been acquired for RTK, and flashes quickly when insufficient satellites are available. The second round light is a pulsing green light indicating radio linkage. When the pulse is intermittent, radio connection is being interrupted. The third, rectangular light is green and indicates battery status. It is steady on when there is sufficient battery power.
Note on the Trimble 5700 that the power on-off button is on the right, the next two buttons to the left show the usage of battery 1 and an optional battery 2. Three LCD lights appear along the bottom left of the 5700 panel. The middle button pulses red and is a satellite indicator: steady 1 second pulse means good satellite reception and fast pulsing means insufficient satellites. The LCD to the left is steady on amber if static data is being logged to the receiver. When you configure the base with the Trimble data loggers, you can set it to do RTK with PPInfill, which will do both RTK and static logging. SurvCE can be used to configure the base or will drive the rover when the base has been configured by the Trimble data logger. A typical antenna usage would be the Zephyr Geodetic for the base (mitigates multi-path) and the Zephyr for the 5800 rover. Consult your Trimble reference manuals for more detailed information.
Trimble Pathfinder
This is another “GIS-level” receiver, which typically gets corrections from either a Beacon or a dedicated satellite in space (Racal), and has an approximate accuracy of 1 meter. An option to read OmniStar has been added. There is no Configure Base or Receiver Utilities option, but there is a Configure Rover option.
Contents Index
Contents Index
This command is used to configure the GPS radios and set the message type to use. This command is used to set radio configurations for both base and rover receivers. If SurvCE is used in conjunction with the Red Controller from Leica, a serial port to radio baud rate of 38400 is often pre-set. SurvCE should be set to conform to that baud rate. A useful feature of the Receiver Utilities is to verify the status of the receiver as either a Base or a Rover (bottom status line).
- Power On/Off Receiver: The receiver can be turned off and on in the command “Receiver Utilities”, option “Power On/Off Receiver”. The Configure Base and Configure Rover commands will typically turn on the receiver automatically. Sometimes, turning off and turning on the receiver can be used as a “troubleshooting” technique to clear conditions and start from a clean slate.
- Radio Type: The Pacific Crest PDL radio type is the default setting, operating at 38400 baud rate. Older Pacific Crest radios are often type RFM96W, defaulting to 9600 baud rate. Other options include Satel radios, Modems, RS232 and User Defined Modem. Phone numbers for cell modems will accept up to 49 characters. When using Freewave or Tait “spread spectrum” radios, the radio type doesn’t matter, but can be set to “User Defined Modem”. Baud rate for Freewave is often 19200 baud.
Connections: With Freewave and other spread spectrum radio linkages, communication must occur within a line-of-sight distance, typically no more than 2 to 5 kilometers except in very flat terrain. With PacCrest radios, the signal can “bend” somewhat, and achieve maximum distances of 10 kilometers, typically. Cell phone linkage allows corrections to be transmitted within the coverage of the cell phones themselves and maintains accuracy up to as much as 50 kilometers. Contact your Leica GPS vendor for appropriate cables for connectivity details. When you select a modem configuration, the “Set Radio Channel” button becomes “Connect Modem”, and when tapped, you are prompted for a Phone Number or IP address and port (for the rover to call the base). The base must also be hooked to a cell phone or modem. The base can actually be set to both cell phone and radio linkage, with the rover set to either cell or radio as preferred. The rover will go from autonomous to float (cell phones are communicating) to fixed with cell phones just like with radio linkage.
Note: Base and rover GPS receivers must have matching radio configurations. If cell phones are used for the rover, then the base must be configured for cell phone use. If PacCrest PDL radios are used on the rover, than PacCrest PDL radios must be used on the base. Also note that cell phone switching is made possible through the C icon or Alt C “on the fly” from commands such as Store Points or Stakeout Points. This is because of the availability of a “Utilities Tab” in Configure Reading when configured Leica GPS.
Reference Station: To obtain corrections from a reference station to a single rover, you typically must set to cell phone or modem linkage, depending on what is required by the reference station.
- Set Radio Channel: This is normally set to channel 0 or channel 1. SurvCE allows up to 16 radio channels (0 to 15). The procedure is to pick the channel, then tap “Set Radio Channel”. Radios on base and rover must be set to the same channel.
- Radio Ports: The Leica GPS receiver has 2 commonly used radio ports (ports 1 and 3). Port 2 may be used in rare occasions.
- Radio Stop Bits: Typically set to 1.
- Message Type: Standard setting is Leica Proprietary. Other message string options are RTCM (an industry standard) and CMR (Trimble message string). RTCM and CMR are used when it is necessary to communicate with non-Leica GPS.
- Radio Parity: Typically set to None.
Contents Index
- Configure RTK Device: Use this page to change your RTK data port settings. This can also be done during base or rover configuration.
- Check RTK: This tells the user why they aren’t in RTK fixed.
- QuickStart (Starfire Only): Starfire corrections often take some time to acquire high levels of accuracy. If you’re returning to a previously surveyed area, you can save time by storing a known position to a reference file. Then you can initialize the Starfire system with this position upon returning to the site by performing a QuickStart.
At the end of the first day, verify that you’re receiving Dual-Frequency Starfire corrections (RTG or WCT) by entering the Navigation Status utility. Enter the QuickStart menu, and press Read GPS. Be sure to physically mark this position in some way so that the exact position can be returned to later. When you have a GPS position, click Save to save the position to a reference file. When you return to the site, first ensure that you’re receiving dual-frequency Starfire corrections, and that you're set up on the position marked the previous day. Then enter the QuickStart menu and choose Load to select the previously stored reference file. Press Initiate to input the loaded starting position to the receiver. To disable an input position, press Disable. Note that if the input position is inaccurate, using the QuickStart routine will slow down the processing of acquiring an accurate position.
- Reset Receiver: Use this tool to reset your receiver (soft reset)
- Factory Reset: Use this tool to reset your receiver (factory reset).
The buttons available in Receiver Utilities depends on the capabilities of the receiver. If a Starfire license is not active, the QuickStart button is not shown.
Check RTK is a very useful tool. It tells the user why they aren’t in RTK fixed and, if connected to a base when pressed, it determines if the base is transmitting corrections, and if not, tells the user why. If connected to the rover, it tells the user if in RTK Fixed and if not, and it tells the user why. Configure RTK Device is the same as the Configure button in the RTK tab of the Base and Rover dialogs.
“QuickStart” allows the user to save a QuickStart point or to QuickStart from a previously saved QuickStart point.
Starfire and QuickStart
Starfire is a space-based GPS correction system capable of 10 cm horizontal accuracy. Vertical will be 1.5 to 2 times as much. It is kind of like WAAS on steroids. The positions that it calculates are ITRF 2000. This is different from the positions calculated in RTK surveys. Since the RTK survey is based on a base point on the ground and the Starfire position is a space based position, they do not match. A localization created from an RTK system cannot be used by a Starfire receiver. The localization must be created using Starfire positions.
It normally takes about an hour to get to the 10cm accuracy. The receiver does not have to be stationary during that time. QuickStart is a method of reducing the “pull in” time to 50 seconds. If a QuickStart point has been saved using the QuickStart dialog, it can be loaded and used to perform a QuickStart. Best results are obtained by performing the QuickStart 5 minutes after turning on the receiver.
Performing a QuickStart to point with a position that is wrong will increase the “pull in” time to 2-3 hours. It will start at the bad position and then drift toward the correct position. It is better to not perform a QuickStart if the receiver has already been on for 30-40 minutes.
RTK Extend™
Introduction
An industry first from Navcom, RTK Extend™ enables continuous RTK position accuracy during radio communication outages by utilizing Navcom’s global Starfire™ corrections. Traditionally, when an RTK rover loses communication with the base station, it is unable to continue to provide position updates for more than a few seconds, resulting in user down-time and reduced productivity. A Navcom Starfire receiver, operating in RTK mode, can transition to RTK Extend mode and maintain centimeter accurate positioning during communication loss for up to 15 minutes or in some cases even longer. RTK Extend allows the user to work more efficiently and without interruption, thus enabling them to concentrate on the work rather than the tools.
The Concept
Using a receiver capable of Starfire and RTK at both the base and the rover locations allows the receivers to compute Starfire and RTK solutions (or corrections) simultaneously. If a communication outage occurs and the rover stops receiving RTK corrections from the base station, the receiver automatically and seamlessly transitions to RTK Extend mode by employing the Starfire signal.
Using RTK Extend, the receiver is able to compute an RTK equivalent position for up to 15 minutes. If the receiver remains in RTK extend mode for more than 15 minutes, the position solution will slowly degrade to the typical 10cm accuracy of the Starfire system. Once the communication link is restored, the rover automatically switches back to the standard RTK solution. The break in communications and the seamless mode transition of RTK Extend is designed to go unnoticed by the user with the exception of the mode flag indicating the receiver is operating in the Starfire-aided RTK Extend mode rather than standard RTK.
How it Works
To enable the RTK Extend process, the base station must compute a Starfire solution and constantly difference this position against the known RTK base station position. This difference information is transmitted to the rover as an additional RTK message. The difference results from two different sources: 1) The Starfire system inherently operates on the ITRF coordinate system and the solution will differ for the known base station position if it was entered using a different coordinate system. 2) Because RTK and Starfire use different techniques to compute a position solution at any given time there will be a few centimeters difference between the two solutions. The rover uses this difference information to prevent any position jumps from occurring when transitioning into or out of RTK Extend mode such that the geodetic datum of the rover position will always be the same as the RTK base station position.
The RTK extend process works by continually forcing agreement between the Starfire and RTK rover solutions at every epoch while receiving a signal from the base station. Prior to initializing Starfire at each epoch, the RTK solution is modified by the delta received from the base station. By first applying the delta, Starfire is initialized to a true Starfire position but with a known offset from the desired RTK position.
When the system transitions to the RTK extend mode all that is required is to subtract the delta prior to outputting the position. Had the delta not first been applied to the RTK position prior to initialization, Starfire would immediately attempt to return to the correct Starfire position once it was no longer locked to the RTK position. In addition to the loss of accuracy that would result if the Starfire solution diverged from the RTK position there would also be a sudden position jump when the link to the base station was restored. Thus by making use of this additional information, the rover is able to extend RTK through position gaps that would normally result from loss of communication with the base station.
Setup
Setting up an RTK system to take advantage of RTK Extend involves very little additional effort. The Starfire-activated receiver at the base station is setup exactly the same as if it were a standard RTK receiver using an external communication link with the addition of two key steps:
- The unit will be configured to navigate as a Starfire™ rover in addition to operating as an RTK base station.
- The unit will be configured to output a third RTK message , namely Navcom’s binary 0x5D message, which carries the Delta between the fixed RTK position and the Starfire-aided navigation position to the rover.
The rover, being able to translate and adjust for the bias mentioned in item two above, is able to instantaneously QuickStart to the Starfire-aided navigation solution when standard RTK corrections are unavailable. While the receiver is navigating in Starfire mode, the position is flagged in its binary output indicating that the Starfire solution is actually “coasting” through an RTK communication dropout.
Frequently Asked Questions
Q: How long are the near-RTK level accuracies maintained if the communication link is lost?
A: To allow a Starfire receiver to work anywhere in the world, rather than just within a few kilometers of an RTK base station, unique processing techniques must be used and the typically obtainable accuracy is around 10 cm rather than the 1-2 cm obtainable with an RTK system. The errors that cause Starfire to fluctuate around the true position by a few centimeters change very slowly. As a result, once Starfire is initialized to a known position, it will stay within 1-2 cm of truth for many minutes, but within an hour or so will begin varying from the true position by a greater amount. Testing has determined that once initialized the Starfire position will stay within 1-2 cm of the true position for at least 15 minutes and in many cases even longer depending on the number of satellites visible and their geometry. Every time the receiver reestablishes the link to the base station and is able to compute an RTK position the 15 minute period is restarted. Thus RTK Extend will coast through several back to back outages as long as none of them are longer than 15 minutes.
Q: Does the base station send more than standard RTK messages to the rover?
A: Yes. The RTK Extend base outputs an additional correction which allows the rover to resolve any biases between the Starfire and RTK solutions. The rover makes use of this information to seamlessly transition between modes of operation.
Q: Can another manufacturer’s receiver or Navcom receiver without Starfire capability be used as a base station?
A: Entering precise ITRF00 Starfire coordinates for the base position will allow the rover to make use of the RTK Extend feature although at a reduced level of performance. In this mode of operation, RTK Extend may only be able to coast through short outages of a few minutes. Depending on the length of the outage there is the possibility of a small position jump when transitioning from RTK Extend back to RTK. The coordinate transformation required to convert the local position into an ITRF00 position can be difficult, and if not done correctly will cause the RTK Extend position to rapidly diverge from truth. As such, a GPS receiver capable of navigating in Starfire mode coupled with the ability to output the bias between these two sets of coordinates is the best approach to ensuring seamless operation.
Q: Which Navcom products are capable of RTK Extend?
A: Navcom’s SF-2040 and SF-2050 product lines are capable of employing RTK Extend. In order to be used in this mode, each receiver (base and rover) must have the RTK option enabled as well as an active Starfire license.
Q: Can a user define whether they want the RTK Extend™ feature to be active?
A: Yes. Each receiver is fully configurable to ignore or accept a variety of correction types. As such, the user may choose to disable the Starfire navigation ability, making the receiver a primary host to RTK, or vice versa.
Q: What is Starfire™ convergence or “pull-in”, and why is it necessary to achieve advertised accuracies from Starfire?
A: When positioning with GPS, there are two types of error sources that affect the accuracy obtainable 1) the errors generated by the GPS satellite system and 2) errors created by the receiver when processing the GPS signal.
The Starfire system is designed to compensate for all satellite based errors by continuously tracking the GPS satellites and calculating the clock and orbit errors in real-time. These errors affect all GPS receivers, but are removed by applying the Starfire corrections. Correcting for the remaining error created by the GPS receiver, involves a different process that must be done by the receiver itself. The process of eliminating these errors involves smoothing the code measurements for up to an hour during which time sufficient satellite geometry changes occur allowing these errors to be estimated. This process is called convergence or “pull-in”.
Q: What is Starfire QuickStart?
A: Navcom offers the unique feature called QuickStart where an accurately known ITRF00 position can be used to initialize Starfire navigation and eliminate the convergence period. This is typically a position previously surveyed and converted to ITRF00 prior to initialization. It can also be a position obtained from the Starfire receiver while in steady state (or fully converged) navigation. For example, vehicular installations can be initialized using the last position from when it was parked and powered down. Employing QuickStart from a position that is not geodetic truth will be followed by a longer-term convergence to geodetic truth, so entering false coordinates into this function is not a recommended approach.
Note: RTK Extend™ is an “automated extension” of QuickStart.
Contents Index
The NovAtel and Sokkia GPS options, like Ashtech, allow for hard and soft resets, permit sending commands to the receiver (consult your dealer) and allow the review and re-setting of base and rover radio channels for Pacific Crest PDL and RFM series radios. Additional options check the communication status (shows the quality of the message string). The Review REF File will display the reference file (which stores the GPS base position information), which also helps in troubleshooting.
Contents Index
The Ashtech Receiver Utilities screen has the following options:
- Base and Rover Radio/GSM Setup: The Base and Rover Radio/GSM setup options will read the receiver, display the current radio channel, and allow the user to change to another channel. This feature is available for Pacific Crest PDL and RFM Series radios and Ashtech internal radios. Be sure that you have the right Radio Port set under the Configure Rover or Configure Base “Ports” tab. For GSM, see discussions under Configure Rover. The Base and Rover radio buttons work similarly. It is important for the user to choose the right button (base radio setup for base receiver and rover radio setup for rover receiver) to ensure that the software will try to connect to the radio on the correct port.
Ashtech Radio Setup – PDL
If the radio is an American PDL radio, it will appear as shown below.
The user can change the channel, the digisquelch (sensitivity), and the over air radio link baud rate. If it is a European radio, channels are not available. Instead, the user will be able to set the frequency, the digisquelch, and the over air radio link baud rate. The digisquelch is best high on rovers and low on bases. To set changes, click on the Set Radio button and the following screen appears:
Ashtech Radio Setup – Thales UHF
Select the appropriate button (see above). The following screen will appear.
Change the frequency to the desired frequency and click Set Radio.
Ashtech Radio Setup – Cable
No configuration options are available when the software is configured to cable.
Ashtech Radio Setup – Older Receivers
Currently, the only radio option available for non-ZMAX Thales/Ashtech receivers is a PDL radio. The Base/Rover radio setup options will assume the radio is a PDL radio on these receivers, and try to configure them accordingly. All the same settings (channel, digisquelch, over air link rate) should still be available, however.
- Hard Reset: Shuts down the receiver and brings it up again with default settings. Resets all port baud rates to 9600 and resets the internal memory.
- Set Factory Defaults: Resets the receiver and changes all parameters to the factory defaults. It is useful in troubleshooting problems.
- Save Settings to Receiver: Use this command is issued as part of the Configure Base and Configure Rover operations. However, you can run this command at any time as an extra “confirmation” of your settings changes (including settings changes within Receiver Utilities). This sends the $PASHS,SAV,Y command to the receiver.
- Beep Off: This disables the Beep sound that emanates from the Receiver when it is turned on.
- Send Command to Receiver: You can send what are known as “pash” commands, internal Thales/Ashtech codes, to the receiver. This should be done only in consultation with your Thales dealer.
- Reset RTK Engine: This resets the carrier phase ambiguities. This is a useful command if you are having difficulty obtaining lock and want to start the process of fixing over again. Receiver settings are retained (so you can think of it as a “soft reset”).
- Bluetooth Settings: The Bluetooth settings in SurvCE’s Bluetooth Manager (discussed in Comm Setup) do not actually change anything in the receiver itself. In order to make changes to the receiver’s internal Bluetooth settings, it is necessary to go into Receiver Utilities and click on Bluetooth Settings.
In this dialog, the user can change the Bluetooth receiver name (Receiver ID in Bluetooth Manager), the Bluetooth passkey (PIN in Bluetooth Manager), or the country code (currently the only choices are France and other countries because France has unique Bluetooth specifications). To change the name, change it in the appropriate text field and click Set New Bluetooth Name. A message confirming success will appear.
To change the passkey, change it in the appropriate text field and click Set New Bluetooth Passkey. A similar message confirming success will appear. To change the country code, click the appropriate radio button for the country and click Set Bluetooth Country Code. A similar message confirming success will appear.
- Power Off Receiver: Sends a command to power off the receiver.
- Update Clock from GPS: This will update the clock on your CE device based on the time recieved from the GPS satellites.
Contents Index
Power Cycle Receiver: This command is the same as turning the TOPCON receiver off and then on.
- Restore Factory Defaults: This command resets the TOPCON receiver to factory settings and the receiver stops acting as base or rover. The baud rate of Port A will be set to 115,200. Reset this to 9600 by turning the receiver off and then on while holding down the FN button. Watch the REC light go from orange to green to red and then let up the FN button. This method can be used if SurvCE cannot establish communications at any time.
- Clear Non-Volatile Memory: This command does everything Restore Factory Defaults does and also clears the almanac data that tells it where to look for the satellites. The receiver then downloads a new almanac from the satellites.
- Send Command to Receiver: This command allows experienced users to type in commands using TOPCON GPS receiver commands to set or report internal settings. (See the TOPCON operations manuals for a complete list of TOPCON GPS receiver commands).
- Set Satellite Status: This feature allows the user to disable a satellite if necessary.
- Initialize to Known Point: The Topcon GPS has a special feature to Initialize to a Known Point which can greatly speed up “move ups” from one base position to another.
Contents Index
Reset Receiver: This will reset the receiver.
- Select Rover Input: If you choose Select Rover Input, you can identify the “station id” of the base to avoid picking up inappropriate base corrections from the wrong base receiver.
- Check Battery: This will display the condition of the receiver's battery.
- Power On/Off Receiver: This will turn on and off the receiver.
Contents Index
This chapter contains troubleshooting tips for Carlson SurvCE, and the various hardware devices supported by SurvCE.
Contents Index
SurvCE records GPS heights as the ellipsoid height, expressed in meters, at either the phase center or the ARP of the antenna, depending on the GPS manufacturer. If the position is recorded to the ARP, then the LS record (antenna height) will only reflect the user-entered value. If the position is recorded to the phase center, then the LS record (antenna height) will reflect the user-entered value plus the phase center offset.
SurvCE records the ARP position for the following GPS manufacturers:
Contents Index
How do I reset the computer after a lock up?
Ranger
Hold down the power button until the computer resets or instructs you to hold it for 5 more seconds to reset.
Allegro
Hold down the power button until the computer resets.
Why can’t I load the software?
The computer may disconnect from ActiveSync when there is not enough memory allocated to “Storage Memory”. In the control panel, select the “System” icon followed by the Memory tab. Position the slider so that there is 5mb (5120 kb) allocated and not in use (i.e. if the “In Use” value says 1024 kb then add 1024 & 5120 to determine what the “Allocated” value should be).
How do I clear the RAM backup and why?
Clearing the RAM backup seems to improve performance on the Ranger platform after new programs have been installed or removed. Make sure that all software applications are closed and select the “RAM Backup” icon from the control panel. Select the Delete button and answer Yes to the three resulting message boxes.
Why can’t I communicate through the COM port?
If you cannot communicate with the instrument, verify all COM settings in SurvCE and make sure that they match the COM settings on the instrument. If communication has previously been working and the COM settings have not been altered, try one of the following to clear up the COM port:
- Exit SurvCE, turn off the computer, Restart the computer and re-enter SurvCE.
- Exit SurvCE and perform a soft reset on the device (Verify that all applications have been closed).
- Exit SurvCE and perform a hard reset on the device (Verify that all applications have been closed).
How do I set the CAPS LOCK status?
Ranger
1) Hold down the yellow shift button [ ^ ] and the [ALT] buttons, then press and release the power button.
2) A small keyboard should be showing. On the small keyboard, press the [CAPS] button then repeat step 1 to dismiss the keyboard.
Allegro
Press and release the blue function button followed by the CapLk/Shift button located at the lower left side of the keyboard.
How frequently should I charge the device?
We recommend starting every day with a fully-charged battery. Refer to your hardware manual for specifics on charging your battery.
How do I calibrate the touch screen?
In the control panel of the CE device, select the “Stylus” icon to configure the “Double Tab” and “Calibration” of the touch screen.
How do I turn on/off the back light?
Ranger
Hold down the shift button [ ^ ] and then press and release the power button.
Allegro
Press and release the yellow function button followed by the F3/F8 button located at the top center of the keyboard.
How can I speed up the Allegro performance?
In the control panel of the Allegro, select the “System” icon and then the “Memory” tab. Set your “Storage Memory” allocation to 8000 KB or 8 MB +/-. This should provide more RAM to the system for operating the programs and increase performance.
How can I Recover the SurvCE Icon if it Disappears?
It may be possible to lose the SurvCE Icon off the desktop if, for example, the power drains out of the CE device. There are safeguards against this, but if it happens, follow these steps to restore the icon:
- Select Start (lower left on most CE devices, Ctrl Esc on the Ranger) and choose Windows Explorer under Programs.
- Navigate to the SurvStar directory (the directory containing SurvCE), which on some devices is \Disk\SurvStar.
- Look for the SurvCE Shortcut and highlight it.
- Choose the Edit pull down in Windows Explorer and choose Copy.
- Then return to the desktop where the icons are visible and press ALT then tap into blank space on the screen (sometimes referred to as ALT-Click).
- Choose Paste Shortcut. That should restore it.
If the icon disappears, this indicates some problem in the original installation of SurvCE, since a process occurs to make the icon permanent. You can help ensure that your restored icon is permanent by going to Start, Settings, Control Panel and choosing Perform Ram Backup. Select Backup Now, as prompted. This should make the SurvCE icon remain even after full loss of battery.
Can I lose data or get bad data if I Re-Boot my CE device?
If you re-boot your Allegro or Carlson Explorer or Ipaq or any other CE device you are using, you can lose your antenna height or prism height information, because SurvCE does not store to memory changes in antenna height or prism height, except in the following scenarios:
The hard save of antenna/prism heights is done when you exit the program, when you save a configuration from the instrument icon at the top of the screen, when you say OK to Configure Rover, Configure Base or Equip/Settings (for TS), when you change jobs, and when you enter Equip/Comm Settings. Prior to release 1.50.007, in November, 2004, even Configure Rover did not save the height information "to disk".
Therefore, if you re-boot, perform a hard reset, or otherwise exit the program by any method other than the normal File, Exit method, recent changes to the prism height or antenna height may not be saved. On re-entering the program, the X,Y position for GPS work, for example, will very likely be correct, but elevations may have been lost. When using GPS, it is recommended, after a re-boot, that you do the command Configure Rover to re-establish the correct elevations, and in all cases (GPS and Total Station) it is recommended that you double-check your antenna or prism heights before proceeding.
Contents Index
Leica Robotic - Do I need to be in RCS (Remote Control) mode?
You must verify that you are NOT in RCS mode when using SurvCE with Leica robotic equipment. It will appear as though you are not communicating with the instrument if this mode is active. Refer to the Leica documentation for how to exit RCS mode.
Leica GPS - What firmware will allow radio channel changing?
Firmware version 3.52 or later is required for SurvCE to have radio channel changing functionality.
Geodimeter 600 - What firmware version is required?
Firmware version 696-03.xx or later is required for SurvCE to operate with this instrument. To check the firmware on the instrument, follow the key strokes: Menu, 5, 4, 1. The Geodimeter 640, for example, does not take measurements in reverse face. Therefore, when doing D&R, set reverse face to angle only.
Sokkia GSR 2700 IS - What do I do when I get the Bluetooth pass key prompt?
This receiver does not require a pass key. If you are prompted for one, do a factory reset on the receiver by holding the power key down until the message displayed is Factory Reset. Then turn the device off and back on again. In Carlson SurvCE, clear the receiver from the Bluetooth connections list and add it back in.
Contents Index
What file types does SurvCE use or convert?
- ALI ISPOL Centerline File (Spain)
- ALN TerraModel Road Alignment File
- ALZ Form of CLIP Vertical Alignment File (Spain)
- ASC ASCII text file for point imports or Inroads Centerline File
- CL Carlson Horizontal Road Alignment File
- CR5 TDS Binary Coordinate File
- CRD Carlson coordinate file in binary form.
- DAT Carlson Localization File
- DXF Drawing file format that can be used for exchanging drawings.
- EGM Carlson EGM Geoid File
- FCL Carlson Field Code Library file.
- FFF Older form of Caice Cross Section File
- FLT Carlson Triangulation Mesh File
- G99 Carlson Geoid99 File
- GRD Carlson Grid File
- GSI Leica file extension for Raw files, Roading files, etc.
- INF Carlson User Preferences Settings File
- INP MOSS Roading Files (Horizontal and Vertical Alignment)
- LIS Form of IGRDS Cross Section File
- NOT Carlson Note File
- OBS Geodimeter Coordinate File
- OSD A form of Geopak Centerline File
- PLT Horizontal Alignment Report file from CLIP (Spain)
- POS Sokkia or Trimble Coordinate File
- PRO Carlson Vertical Road Alignment File
- RAS ISPOL Vertical Road Alignment File (Spain)
- RD5 TDS Road Alignment File
- RDS IGRDS Cross Section File
- REF Carlson Base Station Reference File
- RLN TerraModel Road Alignment File
- RW5 Carlson Raw Data File, TDS Raw Data File
- SC1 ISPOL Cross Section File (Spain)
- SCT Carlson Cross Section File
- SDR Sokkia file extension for Raw Files, Roading files, etc.
- SHP ESRI Shape File
- SUP Carlson Road Superelevation File
- TPL Carlson Road Template File
- TPT Carlson Road Template Transition File
- TRV Traverse PC Coordinate File and CLIP Format for Sections (Spain)
- XML LandXML File may contain a variety of file types (eg. Roading/DTM)
- XRS Form of Geopak Cross Section File
Contents Index
This section outlines the Carlson SurvCE RW5 format.
Contents Index
Carlson SurvCE RW5 Format
This document outlines the Carlson SurvCE RW5 format in detail. The format is a comma delimited ASCII file containing record types, headers, recorded data and comments.
The format is based on the RW5 raw data specification, with the exception of angle sets. Angle sets are recorded as BD, BR, FD and FR records to allow reduction of all possible data that can be recorded by Carlson SurvCE using the Set Collection routine. Essentially, these records are identical to a sideshot record.
With the exception of the aforementioned angle set records, if the RW5 specification is modified to provide enhanced functionality, the added or modified data will reside in comment records to avoid incompatibility with existing software.
Backsight Record
Record type: BK
Field headers:
OP Occupy Point
BP Back Point
BS Backsight
BC Back Circle
Sample(s):
BK,OP1,BP2,BS315.0000,BC0.0044
Job Record
Record type: JB
Field headers:
NM Job Name
DT Date
TM Time
Sample(s):
JB,NMSAMPLE,DT06-27-2003,TM14:21:53
Line of Sight Record
Record type: LS
Field headers:
HI Height of Instrument
HR Height of Rod*
*GPS heights may be recorded to phase center or ARP depending on GPS make.
Sample(s):
LS,HI5.000000,HR6.000000
LS,HR4.000000
Mode Setup Record
The mode setup will be recorded at the beginning of the raw data file.
Record type: MO
Field headers:
AD Azimuth direction ( 0 for North, 1 for South)
UN Distance unit (0 for feet, 1 for meter)
SF Scale factor
EC Earth Curvature (0 for off, 1 for on)
EO EDM offset(inch)
Sample(s):
MO,AD0,UN0,SF1.00000000,EC1,EO0.0,AU0
Occupy Record
Record type: OC
Field headers:
OP Point Name
N Northing (the header is N space)
E Easting (the header is E space)
EL Elevation
-- Note
Sample(s):
OC,OP1,N 5000.00000,E 5000.00000,EL100.000,--CP
Off Center Shot Record
Record type: OF
Field headers:
AR Angle right
ZE Zenith (actual)
SD Slope Distance
Sample(s):
OF,AR90.3333,ZE90.0000,SD25.550000
OF,ZE90.3333,--Vert Angle Offset
Store Point Record
Record type: SP
Field headers:
PN Point Name
N Northing
E Easting
EL Elevation
-- Note
Sample(s):
SP,PN100,N 5002.0000,E 5000.0000,EL100.0000,--PP
Traverse / Sideshot Record / Backsight Direct / Backsight Reverse / Foresight Direct / Foresight Reverse
Record type: TR / SS / BD / BR / FD / FR
Field headers:
OP Occupy Point
FP Foresight Point
(one of the following)
AZ Azimuth
BR Bearing
AR Angle-Right
AL Angle-Left
DR Deflection-Right
DL Deflection-Left
(one of the following)
ZE Zenith
VA Vertical angle
CE Change Elevation
(one of the following)
SD Slope Distance
HD Horizontal Distance
-- Note
Sample(s):
TR,OP1,FP4,AR90.3333,ZE90.3333,SD25.550000,--CP
SS,OP1,FP2,AR0.0044,ZE86.0133,SD10.313750,--CP
BD,OP1,FP2,AR0.0055,ZE86.0126,SD10.320000,--CP
BR,OP1,FP2,AR180.0037,ZE273.5826,SD10.315000,--CP
FD,OP1,FP3,AR57.1630,ZE89.4305,SD7.393000,--CP
FR,OP1,FP3,AR237.1612,ZE270.1548,SD7.395000,--CP
GPS
Record type: GPS
Field headers:
PN Point Name
LA Latitude (WGS84)
LN Longitude (WGS84, negative for West)
EL Ellipsoid elevation in meters*
-- Note
*GPS heights may be recorded to phase center or ARP depending on GPS make.
Sample(s):
GPS,PN701,LA42.214630920,LN-71.081409184,EL-21.8459,--CP /Brass Disk
Alphabetical listing of Record Types
BD Backsight Direct
BK Backsight
BR Backsight Reverse
FD Foresight Direct
FR Foresight Reverse
GPS GPS Position in Lat (dd.mmss) Lon (dd.mmss - Negative for West) and WGS84 Ellipsoid Elevation in meters
JB Job
LS Line of Sight
MO Mode Setup
OC Occupy
OF Off Center Shot
SP Store Point
SS Side Shot
TR Traverse
-- Note Record
Alphabetical listing of Field Headers
AD Azimuth Direction ( 0 for North, 1 for South)
AL Angle-Left
AR Angle-Right
AZ Azimuth
BC Back Circle
BP Back Point
BR Bearing (this field will be recorded as N123.4500W)
BS Backsight (when back point is not defined)
CE Change Elevation
DL Deflection-Left
DR Deflection-Right
DT Local Date (MM-DD-YYYY)
E Easting (the header is E space)
EC Earth Curvature (0 for off, 1 for on)
EL Elevation (GPS value is ellipsoid elevation in meters)
EO EDM Offset
FE Foresight Elevation
FP Foresight Point
HD Horizontal Distance
HI Height of Instrument
HR Height of Rod
LA Latitude
LN Longitude
N Northing (the header is N space)
OC Occupy Point Coordinates
OP Occupy Point
PN Point Name
SD Slope Distance
SF Scale Factor
TM Local Time (HH:MM:SS)
UN Distance Unit (0 for feet, 1 for meter, 2 for US feet)
VA Vertical Angle
ZE Zenith
-- Note
Contents Index
Abbreviations
About SurvCE
Add Job Notes
Areas
Authorizing SurvCE
Auto By Interval
Basics
Battery Status
Calculator
Carlson Technical Support
Centerline Editor
Check Level (Total Station)
COGO
Color Screens
Configure (General)
Configure (Sets)
Configure (View Pt)
Data Transfer
Delete File
DRAW
Draw Centerline
Draw Profile
Draw Template
Elevation Difference
End-User License Agreement
Exit
Feature Code List
FILE
File Format
GPS (Allen-Osbourne)
GPS (Leica 500/1200)
GPS (Leica GIS System 50)
GPS (Magellan/Ashtech)
GPS (Navcom)
GPS (NMEA)
GPS (Novatel)
GPS (Sokkia)
GPS (Topcon)
GPS (Trimble)
GPS Base
GPS Heights
GPS Rover
GPS Setup
GPS Utilities
GPS Utilities (Leica 500/1200)
GPS Utilities (Magellan/Ashtech)
GPS Utilities (Navcom)
GPS Utilities (Sokkia and Novatel)
GPS Utilities (Topcon)
GPS Utilities (Trimble)
Graphic Mode
Graphics Screen Expansion
Grid/Face
Handheld Hardware
Hardware Notes
Hot Keys & Hot List
Import/Export
Input Box Controls
Installing SurvCE
Instrument Selection
Intersections
Inverse
Job
Job Settings (New Job)
Job Settings (Options)
Job Settings (Stake)
Job Settings (System)
Keyboard Input
Keyboard Operation
Leveling
List Points
Localization
Log Raw GPS
Logging
Manual Traverse
Master Centerline
maximize the graphics
Memory
Microsoft ActiveSync
Miscellaneous Instrument Configuration
Monitor/SkyPlot (GPS)
Navigate Data
Orientation (Backsight)
Orientation (Instrument Setup)
Orientation (Remote Benchmark)
Orientation (Robotics)
Peripherals
Pipes
Point Average
Point Projection
Profile Editor
Quick Calculator
Raw Data
Reconnect
Reference Centerline Example
Remote Elevation
Resection
Save System
Set Collection
Stake Line/Arc
Stake Offset
Stake Points
Stake Road
Stake Slope
Stake Station Interval
Station Store
Store Points (GPS Offsets)
Store Points (GPS)
Store Points (TS Offsets)
Store Points (TS)
Store Sections
Supported File Formats
System Requirements
Template Editor
Text mode
Tolerances
TOOLS
Total Station (Geodimeter/Trimble)
Total Station (Leica Robotic)
Total Station (Leica TPS Series)
Total Station (Leica/Wild Older Models)
Total Station (Nikon)
Total Station (Sokkia Robotic)
Total Station (Sokkia Set)
Total Station (Topcon 800/8000/APL1)
Total Station (Topcon GTS)
Transformation
Tutorial 1: Calculating a Traverse (By Hand) with SurvCE
Tutorial 2: Performing Math Functions in Carlson SurvCE Input Boxes
Tutorial 3: Performing a Compass Rule Adjustment
Tutorial 4: Defining Field Codes, Line/Layer Properties & GIS Prompting
Tutorial 5: Standard Procedures for Conducting GPS Localizations
Using the Manual
Utilities
VIEW
View Options